Spend less time staring at a blank email and more time selling. These prompts cover the full cycle — cold outreach, follow-ups, objection replies, discovery prep, and call recaps — with the guardrails that keep them sounding like you, not a template.
Cold email is where most reps lose the deal before it starts. The outreach prompts here force a specific observation in the first line and a single clear ask, because generic openers are exactly what gets deleted. The follow-up and break-up prompts add new value each time instead of “just bumping this,” and the objection prompt reframes price around the cost of the problem rather than instantly discounting.
The post-call prompts are quiet pipeline insurance: a same-day recap that restates what the buyer cares about, and a clean CRM summary that never invents a budget or stakeholder you didn’t hear. Paste your real notes and prospect details — the more specific your input, the less generic the output.
12 prompts · free to copy · example output on each
ChatGPTGeminiClaude
Cold outreach email to a new lead
Write a short, personalized cold email that earns a reply instead of a delete.
The prompt
You are an experienced B2B sales rep known for cold emails that get replies. Write a cold outreach email to [PROSPECT NAME], the [JOB TITLE] at [COMPANY].
Context:
- What we sell: [ONE-LINE PRODUCT DESCRIPTION]
- The problem we solve for companies like theirs: [PAIN POINT]
- One specific thing I noticed about their company: [TRIGGER / RESEARCH NOTE]
Rules:
- Under 120 words, plain language, no buzzwords.
- Open with the specific observation, not "I hope this finds you well."
- One clear call to action: a 15-minute call.
- Plain text, no markdown. Then give me 2 subject line options.
Example output
Subject A: a quick idea for [Company]'s new office
Subject B: [Company] + faster ramp for new reps?
Hi [Name],
Saw [Company] just opened a second support office — congrats. Scaling support usually means new hires fielding the same 20 questions for weeks.
We give support teams an answer layer trained on your own docs, so new reps ramp in days instead of months. [Similar company] cut their ramp time by about a third.
Worth a 15-minute call next week to see if it'd fit your new office? Happy to work around your calendar.
Thanks,
[Your name]
TipPaste a real LinkedIn or news detail into the trigger line — generic openers are exactly what gets cold emails deleted. Asking for "2 subject line options" gives you something to A/B test.
ChatGPTGeminiClaude
Follow-up email after no reply
Nudge a silent prospect without sounding needy or repeating yourself.
The prompt
Write a follow-up email to a prospect who didn't reply to my first message [NUMBER] days ago.
Original email was about: [TOPIC / OFFER].
Rules:
- Don't say "just following up" or "bumping this."
- Add one new piece of value (a stat, a relevant example, or a resource) so the email stands on its own.
- Keep it under 80 words.
- End with a low-friction question they can answer in one line.
Example output
Subject: re: cutting your support ramp time
Hi [Name],
One more reason this might be worth a look: [Similar company] had the same "new reps drowning for weeks" problem and got first-week resolution rates up 22% after switching.
If ramp time isn't a priority right now, no worries — just reply "not now" and I'll close the loop.
Otherwise, open to 15 minutes Thursday?
[Your name]
TipGiving them an easy "not now" out actually raises reply rates — people answer when saying no is painless. Swap the value line each follow-up so you never just repeat the pitch.
ChatGPTGeminiClaude
Break-up email to a cold prospect
Send a final, pattern-breaking message that often revives a dead thread.
The prompt
Write a short "break-up" email — my last attempt to reach a prospect who has gone silent after [NUMBER] emails about [OFFER].
Tone: warm, no guilt-tripping, genuinely closing the loop. Make it easy for them to either re-engage or be left alone. Under 70 words. Give it a subject line that earns the open.
Example output
Subject: should I close your file?
Hi [Name],
I've reached out a few times about helping [Company] shorten new-rep ramp time, and haven't heard back — which usually means it's not the right time, or not a fit.
I'll stop here so I'm not cluttering your inbox. If that changes, just reply and I'll pick it right back up.
All the best,
[Your name]
Tip"Should I close your file?" triggers a reply more often than any pitch — loss aversion does the work. Keep it genuinely gracious; the goodwill is worth more than one deal.
ChatGPTGeminiClaude
Reply to a "too expensive" objection
Respond to price pushback by reframing value, without instantly discounting.
The prompt
A prospect replied that our price is too high. Write a reply that:
- Acknowledges the concern without getting defensive.
- Reframes the conversation around the cost of the problem they have today, not our sticker price.
- Asks one question to uncover what "too expensive" really means (budget, ROI doubt, or comparison).
- Does not offer a discount.
Their message: [PASTE THEIR REPLY]
Our price + what it includes: [DETAILS]
Example output
Hi [Name],
Totally fair to scrutinize the number — that's the right instinct.
Quick reframe: right now, slow ramp is costing roughly [X hours] per new hire before they're productive. At your hiring pace that's the real line item; our price is a fraction of it.
So I can point you the right way — is the concern the budget itself, the payback timeline, or how we compare to [alternative]? Happy to dig into whichever it is.
[Your name]
TipThe diagnostic question is the key move — "too expensive" means three different things and each needs a different answer. Lead with their cost-of-inaction, not your feature list.
ChatGPTGeminiClaude
Discovery call question list
Build a sharp set of questions that surface budget, pain, and decision process.
The prompt
I have a discovery call with [PROSPECT ROLE] at [COMPANY TYPE]. We sell [PRODUCT].
Give me a discovery call script with:
1. Two warm-up questions.
2. Five questions that uncover their current pain and what it's costing them.
3. Three questions that reveal budget, timeline, and who else decides.
4. One question to surface the real objection before it kills the deal.
Keep each question open-ended (no yes/no). Add a one-line note on what I'm listening for under each.
Example output
Warm-up
- "Walk me through how your team handles [process] today." → listening for: their words for the pain.
- "What made you take this call?" → listening for: the trigger event.
Pain & cost
- "Where does that process break down most often?" → the symptom they feel.
- "What happens downstream when it breaks?" → the real cost.
- "How are you working around it now?" → urgency and budget for a fix.
...
Decision
- "Besides you, who'd weigh in on a change like this?" → hidden stakeholders.
TipThe "what is it costing you" questions are what let you sell on ROI later — capture their exact numbers and quote them back in your proposal.
ChatGPTGeminiClaude
Recap email after a sales call
Send a same-day recap that confirms next steps and keeps the deal moving.
The prompt
Turn my rough call notes into a clean recap email to the prospect. Structure:
- One-line thank you.
- "What I heard" — 3 bullets restating their priorities (shows I listened).
- "Next steps" — who does what, by when.
- A clear ask to confirm the next meeting.
Keep it skimmable. Don't invent anything not in my notes.
My notes: [PASTE NOTES]
Example output
Subject: recap + next steps from today
Hi [Name],
Thanks for the time today — useful conversation.
What I heard matters most to you:
- Cutting new-rep ramp from ~6 weeks to under 2.
- Keeping answers accurate as your docs change weekly.
- A rollout that doesn't pull your leads off the floor.
Next steps:
- Me: send the security overview by Friday.
- You: loop in [IT contact] for the data question.
- Both: 30-min technical review next Wed.
Does Wednesday 2pm still work to lock that in?
[Your name]
TipThe "what I heard" section is the secret weapon — restating their priorities in their words builds more trust than any feature recap. Send it within a few hours while it is fresh.
ChatGPTGeminiClaude
Clean up call notes for your CRM
Turn messy call scribbles into structured CRM fields and a next action.
The prompt
Convert my raw call notes into a CRM-ready summary with these exact fields:
- Stage (one of: Discovery / Evaluation / Proposal / Negotiation)
- Pain points (bullets)
- Budget signal (what they actually said about money, or "none mentioned")
- Decision makers
- Objections / risks
- Next action + date
Only use what's in the notes. If a field is empty, write "none mentioned."
Notes: [PASTE NOTES]
Example output
Stage: Evaluation
Pain points:
- 6-week ramp for new support reps
- Docs change weekly, answers go stale
Budget signal: "We have room if it pays back in a quarter."
Decision makers: [Name] (Head of Support), + IT for security sign-off
Objections / risks: Worried about setup time during peak season
Next action: Send security overview — by Fri Jun 19
TipThe "none mentioned" rule stops the AI from inventing a budget or stakeholder you never heard — which is what makes the summary safe to paste straight into your pipeline.
ChatGPTGeminiClaude
LinkedIn connection request that gets accepted
Write a short, non-salesy connection note tied to a real reason to connect.
The prompt
Write a LinkedIn connection request note (under 300 characters) to [NAME], the [ROLE] at [COMPANY].
Reason I'm reaching out: [SHARED GROUP / THEIR POST / EVENT / MUTUAL CONNECTION].
Rules:
- Reference the real reason, not my product.
- Sound like a human, not a pitch.
- No "I'd love to add you to my network."
Example output
Hi [Name] — really liked your post on cutting support onboarding time; the "shadow an expert" point matched what I keep hearing from support leads. I work in that space and would enjoy following your take. Either way, thanks for sharing it.
TipNever pitch in the connection note — the goal is only to get accepted. Save the value for a message a few days later, once you are connected.
ChatGPTGeminiClaude
LinkedIn post from a customer win
Turn a customer result into a story-style post that builds pipeline, not bragging.
The prompt
Write a LinkedIn post based on a customer win. Use a story arc: the problem they had, the turning point, the result.
Details:
- Customer type: [INDUSTRY / SIZE, keep anonymous if needed]
- Before state: [PROBLEM + ROUGH NUMBER]
- After state: [RESULT + NUMBER]
Rules:
- First line must stop the scroll (no "Excited to share...").
- Conversational, short paragraphs, one takeaway lesson.
- Soft CTA at the end, not "DM me to buy."
Example output
A support team told me their new hires were "useless for a month." Their words, not mine.
The problem wasn't the people. New reps were hunting through 400 pages of docs that changed every week — so they guessed, or pinged a senior rep, who then stopped doing their own job.
We gave them one answer layer trained on those same docs. First-week resolution rates went from 51% to 73%.
The lesson: onboarding speed is usually a findability problem, not a training problem.
Curious how other support leaders are tackling ramp time — what's worked for you?
TipLead with a real quote or a number, never "Excited to share." End by asking a question so the post earns comments — which is what gets it shown to more feeds.
ChatGPTGeminiClaude
Executive summary for a proposal
Condense a long proposal into a one-paragraph summary an exec will actually read.
The prompt
Write a one-paragraph executive summary to open a sales proposal. It should make a busy executive want to read on.
Cover, in plain language: the business problem, what we propose, the expected result (with a number if I give one), and the investment.
Details: [PASTE KEY PROPOSAL POINTS / PRICE / EXPECTED ROI]
Keep it under 120 words, confident but not hypey.
Example output
[Company] is spending roughly six weeks getting each new support rep to full productivity — time that costs both salary and senior-rep attention. This proposal outlines an answer layer trained on your existing documentation that gets new reps productive in under two weeks and keeps answers accurate as your docs change. Based on your current hiring pace, the expected payback is under one quarter. The investment is [PRICE] per year, including onboarding and your team's data setup. The sections below detail the rollout plan, security review, and success metrics we'd track together in the first 90 days.
TipPut the result and the payback period in the first three sentences — executives decide whether to keep reading there. Save features for the body.
ChatGPTGeminiClaude
Demo prep brief from prospect research
Get a tailored demo plan so you show the right features to the right buyer.
The prompt
Help me prep a product demo. Based on what I know about the prospect, tell me which features to lead with and which to skip.
Prospect: [ROLE] at [COMPANY TYPE]
Their main pains (from discovery): [PAINS]
Our features: [LIST FEATURES]
Give me: a 3-beat demo flow mapped to their pains, the one "wow" moment to land, and two questions to ask mid-demo to keep it a conversation.
Example output
Demo flow (map each beat to their pain):
1. Start at the new-rep view → "here's day one for a new hire." (pain: 6-week ramp)
2. Show a doc update auto-syncing → "answers never go stale." (pain: weekly doc changes)
3. Manager dashboard → resolution rate by rep. (pain: no visibility)
Wow moment: ask them for a real question their reps get, type it live, show the sourced answer.
Mid-demo questions:
- "Is this the kind of question that trips up new reps?"
- "Who on your side would live in this dashboard?"
TipSkipping features is as important as showing them — a demo that covers everything lands nothing. The live "type their real question" moment beats any scripted example.
ChatGPTGeminiClaude
Win/loss summary from deal notes
Extract why a deal was won or lost so the next one goes better.
The prompt
Analyze my notes from a closed deal and produce a win/loss summary:
- Outcome: Won / Lost
- Primary reason (one sentence)
- Contributing factors (bullets)
- What the competitor did, if mentioned
- One thing I'd do differently next time
Be honest, not flattering. Only use what's in the notes.
Deal notes: [PASTE NOTES]
Example output
Outcome: Lost
Primary reason: We were brought in too late — they'd already shortlisted two vendors before our first call.
Contributing factors:
- Champion liked us but wasn't the budget owner.
- Our security review took 9 days; competitor turned theirs around in 2.
- We never got a meeting with the CFO.
Competitor: Won on faster procurement, not product.
Do differently: Qualify "where are you in the process?" on call one, and pre-stage the security packet.
TipRun this on both wins and losses — patterns across 10 of these tell you more about your sales process than any single deal. Be ruthlessly honest in the notes or the summary is useless.
How do I write a cold email with ChatGPT that gets replies?
Use the cold-outreach prompt and feed it a real, specific detail about the prospect (a recent post, hire, or launch). It opens with that observation, keeps the email under 120 words, and ends with one low-friction ask — the pattern that earns replies.
Can ChatGPT handle a pricing objection for me?
It can draft a strong reply. The objection prompt acknowledges the concern, reframes around the cost of the current problem, and asks one diagnostic question to find out whether “too expensive” means budget, ROI doubt, or a competitor — without auto-discounting.
Will these emails sound generic?
Only if your input is generic. The prompts are built to demand specifics — a trigger event, a real number, the prospect’s actual words — so the output reflects your deal, not a template. Always do a quick personal edit before sending.
How do I turn call notes into a CRM update?
Paste your raw notes into the “clean up call notes for your CRM” prompt. It maps them to fields — stage, pain points, budget signal, decision makers, next action — and writes “none mentioned” instead of inventing anything.