The AI Prompt Library for Business Teams

Act as a business analyst. Research [competitor name] and summarize: (1) their core offer, (2) pricing model, (3) who they target, (4) one thing they do better than us, (5) one clear gap we could exploit. Keep it under 200 words.

When to use: Before a positioning review or new feature decision.

I'm evaluating whether to enter the [market/niche] market. Give me a rough top-down and bottom-up market size estimate, your key assumptions, and 2 sources I should verify manually.

When to use: Early-stage go/no-go decisions.

Summarize the attached document in 3 sections: (1) the single most important takeaway, (2) 5 supporting facts with numbers, (3) what this means for a [role, e.g. operations manager] making a decision this quarter.

When to use: Skimming industry reports, earnings calls, or long PDFs.

I need to decide between [option A] and [option B] by [deadline]. List the top 3 arguments for each, the biggest risk of each, and which one you'd pick if you had to choose today, with your reasoning in 2 sentences.

When to use: Fast decisions where you want a structured second opinion.

Here are [number] pieces of customer feedback: [paste feedback]. Group them into themes, rank themes by frequency, and suggest the single highest-leverage fix.

When to use: Reviewing support tickets, reviews, or survey responses.

Here's my plan: [describe plan]. Play devil's advocate. What are the 3 weakest assumptions I'm making, and what would have to be true for this to fail?

When to use: Before committing budget or headcount to a plan.

Explain [technical/complex topic] the way you'd explain it to a smart colleague who has 5 minutes and no background in it. Use one analogy. No jargon.

When to use: Briefing stakeholders who don't have domain context.

Write a [tone: direct/friendly/formal] email to [recipient/role] about [topic]. Goal: [what you want them to do]. Keep it under 120 words. End with a clear single ask.

When to use: Any email where you know the point but not the phrasing.

Here are my rough notes: [paste notes]. Turn this into a clean, structured [memo/proposal/update], with headers, in my usual direct tone. Don't add information I didn't give you.

When to use: Converting meeting notes or bullet points into a shareable doc.

Cut this to half the length without losing any key facts or numbers: [paste text]. Keep my original tone.

When to use: Editing anything that's running too long.

Here are 2 examples of how we normally write: [paste examples]. Write a new [piece type] about [topic] in the same voice, structure, and length.

When to use: Keeping brand or personal voice consistent across content.

Give me 8 options for a [subject line/headline] about [topic]. Vary the angle: curiosity, benefit-driven, direct, and urgency. No clickbait.

When to use: Emails, blog posts, or ad copy that needs to earn attention.

Rewrite this for [new audience, e.g. non-technical executives] instead of [original audience]. Keep the core message the same, adjust vocabulary and detail level only.

When to use: Repurposing the same content for different stakeholders.

Here's a draft proposal: [paste]. Rewrite the closing section so the ask is unmistakably clear: what I want, by when, and what happens next if they say yes.

When to use: Proposals, pitches, or internal budget requests.

Here's everything on my plate this week: [list tasks]. Sort into: (1) must happen this week, (2) can slip a week, (3) shouldn't be on my list at all and why.

When to use: Monday planning or when the list feels unmanageable.

My goal is [goal] by [deadline]. Break it into phases, list the 5 highest-leverage tasks in each phase, and flag anything that depends on someone outside my control.

When to use: Turning a goal into something you can actually execute.

I need a [30/60]-minute meeting about [topic] with [attendees]. Build an agenda with time boxes, and one clear decision or outcome we need by the end.

When to use: Any meeting you're organizing, to keep it from drifting.

Imagine it's [timeframe] from now and [project] has failed. Write the most likely reasons why, based on what you know about the plan: [describe plan].

When to use: Before launching something you can't easily undo.

I need to hand off [task] to someone with [experience level]. Write step-by-step instructions clear enough that they don't need to ask me anything to get started.

When to use: Delegating without a 30-minute explanation call.

Compare [option 1], [option 2], [option 3] on: cost, time to implement, and risk. Use a simple table. End with your recommendation and the one factor that would change it.

When to use: Vendor selection, tool choices, hiring decisions.

Here's what happened this quarter: [paste wins/misses/metrics]. Identify: (1) what to keep doing, (2) what to stop doing, (3) the one change most likely to move the needle next quarter.

When to use: Quarterly or monthly team/business reviews.

Here's a raw meeting transcript/notes: [paste]. Extract: (1) decisions made, (2) action items with an owner and due date if mentioned, (3) open questions nobody answered.

When to use: Right after any meeting, before details fade.

I need to tell [recipient] that [difficult news]. Write it so it's honest and clear, not harsh, and doesn't leave room for the wrong interpretation. 2 versions: one direct, one softer.

When to use: Delivering pushback, bad news, or a boundary.

I sent this message [timeframe] ago and got no reply: [paste original]. Write a short follow-up that adds a reason to respond now, not just 'checking in.'

When to use: Chasing replies without sounding pushy.

I'm meeting with [person/role] about [topic]. Give me 3 questions I should ask, 1 thing I should be ready to answer, and 1 risk of this conversation going badly.

When to use: Prepping for calls that matter — clients, investors, reviews.

I received this feedback: [paste feedback]. Separate what's actionable from what's just opinion, and suggest 3 concrete next steps for the actionable parts.

When to use: Performance reviews, client feedback, user testing notes.

Write a status update on [project] for [audience]. Structure: what's done, what's in progress, what's blocked, what I need from them. Under 150 words.

When to use: Weekly/biweekly stakeholder updates.