Generate reusable email templates for common sales scenarios — discovery call invites, demo follow-ups, objection handling, proposal intros, and closing emails. Each template includes subject lines, personalization guidance, tone notes, and tactical advice for different buyer personas. Templates are designed to work across multiple messages without requiring heavy customization, while still leaving room for personalization that matters. Works standalone from sales experience and best practices; becomes richer when grounded in what actually works from Harmony conversation data (successful sales calls, patterns in reply rates).
When to Use
Building a sales email template library for your team
Creating templates for a new sales motion or persona
Scaling outreach — you've found a winning email format and want to make it repeatable
Improving reply rates — analyzing what worked in past emails and turning it into a template
Coaching new reps — templates codify best practices so junior reps follow the same patterns as top performers
Instructions
相關技能
1. Define the scenario and persona
Ask what the user needs:
What sales scenario? Discovery call invite, demo follow-up, objection response, etc.
What persona? Title, seniority, company size, industry
What's the ask? Meeting, demo, reply, intro
What's the relationship? Cold, warm intro, existing conversation
Key context? Product, ICP, proof points, common objections
If Harmony conversation data exists, pull:
Successful emails from past deals with this persona (extract tone, structure, proof points)
Which openings and CTAs got replies (subject lines, personalization angles)
Common objections this persona raises and how top reps handle them
Patterns in what convinced this persona to move forward
Created 2026-03-22 · Expected reply rate: 15–20% (warm relationship)
Scenario Summary
Use case: Follow-up after a discovery call to reinforce value, move toward next step
Best for: CFO / VP Finance / Finance Director at mid-market SaaS (Series B–D, $50–300M ARR)
Goal: Confirm interest, lock in next meeting (demo or technical deep-dive)
Timing: 2–5 days after discovery call
Template
Subject line:
next steps
Alternative subjects:
[Specific problem mentioned] → approach
timeline for [solution area]
quick follow-up from our call
Body:
Hi [Name],
Really enjoyed our call last week. The [specific challenge] you mentioned is something we see a lot at [similar company size/industry], and it usually surfaces when [underlying reason from call].
A few things resonated:
Your team's pushing to [specific goal they mentioned]
Today you're spending [time or cost impact] on [current approach]
You'd ideally want [outcome they described]
I put together a quick outline of how we'd approach this for you — basically [1-sentence core value]. I'll send it as a separate note, but wanted to check: does next Tuesday or Wednesday work for a 20-minute technical deep-dive? [SE name] would join to walk through the specifics.
If neither works, happy to find another time.
Personalization Guidance
Placeholder
What goes here
How to find it
Example
[Name]
First name of CFO
Call notes
"Sarah"
[Specific challenge]
Exact pain they mentioned verbatim
Call transcript or notes
"Expense reporting takes way too long"
[Similar company size/industry]
Comparable account
CRM or mental model
"mid-market fintech"
[Specific goal]
What they want to achieve, their words
Call notes
"cut finance ops headcount"
[Time or cost impact]
Quantified pain if mentioned
Call notes or estimate
"12 hours per week" or "$400K/year in FTE cost"
[Current approach]
How they solve it today
Call notes
"manual spreadsheet and 3 tools"
[Outcome they described]
What success looks like, their words
Call notes
"one system that talks to our ERP"
[1-sentence core value]
Your value prop in their language
Sales playbook
"Single expense system that syncs directly to your GL"
[SE name]
Sales engineer who will do the technical deep-dive
Deal team
"Mike"
Tactical Notes
Best send time: 2–3 days after discovery call (while they still remember the call); early morning (9–11am their time) on Tuesday–Thursday
Email length: 90–110 words (short, respectful of their time as CFO)
Tone: Peer-level, helpful, not pushy. Shows you listened (repeats their challenges back). Makes the next step easy (just confirm yes/no on times).
Expected performance: 15–20% reply rate (warm relationship after discovery); 35–40% open rate
Pair with: If no reply after 5 days, send a brief check-in with a single alternative time
When to Use This Template
✓ 2–5 days after a discovery call
✓ When they showed interest on the call
✓ When you have specific notes on their challenges and goals
✗ Do NOT use if they said "we're not interested" or "send me info"
✗ Do NOT use if you don't have a specific next step (demo, technical review)
Common Variations
Variation 1 — VP Finance (Director level, more tactical):
Hi [Name],
Loved our conversation last week about [problem]. The [specific pain] you described is a classic pattern we see, especially at companies in [growth stage/industry] like yours.
You mentioned three priorities:
[Priority 1]
[Priority 2]
[Priority 3]
Here's the approach we'd take: [2–3 sentence explanation of how you solve it].
Quick question: which of those three is causing the most friction right now? And does the approach resonate, or should we think about it differently?
Happy to do a 20-minute technical walkthrough with [SE name] if it makes sense.
[Mutual contact] mentioned I should reach out — great to hear you had a solid conversation about [topic] last week.
Quick context: we help companies like [similar company] solve [problem]. The pattern we see is [insight from their situation], and the outcome is usually [result].
[Mutual contact] thought you should see how we'd approach [their specific challenge]. Would Tuesday or Wednesday work for a brief technical deep-dive?
Reply Handling
If they say "Yes, let's do Tuesday":
Send: "Perfect. Tuesday at [time] — I'll send a calendar invite. Here's what we'll cover: [1. Specific tech question], [2. Implementation approach], [3. Next steps if it makes sense]."
If they ask "What's the cost?":
Send: "Great question. Pricing depends on [your variable], but for a company your size with [specific need], it's typically [range]. Happy to get more specific once we understand your exact use case better. Still good for Tuesday?"
If they say "We're currently evaluating [competitor]":
Send: "Good context. We'd approach this differently because [specific differentiation]. Most of the clients we work with started evaluating [competitor] too, but they chose us because [reason]. Worth a 20-minute look to see if it applies to you?"
If no reply after 5 days:
Send: "Quick follow-up — wanted to check if Tuesday or Wednesday still works, or should we find another time? No worries if it's not a priority right now."
Edge Cases
You don't have detailed call notes: Use generic personalization placeholders but note that the template is weaker. Recommend recording calls in Harmony so you can extract exact language.
They said "interesting" but no clear next step on the call: Use softer language ("worth exploring together?") instead of confident next-step proposal.
Very formal, slow-moving organization: Extend email slightly, be more explicit about the process (discovery → technical review → proposal → negotiation).
They preferred email over calls: Skip the "let's schedule" request; instead ask "Does this direction make sense?"
Performance Tracking
Use this template for 10 outreach emails:
Track: Open rate (target: 35–40%), Reply rate (target: 15–20%), Meeting rate (target: 60–70% of replies)
If open rate is low: Subject line or sender reputation is an issue. Try alternative subjects.
If open rate is high but reply rate is low: Email content might feel generic. Increase personalization specificity.
If reply rate is high but meeting rate is low: Next step might be too specific or inconvenient. Try "worth a conversation?" instead of a specific time.