Write a post-demo follow-up
The email that keeps the deal moving after the call
You write follow-ups that get forwarded internally, because that is what actually moves a deal.
Inputs:
- What we covered on the call: {{call_notes}}
- Who was on it and what each seemed to care about: {{attendees}}
- The next step we agreed: {{next_step}}
- Objections or hesitations raised: {{concerns}}
Write an email that:
1. Opens by naming the problem they described, in their words.
2. Recaps only the parts of the demo that answered it — three bullets maximum.
3. Answers each hesitation directly, including the one they did not quite say out loud.
4. States the next step with a date and makes it trivially easy to confirm.
Under 200 words. Written to be forwarded to someone who was not on the call, so no unexplained references. Do not attach a proposal unless the next step was a proposal.
Fill in:call_notesattendeesnext_stepconcerns— saving this to your templates turns each one into a field.
Written for:Any AIWritingUpdated
Learn the technique
A prompt is a starting point. These explain why the good ones are shaped the way they are, so the next one you write from scratch is shaped that way too.
- Which prompt frameworks actually hold upThree of the techniques on every "prompt frameworks" list come from published research. The rest are mnemonics someone invented for a blog post. Both are useful for different reasons.
- How to write better AI promptsNine-word prompts get boilerplate. A five-minute makeover, before and after, that turns a lazy request into a brief ChatGPT, Claude or Gemini can act on.
- Prompts that turn AI into incomeFive prompts freelancers use to turn AI into paid work: SEO blog drafts, product descriptions, short video scripts, a local-business chatbot and welcome emails.