---
name: post-demo-followup
slug: post-demo-followup
description: This skill should be used when the user asks to "write a post-demo follow-up email", "design a post-demo sequence", "follow up after a demo", "create post-demo email templates", "build a follow-up cadence after demo", "write a demo recap email", "design post-meeting follow-up", "create a post-discovery follow-up", "write demo follow-up emails", or any variation of designing follow-up emails and sequences after a B2B SaaS demo or discovery call.
category: general
---

# Post-Demo Follow-Up

The post-demo follow-up determines whether a demo turns into a deal or a dead contact. 80% of deals require 5+ follow-up touches after the initial meeting. But most reps send one "thanks for your time" email and wait. The follow-up sequence should advance the deal, not just acknowledge the meeting happened.

The principle: the follow-up email is not a recap. It's a next-step accelerator. Every email should make it easier for the prospect to take the next action: share internally, loop in their boss, start a trial, or schedule the next meeting.

## The 2-Hour Rule

Send the post-demo follow-up within 2 hours of the meeting ending. Not tomorrow. Not "when I get back to my desk." Within 2 hours.

| Timing | Impact | What the prospect is doing |
|--------|--------|---------------------------|
| Within 1 hour | Best. Prospect still has the demo fresh in mind | Processing what they saw. Might mention it to a colleague right now |
| 1-2 hours | Strong. Still same-day. Context is fresh | Back in meetings but demo is still recent |
| Same day (2-6 hours) | Acceptable. Still the day they saw the demo | End of day. May forward to a colleague before leaving |
| Next day | Declining. Demo is yesterday's news | New priorities. Demo competes with 20 other things from today |
| 2+ days later | Weak. Context is mostly lost | "What demo? Oh right, that thing" |

---

## The 4-Email Post-Demo Sequence

| Email | Name | Timing | Purpose | Who sends |
|-------|------|--------|---------|-----------|
| 1 | Demo recap + next step | Within 2 hours | Summarize key points. Confirm next step. Make internal sharing easy | AE |
| 2 | Value reinforcement | Day 3 | Send a resource that reinforces the #1 pain point discussed | AE |
| 3 | Stakeholder enablement | Day 6 | Help the champion sell internally | AE |
| 4 | Next-step check | Day 10 | Confirm timeline. Surface blockers | AE |

---

## Email 1: Demo Recap + Next Step (Within 2 Hours)

This is the most important follow-up email in the entire sales cycle. It sets the tone, confirms alignment, and creates a forwardable document the champion can share internally.

### Structure

```
Subject: {company} + {your_company} next steps

{first_name}, thanks for the time today. Quick recap and
next steps:

**What we covered:**
- {Pain point 1 they described, in their words}
- {How your product addresses it, 1 sentence}
- {Pain point 2, if discussed}
- {How your product addresses it, 1 sentence}

**What stood out:**
- {The feature or capability they reacted most positively to}
- {The specific outcome or metric that resonated}

**Next steps:**
- {Next step you agreed to, with specific date if possible}
  Example: "I'll send the security questionnaire by Thursday"
  Example: "You'll loop in {stakeholder name} for a follow-up next week"
- {Your action item, with deadline}
  Example: "I'll put together pricing options and send by Friday"

**Resources:**
- {Recording link, if you recorded the demo}
- {Relevant case study matching their use case}
- {Product one-pager or overview doc}

Let me know if I missed anything or if you have questions.

{rep_name}
```

### Email 1 rules

- **Use bullet points, not paragraphs.** The prospect will scan, not read. Bullets are scannable. Paragraphs are not
- **Describe their pain in their words.** If they said "our SDRs waste half their day on research," write that. Don't translate it into your marketing language ("manual prospecting inefficiency")
- **Include specific next steps with dates.** "Let's reconnect next week" is vague. "I'll send pricing by Friday. Want to schedule a follow-up for Tuesday to review with your VP?" is actionable
- **Make the email forwardable.** The champion will forward this to their boss, their technical evaluator, or their team. It should read as a professional summary, not an internal sales email. No pitchy language. No "just following up"
- **Attach or link the recording.** If the demo was recorded, include the link. This is the single most valuable asset for internal selling. The champion can share the recording instead of explaining the demo themselves
- **Include one relevant case study.** Match the case study to their use case, not your most impressive logo. A case study from a similar-sized company in their vertical matters more than a Fortune 500 name
- **Don't CC anyone who wasn't on the call.** Sending the recap to 5 people the prospect hasn't met is aggressive. Send to the attendees. Let the champion decide who else to share it with

