Free tool

Prompt library: copyable AI prompts by role for everyday work

This prompt library gives you 64 free, copyable AI prompts by role, eight each for marketing, sales, HR and recruiting, finance and accounting, customer support, operations, product, and managers and founders. Search or filter below, copy a prompt, replace the square-bracket placeholders with your own details and paste it into ChatGPT, Claude, Gemini or Copilot.

How do you use this prompt library?

Find your role, pick the prompt that matches the task in front of you, copy it and fill in every placeholder before you run it. Each prompt has a one-line note on when to use it, so you can skip the ones that do not fit.

Treat each prompt as a starting point for work, not a finished answer. Every prompt in this prompt library for work ends by asking the tool for something you can check, such as a list of assumptions or the claims it could not support, because checking is where most of the value comes from.

How do you adapt a prompt with your own details?

Replace each square-bracket placeholder with something specific, then add one or two lines of context the prompt cannot know. A placeholder such as [audience] works far better as 'finance directors at UK manufacturers with 50 to 200 staff' than as 'business people'.

Add the facts the tool may use and say that these are the only facts allowed. If you want a certain length, tone or format, say so. If a result misses, do not start again: tell the tool what was wrong, for example 'the second paragraph repeats the first, cut it', and ask for a revision.

How do you check what the AI gives back?

Check every name, number, date, quote and promise against your own source before you use the output. AI tools write fluently even when they are wrong, so a confident sentence is not evidence of a correct one.

Read the list the prompt asked for, such as unsupported claims or open questions, and deal with each item. Then read the output as the recipient would: would a customer, a candidate or your finance director find anything unclear, unfair or overstated? If so, fix it yourself or ask for a targeted revision.

What should you never paste into an AI tool?

Do not paste personal data, confidential company information or anything your company's AI policy forbids, unless your company has approved that tool for that data. That includes customer names and contact details, employee records, salaries, health information, passwords, unreleased financial results and contract terms.

The prompts here are written so you can describe a situation in general terms or use anonymised notes. Where a task needs real detail, swap names for roles, such as 'Customer A' or 'the candidate', and round or remove sensitive figures. When in doubt, ask whoever owns AI use at your company.

Browse the prompts

Marketing

Campaign brief from rough notes

Use it when you have scattered ideas for a campaign and need a one-page brief to share.

Turn my notes into a one-page campaign brief for [product or service]. Audience: [audience]. Goal: [goal, for example sign-ups or enquiries]. Budget range: [budget range]. My notes: [paste your notes]. Use these headings: objective, audience, key message, channels, timeline, success measure. Use only what is in my notes. At the end, list every gap you had to leave blank and any assumption you made.

Three ad headline angles

Use it when you need distinct headline options to test rather than ten versions of one idea.

Write three different headline angles for an ad about [product or offer] aimed at [audience]. Angle 1 focuses on the problem, angle 2 on the outcome, angle 3 on a specific feature: [feature]. Give two headlines per angle, each under [character limit] characters. Facts you may use: [facts]. Do not invent statistics, awards or customer names. After the headlines, list any claim that would need evidence before it could run.

Blog outline from a search query

Use it before drafting a blog post, to agree the structure first.

Create an outline for a blog post that answers the search query '[search query]' for [audience]. Use question-style H2 headings, each followed by a one-sentence direct answer. Include a short FAQ section of four questions. Our point of view: [your angle or opinion]. Do not write the full post. At the end, list the facts or sources I need to supply for each section.

Repurpose one piece into social posts

Use it when you have published an article or webinar and want posts for several channels.

Here is the summary of a piece we published: [paste summary]. Write [number] social posts from it: two for LinkedIn of up to 120 words, and two for [other channel] of up to 40 words. Keep our tone: [tone, for example plain and practical]. Each post must make one point from the summary only. Under each post, quote the sentence from the summary it is based on so I can check it.

Customer story from interview notes

Use it after an anonymised customer interview, to draft a story you will send for approval.

