What you'll get
- 5 copy-ready blocks
- 6 min read
A follow up email after demo has one job, and it is not gratitude: it is converting what happened in the room into the next movement of the account. These five run in order. Many deals need only the first three; the last two exist for silence, and they work better than the fourth chaser everyone sends instead.
Email 1: The same-day recap (within 24 hours)
Subject: [the problem], where we got to
[First name], three things from today rather than a deck:
1. [Problem owner]'s point that [their words]: noted, and the pilot
design below reflects it.
2. [Evaluator]'s question on [topic]: answer attached, two paragraphs.
3. [Budget holder]'s measure, [the metric]: that becomes the pilot's
success test.
Next step as agreed: [the step] on [date]. Anything I misheard,
say so and I will correct it.No deck, no "great to meet you". The recap proves you listened, in writing the room can forward. If the meeting was transcribed, the transcript to forwardable recap hack produces the neutral version for your champion to send internally; this one goes from you.
Email 2: The stakeholder add (day 2 or 3)
Subject: one page for [missing role]
[First name], [missing person or role] was not in the room, and in my
experience this is where their questions land later. Attached is one
page written for them: [what it costs, how it connects, what the pilot
proves: pick what their role cares about].
Would you pass it on, or would a short call with them directly be
easier? Either works.Every demo has a missing role; the demo script by committee role will have told you which. This email is multithreading with a reason attached.
Email 3: The pilot proposal (once the recap lands)
Subject: the pilot, scoped
[First name], as discussed, a pilot shaped to settle the open question:
What it covers: [one scope line]
What it proves: [budget holder's measure, from the demo]
Who it needs: [names and hours, theirs and yours]
How long: [weeks], starting [date]
What it costs: [the arrangement, or "covered in the attached"]
What happens after: a decision either way, on the numbers above
If the scope is wrong, mark it up. If it is right, shall we hold
[date] for the kick-off?The last line of the scope matters most: a pilot that ends in "a decision either way" is easy to approve, because saying yes to it is not saying yes to everything.
Email 4: The chase that adds something (a week of silence)
Subject: re: the pilot, scoped
[First name], adding one thing since I wrote: [a new fact: a reference
call offer, a peer result, an answer to the evaluator's second
question, a relevant change at their company].
Still make sense to talk this week, or has something shifted on your
side? Both are useful to know.One chase, one new thing, one honest question. "Just bumping this" teaches the buyer your emails can be skipped; a chase that arrives with cargo does not.
Email 5: The honest close (two chases, still silence)
Subject: parking this
[First name], silence usually means priorities moved, which is fair.
I will stop here rather than keep nudging.
If [the problem] comes back onto the list, the pilot scope stands and
so does the [metric] test we agreed. I will check in around [month]
unless I hear sooner.Then do exactly that. The close is not a guilt trip; it is a bookmark. Parked accounts with dates come back; chased accounts change their email filters. The discipline around meeting two itself is the second-meeting plan.
Worked example (illustrative, not a real company)
Dana Whitfield demos to Calder Cold Chain on a Tuesday. Email 1 goes Wednesday morning with the finance lead's pilot measure in it; the champion forwards it unprompted. Email 2 offers a one-pager for the absent IT manager, and the champion asks for the call version instead: a new committee member reached. Email 3 scopes a four-week pilot against the overtime metric. Silence follows; email 4 adds a reference offer from a peer logistics firm and gets a reply in an hour: budget meeting is next month. Email 5 never sends, because the chase learned the real date. All names are invented.
Five mistakes to avoid
- Opening with thanks. Everyone else does; the recap that proves listening is the differentiator in the thread.
- Attaching the full deck. It re-runs the demo badly to people who were there and says nothing to those who were not. The one-pager per role in email 2 travels; the deck sinks.
- Proposing a pilot without a success measure. A pilot that proves nothing specific becomes an unpaid extended trial. The measure came from the budget holder in the room; use their words.
- Chasing with nothing. Each follow-up must carry a fact, an offer or a question that was not in the last one. No cargo, no send.
- Never closing the loop. The fifth email feels like giving up and works like strategy: it is the only message in the sequence that reliably gets a reply from a genuinely stalled buyer.
Why this works on named accounts
Common questions
What should you send after a sales demo?
Within a day, a recap of what each person said with the agreed next step; within three days, something for the stakeholder who was not in the room; then a scoped pilot proposal with a success measure the budget holder named. Gratitude and decks move nothing; the recap, the missing role and the measure do.
How long should you wait before following up after a demo?
The recap goes same day or next morning while the demo is fresh. The pilot proposal follows as soon as the recap is acknowledged. After that, one week of silence earns one chase with something new in it, and a second week earns the honest close with a parking date.
How many follow-up emails are too many?
Five, in this structure: recap, stakeholder add, proposal, one chase, one close. Beyond that you are negotiating with silence. The close with a dated check-in keeps the account alive without another send; replies to it tend to arrive quickly, because it is the first email that is easy to answer.
More from the Academy
Transcript to Forwardable Recap
For sellers who send meeting summaries nobody forwards.
You leave with a prompt that writes the recap for the absent decision makers, a length rule and a check that keeps it true to the transcript.
Second-Meeting Plan
For sellers whose first meetings go well and then go quiet.
You leave with a close for the last five minutes of meeting one, three things to change before meeting two, a 25-minute agenda and an honest parking rule.
Demo Script by Committee Role
For sellers demoing to a mixed room.
You leave with a script in five scenes, one per committee role, the order that keeps everyone awake and the lines that hand the demo back to the audience.
Want this in your inbox?
Optional. We use your email only to send you this, nothing else.