Sales reps who use AI well don’t use it to write generic emails at scale — they use it to think faster and prepare more thoroughly. The prompts below cover the moments in a sales cycle where most time gets wasted: crafting a first touch that doesn’t sound like a template, building a discovery call agenda from a prospect’s LinkedIn and website, and handling an objection you’ve heard a hundred times without sounding scripted.
How to Use These Templates
Each template uses a Role/Task/Context/Format structure. The [brackets] are your fill-in fields. Don’t skip the Role line — it dramatically changes the default vocabulary and level of specificity the model applies. “Senior enterprise AE with SaaS experience” generates different copy than no role at all, even for identical tasks.
Where the template specifies something to avoid, take it seriously. AI defaults to the most common patterns in its training data, which means it defaults to the exact phrases every prospect has already seen 50 times (“I hope this finds you well,” “I wanted to reach out”). The avoid clauses are there to block those patterns explicitly.
For a faster setup, the AI Prompt Generator lets you enter your Role, Task, Context, and Format once and outputs a clean, ready-to-test prompt. Use it when you’re building a new template for a use case not covered here.
Cold Outreach Templates (1–5)
1. First-Touch Cold Email
Role: You are a senior B2B AE at a SaaS company with a 15%+ cold reply rate.
Task: Write a first-touch cold email to [PROSPECT NAME], [TITLE] at [COMPANY].
Context: They recently [TRIGGER EVENT — funding, hiring, product launch, job post]. My product [PRODUCT] solves [SPECIFIC PAIN] for companies like theirs. One relevant customer: [SIMILAR CUSTOMER + RESULT].
Format: Subject line under 7 words (no questions, no "quick" or "just"). Body under 90 words. CTA: one yes/no question or a specific offer (not "let me know if you're interested").
Avoid: "I hope this finds you well," "I wanted to reach out," "touching base," feature lists.2. LinkedIn Connection Request Note
Role: You are a B2B sales rep who writes LinkedIn connection notes that get accepted.
Task: Write a connection request note for [PROSPECT NAME] at [COMPANY].
Context: Reason for connecting: [GENUINE REASON — common contact, article they wrote, company news, shared interest]. My role: [YOUR ROLE]. Don't pitch in the note.
Format: Under 300 characters. One specific reason for connecting. No ask other than to connect.3. Cold Call Voicemail Script
Role: You are a sales development rep who leaves voicemails with a 25%+ callback rate.
Task: Write a voicemail script for a cold call to [PROSPECT TITLE] at [COMPANY TYPE].
Context: Product: [PRODUCT]. Value prop in one sentence: [VALUE PROP]. One specific hook: [STAT OR RESULT].
Format: Under 30 seconds (roughly 60-70 words). State name and company in the first 3 seconds. Leave a specific reason to call back, not a generic "I'd love to connect."4. Referral Request Email
Role: You are a sales rep writing to a happy customer to ask for a referral.
Task: Write an email asking [CUSTOMER NAME] at [CUSTOMER COMPANY] for a referral.
Context: They've been a customer for [TIME PERIOD]. Recent positive signal: [POSITIVE INTERACTION/REVIEW/RESULT]. Ideal referral profile: [ICP].
Format: Subject + body under 150 words. Make the ask specific (a name, not "anyone you know"). Offer something in return if appropriate.5. Conference Follow-Up Email
Role: You are an AE writing a follow-up email after a conference or networking event.
Task: Write a follow-up email to [PROSPECT NAME] met at [EVENT].
Context: What you discussed: [TOPIC]. Next step discussed (if any): [NEXT STEP]. Something specific from the conversation to reference: [DETAIL].
Format: Subject references the event or conversation topic specifically. Body under 120 words. One clear next step as a CTA.Discovery and Qualification Templates (6–10)
6. Discovery Call Agenda Builder
Role: You are a senior AE preparing for a discovery call with a new prospect.
Task: Build a 45-minute discovery call agenda for [PROSPECT COMPANY].
Context: Prospect info: [PASTE LINKEDIN HEADLINE / COMPANY OVERVIEW / RECENT NEWS]. My product: [PRODUCT]. My hypothesis about their pain: [HYPOTHESIS].
Format: Agenda with time blocks: [0-5 min] rapport/context setting, [5-20 min] discovery questions, [20-35 min] solution exploration, [35-45 min] next steps. For the discovery section, provide 6-8 questions in order of conversational flow, not importance.7. MEDDIC Qualification Questions
Role: You are an enterprise AE trained in MEDDIC qualification.
Task: Write MEDDIC qualification questions tailored for selling [PRODUCT] to [ICP].
Context: Common deal blockers in this segment: [BLOCKERS]. Typical champion profile: [CHAMPION TITLE]. Economic buyer is usually: [EB TITLE].
Format: 2-3 questions per MEDDIC element (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion). Label each section. Questions should feel conversational, not interrogative.8. Prospect Research Summary
Role: You are a sales intelligence analyst.
Task: Summarize the following information about [PROSPECT COMPANY] into a pre-call briefing.
Context: [PASTE: company About page, recent press release, LinkedIn page, or any prospect info you have].
Format: 5 sections: Company overview (2-3 sentences), Recent news/signals, Likely pain points for [YOUR PRODUCT CATEGORY], Potential internal champion roles, Suggested opening hook for outreach. Total under 300 words.9. Stakeholder Mapping Prompt
Role: You are a B2B sales strategist who specializes in multi-stakeholder enterprise deals.
Task: Create a stakeholder map for selling [PRODUCT] into [COMPANY/INDUSTRY TYPE].
Context: Deal size: [SIZE]. Typical departments involved: [LIST]. Known contacts: [PASTE NAMES/TITLES IF KNOWN].
Format: Table with columns: Role/Title | Their likely priority | Their likely concern about [PRODUCT] | How to approach them | Who they likely report to.10. Pre-Call Hypothesis Statement
Role: You are a consultative sales rep preparing for a discovery call.
Task: Write a hypothesis statement to open a discovery call with [PROSPECT].
Context: What I know about their situation: [RESEARCH]. My product solves: [PAIN]. My hypothesis about why they might be looking: [HYPOTHESIS].
Format: 2-3 sentences, first person. Structured as: "Based on [what you observed], my hypothesis is that [pain/goal]. Is that directionally right?" — a statement they can correct, not an open-ended question.
Objection Handling Templates (11–14)
11. Price Objection Response
Role: You are a seasoned AE who handles price objections without discounting reflexively.
Task: Write a response to the objection: "Your price is too high / we don't have budget right now."
Context: Product: [PRODUCT]. Deal size: [DEAL SIZE]. ROI data available: [RESULT/STAT]. Alternative options if price is genuinely a blocker: [ALTERNATIVES — phased rollout, smaller pilot, etc.].
Format: Under 100 words. Acknowledge the concern without validating it as a reason to stall. Redirect to value or ROI. Do not offer a discount unprompted.12. “We’re Already Using a Competitor” Objection
Role: You are an AE competing against [COMPETITOR NAME] in an active deal.
Task: Write a response to: "We already use [COMPETITOR] and we're happy with it."
Context: Our key differentiators vs. [COMPETITOR]: [DIFFERENTIATORS]. A case where we beat [COMPETITOR]: [CUSTOMER STORY if available].
Format: 3-4 sentences. Validate the existing relationship briefly, then introduce one specific differentiator that creates curiosity. End with a question that opens a gap analysis conversation.13. “Not the Right Time” / Stall Response
Role: You are an AE handling a prospect who is genuinely interested but stalling on timing.
Task: Write a response to: "This isn't the right time — let's revisit in [TIMEFRAME]."
Context: Reason for their timing: [WHAT YOU KNOW]. What might change or not change by then: [ASSESSMENT]. Risk of waiting: [SPECIFIC COST OF DELAY if known].
Format: Under 80 words. Don't pressure. Ask one diagnostic question to determine whether timing is genuine or a soft no.14. Technical / Security Objection
Role: You are an AE with a strong technical understanding of your product's security and compliance posture.
Task: Write an initial response to a technical or security objection: "[PASTE THEIR OBJECTION]."
Context: Product: [PRODUCT]. Available documentation: [CERTIFICATIONS/WHITEPAPERS]. Appropriate next step: [BRING IN SE / SEND SECURITY QUESTIONNAIRE / SCHEDULE TECHNICAL CALL].
Format: 3-4 sentences. Validate the concern as legitimate and specific. Provide one direct answer if you can. Propose a concrete next step that moves forward rather than stalling.Try it free
GetResponse
Build automated email sequences, landing pages, and nurture funnels with AI assistance.
Proposal, Follow-Up, and Closing Templates (15–20)
15. Executive Summary for Proposal
Role: You are an enterprise AE writing the executive summary section of a formal proposal.
Task: Write a 1-page executive summary for a proposal to [PROSPECT COMPANY].
Context: Their stated goals: [GOALS]. Their current pain: [PAIN]. What we're proposing: [SOLUTION OVERVIEW]. Business case: [ROI/OUTCOMES]. Timeline: [PROPOSED TIMELINE].
Format: 4 short sections: Situation (their current state), Complication (why it's a problem), Resolution (what we're proposing), Value (what they get). Total under 300 words. No jargon. No feature lists.16. Follow-Up After No Response (Bump Email)
Role: You are an AE writing a follow-up bump email after a prospect went quiet.
Task: Write a follow-up email to [PROSPECT] who hasn't responded to the previous email sent [X] days ago.
Context: Original email topic: [TOPIC]. New value to add or different angle: [NEW ANGLE — changed something, new resource, question about their priority].
Format: Subject references previous thread or tries a new angle. Body under 60 words. No guilt. One new piece of value or a different question.
Avoid: "Just following up," "I wanted to circle back," "touching base," "checking in."17. Mutual Action Plan (MAP) Template
Role: You are a senior AE structuring a mutual action plan for a deal in late-stage evaluation.
Task: Write a mutual action plan structure for closing a deal with [PROSPECT COMPANY] by [TARGET CLOSE DATE].
Context: Current stage: [STAGE]. Remaining steps on their side: [THEIR STEPS]. Remaining steps on our side: [YOUR STEPS]. Known blockers: [BLOCKERS].
Format: Table with columns: Action Item | Owner | Due Date | Status. Separate sections for Prospect Actions and Vendor Actions. Then a 2-sentence cover note to send with the MAP.18. Contract Negotiation Prep
Role: You are a sales manager preparing an AE for contract negotiation.
Task: Identify likely negotiation pressure points and prepare responses for a deal with [PROSPECT].
Context: Deal size: [SIZE]. What they've asked about: [PRICING/TERMS THEY FLAGGED]. Our flexibility: [WHAT WE CAN MOVE ON]. Our floor: [WHAT WE CANNOT MOVE ON].
Format: Table: Issue | Their likely ask | Our position | Acceptable tradeoff | Concession framing language.19. Champion Enablement Email
Role: You are an AE helping your internal champion sell the deal upward to the economic buyer.
Task: Write a short email your champion can forward to their boss to explain why they're recommending [PRODUCT].
Context: Champion: [TITLE]. Economic buyer: [EB TITLE]. Business case: [ROI]. Risk of not acting: [COST OF DELAY/STATUS QUO].
Format: Under 200 words. Written as if the champion wrote it themselves (first-person from their perspective). One clear ask of the EB.20. Win/Loss Analysis Prompt
Role: You are a sales strategist conducting win/loss analysis.
Task: Analyze the following deal notes and categorize the primary reason for [WIN/LOSS].
Context: [PASTE DEAL NOTES, CALL SUMMARIES, CLOSE DATE, DEAL SIZE, COMPETITOR IF KNOWN].
Format: 4 sections: Primary reason for outcome (1 sentence), Supporting evidence from the notes (2-3 bullet points), What could have changed the outcome (1-2 actionable items), Pattern to watch for in future deals (1 sentence).Get Your Prompts Built and Ready to Copy
Customizing all 20 of these templates every time you start a new campaign or deal cycle is repetitive work. The AI Prompt Generator lets you set your product, ICP, brand voice, and key differentiators once and outputs structured prompts ready to paste into any model. For teams running these at scale, pair it with the guidance in AI prompt templates for marketing — many of the cold outreach and follow-up patterns overlap.
Frequently asked questions
Are these templates more effective in ChatGPT or Claude? Both work well. Claude tends to produce slightly more precise, less padded copy for cold emails, which is useful for short-form outreach. GPT-4o handles longer structured outputs (proposals, stakeholder maps) with better formatting consistency. Test your three highest-volume templates in both and standardize on whichever produces closer-to-deployable first drafts.
Should I personalize these prompts per prospect or use them as batch generators? Personalize for high-priority accounts where a 1% improvement in reply rate has real revenue impact. Use batch generation for high-volume SDR outreach where the economics favor speed over hyper-personalization. The trigger event field in Template 1 is the minimum personalization that meaningfully lifts reply rates in cold outreach.
How do I prevent my AI cold emails from sounding like AI wrote them? The avoid clauses in each template block the most obvious AI defaults. Beyond that, add specific details: real company names, real numbers from their press releases, actual product names. Generic claims (“increase efficiency”) produce generic output. Specific claims (“reduce time spent on manual data entry in your Salesforce instance”) produce specific output.
Do these prompts work for PLG or product-led sales motions? Many of them do, with adjustments. Discovery templates work for expansion conversations (“you’re using our Starter plan, what’s driving the team’s usage up?”). Objection handling templates apply to upgrade conversations. The cold outreach templates are less relevant if leads are already activated users — adapt them for expansion plays instead.
Can I use these in a CRM like Salesforce or HubSpot via AI integrations? Yes. The prompts here are model-agnostic and work in any chat interface or API. For CRM integration, use the template text in Salesforce Einstein, HubSpot’s AI content tools, or a custom integration via the OpenAI API. The Role/Task/Context/Format structure translates directly to system prompt + user message structure in API calls.