Draft a 300-word customer story from these anonymised interview notes: [paste notes]. Structure: situation, problem, what they did, result. Use only facts and quotes that appear in the notes, and keep quotes word for word. Refer to the customer as [placeholder name] for now. After the draft, list every sentence that goes beyond the notes and every quote, so I can confirm them with the customer.

Competitor messaging summary

Use it when you have collected public copy from competitor websites and want to see the patterns.

Below is public copy from the websites of [number] competitors in [market]: [paste public copy with competitor labels]. Summarise for each one their main promise, target audience and proof points. Then list messages that two or more of them share and gaps none of them cover. Base every point on the copy provided and quote the phrase it comes from. Mark anything you inferred rather than read.

Email newsletter draft

Use it for a regular newsletter when you know the three items to include.

Write a newsletter email for [audience] covering these items: 1. [item and key facts], 2. [item and key facts], 3. [item and key facts]. Subject line options: give three, under 50 characters. Keep the body under [word count] words with one clear call to action: [action]. Do not add offers, dates or prices that are not in my list. Finish with a checklist of every fact used so I can verify it.

Landing page copy review

Use it before a landing page goes live, to find weak or risky copy.

Review this landing page copy for [product] aimed at [audience]: [paste copy]. Check it for: a clear promise in the first two lines, jargon, vague claims, claims that need evidence, and a single clear call to action. Give your findings as a table with columns for the line, the issue and a suggested rewrite. Do not rewrite the whole page. List any claim that could breach advertising rules if it is not supported.

Sales

Account research summary

Use it before a first call, using public information you have gathered.

Here is public information about [company type, for example a 60-person logistics firm]: [paste notes from their website, news and annual report]. Summarise what they do, recent changes, likely priorities and three questions I could ask on a discovery call about [our product area]. Base each point on the notes and say which note it comes from. List anything you inferred and could not confirm.

Discovery call question plan

Use it when preparing for a discovery call with a new prospect.

Write a discovery call plan for a prospect in [industry] with the role [buyer role]. Our product helps with [problem]. Give eight open questions in a logical order: current process, pain, impact, decision process, timing. For each question, add a follow-up to use if the answer is vague. Do not include questions about budget in the first three. Finish with the two answers that would tell me this is not a good fit.

Follow-up email after a call

Use it straight after a sales call, while your notes are fresh.

Write a follow-up email after a call with [prospect role] at [company type]. My anonymised notes: [paste notes]. Include a short recap of what they told me, the next step we agreed: [next step], and the date: [date]. Keep it under 150 words and plain in tone. Do not promise pricing, discounts or features that are not in my notes. After the email, list each statement and the note it comes from.

Objection handling practice

Use it to prepare honest answers to an objection you keep hearing.

Prospects in [industry] often say: '[objection]'. Our product: [short description]. Facts I can use: [facts, for example pricing model, trial, features]. Give three honest ways to respond, each under 60 words: one that asks a question, one that reframes, one that offers proof. Do not exaggerate or invent results. For each response, say what fact it relies on and when it would be the wrong response to use.

Proposal executive summary

Use it when you need a short summary at the front of a proposal.

Write a 200-word executive summary for a proposal to [prospect type]. Their problem in their own words: [paste anonymised quotes or notes]. Our solution: [solution]. Scope and price range: [scope and price]. Timeline: [timeline]. Lead with their problem, not our company. Use only the facts given. After the summary, list any claim a sceptical buyer might ask us to prove.

Lost deal review

Use it after losing a deal, to learn something useful rather than guess.

Help me review a lost deal. Anonymised timeline of the deal: [paste timeline]. Reason the buyer gave: [reason]. Identify the three moments where the deal was most likely lost, based only on the timeline, and what I could have done differently at each. Separate what the timeline shows from what you are guessing. Finish with two questions I could ask the buyer to confirm the real reason.

Cold email with a specific reason

Use it when writing to a new prospect and you have one genuine reason to contact them.

