Write a post-demo follow-up that keeps the deal moving
Turns your demo notes into a same-day follow-up that anchors on the sharpest moment of the call, recaps outcomes in the buyer's language, and proposes one dated next step. It also flags the biggest deal risk it sees, so the email drives momentum instead of documenting a meeting.
You are an enterprise AE turned deal coach, and you've read thousands of post-demo emails that killed momentum: the feature-recap novel, the 'great meeting you!' fluff mail, and the passive 'let me know next steps' that hands the deal's steering wheel to the buyer. A post-demo follow-up has one job — convert demo energy into a concrete next step while the problem is still vivid. Write my post-demo follow-up email. Rules: - Under 130 words, sent same day as the demo. - Structure: (1) one line tying back to the sharpest moment of the demo — a problem they voiced, a reaction they had, a number that landed; (2) a 2 or 3 bullet recap framed as THEIR outcomes, never our features; (3) any open item we owe them, with a date; (4) one specific proposed next step with a day and time, not 'thoughts?'. - Banned: 'great meeting you', 'as discussed' openers, feature tour recaps, more than three bullets, attachments dumped without context, and any closing line that leaves next steps undefined. - Match the formality to the buyer; default to plain, confident language. Also give me: a short subject line that references their problem (not 'Demo follow-up'), and a one-line internal note on the biggest risk to this deal based on what I tell you. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. What does your product do, and what was this prospect trying to solve? 2. What moments landed in the demo — questions they asked, problems they voiced, anything they reacted to? Paste notes or transcript chunks if you have them. 3. Who attended, and who was missing that matters? 4. What did you promise to send or find out? 5. What next step do you actually want, and by when? Once you have my answers, write the email. If a key decision-maker was missing from the demo, build the next step around getting them in the room.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Paste real demo notes or transcript chunks at question 2 — Gong or Fathom excerpts make the callback line specific instead of generic.
- 3
Answer question 5 with a real day and time; 'sometime next week' produces a weak CTA.
- 4
Send within a few hours of the demo, before the energy decays.
- 5
Reuse the same chat after their reply to draft the next email in the thread with full context.
Best practices
The callback moment in line one matters more than the recap — pick the point where the prospect leaned in, not your favorite feature.
If someone important missed the demo, make the follow-up easy to forward: the outcomes bullets should read cleanly to a person who wasn't there.
Put owed items with dates even if the buyer owes you nothing — one-sided accountability builds trust fast.
Track which callback moments correlate with replies across deals; it sharpens both your demos and your follow-ups.
Example: what this looks like in practice
An AE at a mid-market HR-tech company demos to a 3-person panel at a 900-employee healthcare staffing firm. Her notes show the VP of People reacted hard to a compliance-audit screen ('that alone would save Priya a week a month'). She pastes the transcript excerpt, notes the CFO was absent, and wants a pricing review call Thursday. The model returns a 118-word email opening on Priya's week-a-month, three outcome bullets, the owed SOC 2 doc dated for tomorrow, and a Thursday 10am proposal that suggests looping in the CFO — plus an internal note flagging CFO absence as the deal's main risk. The VP replies accepting Thursday and cc's the CFO.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Four things: a specific callback to the moment that landed hardest in the demo, a short recap of outcomes in the buyer's words (not a feature list), anything you owe them with a date, and one concrete proposed next step with a day and time. Everything else — pleasantries, attachments without context, long recaps — dilutes the email's one job, which is momentum.
More follow-ups & sequences prompts
Build a complete 4-touch cold email sequence from scratch
Generates a launch-ready 4-touch sequence where each email plays a defined role — opener, proof, angle shift, close — with word caps, subject lines, and send delays included. The interview extracts your offer, segment, and proof first, so the sequence reads like one coherent argument instead of four disconnected pitches.
Write value-add bump emails that never say 'just following up'
Produces touch 2 and touch 3 bump emails that each introduce a new angle — proof, insight, or resource — instead of re-asking for attention. It bans every nagging cliché that kills reply rates and caps each touch at 75 words, so your follow-ups earn the reply the first email didn't get.
Ask for a referral in a follow-up without making it awkward
Produces a complete referral kit: a specific, well-timed ask email, a forwardable third-person blurb your contact can paste without writing anything, and a pressure-free bump. It engineers out the two reasons referral asks fail — vagueness and effort — and refuses to let you ask at a bad moment.