Skip to main content

Business AI Prompt Templates

80 free, copy-pasteable AI prompt templates for business — built for founders, product managers, sales, marketing, and customer success. Each one works in ChatGPT, Claude, and Gemini, has been tested, comes with a one-line rationale, and tells you exactly what to swap in.

Browse by category

Each category page has the full set of templates for that kind of work, plus notes on when to reach for each one.

Start with these

One template from each category — copy it, swap the highlighted fields, and paste it into whichever assistant you already use.

Sales follow-up email after no reply

Re-engage a prospect who has gone silent without sounding desperate.

You are a B2B sales rep writing a follow-up email. The previous email was sent days ago days ago and got no reply.

Context about the prospect:
- Company: company
- Role: role
- Original ask: original ask

Write a 4–6 line follow-up that:
1. Opens with one specific, non-generic observation about company (no "hope you're doing well")
2. Acknowledges the silence without guilt-tripping
3. Offers a low-friction next step (a question, a 1-line answer, or an opt-out)
4. Signs off without a CTA stack

Tone: confident, peer-to-peer, no jargon. Output only the email body.
Why it works
Constrains length, bans the cliché openers most AIs default to, and forces a single low-friction CTA.
What to swap
Replace the highlighted fields. Set the follow-up gap to control urgency.

Compare two tools for a specific use case

Get an opinionated comparison, not a vendor-neutral feature matrix.

Compare tool a and tool b for the specific use case: use case.

I am: user context.

Output:
1. **Verdict in one sentence** — which one I should pick and why.
2. **Three reasons** the verdict tool wins for my use case.
3. **One reason** the other tool would actually be better, so I know the trade.
4. **When to switch** — what would have to change for the verdict to flip.

Do not list every feature. Do not be diplomatic. Pick a winner.
Why it works
Demands a verdict. Models default to 'it depends' — this prompt removes that escape hatch and surfaces the real trade-off.
What to swap
user_context is critical: 'solo founder' vs 'enterprise IT' will flip most verdicts.

Generate a meeting agenda from a goal

Turn a vague 'we need to meet about X' into a real agenda.

Build a meeting agenda for this outcome.

Goal of the meeting: goal
Attendees: attendees
Length: minutes minutes

Produce:
1. **One-sentence purpose** — what success looks like by the end.
2. **Pre-read** (if any) — what each attendee should read first.
3. **Agenda** — 3–5 items, each with: topic, time-box (minutes), owner, expected output.
4. **Decisions required** — bulleted list of decisions that must be made (not discussions had).
5. **What this meeting is NOT for** — to defend the time-box.

Total time across agenda items must equal minutes minutes.
Why it works
The 'what this is NOT for' line stops scope-creep mid-meeting. The decision list prevents discussion-only meetings.
What to swap
Be honest about minutes — agendas built for 60 minutes don't compress to 30.

Write a one-page PRD from a fuzzy product idea

Turn a rough brief or Slack message into a structured requirements document ready for an engineering conversation.

Write a one-page product requirements document (PRD) from the idea below.

The idea: idea
Target user: target user
Why now: why now

Structure the PRD as follows:
1. **Problem statement** — what the user cannot do today, and the cost of that. No features yet.
2. **Target user segment** — who specifically, described by behavior not demographic.
3. **Success metric** — one measurable outcome. "More engagement" is not a metric.
4. **Scope: in** — what this version includes.
5. **Scope: out** — what this version explicitly does not include.
6. **Open questions** — what the team must resolve before building starts.

Rules:
- Do not list features until the problem statement is solid.
- Every item in Scope: in must connect to the success metric.
- Open questions must be answerable — no rhetorical or philosophical ones.
Why it works
PRDs built feature-first solve the wrong problem. Forcing the problem statement and success metric before scope prevents the most common PM failure mode.
What to swap
The success metric is the hardest field. If you write 'improve retention', the model will let it through — push yourself to write a number and a timeframe.

Generate names for a product, startup, or feature