Write a cold email to a [role] at a [company type]. The specific reason I am writing: [reason, for example a public announcement]. Our relevant offer: [offer]. Keep it under 90 words, with one question as the call to action. No flattery, no fake familiarity and no claims about results we have not got. Give two subject lines. After the email, note any line that could read as generic and suggest a sharper version.

Pipeline update for my manager

Use it before a weekly pipeline review to turn deal notes into a clear update.

Turn these anonymised deal notes into a pipeline update for my manager: [paste notes, one line per deal with stage, value and next step]. Group deals by stage, flag any deal with no next step or a next step older than [number] days, and list the three deals most at risk with the reason. Use only the notes. Finish with any deal where the notes are too thin to judge.

HR and recruiting

Inclusive job description

Use it when writing or refreshing a job description.

Write a job description for a [job title] in a [team and company type]. Responsibilities: [list]. Must-have skills: [list]. Nice-to-have skills: [list]. Location and working pattern: [details]. Salary range: [range]. Use plain, inclusive language and keep requirements to those listed. After the draft, list any phrase that could put off qualified applicants, any requirement that may not be essential, and anything I need to confirm.

Structured interview questions

Use it to prepare a fair, consistent interview for every candidate.

Create a structured interview plan for a [job title]. The four skills to assess: [skills]. For each skill, give two behavioural questions, what a strong answer includes and what a weak answer looks like, so every interviewer scores the same way. Avoid questions about age, family, health, religion or anything unrelated to the job. Finish with a note on any question that could be unfair to some candidates.

Policy draft in plain English

Use it when you need a first draft of a workplace policy to send for review.

Draft a plain-English [policy name, for example hybrid working] policy for a [company size and type] in [country]. Our decisions: [key rules you have decided]. Sections: purpose, who it applies to, the rules, how to ask questions, review date. Keep it under [word count] words. Do not add rules I have not listed. At the end, list points that need legal or HR review in [country] before the policy is used.

Onboarding plan for the first two weeks

Use it when preparing for a new starter in any role.

Create a two-week onboarding plan for a new [job title] joining [team]. Systems they need: [systems]. People they should meet: [roles, not names]. First small piece of work: [task]. Lay it out day by day with one main goal per day. Keep the first two days light. After the plan, list anything that depends on someone else being ready, so I can check it in advance.

Employee survey questions

Use it when designing a short engagement or pulse survey.

Write a [number]-question survey about [topic, for example workload] for employees at a [company type]. Mix rating questions and two open questions. Each question must ask about one thing only and avoid leading wording. Explain in one line what each question would tell us. Finish with any question that might make people feel identifiable in a team of fewer than [number] people.

Rejection email that stays respectful

Use it when telling candidates they have not been selected.

Write a short rejection email to a candidate who reached the [stage] stage for a [job title]. Tone: warm and direct. Include thanks for their time and, if appropriate, an offer to keep their details on file for [period]. Do not give reasons or feedback in this email. Under 110 words. After the email, point out any phrase that could be read as a promise of future employment.

Training needs summary

Use it after collecting anonymised feedback about skills gaps in a team.

Here is anonymised feedback about skills gaps in our [team]: [paste feedback]. Group it into themes, rank the themes by how often they appear, and suggest one practical training action for each. Quote the feedback that supports each theme. Do not create themes that are not in the feedback. Finish with any point that is mentioned once but could be important.

Job advert screening criteria

Use it to agree fair screening criteria before reading applications.

From this job description: [paste job description], create a screening checklist with no more than six criteria that can be judged from a CV or application form. For each criterion, say what counts as met, partly met and not met. Only use requirements stated in the job description. Finish with any criterion that could screen out good candidates unfairly and how to word it better.

Finance and accounting

Variance commentary draft

Use it at month end to explain movements against budget.

Write variance commentary for [period]. Figures: [paste a summary table of budget, actual and variance by line, with sensitive detail removed]. Known reasons: [list reasons you know]. For each line with a variance above [threshold], write one or two sentences explaining it using only the known reasons. Where no reason is given, write 'reason to be confirmed'. Finish by listing every figure you used so I can check it against the source.

