Claude-optimized prompt structure shaped for chatgpt.
# Task
Write a post-demo follow-up email. Use ONLY what was actually discussed.
# Inputs- Demo notes: {demo_notes}- Stakeholders: {stakeholders}- Agreed value: {agreed_value}- Next steps: {next_steps}- CTA: {cta}- Tone: {tone}# Anti-hallucination rules1. Only reference features, benefits, and outcomes discussed in the demo.
2. Do not claim agreement on points that weren't confirmed.
3. Mark anything uncertain with [TO CONFIRM].
# Email design principles1. **Easy to forward**: Write the email so the recipient can forward it to their boss or buying committee without editing. Include enough context for someone who wasn't on the call.
2. **Momentum-building**: Include a specific date/time for the next interaction. Never end with "let me know when works."
3. **Stakeholder-aware**: If multiple stakeholders attended, acknowledge each by role.
# Email structure1. **Subject line**: Include the company name and key outcome (e.g., "Acme + [Product] — Next Steps from Today's Demo")
2. **Opening** (1-2 sentences): Reference a specific moment from the demo that resonated.
3. **Value recap** (3-5 bullets): What you showed, what problem it solves for THEM, and any agreed outcomes. Format for scanning.
4. **Next steps** (numbered list): Each with owner and date. Bold the dates.
5. **Soft ask** (1 sentence): The CTA, tied to a specific date.
6. **Sign-off**: Warm, brief.
# Output1. Full follow-up email
2. Internal-forward version (shorter, exec-friendly, 3-4 sentences max)
3. Suggested follow-up if no response in 3 days (2-3 sentences, new angle)
claudegrounded_factsexamples
claude variant
Claude-optimized prompt structure shaped for claude.
<context><demo_notes>{demo_notes}</demo_notes><stakeholders>{stakeholders}</stakeholders><agreed_value>{agreed_value}</agreed_value><next_steps>{next_steps}</next_steps><cta>{cta}</cta><tone>{tone}</tone></context><task>Write a post-demo follow-up using ONLY what was discussed.</task><instructions>
Only reference discussed features. Mark uncertain items [TO CONFIRM].
Design for internal forwarding. Include specific next-step dates. Acknowledge stakeholders by role.
Structure: Subject (company + outcome) > Opening (specific demo moment) > Value recap (3-5 bullets) > Next steps (numbered, with owners and bold dates) > Soft ask > Sign-off.
</instructions><output>
Return: full email, internal-forward version (3-4 sentences), and 3-day follow-up if no response.
</output>
geminigrounded_factsexamples
gemini variant
Claude-optimized prompt structure shaped for gemini.
Demo notes: {demo_notes}
Stakeholders: {stakeholders}
Agreed value: {agreed_value}
Next steps: {next_steps}
CTA: {cta}
Tone: {tone}
Rules: only discussed content, mark uncertain items [TO CONFIRM], design for forwarding, include specific dates.
Structure: Subject (company + outcome) > Opening (demo moment) > Value recap (3-5 bullets) > Next steps (numbered, owners, dates) > CTA > Sign-off.
Based on the entire content above, return: full email, internal-forward version (3-4 sentences), and 3-day follow-up.
Related templates
More templates in the same working category.
Email Reply
Draft a professional email reply that matches the thread tone, addresses every point raised, and drives toward a clear next step.