5 Prompt Patterns for Sales Outreach and Follow-ups

Sales outreach lives or dies on personalization and timing. Generic emails get deleted. Slow follow-ups lose deals. And most sales reps spend more time writing emails than actually selling.

AI can handle the writing — but only if the prompt captures the context that makes sales communication effective. "Write a sales email" produces something that reads like every other automated outreach in your prospect's inbox. These five patterns produce communication that's specific to the prospect, relevant to their situation, and structured to get a response.

The key difference: these patterns require you to input what you know about the prospect. The more context you provide, the better the output. If you don't know anything about the prospect, you need to do research first — no prompt can fix a lack of preparation.

Pattern 1: The Personalized Cold Outreach

This pattern generates first-touch emails that demonstrate you've done your homework. It's built around a specific trigger — something that makes this the right time to reach out to this specific person.

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

About the prospect:
- Name and title: [e.g., "Sarah Chen, VP of Operations"]
- Company: [Name, size, industry]
- Trigger for outreach: [Why now — a job change, company news, funding round, hiring pattern, social media post, etc.]
- Likely pain point based on their role/company: [Your hypothesis]

About us:
- What we sell: [One sentence]
- Relevant proof point: [One specific result — a customer win, a metric, a case study]
- The ask: [What you want them to do — reply, book a call, watch a demo]

Write the email:
- Subject line: Under 6 words. Reference their situation, not your product.
- Opening line: Connect the trigger to their likely situation — show you know what's going on in their world.
- Value bridge: 1-2 sentences connecting their pain to your solution. Lead with their problem, not your features.
- Proof: One sentence with a specific, relevant result.
- CTA: One question that's easy to say yes to. Low commitment.
- Total: Under 90 words (body only, excluding subject line).

Rules:
- No "I hope this email finds you well"
- No "I'd love to pick your brain" or "I'd love to learn more about your business"
- Don't lead with who you are or what your company does — lead with their world
- Sound like a person, not a sequence

Why it works: The trigger-based approach means you're reaching out for a reason, not just because they're on a list. The 90-word limit forces extreme conciseness — long cold emails don't get read. Leading with the prospect's world (not your product) is the single biggest differentiator between cold emails that get replies and ones that don't.

Example output snippet:

Subject: Your ops team expansion

>

Hi Sarah,

>

Noticed you're hiring 4 operations analysts — that usually means the manual reporting workload is hitting a ceiling.

>

We help ops teams like yours automate the data reconciliation step that typically eats 10+ hours per week. Acme Corp's ops team cut their monthly close from 5 days to 2 after switching.

>

Worth a 15-minute call to see if there's a fit?

Pattern 2: The Discovery Call Prep

Showing up to a discovery call prepared is what separates good reps from average ones. This pattern generates a briefing document and question set tailored to the specific prospect.

You are a sales strategist preparing a rep for a discovery call.

Prospect details:
- Company: [Name, industry, size, stage]
- Contact: [Name, title, how long in role]
- What we know so far: [Any intel from previous interactions, their website, LinkedIn, news]
- Why they took the meeting: [How did this call get booked? Inbound lead? Cold outreach? Referral?]
- Our product/service: [Brief description]
- Ideal outcome of this call: [e.g., "qualify the opportunity and book a demo"]

Create a discovery prep document:

1. **Company context** (3-4 bullet points): Key facts about their business, recent news, and likely priorities based on their industry and stage.

2. **Hypothesis**: What problem do we think they have? Frame it as a testable hypothesis, not a certainty. "They're probably struggling with X because of Y."

3. **Discovery questions** (8-10 questions, organized):
   - Situation questions (2-3): Understand their current state
   - Problem questions (3-4): Dig into pain points and their impact
   - Implication questions (2-3): Explore what happens if they don't solve this
   - Each question should feel conversational, not like a checklist interrogation

4. **Red flags to listen for**: 3-4 signals that this isn't a good fit (wrong timeline, no budget authority, no real pain)

5. **Competitive intel**: If they're likely evaluating alternatives, what would those be and how do we differentiate?

6. **Closing move**: The specific next step to propose at the end of the call, phrased as a question.

Format as a one-page briefing document. The rep should be able to read this in 5 minutes before the call.

Why it works: The hypothesis approach (not assumption) keeps the rep curious rather than prescriptive during the call. Organizing questions by Situation-Problem-Implication follows the SPIN selling framework, which is conversation-based. Red flags prevent wasted time on unqualified opportunities. The 5-minute-read constraint keeps the prep focused.