Explain a report to non-finance colleagues

Use it when managers need to understand a financial report without the jargon.

Explain this summary of our [report name] to department heads with no finance background: [paste summary figures and notes]. Use plain English, under [word count] words, and cover what changed, why it matters to them and what we need from them. Do not add figures that are not in the summary. Finish with a list of terms you simplified, so I can check the meaning is still accurate.

Spreadsheet formula helper

Use it when you know what you want a spreadsheet to calculate but not the formula.

In [Excel or Google Sheets], I have data in columns [describe columns and what they contain]. I want a formula in column [column] that [describe the result]. Give the formula, explain each part in one line, and give two test cases with made-up values and the expected result so I can confirm it works. Mention any case where the formula would give a wrong or error result.

Cash flow assumptions check

Use it to stress-test the assumptions behind a cash flow forecast.

Here are the assumptions behind our [period] cash flow forecast for a [company type]: [list assumptions]. For each one, say what would happen to cash if it turned out [percentage] worse, and which assumptions the forecast is most sensitive to. Show your working in a simple table. Do not invent figures not in my list. Finish with the questions I should ask the owners of the three riskiest assumptions.

Supplier payment reminder

Use it to chase an overdue invoice politely and clearly.

Write a payment reminder to a customer whose invoice [invoice reference] for [amount] was due on [date]. This is reminder number [number]. Tone: [polite, firm]. Include how to pay: [payment details placeholder] and who to contact with questions. Under 120 words. Do not threaten action we have not decided on. After the email, list every amount and date used so I can check them.

Process note for a finance task

Use it to document a recurring task, such as a reconciliation, so someone else can do it.

Write a step-by-step process note for [task, for example the monthly bank reconciliation] in [system]. My rough steps: [paste steps]. Number each step, say what to check at each stage and what to do if something does not match. Keep my steps in order and do not add system features I have not mentioned. Finish with any step where my notes were unclear and need more detail.

Board pack summary

Use it to draft the one-page summary at the front of a board or owner pack.

Draft a one-page summary for [board or owners] from these key points: [paste key figures and messages, with sensitive detail removed]. Structure: headline result, three things that went well, three concerns, decisions needed. Keep each point to one sentence. Use only the figures provided. Finish with a list of every number used and the point it supports.

Expense policy question answers

Use it to draft clear answers to common expense questions from staff.

Here is our expense policy: [paste policy text]. Write answers to these staff questions: [list questions]. Base every answer only on the policy and quote the section it comes from. If the policy does not answer a question, say 'not covered by the policy, ask [role]' rather than guessing. Finish with any gap in the policy the questions revealed.

Customer support

Reply to a frustrated customer

Use it when a customer is upset and you need a calm, accurate reply.

Draft a reply to a customer who wrote: [paste anonymised message]. Facts I can use: [facts about the order or issue]. What we can offer: [approved options]. Acknowledge the problem in one sentence, explain what happened plainly and give the options. No new promises, refunds or dates beyond those listed. Under 130 words. After the reply, list each fact and option used so I can check it.

Help article from repeated questions

Use it when the same question keeps arriving in the support inbox.

Write a help article answering '[customer question]'. The correct steps are: [paste steps]. Audience: [type of customer]. Start with a one-sentence answer, then numbered steps, then a short 'if this did not work' section. Use only the steps given. Finish with any step that might confuse a non-technical customer and a suggestion for a screenshot.

Ticket theme summary

Use it weekly to see what customers are contacting you about.

Here are [number] anonymised ticket subjects and short descriptions from this week: [paste list]. Group them into themes, count the tickets in each, and give one example per theme. Suggest one fix for the top three themes, such as a help article or a product change. Do not merge themes that are clearly different. Finish with any ticket you could not place in a theme.

Saved reply set

Use it to build consistent saved replies for common situations.

