Prompt library
Write the follow-up email after a demo
Opening with their words and mapping bullets to voiced priorities proves listening, which is the actual differentiator in follow-ups. The single dated next step converts momentum into calendar reality, and the skeptic P.S. works the deal's real decision dynamics instead of just its champion.
Last reviewed July 17, 2026
The prompt
Write the follow-up email after a demo.
Demo notes (what they reacted to, questions, objections, who attended): {{notes}}
The proposed next step: {{nextStep}}
Rules:
1. Subject references THEIR priority, not our product name.
2. Open with the moment that mattered: the specific thing they said or reacted to, quoted or closely paraphrased, so the email is unmistakably about their meeting.
3. Middle: 2-3 bullets mapping each priority they voiced to what they saw. Nothing they did not care about, however proud we are of it.
4. Answer the open question they asked that we deferred, or state exactly when the answer arrives.
5. Close with ONE next step tied to a date, with the fallback framed ("if Thursday does not work, send two times that do").
6. Under 150 words. Every sentence they could not have gotten from a brochure.
Then a P.S. variant for the attendee who was skeptical, addressing their specific reservation head-on in one sentence.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{notes}} | What happened in the demo | [paste your demo notes: reactions, questions, objections, attendees] |
| {{nextStep}} | What you want to happen next | security review call with their IT lead this week |