This page collects ai prompts for sales teams: ready-to-use instructions for prospecting, discovery, objection handling, follow-up, and deal reviews. It is written for sales team leads and account managers who want consistent output across ChatGPT, Claude, Copilot, and Gemini, without asking a developer for help. Copy a prompt, swap the variables, and run it.

What is in this pack

Twenty-plus prompts organized into five categories: prospecting and outreach, discovery and qualification, objection handling, follow-up sequences, and pipeline reviews. Each prompt is ready to copy, with variables in brackets so your team can adapt them in under a minute.

The pack is practical rather than comprehensive. It covers the moments where inconsistency costs deals: the first cold email, the recap after a discovery call, the response to a price objection. It does not cover every edge case in a sales process, and it is not a substitute for understanding your buyer.

One honest caveat: these prompts will not fix a weak value proposition. If your offer is unclear, AI will produce cleaner versions of unclear messaging. Get the positioning right first, then use these to move faster.

For prompts built around other business roles, see the full prompts by role library or the adjacent packs for AI prompts for marketers and AI prompts for business teams.

The prompts, by category

These 20 prompts cover the moments where sales teams lose the most time: writing outreach, preparing for calls, following up, and making sense of what's in the CRM. They're grouped by stage so you can find what you need fast.

A quick note before you start. These prompts work well for drafting and structuring. They don't know your buyer's actual history, your pricing constraints, or the context from a call last Tuesday. Treat every output as a first draft that needs a human pass before it goes anywhere near a prospect.

CategoryPromptsBest used
Prospecting & outreach1-5Before first contact
Discovery & call prep6-9Day before a call
Objection handling10-13Live or post-call
Follow-up & proposals14-17Within 24 hrs of meeting
Pipeline & reporting18-20Weekly review

Prospecting & outreach

1. Write a cold outreach email from a job posting

When to use it: You've found a signal (a new hire, a job ad, a funding announcement) and want to open a conversation without sounding like you ran a mail merge. What to change first: The signal itself. The more specific the trigger, the better the first line lands.