Write saved replies for these situations: [list situations, for example password reset, delivery delay]. Our tone: [tone]. Facts for each: [facts]. Each reply must be under 80 words, use [customer name] as a placeholder and end with a clear next step. After each reply, note what an agent must check or personalise before sending it.

Escalation note for another team

Use it when passing a complex issue to engineering, billing or another team.

Write an escalation note for the [team] team about this issue: [paste anonymised summary of the ticket and what you have tried]. Include: what the customer reported, steps to reproduce, what has been tried, impact on the customer, and what we need from them. Keep it factual and under 200 words. Finish with any missing information the other team is likely to ask for.

Translate a technical answer into plain English

Use it when an internal technical explanation needs to go to a customer.

Rewrite this technical explanation for a customer with no technical background: [paste internal explanation]. Keep it accurate, under [word count] words, and explain what happened, what we did and what they need to do, if anything. Do not add causes or fixes that are not in the explanation. After the rewrite, list any technical point you simplified so a colleague can confirm it is still correct.

Review my draft reply

Use it before sending a reply you are unsure about.

Review my draft reply to a customer: [paste draft]. The customer's original message: [paste anonymised message]. Check whether my reply answers every question they asked, uses a respectful tone, avoids jargon and makes no promise we cannot keep. Give feedback as a short list of issues with suggested fixes. Do not rewrite the whole reply. Tell me if any question in their message is still unanswered.

Customer feedback summary for the product team

Use it monthly to pass useful feedback to the product team.

Summarise this anonymised customer feedback for our product team: [paste feedback]. Group it into feature requests, bugs and confusion about how things work. For each group, give the number of mentions and two representative quotes word for word. Do not add requests that are not in the feedback. Finish with any single piece of feedback that seems urgent.

Operations

Standard operating procedure draft

Use it to turn how a task is actually done into a written SOP.

Write a standard operating procedure for [task] from these rough notes: [paste notes]. Sections: purpose, who does it, what you need, numbered steps, checks, what to do if something goes wrong. Keep my steps in my order. Do not add tools or approvals that are not in the notes. Finish with every place where my notes were vague and a question that would clarify each one.

Meeting notes to actions

Use it after a meeting to send a clear list of decisions and actions.

Turn these meeting notes into a summary: [paste notes]. Give three sections: decisions made, actions with an owner (use roles, not names) and a due date, and open questions. Only list a decision if the notes show it was agreed. If an action has no owner or date in the notes, write 'to be confirmed'. Finish with anything in the notes that could be read two ways.

Process bottleneck analysis

Use it when a process is slow and you want to find where time is lost.

Here is how our [process] works, step by step, with rough times: [paste steps and times]. Identify the three steps most likely causing delay and explain why, based on the times and handovers. Suggest one small change for each that we could test within [period]. Separate what the data shows from your guesses. Finish with what I should measure to know if a change worked.

Supplier comparison table

Use it when choosing between suppliers using quotes you already have.

Compare these supplier quotes for [goods or service]: [paste key terms from each quote, with supplier labels A, B, C]. Create a table covering price, delivery time, minimum order, payment terms and anything else in the quotes. Do not fill gaps with guesses: write 'not stated'. After the table, list the questions I should ask each supplier before deciding.

Project status update

Use it to write a weekly status update from your own notes.

Write a project status update for [project] for [audience]. My notes: [paste notes on progress, risks and next steps]. Format: overall status (on track, at risk or off track) with one-line reason, done this week, next week, risks and help needed. Under 200 words. Use only my notes. Finish by flagging any risk in the notes that I have not given an owner or a mitigation.

Checklist from a policy or procedure

Use it to turn a long document into a checklist people will actually use.

Turn this procedure into a short checklist for [role] to use while doing [task]: [paste procedure]. Each item must be one action that can be ticked off. Keep the order of the procedure. Do not add steps that are not in it. After the checklist, list any part of the procedure that was too vague to turn into a clear checklist item.

Risk register entries

Use it when starting a project or change and you need a first list of risks.

