You ran a great demo. Everyone nodded, someone asked about pricing, and the call ended with "this looks really interesting." Then: silence. The follow-up email is where demos either turn into deals or quietly die, and most follow-ups die because they say "just checking in" and give the buyer nothing to act on.
Below are seven templates you can copy today, ordered by when you'd use them in a deal. After the templates: the timing rules, the elements every demo follow-up needs, and the mistakes that get you archived.
The golden rule: send it within 24 hours
Send your recap while the demo is still fresh, ideally the same day. Every day you wait, the details blur, competing priorities take over, and your champion has less material to work with internally. If you demo in the morning, the follow-up goes out that afternoon.
Template 1: The same-day recap
Use this after every demo, no exceptions. Its job is to confirm what they cared about, restate value in their words, and lock in the next step.
Subject: Recap + next steps from today's demo
Hi {{FirstName}},
Thanks for the time today. Quick recap so we're on the same page:
What you're solving: {{their problem, in the words they used}}
What resonated:
- {{feature or workflow they reacted to}} and how it handles {{their specific use case}}
- {{second point, e.g. "the reporting your VP asked about"}}
Open questions: {{question they raised}}. Short answer: {{answer or "I'm confirming with our team and will have it for you by Thursday"}}.
Next step: you mentioned looping in {{colleague}}. Does {{day/time}} work for a 30-minute session focused on {{their area}}?
{{YourName}}
The recap works because it does the buyer's internal summary for them. When they forward it to their boss, your framing travels with it.
Template 2: The multi-stakeholder recap
Use this when several people attended and each cared about something different. Generic recaps flatten the demo; this one gives each person their own line, which matters in deals with a real buying committee.
Subject: Demo recap: what matters for each of you
Hi all,
Great questions today. Since you each look at this from a different angle, here's the short version per area:
{{Name, role}}: {{the thing they asked about}} works like {{one-sentence answer}}. Docs here: {{link}}.
{{Name, role}}: on {{their concern, e.g. security review}}, here's our {{SOC 2 report / security page}}: {{link}}.
{{Name, role}}: the {{workflow}} you wanted to see again, 2-minute clip: {{link}}.
Suggested next step: {{a working session / pilot scope call}} on {{date}}. Who else should be there?
{{YourName}}
Template 3: The forwardable email for your champion
Use this when your contact loves the product but has to sell it internally. Don't make them write the pitch; write it for them. This is the core of champion enablement: your champion forwards it to the decision-maker as-is.
Subject: The summary you can forward
Hi {{FirstName}},
You mentioned you'd be presenting this to {{decision-maker}}. To save you time, here's a summary written so you can forward it directly:
What it is: {{product}} helps {{team}} {{outcome}} by {{mechanism, one sentence}}.
Why now: we currently {{cost of the status quo: hours lost, deals slipping, tool sprawl}}.
What it would cost: {{price range}}, which pays back if it {{simple ROI statement}}.
Risk: {{trial/pilot terms}}, so we can validate before committing.
Happy to join the conversation with {{decision-maker}} if useful, or adjust any of this to match how you'd frame it.
{{YourName}}
Template 4: The no-response bump
Use this 3 to 4 business days after the recap if you've heard nothing. The mistake here is "just checking in", which adds zero value. Always attach a reason to reply.
Subject: Re: Recap + next steps from today's demo
Hi {{FirstName}},
One thing I forgot to mention: {{new piece of value, e.g. "the integration you asked about ships next month" or "here's how {{similar company}} handled the exact rollout concern you raised"}}.
Still happy to set up the session with {{colleague}}. Would {{two concrete time options}} work?
{{YourName}}
Template 5: The resource drop
Use this when a specific question or objection came up that you couldn't fully answer live. Answering it precisely, quickly, and in writing is one of the strongest trust signals you can send.
Subject: The answer to your {{topic}} question
Hi {{FirstName}},
You asked whether {{their question}}. Confirmed with our team: {{clear answer}}.
Two things that back this up:
- {{case study or doc}}: {{link}}, see the section on {{relevant part}}
- {{short customer proof point with a number}}
Does this resolve it, or is there a scenario I should dig into further?
{{YourName}}
Template 6: The pricing and next-steps push
Use this when the demo went well and pricing came up. Don't bury the number; buyers who asked want to anchor internally, and vagueness reads as expensive.
Subject: Pricing + a plan to get you live
Hi {{FirstName}},
As promised, pricing for your team of {{size}}: {{clear price or range, with what's included}}.
If you decide to move forward, here's what the path looks like:
- {{Week 1: kickoff and setup}}
- {{Week 2: your data/workflows in, team onboarded}}
- {{Week 3: live, first results}}
If it helps to align everyone on this, I can put it into a shared plan with owners and dates. Want me to draft that?
{{YourName}}
That shared plan is a real thing, not a figure of speech: a mutual action plan turns "sounds good" into committed steps on both sides.
Template 7: The break-up email
Use this after two or three unanswered follow-ups. It either revives the deal or gives you a clean close, and it gets replies surprisingly often.
Subject: Should I close the file?
Hi {{FirstName}},
I haven't heard back, which usually means one of three things: the timing is wrong, priorities changed, or my emails are landing in a folder you never open.
If it's timing, no problem. Tell me when to circle back and I will.
If this is dead, that's genuinely fine too. A quick "not now" and I'll stop filling your inbox.
{{YourName}}
The key elements of a demo follow-up email
Every template above is built from the same six parts:
- A specific subject line. "Recap + next steps" beats "Great meeting you!" because it tells them what's inside.
- Personalization that proves you listened. Reference their words, their use case, their colleague's question. One specific detail outperforms three paragraphs of enthusiasm.
- A recap in their language. Restate the problem the way they described it, not the way your marketing site does.
- Answers to open questions. Anything unresolved from the demo gets answered or given a deadline.
- One clear call to action. One next step, with concrete times. Two CTAs means no CTA.
- Proof. A case study, a number, a doc link. Something forwardable that doesn't depend on you being in the room.
Mistakes that kill demo follow-ups
- "Just checking in." No new information, no reason to reply. Every touch needs to add something.
- The essay. If the email needs scrolling, the recap becomes homework. Keep it under 150 words where you can; push depth into links.
- One email for five stakeholders. Different roles bought into different things. Flatten the message and you flatten the interest (see Template 2).
- Attachment soup. Four PDFs and a deck get skimmed once, then lost in the thread. This is exactly what a digital sales room fixes: one link that holds the recap, the demo recording, pricing, and security docs, so the buyer's whole committee finds everything in one place and you see who actually opened what.
- Giving up after one email. Most replies come from follow-ups two through four. Persistent and useful beats persistent and annoying, and the templates above keep you on the useful side.
FAQ
How soon after a demo should I send the follow-up? Within 24 hours, same day if you can. The recap is most valuable while the demo is fresh.
How many times should I follow up? Three to five touches over two to three weeks is normal for B2B deals: recap, bump, resource drop, then the break-up email. Space them 3 to 5 business days apart.
What if they asked for pricing but I need approval to share it? Say exactly that, with a date: "Pricing needs a quick internal sign-off; you'll have it by Thursday." A concrete deadline beats a vague "soon" every time.
Can I automate demo follow-ups? Automate the scheduling, not the substance. Sequence tools are fine for the bump and break-up, but the recap must be written from your notes, because its whole value is specificity. If you want reusable structure, keep a personal template library, and see our stakeholder email templates for the surrounding touches (intro, security review, procurement).
Turn the follow-up into a place, not a thread
Email threads decay: attachments get buried, new stakeholders miss context, and you never know what was read. The strongest teams follow up with a single living link where the recap, recording, pricing, and plan live together and every stakeholder sees the version meant for them. That's what demoshake does; the follow-up becomes a deal room the buying committee actually returns to, and you see exactly which stakeholder engaged with what.
Before the next demo, it's worth tightening the front end too: our demo preparation guide covers the discovery that makes these follow-ups easy to write, because a good recap is mostly a product of having listened well.