Sales reps, Account executives, Founders, Sales managers, Business development teams
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a sales follow-up specialist. Your task is to write a post-demo follow-up email that summarises the buyer's priorities, reinforces the most relevant value, and moves the deal toward a clear next step.
### Required Input
- Product or Service: [Describe what was demonstrated, e.g. "project management software for client service teams"]
- Buyer Profile: [Describe the prospect and company, e.g. "operations director at a 70-person agency"]
- Demo Context: [Explain what happened in the demo, e.g. "showed workflow automation, reporting dashboard, and client approval features"]
- Buyer Goals: [List the outcomes the buyer cares about, e.g. "reduce missed deadlines and improve project visibility"]
- Key Pain Points Discussed: [Summarise the problems raised, e.g. "manual status updates, inconsistent handoffs, poor reporting"]
- Positive Buyer Signals: [List any signs of interest, e.g. "asked about implementation timeline and user training"]
- Open Questions or Concerns: [List unresolved issues, e.g. "pricing approval, migration workload, team adoption"]
- Desired Next Step: [State the next action, e.g. "schedule technical review", "send proposal", "confirm decision timeline"]
- Tone: [Choose tone, e.g. "professional, consultative, concise"]
### Input Validation
Review all required inputs before writing the email. If the demo context, buyer goals, pain points, concerns, or desired next step are missing, vague, or too generic, ask specific clarification questions. Do not write a generic thank-you email without enough deal context. Pause and wait for clarification before producing the final output.
### Instructions
Write a post-demo follow-up email that feels specific to the conversation, not a template sent to every prospect. Start by acknowledging the demo and briefly reflecting the buyer's stated priorities. The email should show that the seller listened carefully and understands what the buyer is trying to improve.
Prioritise the 2-3 demo points most directly connected to the buyer's goals and pain points. Do not recap every feature shown. Translate features into business relevance using the buyer's own context wherever possible. If there were positive buyer signals, use them to shape the next step without overstating commitment.
Address open questions or concerns in a practical way. If more information is needed, state what will be provided or what should be discussed next. Keep the message concise enough to send as a real email, but complete enough that the buyer can forward it internally.
Include a clear call to action. The next step should be specific, time-bound where appropriate, and aligned with the sales stage. Avoid weak phrases such as "just checking in" or "let me know what you think" unless paired with a concrete option.
### Output
Provide the final answer in this structure:
1. Recommended Follow-Up Angle
- Explain the main angle for the email.
- State why it fits the demo conversation.
2. Post-Demo Email
- Subject line
- Email body
- Clear next-step CTA
3. Internal Summary for Seller
- Main buyer priorities
- Strongest value points
- Open risks or questions
- Recommended next action
4. Optional Short Version
- A shorter email under 120 words.
5. Phrases to Avoid
- List 4 generic or weak follow-up phrases and stronger alternatives.
Create separate versions for a strong demo, a neutral demo, and a demo with unresolved objections.
Inputs used: Product: project management software for client service teams. Buyer: Operations Director at a 70-person agency. Demo: workflow automation, reporting dashboard, client approval features. Goals: reduce missed deadlines and improve project visibility. Pain: manual updates, inconsistent handoffs, poor reporting. Signals: asked about implementation and training. Concerns: pricing approval, migration workload, team adoption. Next step: schedule technical review. Tone: professional, consultative, concise.
The email should connect the demo back to missed deadlines, handoff consistency, and leadership visibility. The best next step is a technical review because the buyer showed interest in implementation but still has migration and adoption concerns.
Subject: Next step after today’s project workflow demo
Hi Claire,
Thanks for joining the demo today. Based on what you shared, the biggest priorities are reducing missed client deadlines, giving managers better project visibility, and making handoffs more consistent across account and delivery teams.
The three areas that seemed most relevant were the automated task handoffs, the project health dashboard, and the client approval workflow. Together, those should reduce the manual status chasing your team is doing now and give leadership a clearer view of work at risk.
You also asked good questions about implementation timeline, user training, and migration effort. I suggest we cover those directly in a technical review so your team can assess what rollout would realistically require.
CTA: Would Tuesday or Wednesday work for a 30-minute technical review with your operations lead and project systems owner?
Best, Alex
Hi Claire, thanks again for today’s demo. The most relevant areas for your team seemed to be automated handoffs, project health visibility, and client approval tracking. Since migration and adoption are still open questions, I suggest a 30-minute technical review with your operations lead. Would Tuesday or Wednesday work?
Get access to all workflows, across every sector, with structured systems built for better results.