List the main risks for [project or change] at a [company type]. Context: [short description, timeline and constraints]. For each risk, give a one-line description, likelihood (low, medium, high), impact (low, medium, high) and one mitigation. Give no more than [number] risks. Mark which risks come from my context and which are general risks you added, so I can judge them.

Rota or schedule check

Use it to check a draft rota or schedule against your rules before publishing it.

Check this draft schedule: [paste schedule using initials or roles, not full names]. Rules it must follow: [list rules, for example minimum cover per shift, maximum consecutive days]. List every place the schedule breaks a rule, with the day and the rule broken. Do not rearrange the schedule yourself. Finish with any rule that was unclear or that you could not check from the data.

Product

User research synthesis

Use it after a round of anonymised user interviews.

Synthesise these anonymised interview notes from [number] users of [product]: [paste notes, labelled User 1, User 2 and so on]. Identify the main problems users describe, how many users mentioned each and a direct quote for each. Separate what users said from what you infer. Do not suggest features yet. Finish with any theme that only one user mentioned but that seems significant.

Problem statement and success measures

Use it before writing requirements, to agree what problem you are solving.

Write a problem statement for this issue: [describe the problem and who has it]. Evidence we have: [list evidence]. Use the format: who has the problem, what they are trying to do, what gets in the way, and why it matters now. Then suggest three success measures we could track. Base the statement only on the evidence. Finish with the weakest piece of evidence and how we could strengthen it.

Requirements draft

Use it to turn an agreed idea into a first requirements document.

Draft requirements for [feature] in [product]. Problem: [problem statement]. Users: [user types]. Agreed scope: [in scope]. Out of scope: [out of scope]. Write user stories with acceptance criteria for each. Keep strictly to the agreed scope. Finish with open questions for design and engineering, and any acceptance criterion that may be hard to test.

Release notes in plain language

Use it when shipping changes and writing notes for customers.

Write customer-facing release notes from this internal change list: [paste change list]. Group changes into new, improved and fixed. Describe each change by what the customer can now do, in one sentence, without internal names or jargon. Leave out anything marked internal. Finish with any change where the customer benefit is unclear from the list.

Prioritisation discussion prep

Use it before a prioritisation meeting to compare ideas consistently.

Here are [number] product ideas with notes on reach, impact, confidence and effort: [paste ideas and notes]. Score each using RICE, show the calculation, and rank them. Where my notes do not give a value, write 'missing' rather than estimating. Finish with the two ideas whose ranking would change most if one assumption were wrong, and which assumption that is.

Survey questions for a feature

Use it to learn whether users want or understand a feature.

Write a short survey of [number] questions for users of [product] about [feature or problem]. Include one question on how often they face the problem, one on how they solve it today and one open question. Avoid leading questions and questions that describe our solution. Explain what each question will tell us. Finish with any question that might be confusing to someone new to the product.

Competitor feature comparison

Use it when you have gathered public information about competitor products.

Compare these products on [list of capabilities] using only the public information I provide: [paste notes labelled by competitor, with the source page for each]. Create a table with 'yes', 'no' or 'not stated' for each capability, and cite the note behind every 'yes'. Do not rely on your own knowledge of these products. Finish with the capabilities where information was missing for most competitors.

Stakeholder update on a delay

Use it when a release slips and you need to tell stakeholders clearly.

Write an update to [stakeholder group] that [feature or release] will be later than expected. Original date: [date]. New expected date: [date or range]. Reason: [reason]. What we are doing about it: [actions]. Impact on them: [impact]. Keep it under 150 words, direct and without blame. Do not promise a new date firmer than the one I gave. Finish with questions stakeholders are likely to ask.

Managers and founders

One-to-one meeting preparation

Use it before a one-to-one, to plan a useful conversation.

Help me prepare for a one-to-one with a [role] in my team. Topics I want to cover: [topics]. What I know about their recent work: [brief, non-sensitive notes]. Suggest an agenda for [length] minutes, three open questions and one way to ask for feedback on my own management. Avoid questions about their personal life. Finish with any topic on my list that might be better handled in a different setting.