Variables: [YOUR NAME], [YOUR COMPANY], [PROSPECT NAME], [PROSPECT COMPANY], [JOB POSTING DETAIL OR SIGNAL], [WHAT YOU SELL], [ONE RELEVANT OUTCOME YOU'VE DELIVERED]

You are an experienced B2B sales rep writing a cold outreach email.

Context:
- Sender: [YOUR NAME] at [YOUR COMPANY]
- Prospect: [PROSPECT NAME] at [PROSPECT COMPANY]
- Signal: [PROSPECT COMPANY] recently posted a job for [JOB POSTING DETAIL OR SIGNAL]
- We sell: [WHAT YOU SELL]
- Relevant outcome: [ONE RELEVANT OUTCOME YOU'VE DELIVERED]

Write a cold email that:
1. Opens with a single sentence referencing the job posting as a genuine observation, not a compliment
2. Connects that signal to a specific problem [WHAT YOU SELL] solves
3. Mentions [ONE RELEVANT OUTCOME YOU'VE DELIVERED] in one sentence
4. Ends with a low-friction ask (a short call, a resource, a yes/no question)
5. Is under 120 words total
6. Uses plain, direct language. No phrases like "I hope this finds you well" or "I wanted to reach out"

Output the email only, no subject line, no commentary.

[NEEDS REAL OUTPUT] What to notice:, ---

2. Generate five subject line variants for a cold email

When to use it: You have a draft email but the subject line is generic. Run this before sending to a large sequence. What to change first: Swap in the specific pain point relevant to this segment.

Variables: [EMAIL BODY], [PROSPECT ROLE], [PRIMARY PAIN POINT]

Here is a cold sales email aimed at [PROSPECT ROLE]:

[EMAIL BODY]

Write five subject line options. Requirements:
- Each under 8 words
- No clickbait, no false urgency, no ALL CAPS
- At least two should reference [PRIMARY PAIN POINT] directly
- At least one should be a plain, curiosity-gap line with no selling
- List them numbered, no commentary

3. Rewrite a generic value proposition for a specific vertical

When to use it: Your standard pitch deck line doesn't resonate with a new industry you're targeting. What to change first: The vertical and the business outcome they care about most.

Variables: [GENERIC VALUE PROP], [TARGET VERTICAL], [TOP BUSINESS PRIORITY FOR THIS VERTICAL]

Our current value proposition is:
"[GENERIC VALUE PROP]"

Rewrite it for [TARGET VERTICAL], where the primary business priority is [TOP BUSINESS PRIORITY FOR THIS VERTICAL].

Produce three versions:
1. One sentence (for a subject line or social bio)
2. Two sentences (for an email intro)
3. Four sentences (for a discovery call opener)

Stay factual. Do not invent metrics or outcomes we haven't claimed.

4. Turn a LinkedIn profile into a personalized first line

When to use it: You want a genuine opening line for each prospect but don't have time to read every profile in detail. What to change first: Paste only the most recent role and summary section; full profiles add noise.

Variables: [LINKEDIN PROFILE TEXT], [WHAT YOU SELL]

Here is a LinkedIn profile section:
[LINKEDIN PROFILE TEXT]

We sell: [WHAT YOU SELL]

Write three possible opening lines for a cold outreach email. Each should:
- Reference something specific from the profile (a project, a career move, a stated priority)
- Not be a compliment ("Impressive background" is banned)
- Connect naturally to a problem [WHAT YOU SELL] addresses
- Be one sentence, under 25 words

Output as a numbered list. No explanation.

5. Build a two-touch outreach sequence for an inbound lead

When to use it: Someone filled out a form but hasn't responded to the first email. You need a follow-up that adds value rather than just nudging. What to change first: The content asset or resource referenced in touch two.

Variables: [PROSPECT NAME], [PROSPECT COMPANY], [WHAT THEY DOWNLOADED OR REQUESTED], [WHAT YOU SELL], [RELEVANT RESOURCE OR CASE STUDY]

Write a two-email sequence for an inbound lead who hasn't replied.

Touch 1 (send day 1):
- Subject line included
- Under 80 words
- Acknowledge what they requested
- One clear next step

Touch 2 (send day 4):
- Subject line included
- Under 70 words
- Offer [RELEVANT RESOURCE OR CASE STUDY] as a reason to reply, not just a chase
- Soft close only

Format: label each email clearly. No filler phrases.

[NEEDS REAL OUTPUT] What to notice:, ---

Discovery & call prep

6. Build a discovery call agenda from a company description

When to use it: You have a call booked but only a company website and a name to go on. What to change first: Add any intel from their job postings or recent news before running this.

Variables: [COMPANY NAME], [COMPANY DESCRIPTION OR WEBSITE COPY], [WHAT YOU SELL], [CALL LENGTH IN MINUTES]

Prepare a discovery call agenda for a [CALL LENGTH IN MINUTES]-minute call with [COMPANY NAME].

Company context:
[COMPANY DESCRIPTION OR WEBSITE COPY]

We sell: [WHAT YOU SELL]

Produce:
1. A two-sentence call opener (not a monologue)
2. Four to six discovery questions ordered from situation to implication
3. One question that surfaces their decision-making process
4. A suggested close for the call that confirms next steps

Flag any assumptions you've made about their business.

7. Generate SPIN-style questions for a specific deal

When to use it: You're preparing for a second or third call and want to move from surface-level conversation to uncovering real impact. What to change first: The implication questions. They're the hardest to write and the most valuable.

Variables: [PROSPECT COMPANY], [PROSPECT ROLE], [PROBLEM YOU BELIEVE THEY HAVE], [WHAT YOU SELL]

Generate a set of SPIN-style questions for a sales conversation with [PROSPECT ROLE] at [PROSPECT COMPANY].

We believe their core problem is: [PROBLEM YOU BELIEVE THEY HAVE]
We sell: [WHAT YOU SELL]

Produce:
- 2 Situation questions
- 2 Problem questions
- 3 Implication questions (focus on business cost of the problem)
- 2 Need-payoff questions

Output as a table with columns: Type | Question | What you're listening for

[NEEDS REAL OUTPUT] What to notice:, ---

8. Summarize a long email thread before a call

When to use it: The deal has been going on for weeks and you need to walk into the call without re-reading 40 emails. What to change first: Nothing. Paste the thread and run it.

Variables: [EMAIL THREAD]

Here is an email thread from an active sales deal:

[EMAIL THREAD]

Summarize it for a sales rep who has 3 minutes before a call. Include:
1. What the prospect wants (in their words if possible)
2. What concerns or objections have come up
3. What was promised or agreed so far
4. One thing to address or clarify on the call

Use bullet points. Be direct. Do not pad.

9. Identify likely objections before a demo

When to use it: You know the prospect's industry and role. Use this to prepare, not to script every response. What to change first: The role. A CFO and a VP of Engineering will object to different things.

Variables: [PROSPECT ROLE], [PROSPECT INDUSTRY], [WHAT YOU SELL], [DEAL SIZE OR CONTRACT TYPE]

We are about to run a product demo for [PROSPECT ROLE] at a [PROSPECT INDUSTRY] company.
We sell: [WHAT YOU SELL]
Deal type: [DEAL SIZE OR CONTRACT TYPE]

List the five most likely objections this buyer will raise, based on their role and industry.

For each objection:
- State the objection as they would say it
- Explain the underlying concern in one sentence
- Suggest one response approach (not a script)

Format as a table: Objection | Underlying concern | Response approach

Objection handling

10. Reframe a price objection without discounting

When to use it: The prospect says you're too expensive and you don't want to go straight to a discount. What to change first: The business outcome. Generic ROI language won't land; you need a specific number or result.

Variables: [PRICE OBJECTION QUOTE], [WHAT YOU SELL], [SPECIFIC OUTCOME OR ROI EXAMPLE], [PROSPECT'S STATED GOAL]

The prospect said: "[PRICE OBJECTION QUOTE]"

We sell: [WHAT YOU SELL]
Relevant outcome from a similar customer: [SPECIFIC OUTCOME OR ROI EXAMPLE]
Their stated goal: [PROSPECT'S STATED GOAL]

Write a response that:
1. Acknowledges the concern without apologizing for pricing
2. Reframes cost against the value of achieving [PROSPECT'S STATED GOAL]
3. Uses [SPECIFIC OUTCOME OR ROI EXAMPLE] as evidence
4. Ends with a question that returns the conversation to their priorities

Under 100 words. No hollow phrases like "I totally understand."

[NEEDS REAL OUTPUT] What to notice:, ---

11. Respond to "we already have a solution for that"

When to use it: A prospect shuts down the conversation early by pointing to an existing vendor or internal tool. What to change first: The incumbent. Research what the competitor is known to be weak at before running this.

Variables: [EXISTING SOLUTION THEY NAMED], [WHAT YOU SELL], [ONE GENUINE DIFFERENTIATOR], [PROSPECT ROLE]

The prospect told us they already use [EXISTING SOLUTION THEY NAMED].

We sell: [WHAT YOU SELL]
Our genuine differentiator: [ONE GENUINE DIFFERENTIATOR]

Write a two to three sentence response that:
- Doesn't disparage [EXISTING SOLUTION THEY NAMED]
- Raises one specific gap or limitation that [ONE GENUINE DIFFERENTIATOR] addresses
- Ends with a question that tests whether the gap matters to them

Keep it conversational. This is a spoken reply, not an email.

12. Handle a "not the right time" stall

When to use it: The deal is going quiet and "timing" is the stated reason. You want to keep the door open without being pushy. What to change first: The future trigger event. This is what makes the follow-up feel earned rather than automatic.

Variables: [PROSPECT NAME], [PROSPECT COMPANY], [WHAT YOU SELL], [TRIGGER EVENT THAT MIGHT CHANGE THEIR TIMELINE]

[PROSPECT NAME] at [PROSPECT COMPANY] told us it's not the right time.

We sell: [WHAT YOU SELL]
A realistic trigger event that could change their timeline: [TRIGGER EVENT THAT MIGHT CHANGE THEIR TIMELINE]

Write a short email (under 80 words) that:
1. Accepts their timeline without pushback
2. Plants a specific reason to re-engage around [TRIGGER EVENT]
3. Ends with a concrete offer to reconnect at that point

No guilt, no urgency. The tone is confident and respectful.

13. Turn a lost deal debrief into reusable objection intel

When to use it: After losing a deal, before the context disappears from memory. Run this with your own notes or a call transcript. What to change first: Be honest in the notes. Sanitized post-mortems produce useless output.

Variables: [DEAL NOTES OR CALL TRANSCRIPT], [WHAT YOU SELL], [DEAL SIZE], [STAGE LOST AT]

Here are notes from a lost deal:
[DEAL NOTES OR CALL TRANSCRIPT]

We sell: [WHAT YOU SELL]
Deal size: [DEAL SIZE]
Stage lost at: [STAGE LOST AT]

Analyze the notes and produce:
1. The three core reasons we lost (be specific, not generic)
2. The earliest signal we should have caught
3. Two questions we should add to future discovery calls to surface this pattern earlier
4. One change to our messaging that might have mattered

Be direct. Do not soften findings.

Follow-up & proposals

14. Write a post-demo follow-up email

When to use it: Within a few hours of a demo, before the prospect's attention moves on. What to change first: The specific moments from the demo. Generic recaps get ignored.

Variables: [PROSPECT NAME], [PROSPECT COMPANY], [KEY POINTS COVERED IN DEMO], [QUESTIONS THEY ASKED], [AGREED NEXT STEP], [YOUR NAME]

Write a follow-up email after a product demo.

Prospect: [PROSPECT NAME], [PROSPECT COMPANY]
Demo highlights: [KEY POINTS COVERED IN DEMO]
Questions they raised: [QUESTIONS THEY ASKED]
Next step agreed: [AGREED NEXT STEP]
Sender: [YOUR NAME]

Requirements:
- Under 150 words
- Open by referencing something specific they said or reacted to
- Recap only the two or three points most relevant to their stated priorities
- Confirm the next step clearly
- No "it was great to meet you" openers

[NEEDS REAL OUTPUT] What to notice:, ---

15. Draft an executive summary section for a proposal

When to use it: Your proposal is detailed but the economic buyer only reads the first page. What to change first: Their stated business priority. If you don't know it, don't guess.

Variables: [PROSPECT COMPANY], [PROSPECT'S STATED BUSINESS PRIORITY], [WHAT YOU SELL], [PROPOSED SOLUTION SUMMARY], [EXPECTED OUTCOME OR RESULT]

Write the executive summary section of a sales proposal for [PROSPECT COMPANY].

Their stated priority: [PROSPECT'S STATED BUSINESS PRIORITY]
What we're proposing: [PROPOSED SOLUTION SUMMARY]
Expected outcome: [EXPECTED OUTCOME OR RESULT]

Requirements:
- 150 words maximum
- Written for a C-level reader who has not attended any demos or calls
- Lead with their problem, not our product
- State the proposed solution in one sentence
- Close with the expected outcome in measurable terms where possible
- No jargon, no superlatives

16. Write a mutual action plan intro for a complex deal

When to use it: You're moving into a multi-stakeholder evaluation and want to align on a shared timeline. What to change first: The milestone dates. Placeholder dates in a real proposal undermine credibility immediately.

Variables: [PROSPECT COMPANY], [YOUR COMPANY], [EVALUATION START DATE], [TARGET DECISION DATE], [KEY MILESTONES], [MAIN PROSPECT CONTACT]

Write the introductory paragraph

## Real example outputs

Five prompts in this pack have been run against real models to show what the output looks like in practice. Those outputs are marked [NEEDS REAL OUTPUT] and will be replaced with captured screenshots before publication. In the meantime, the table below records what each prompt was given, which model ran it, and what a reviewer should look for in the result.

| Prompt | Input summary | Model | What to notice |
|---|---|---|---|
| Cold outreach email | SaaS product, CFO persona, Q4 budget angle | GPT-4o | Tone match to persona; no generic opener |
| Discovery question set | Enterprise deal, 3 known pain points | Claude 3.5 | Questions address each pain point without repeating it |
| Objection response | "We already have a solution" objection | Gemini 1.5 Pro | Specificity of the counter; avoids dismissing the objection |
| Deal review summary | Opportunity at proposal stage, 60-day stall | Copilot | Flags risk clearly; recommends a next action |
| Follow-up sequence | Post-demo, no response after 5 days | GPT-4o | Escalation in urgency across three touches without sounding desperate |

[NEEDS REAL OUTPUT]

## How to adapt these for your team

The prompts above are starting points, not finished assets. A cold outreach prompt that works for enterprise software will fall flat for a regional services firm, and the fastest way to break that gap is to replace the variables with specifics from your own context.

Start with the three brackets that matter most: [PRODUCT/SERVICE], [PAIN POINT], and [COMPANY NAME]. Filling those in accurately is worth more than any other edit.

After that, consider these adjustments:

- **Tone:** If your buyers are technical, remove the business-outcome framing and add product-level detail. If they are C-suite, do the opposite.
- **Length:** Paste a prompt output into a follow-up message asking the model to cut it by a third. Sales copy almost always benefits from this.
- **Voice:** Add two or three sentences of your own writing as an example, then ask the model to match that style.

One honest note: these prompts will not replace a rep who knows the account. They speed up the mechanical parts so that rep has more time to do the work AI still cannot.

## Save this folder to your workspace

These prompts work best when your whole team is pulling from the same source. If everyone adapts their own local copies, you end up with twenty slightly different versions of the same outreach template and no way to know which one actually converts.

:::cta heading="Want your sales team working from one shared prompt library?" href="/product/shared-folders" button="Start free"
Convergence shared folders let your team save, organize, and update prompts across ChatGPT, Claude, Copilot, and Gemini. One folder, every model, no copy-pasting between tools.
:::

The practical approach: create a folder called "Sales" in your Convergence workspace, drop each category from this page in as a subfolder, and pin the two or three prompts your team uses every week to the top.

When a prompt stops performing, update it once and everyone gets the new version. When a new rep joins, share the folder link instead of a Google Doc that will be outdated in a month.

For prompts used by other parts of the business, the [prompts by role library](/prompts) covers adjacent teams, including [marketing](/prompts/marketing) and [broader business use cases](/prompts/business).

## Frequently asked questions

### Are these ai prompts for sales usable across different AI tools?

Yes. Every prompt in this pack works in ChatGPT, Claude, Copilot, and Gemini without modification. The bracketed variables are the only parts you need to change. If a particular model gives a weaker result, try adding "be concise and direct" to the end.

### Do I need a paid AI subscription to use these prompts?

No. Free tiers of ChatGPT and Gemini handle most of these tasks adequately. Longer prompts, like the account plan builder, may hit token limits on free plans, in which case a paid tier or Claude's extended context is worth it.

### Can I share this prompt set with my whole sales team?

Yes, and sharing is where the real value compounds. A [shared folder in Convergence](/product/shared-folders) keeps everyone on the same version without file management.

### What should I do when a prompt gives a generic answer?

Add one specific constraint. Name the industry, the objection, or the deal size, and the output sharpens immediately.

### Are these prompts a replacement for sales training?

No. Prompts improve speed and consistency; they do not teach reps how to read a prospect or handle a difficult conversation.