### Subject line for Email 1

Use `{their_company} + {your_company} next steps` or `{their_company} demo recap`. Keep it findable. The prospect will search for this email later.

---

## Email 2: Value Reinforcement (Day 3)

**Purpose:** Reinforce the #1 pain point from the demo with a proof point they haven't seen. This email keeps the conversation alive without asking for anything.

### Structure

```
Subject: {topic from demo}

{first_name}, one thing that stuck with me from our
conversation: {their specific pain point or question}.

{Peer company} had the same challenge. {One sentence on what
they did}. They saw {specific result with a number}.

Full story here if useful: {link to case study or blog post}

{If next step is pending: "Looking forward to {next step}
on {date}."}

{rep_name}
```

### Email 2 rules

- **Don't recap the demo again.** Email 1 did that. Email 2 adds new value
- **Pick the #1 pain point, not all of them.** The prospect mentioned 3 problems. Pick the one they reacted most strongly to. Depth beats breadth
- **The proof point must be new.** If you included a case study in Email 1, use a different one here. Or use a data point, a blog post, or a peer example that wasn't in the demo
- **No ask in Email 2.** Don't ask for a meeting. Don't ask "where does this stand." Just deliver value. The ask comes in Email 3 or 4
- **Reference the agreed next step.** A casual reminder: "Looking forward to connecting Tuesday" keeps the timeline alive without being pushy

---

## Email 3: Stakeholder Enablement (Day 6)

**Purpose:** Help the champion sell internally. Most deals stall because the champion can't articulate the value to their boss, their technical team, or their procurement committee. Give them the tools to do it.

### Structure

```
Subject: sharing with your team

{first_name}, in case it's helpful as you discuss this
internally:

**For {economic_buyer_title}:**
Here's a one-pager on the business case: {link}
Key takeaway: {one sentence on ROI or business outcome}

**For {technical_evaluator_title}:**
Technical overview and integration docs: {link}
Security questionnaire (pre-filled): {link}

**For your team:**
Demo recording: {link}
Product overview: {link}

Happy to jump on a quick call with {stakeholder name} if
that would help move things along. No pressure either way.

{rep_name}
```

### Email 3 rules

- **Segment materials by stakeholder role.** The VP cares about ROI. The engineer cares about integration. The end user cares about ease of use. Provide each with the right document
- **Pre-fill what you can.** A security questionnaire that's already filled out saves the technical evaluator 2 hours. That's a tangible gift that accelerates the deal
- **Offer to meet the stakeholder directly.** "Happy to jump on a call with your VP" reduces the burden on the champion. They don't have to play telephone between you and their boss
- **This email is the champion's internal selling toolkit.** Every link should be something they can forward directly to the relevant person. No login required. No gated content. Direct links to PDFs, recordings, and docs
- **Label stakeholder materials explicitly.** "For your VP" and "For your engineering team" makes it scannable. The champion can copy-paste the relevant section into a separate email to each stakeholder

---

## Email 4: Next-Step Check (Day 10)

**Purpose:** Surface blockers. Confirm timeline. If the deal is moving, great. If it's stalling, find out why now, not in 3 weeks.

### Structure (if next step was agreed to)

```
Subject: re: {original subject thread}

{first_name}, checking in on {agreed next step}. Are we still
on track for {date/action}?

If anything's changed or you need more from my end, happy to
help. {One specific offer: "I can put together custom pricing
for your team size" or "I can do a technical deep-dive with
your engineering lead."}

{rep_name}
```

### Structure (if no clear next step was agreed to)