Decision memo

Use it when you need to set out a decision and its options clearly for others.

Write a one-page decision memo on [decision]. Options: [list options with known costs and effects]. Constraints: [constraints]. My current preference and why: [preference]. Structure: the decision needed, options with pros and cons, recommendation, risks, what would change my mind. Use only the facts given. Finish with any option where the facts are too thin to compare fairly.

Team AI use guidance

Use it to draft simple rules for how your team uses AI tools.

Draft one page of guidance on using AI tools for a [team or company size and type]. Tools we allow: [tools]. Data that must never go into them: [types of data]. Tasks where AI is encouraged: [tasks]. Tasks that need human review: [tasks]. Write it as short do and do not lists in plain English. Finish with questions I should answer before sharing it, such as who people ask when unsure.

Hiring plan check

Use it when planning hires for the next few months.

Review this hiring plan for a [company type]: [paste roles, timing and budget range]. Our main goals for the next [period]: [goals]. For each role, say which goal it supports and whether the timing makes sense. Flag roles that do not link to a goal and any goal with no role supporting it. Do not invent salary benchmarks. Finish with the assumptions this plan depends on most.

Feedback I need to give

Use it to prepare clear, fair feedback on a specific piece of work or behaviour.

Help me plan feedback for a team member about [situation, described without names]. What happened: [specific examples]. Impact: [impact on the team or work]. What I would like to see instead: [change]. Write a short script using the situation, behaviour, impact model, with an open question to hear their side. Keep it factual and avoid labels about personality. Finish with any part of my examples that sounds like opinion rather than fact.

Quarterly priorities from a long list

Use it when you have too many priorities and need to choose a few.

Here is my list of possible priorities for next quarter: [paste list]. Our goals for the year: [goals]. Our team capacity: [rough capacity]. Group related items, link each group to a goal and recommend no more than [number] priorities. For each item you leave out, give a one-line reason. Use only my list and goals. Finish with the trade-off I should discuss with the team before deciding.

Investor or owner update

Use it to draft a regular update to investors, owners or a board.

Draft a monthly update for [investors or owners]. Key figures: [paste headline figures with sensitive detail removed]. Wins: [list]. Challenges: [list]. Asks: [what you need from them]. Keep it under 300 words, honest about challenges and specific in the asks. Do not add figures or wins I have not listed. Finish with every number used, so I can check each against the source.

Pre-mortem for a new initiative

Use it before launching a project, to find what could go wrong while there is time to act.

Run a pre-mortem on [initiative]. Imagine it is [date] and the initiative has failed. Context: [goal, team, budget range, timeline]. List the eight most likely reasons it failed, grouped into people, process, market and money. For each, suggest an early warning sign and one action to take now. Mark which reasons come from my context and which are general, so I can judge how relevant they are.

Before you decide

A few good questions.

Is the prompt library free?

Yes. Every prompt in the library is free to copy and use, with no sign-up. You can use them in ChatGPT, Claude, Gemini, Copilot or any similar AI tool.

Which AI tools do these prompts work with?

They are written in plain language, so they work in any general AI assistant, including ChatGPT, Claude, Gemini and Microsoft Copilot. Results vary by tool, so always check the output.

Why do the prompts have square brackets?

The square brackets mark placeholders for your own details, such as the audience, the product or the goal. Replace every one with something specific before you run the prompt, because vague inputs produce vague results.

Can I paste customer or employee information into these prompts?

Only if your company has approved that AI tool for that kind of data. Otherwise, describe the situation in general terms or anonymise it, for example by using roles instead of names and removing sensitive figures.

How do I get better at writing my own prompts?

Practise on real tasks and get feedback on the results. The prompt engineering guide explains the method, and the Tosheo.ai prompt engineering course has you write prompts for your own role, marked against a visible rubric.

Give your team a path, not another playlist.

Explore role-specific lessons, practical tasks and the manager view.

Start free trial7-day free trial · No credit card needed