Brainstorm 20 name candidates with real category diversity between them.

Generate 20 candidate names for: thing to name.

The vibe I am going for: vibe
Names too close to existing brands or that I want to avoid: avoid
Constraints: no generic -ly / -ify / -ify suffixes; domain availability matters: domain matters

Rules:
- Mix categories: real words, invented words, compound words, metaphors, mythology references, foreign-language words.
- For each name, give a 5-word justification.
- Flag any that are too close to existing brands or trademarked terms.
- After the 20, pick your top 3 and explain why each one holds up under pressure.

Output as a numbered list.
Why it works
Forcing category diversity is the single change that prevents 20 variations of the same root word. Most naming AI defaults to compound SaaS words without this constraint.
What to swap
Vibe matters more than thing_to_name. 'Trustworthy legal-tech' and 'scrappy legal-tech' produce completely different lists.

Prepare a quarterly business review from raw account data

Turn usage data and account notes into a structured, confident QBR.

Build a quarterly business review (QBR) structure from the account information below.

Customer: customer name
Their stated goals at onboarding: onboarding goals
Usage and metrics this quarter: metrics
Recent interactions (support, calls, emails): recent interactions
Renewal date: renewal date

Produce:
1. **Account health summary** — one sentence, honest.
2. **Three proof points of value delivered this quarter** — specific outcomes the customer can verify. Feature usage stats do not count.
3. **Risks the customer hasn't raised** — signals in the data or interactions that suggest a problem they may not have named yet.
4. **One joint goal for next quarter** — tied to their onboarding goals. Our product roadmap is irrelevant here.
5. **The renewal conversation starter** — one sentence that opens the renewal conversation from a position of value. Do not use urgency.

If the data is too thin to support a specific proof point, say so.
Why it works
QBRs built from data dumps look like data dumps. The 'risks they haven't raised' section is what separates a consultative CSM from a reporter — it demonstrates you understand the account, not just the metrics.
What to swap
Anchor every proof point to the customer's own stated goals — a metric they didn't care about at onboarding is not a proof point.

Explain unfamiliar code line-by-line

Understand code you didn't write before changing it.

Explain the following code as if to a competent developer who is unfamiliar with this specific codebase.

For each logical block (not each line — group sensibly):
1. What it does in one sentence.
2. Why it might be written this way (the non-obvious motivation).
3. Any side effects, hidden state, or gotchas.

At the end, list:
- Three questions I should ask the original author before changing it.
- One thing that looks like a bug or smell, if any.

Language/framework: language and framework
Code:
"""
paste code here
"""
Why it works
Demanding the 'non-obvious motivation' is what separates a real review from line-by-line narration.
What to swap
Always state language_and_framework — generic explanations miss idioms.

Generate landing page headlines that don't sound AI-written

Brainstorm headline candidates that pass the 'this sounds human' bar.

Generate 12 landing page headline candidates.

Product: product
Audience: audience
The single most painful problem this audience has: pain
The unique mechanism we use to solve it: mechanism
Banned words (overused in this space): banned words

Headline rules:
- Maximum 9 words.
- No words from the banned list.
- No "Unlock", "Empower", "Transform", "Revolutionize", "Cutting-edge", "Game-changer", "Seamless".
- At least 4 should be questions or statements written in the audience's own voice.
- Mix: pain-led, outcome-led, mechanism-led, contrarian.

For each headline, label its style. After the 12, pick your top 3 and explain why.
Why it works
The banned-words list is the single biggest quality lever. Default AI headlines are 80% the same words.
What to swap
Add your own banned words — every category has its own clichés.

Frequently asked questions

The best business AI prompt templates are the ones that constrain the model instead of just asking it a question — they set length limits, ban filler openers, and force a single clear output. This library groups them by business function (founders, product, sales, marketing, customer success, operations, and more) so you can jump straight to the task you're doing. Every template is copy-pasteable and works in ChatGPT, Claude, and Gemini.

Have a prompt that earns its keep? Send it in and we will add it to the next batch.