```
Subject: re: {original subject thread}

{first_name}, wanted to check back after our demo last week.

Where does this sit for your team? A few options depending on
where you are:

1. **Ready to move forward:** I can send over pricing and a
   proposed timeline
2. **Need more info:** Happy to do a deeper dive on {specific
   area they were most interested in}
3. **Timing's off:** No problem. I'll check back in {timeframe}

{rep_name}
```

### Email 4 rules

- **Reply in the original thread.** Don't start a new email thread. Reply to Email 1 so the full context (recap, resources, stakeholder materials) is visible below
- **Offer specific options, not open-ended questions.** "Where does this stand?" puts the burden on the prospect to figure out the answer. Three options with clear next steps per option makes it easy to respond
- **Include one specific offer of help.** Not "let me know how I can help" (vague). "I can put together a custom ROI analysis for your VP" (specific and valuable)
- **This is not a guilt email.** No "I haven't heard back." No "Just wanted to follow up." No "Bumping this up." Ask about the next step or offer value. Nothing else
- **If no response to Email 4:** Wait 7 days, then send a clean breakup: "Should I close the loop on this, or does it make sense to revisit in a few months?" (see cold-outbound-email-writing skill for breakup email rules)

---

## Post-Demo Follow-Up by Meeting Type

Different meeting types require different follow-ups.

### Discovery call follow-up

| Difference from demo follow-up | How to adjust |
|-------------------------------|---------------|
| No product was shown. Just a conversation about pain | Recap section focuses on problems discussed, not features shown |
| Next step is usually a demo | CTA: "Based on what you shared, I'd love to show you how we handle {specific problem}. Here are a few times for a demo" |
| Lighter resource package | One relevant case study. No need for technical docs yet |
| Shorter email | 60-80 words. Discovery recaps should be concise |

### Technical evaluation follow-up

| Difference from demo follow-up | How to adjust |
|-------------------------------|---------------|
| Audience is engineering/IT, not business | Lead with technical resources: API docs, integration guides, architecture diagrams |
| Questions are about "can it do X" not "should we buy" | Address every technical question raised. If you said "I'll get back to you on that," get back to them now |
| Next step is usually a POC or sandbox access | CTA: "Want me to set up a sandbox so your team can test the integration?" |
| Security/compliance materials | Include SOC 2 report, DPA, security questionnaire proactively |

### Executive meeting follow-up

| Difference from demo follow-up | How to adjust |
|-------------------------------|---------------|
| Audience is VP/C-level | Lead with business outcomes, not features. ROI, competitive risk, strategic alignment |
| Shorter. Executives don't read long emails | 50-70 words max. Bullet points only. One attachment at most |
| Next step is usually a decision or a delegate | CTA: "Who should I work with on the technical and commercial details?" |
| Tone is peer-to-peer | Less formal. No "Dear [name]." Just "{first_name}," |

### Multi-stakeholder meeting follow-up

| Difference from demo follow-up | How to adjust |
|-------------------------------|---------------|
| Multiple people on the call with different concerns | Send one recap email to all attendees. Address each person's concern in a separate bullet |
| Different next steps per person | "Next steps: {name_1} will review the integration docs. {name_2} and I will reconnect on pricing. {name_3} will share this with the team." |
| Follow-up with the champion separately | Send the group recap. Then send a separate 1:1 to the champion: "How do you think that went? Anything I should know about {stakeholder}'s reaction?" |

---

## What to Include in the Follow-Up Package

### Tier by deal stage

| Deal stage | Include | Don't include yet |
|-----------|---------|------------------|
| Post-discovery (no demo yet) | Relevant case study, company overview one-pager | Pricing, security docs, technical specs |
| Post-demo | Demo recording, case study, product overview, pricing preview (if discussed) | Contract, MSA, detailed technical specs (unless asked) |
| Post-technical evaluation | API docs, integration guide, security questionnaire, sandbox access | Unless they asked for it |
| Post-executive meeting | ROI one-pager, executive brief, customer reference list | Detailed technical docs (wrong audience) |

### Resource rules

