Post-Demo Follow-Up Email Templates

Send within one hour of the demo ending: recap value in the buyer's language, using their words from the call, not your feature names.

Template A: Standard Recap (send within 1 hour, every demo)

Subject: [Company]: recap + next step

``` Hi [Name],

Good talking through this today. Pulling together what you told me so it's in one place for you and the team:

You're dealing with [specific pain, in their words]. Right now that's costing you [specific consequence they named: time, money, risk].

What we showed you does three things about that:

1. [Scene 1 outcome, tied to their pain, not the feature name]
2. [Scene 2 outcome]
3. [Scene 3 outcome]

You asked about [specific question they raised], the short answer is [one-line answer]. Happy to go deeper on that whenever useful.

Next step: [specific action], [specific date/time if already agreed, or a concrete ask: "does Thursday at 2pm work for a 20-min follow-up with [stakeholder]?"]

[Rep name] ```

Template B: Multi-Stakeholder / Forward-to-Team Version

Subject: [Company] demo recap: for the wider team

``` Hi [Name],

Since [absent stakeholder(s)] couldn't join today, here's a version you can forward straight to them.

Context: [Company] is looking at [Product] to solve [pain], specifically around [specific process/team affected].

What we covered:

• [Outcome 1]
• [Outcome 2]
• [Outcome 3]

For [absent stakeholder]'s specific concern about [their likely angle, security/budget/workflow]: [one paragraph addressing it directly].

Recording of the session (if useful to forward instead): [link]

Next step: [specific action + date]

[Rep name] ```

Template C: Technical Buyer Follow-Up

Subject: [Company]: technical details from today

``` Hi [Name],

Following up on the technical questions from today's session:

• Integration with [their stack]: [answer]
• Security/compliance (SOC 2, data residency, etc.): [answer + doc link]
• API/rate limits/uptime SLA: [answer + doc link]
• Implementation timeline for a team your size: [typical range]

Attached: [security overview / API docs / architecture diagram]

Happy to get your engineering lead on a call directly if that's faster than routing through me, just say the word.

Next step: [specific action + date]

[Rep name] ```

Template D: Economic Buyer / ROI Follow-Up

Subject: [Company]: the numbers from today

``` Hi [Name],

Quick summary with the numbers in view, since that's what matters most on your end:

Current cost of the problem: [their stated cost/time/risk, quantified] Estimated impact of fixing it: [quantified estimate based on what they shared: be conservative, cite the method] Comparable result: [Customer], similar size/industry: [specific metric, verbatim quote if available]

Investment: [pricing tier discussed], payback period at your numbers is roughly [X months].

Next step: [specific action + date, e.g., "a short call with finance to walk through the ROI model together"]

[Rep name] ```

Template E: No Clear Next Step Yet (use only if the demo ended without one)

Subject: [Company]: one thing before you go

``` Hi [Name],

Realized we didn't nail down a specific next step at the end there, my fault for not pinning it down live.

Based on what you said about [priority/timeline], does it make sense to [specific concrete suggestion, e.g., "get [stakeholder] on a 15-min call this week"] or would [alternative] be more useful right now?

Either way, no pressure, just want to make sure this doesn't stall on my end.

[Rep name] ```