Follow-up email after a demo: templates

The demo follow-up is where deals quietly stall. This template restates their problem in their words, links each thing you showed to it, and confirms the next step with a date. If the buyer has to convince someone else, the internal-champion version gives them a paragraph they can forward as-is.

Template;sl-postdemo

Hi First name, Thanks for the time today. What I heard: Their problem in their words. What we looked at: - Feature 1, for Why it matters 1 - Feature 2, for Why it matters 2 Next step, as agreed: Next step by Date in 7 days. I'll send the invite. Anything I missed? ;sig-work

Then type ;sl-postdemo in any app.

Variations

The same message for a different channel or tone. Copy the one that fits.

When the demo was informal and a full recap would feel heavy.

Short

Hi First name, thanks for today. As promised, here's the recording: Clipboard Next step is Next step. Does Date in 3 days still work on your side?

When your contact has to get approval. Gives them a forwardable summary.

For their boss

Hi First name, Thanks for today. Since you mentioned running this past Decision maker, here's a short summary you can forward: "We looked at [Your product] to fix Their problem in their words. It would let us Outcome. Rollout takes about Rollout time, and the cost is Price." Happy to join a call with Decision maker if questions come up. ;sig-work

When to use it

Same day as the demo, ideally within a couple of hours.
You agreed a next step on the call and want it in writing.
Your contact needs to sell the decision to someone who wasn't there.

What to avoid

Don't list every feature you clicked on. Two or three that matter to them is enough.
Don't leave the next step vague ("let me know your thoughts"). Name it and date it.
Don't attach the full product deck unless they asked for it.

The fields in this template

Retext fills these in when the snippet expands. In plain text they become [brackets] to replace by hand.

First name{fill:First name}: Your main contact's first name.
Their problem in their words{fill:Their problem in their words}: Quote or closely paraphrase how they described the problem on the call.
Feature 1{fill:Feature 1}: The first thing you showed that mattered to them.
Why it matters 1{fill:Why it matters 1}: Why it matters for their problem, in one phrase.
Feature 2{fill:Feature 2}: The second thing you showed.
Why it matters 2{fill:Why it matters 2}: Why that one matters.
Cursor{cursor}: Where your cursor lands after the snippet expands, so you can start typing the personal part straight away.
Next step{fill:Next step}: The step you both agreed, e.g. "a trial with two team leads".
Date in 7 days{date+7}: Inserts the date 7 days from today, worked out when the snippet expands. Useful for deadlines and return dates.
;sig-work{snippet:sig-work}: Pulls in your ;sig-work snippet, so a change to that snippet updates every reply that uses it. Create a snippet with that trigger first (any template in the email signatures pack works), or the field stays as typed.
Clipboard{clipboard}: Pastes whatever you last copied, such as an order number or a link, into that spot.
Date in 3 days{date+3}: Inserts the date 3 days from today, worked out when the snippet expands. Useful for deadlines and return dates.
Decision maker{fill:Decision maker}: The person who signs off, by first name or title.
Outcome{fill:Outcome}: What changes for them, e.g. "answer tickets in one place".
Rollout time{fill:Rollout time}: A realistic setup time, e.g. "two weeks".
Price{fill:Price}: The price you discussed.

More about dynamic fields

Tips

•Write "their problem in their words" from your call notes. Hearing their own phrasing back is what makes the email feel personal.
•{date+7} keeps the follow-up date right without checking a calendar. Change the number if your next steps usually run longer.
•Copy the recording link before you type ;sl-postdemo in the short version and {clipboard} fills it in.

Works in Gmail, Outlook, HubSpot, Salesforce and every other app

Retext types the snippet wherever your cursor is. To use a different version in one app, give it the same trigger and limit it to that app with per-app snippets. They go by app, not website, so every tab in your browser counts as one app.

Use it with your team

Managers can check in the CRM whether reps are sending a post-demo follow-up at all. A shared template makes "same-day follow-up" a habit rather than a rule people forget.

See Retext for Teams

Questions

When should I send a follow-up after a demo?

The same day, while the call is fresh for both of you. A follow-up sent a day or two later reads as an afterthought.

What should a post-demo email include?

Their problem in their own words, the two or three things you showed that address it, and the agreed next step with a date. Anything more belongs in an attachment they asked for.

How do I help my contact get internal approval?

Give them a short paragraph they can forward without editing: the problem, the outcome, the rollout time and the cost. The champion variant of this template is written for exactly that.

Related templates

Post-call recap

;sl-recap

Sales

Hi [First name], Quick recap of today's call so we're on the same page. Decided: - [Decision] Still open: - [Open questi…

Pricing proposal email

;sl-proposal

Sales

Hi [First name], As promised, here's the proposal for [Company]. Total: [Price] per [Billing period], for [Seats or scop…

Sales follow-up (no reply)

;sl-nudge

Sales

Hi [First name], Checking in on [Next step]. Is it still on the cards for this month, or has something else jumped the q…

All sales templates Browse every snippet pack

Type ;sl-postdemo, get the whole reply

Retext expands your snippets in every Mac app and fills in names, dates and order numbers for you.

Download Retext free Retext for Teams

Free to start. No account required on the Mac.