- **Never send pricing without context.** A pricing PDF forwarded without the "here's how we'd structure it for your team" conversation gets evaluated on price alone. Send pricing with a personalized note explaining the recommendation
- **Include only what's relevant to their use case.** A 40-page product guide is overwhelming. A 2-page overview tailored to their specific use case is useful. Curate, don't dump
- **Make every document shareable.** No login walls. No "request access." Direct PDF links or public URLs. The champion needs to forward these to 3 people who've never heard of you
- **Label each resource.** "ROI Calculator for {Company}" not "Sales_Doc_v3_Final_FINAL.pdf." Professionalism in document naming signals professionalism in everything else

---

## Stalled Deal Recovery

When a post-demo deal goes silent (no response to Emails 1-4), run a stalled deal recovery sequence.

### Recovery sequence

| Touch | Timing | Channel | Content |
|-------|--------|---------|---------|
| 1 | Day 14 (4 days after Email 4) | Email | New angle: share a new resource or a recent customer win relevant to their use case |
| 2 | Day 17 | LinkedIn | Engage with their recent post. Don't pitch. Just be visible |
| 3 | Day 21 | Email | Clean breakup: "Should I close the loop, or does it make sense to revisit next quarter?" |
| 4 | Day 21 | Phone | One call attempt. Reference the breakup email. Leave a 20-second voicemail if no answer |

### Recovery rules

- Don't restart from scratch. Reference the demo and the recap. "Picking up from our conversation on {date}" not "I'd love to tell you about our product"
- The breakup email is your strongest recovery tool. Loss aversion drives responses. "Should I close the loop?" gets a response 15-20% of the time
- If the breakup gets no response, STOP. Move the deal to "Closed Lost - No Response." Add to quarterly re-engagement. Don't keep chasing. 4 post-demo emails + 4 recovery touches = 8 touches. That's enough
- Log the stall reason in CRM. Was it timing? Budget? Lost to competitor? No response at all? This data informs pipeline forecasting and identifies deal-stage conversion problems

---

## Measurement

| Metric | Definition | Target | Frequency |
|--------|-----------|--------|-----------|
| Follow-up speed | Time from demo end to Email 1 sent | < 2 hours | Per demo |
| Email 1 open rate | Opens on recap email | > 80% | Monthly |
| Email 1 reply rate | Replies to recap email | > 30% | Monthly |
| Next meeting booked rate | % of demos that result in a next meeting | > 60% | Monthly |
| Demo-to-opportunity rate | % of demos that become opportunities | > 50% | Monthly |
| Demo-to-closed-won rate | % of demos that close | 15-25% | Quarterly |
| Stall rate | % of post-demo deals with no response after 4 emails | < 30% | Monthly |
| Recovery rate | % of stalled deals recovered by breakup sequence | 10-20% | Quarterly |

---

## Anti-Pattern Check

- "Thanks for your time today!" with no recap, no next step, no resources. This is the most common follow-up email and it's useless. It acknowledges the meeting happened and does nothing to advance the deal. Include a recap, next steps, and resources
- Follow-up sent the next day. The prospect has moved on. Context is fading. Send within 2 hours. Pre-write the template before the demo. Fill in specifics during or immediately after
- Recap uses your marketing language instead of their words. They said "our SDRs waste half their day researching." Don't write "manual prospecting efficiency challenges." Use their exact words. It proves you listened
- CC'ing 5 stakeholders who weren't on the call. The champion controls who sees the recap. Send to attendees only. The champion forwards it when and to whom they choose
- No forwardable materials. The champion needs to sell internally. If the recap email and attachments aren't something they can forward to their VP without embarrassment, the materials are wrong
- All 4 emails say "following up." No new value in any email. Each email must add something: a new proof point, new materials, a new offer. "Just checking in" is not value
- No breakup email when the deal stalls. The AE sends 8 "following up" emails over 6 weeks. The prospect ignores all of them. A clean breakup at Day 21 triggers loss aversion and either gets a response or frees the AE to focus elsewhere
- Sending pricing in Email 1 when it wasn't discussed. If pricing came up in the demo, include a preview. If it didn't, don't introduce it. Let the conversation progress naturally to the pricing stage