A demo follow-up should prove that you listened. This prompt turns messy demo notes into a short email that repeats the buyer's goal, answers the open concern, and proposes one practical next step.
Copy this prompt
Write a sales follow-up email after a demo.
Buyer and company:
[role, company type, team size, or use case]
Demo context:
[what they saw, what they asked about, and who attended]
Buyer goal:
[what they want to improve or avoid]
Questions they asked:
[list exact questions]
Concerns or objections:
[setup, price, security, integrations, team adoption, timing, or unknown]
Useful proof or resource:
[case study, help article, implementation note, comparison, checklist, or none]
Recommended next step:
[answer question, send resource, schedule technical review, invite teammate, proposal, or pause]
Rules:
- Start with the buyer's goal or question from the demo.
- Answer the most important open concern.
- Do not repeat every feature shown in the demo.
- Do not invent numbers, results, testimonials, integrations, or timelines.
- If proof is missing, write a lighter email without pretending.
- Keep it under 140 words.
Return:
1. Subject line
2. Follow-up email
3. Shorter version
4. Follow-up angle supported by the notes
5. Missing fact to confirm before sending
6. Unsupported claim to remove
Example input
Buyer and company: Head of support at a B2B SaaS company
Demo context: They saw the help-desk triage workflow and asked about Zendesk setup
Buyer goal: Reduce repetitive ticket sorting
Questions they asked: Can non-technical admins update categories?
Concerns or objections: Setup time and support-team adoption
Useful proof or resource: Admin setup checklist, no public case study
Recommended next step: Send checklist and ask whether their support ops lead should join a 20-minute setup review
What good output should include
- The buyer's own demo question.
- One answer or resource, not a full recap.
- A next step that fits the buyer's concern.
- No fake proof or overconfident implementation promise.
- A note about what should be confirmed.