Example output snippet:

Hypothesis: With 4 new ops hires, they're scaling a process that's currently manual. They probably need the team productive fast, which means their onboarding and tooling gaps are urgent — not a "nice to have Q4 project."

>

Problem questions:

- "What does the data reconciliation process look like today? Walk me through a typical cycle."

- "When the process breaks — and I'm guessing it does — what's the impact on downstream teams?"

- "How much time does your most experienced person spend on tasks you wish were automated?"

>

Red flag: If they say "we're just exploring options for next year" — low urgency, likely to stall.

Pattern 3: The Objection Handler

This pattern generates responses to common sales objections. It doesn't just provide rebuttals — it acknowledges the concern, reframes it, and provides evidence.

You are a sales coach training a rep to handle objections.

Context:
- What we sell: [Product/service description]
- Price point: [Approximate pricing]
- Typical buyer: [Who makes the decision]
- Sales stage: [Where these objections typically come up — discovery, demo, negotiation]

The prospect said: "[Paste the exact objection]"

Create a response using the AER framework:
1. **Acknowledge**: Show you heard and respect their concern. Don't dismiss it. (1 sentence)
2. **Explore**: Ask a clarifying question to understand the real concern behind the stated objection. (1 question)
3. **Reframe**: After they answer, here's how to reframe the concern. Provide 2-3 response options:
   - Option A: Evidence-based (use a specific proof point or case study)
   - Option B: Question-based (turn the objection into a discovery question)
   - Option C: Reframe-based (shift the perspective on the concern)

Also provide:
- **What they're really saying**: The underlying concern behind this objection
- **What NOT to say**: Common mistakes reps make when handling this specific objection
- **If they push back again**: A graceful way to move forward without being pushy

Why it works: The AER framework prevents the common sales mistake of immediately arguing against an objection. The "what they're really saying" section helps reps understand subtext. Providing three response options lets the rep choose based on their read of the conversation. The "what NOT to say" prevents counterproductive responses.

Example output snippet:

Objection: "Your pricing is too high. We can get something similar for half the cost."

>

What they're really saying: They may not see enough differentiation to justify the premium, or they need ammunition to justify the budget internally.

>

Acknowledge: "That's a fair point — budget matters, and I wouldn't want you paying more than the value you'd get."

>

Explore: "Help me understand — when you say 'something similar,' which specific capabilities are you comparing? I want to make sure we're looking at the same thing."

>

Reframe options:

- Evidence: "Acme Corp had the same concern. They ran a 30-day comparison and found the cheaper tool required 15 hours/month of manual workarounds. The math on that alone exceeded the price difference."

- Question: "If the less expensive option requires your team to handle X and Y manually, what would that cost you in hours per month?"

>

What NOT to say: Don't trash the competitor. And don't immediately offer a discount — it signals that the original price wasn't real.

Pattern 4: The Proposal Drafter

This pattern generates the narrative sections of a sales proposal — not the pricing table, but the parts that frame the value and connect your solution to the prospect's specific needs.

You are a sales proposal writer creating a proposal for a specific prospect.

Prospect details:
- Company: [Name, size, industry]
- Decision maker: [Name, title]
- Their problem: [What they told us in discovery — use their words where possible]
- Their goals: [What success looks like for them]
- Current situation: [How they're handling things today]
- Why now: [What's driving urgency]
- Budget signals: [Any pricing expectations or budget constraints mentioned]
- Evaluation criteria: [What they said matters most in their decision]

Our solution:
- What we're proposing: [Specific solution, not the full product catalog]
- Key differentiators for THIS prospect: [What matters most to them about us]
- Relevant case study: [Similar customer, similar problem, specific results]
- Implementation timeline: [How long to get value]

Write these proposal sections:

1. **Executive summary** (under 150 words): Frame the problem in their language, state what we're proposing, and preview the expected outcome. This should be compelling enough to stand on its own.

2. **Problem statement**: Describe THEIR situation — not a generic industry problem. Reference specific things they said in discovery.

3. **Proposed solution**: How our product/service addresses their specific needs. Organized by their evaluation criteria, not our feature list.

4. **Expected outcomes**: What they should expect, tied to their stated goals. Be specific where data supports it; be honest where it's an estimate.

5. **Why us**: 2-3 reasons to choose us over alternatives — framed around what matters to this prospect, not generic company differentiators.

Rules:
- Use the prospect's language, not our marketing language
- Don't over-promise — state outcomes we can actually deliver
- Every section should reference something specific from discovery
- This is a business document, not a brochure. No puffery.

Why it works: Framing every section around the prospect's words and priorities makes the proposal feel custom, not templated. Organizing by their evaluation criteria (not your feature list) shows you listened. The "no puffery" instruction prevents the AI from inflating claims.

Example output snippet:

Executive summary:

Your operations team spends an estimated 40 hours per month reconciling data between Salesforce and your reporting tools — time Sarah described as "the most expensive busy-work in our department." We're proposing an automated integration that eliminates manual reconciliation entirely, targeting a reduction to under 2 hours per month. Based on our work with similar mid-market ops teams, we expect full deployment within 3 weeks and measurable time savings within the first month.

Pattern 5: The Deal Accelerator Follow-Up

Deals stall. This pattern generates follow-ups designed to restart momentum without being annoying. Each follow-up adds value and creates a reason to re-engage.

You are a senior sales rep writing a follow-up to restart a stalled deal.

Deal context:
- Prospect: [Name, title, company]
- Last interaction: [What happened and when]
- Where the deal stalled: [After demo, after proposal, after pricing, etc.]
- What I think happened: [Why it stalled — internal politics, lost priority, budget freeze, evaluating competitor, etc.]
- Our value proposition for them: [The key reason they should buy]
- What I've already tried: [Previous follow-up attempts]

Write a follow-up email that:

1. **Does NOT open with "just checking in" or "following up on..."** — find a different entry point
2. **Adds genuine value**: Attach or reference something useful:
   - Choose one: A relevant insight, a case study they haven't seen, a new feature that addresses a concern they raised, a piece of industry news that relates to their problem, or a competitive update
3. **Gently resurfaces the opportunity** without being pushy
4. **Provides an easy out**: Give them a graceful way to say "not now" — counterintuitively, this often restarts conversations
5. **Ends with a specific, low-commitment CTA**

Total: under 100 words.
Tone: helpful and confident, not desperate or guilt-tripping.

Also provide:
- **Alternative approach**: If email isn't working, suggest one other channel or tactic to try (voicemail, LinkedIn message, mutual connection intro, send something physical)

Why it works: The value-add requirement transforms the follow-up from "are you still interested?" (which is about you) to "here's something useful" (which is about them). The easy out is counterintuitive but effective — it removes pressure and often elicits an honest response. The alternative approach gives the rep another play when email fails.

Example output snippet:

Hi Sarah,

>

Saw that Gartner just published their 2026 Operations Efficiency benchmark — your industry segment was one of the biggest movers. Thought you'd find page 12 relevant to the reconciliation problem we discussed. (Attached the summary.)

>

I know Q2 planning may have shifted your priorities. If the timing isn't right, totally fine to say so — I'd rather know than keep guessing.

>

If it is still on your radar, want to grab 10 minutes next week?

>

Alternative approach: Send a 60-second personalized Loom video walking through how a similar company solved the exact problem Sarah described. Video follow-ups have significantly higher engagement than text for stalled deals.

Quick Tips for Sales Outreach Prompts

• Input your research, not just the ask. The prompt is only as good as the context you provide about the prospect. Two minutes of LinkedIn research before writing the prompt makes the output dramatically better.
• Keep emails short. Add a word count to every email prompt. The ideal cold email is under 100 words. The ideal follow-up is under 80. If the AI writes more, the email is too long.
• Include what NOT to say. Sales cliches ("synergy," "touch base," "loop back") trigger the delete reflex. Ban them explicitly.
• Write for mobile. Most business emails are read on phones. Short paragraphs, no formatting-heavy layouts, and a CTA that's visible without scrolling.
• Test subject lines separately. Run a separate prompt: "Generate 10 subject line variations for this email — under 6 words each, no clickbait" and pick the best one.

When to Use Templates vs. Write From Scratch

Use these patterns when:

• You're doing high-volume outreach and need a consistent quality baseline
• You're onboarding new reps who need frameworks for common sales situations
• You're stuck on a specific email and need a structural starting point

Write from scratch when:

• The deal is strategic and high-value enough to justify fully custom communication
• You have a deep personal relationship with the prospect that makes templates feel inauthentic
• The situation is genuinely novel (company crisis, unexpected competitor move, major industry shift)

For sales teams that scale outreach, SurePrompts' Template Builder lets you save these patterns with your product details, proof points, and voice pre-filled — so each rep can personalize quickly without starting from a blank prompt.