High-Conversion Post-Discovery Follow-Up
Send professional, direct follow-up emails that bridge discovery calls to product demos without the sales fluff.
Customise & copy
Add the context you have. The prompt updates as you work.
First name of the prospect
Name of the prospect's company
The key challenge or topic discussed during the initial conversation
Direct link to watch or try the product demo
Suggested next step or meeting time
Live prompt
5 fieldsWrite a concise, high-conversion customer follow-up email to Sarah at Acme Corp. Context from our recent conversation: Scaling customer support response times during peak hours Include the following product demo link naturally: https://example.com/demo End with this specific call-to-action: Let me know if Thursday at 2 PM works for a quick walkthrough. Requirements: - Write a subject line that references the previous discussion without clickbait or hype. - Start with a short opening sentence acknowledging the prior interaction. - Keep paragraphs short and scannable. - Maintain a professional, direct, and conversational tone with zero hype openers, politeness padding, or fabricated statistics/social proof.
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-03
{
"demo_url": "https://app.apexplatform.io/demo-view",
"pain_point": "Tracking fleet fuel efficiency across regional distribution hubs",
"company_name": "Apex Logistics",
"prospect_name": "Marcus",
"call_to_action": "Are you free this Wednesday at 10 AM to review how this fits your workflow?"
}A small ritual that works
How to use it
- 01Input the prospect's name and company.
- 02Paste the specific pain point discussed during your call.
- 03Insert your demo link and preferred call-to-action.
- 04Review the generated email for tone and send directly to the prospect.
Why it works
The prompt establishes a strict, professional framework for customer follow-up emails by requiring zero hype, scannable paragraphs, a direct opening acknowledging prior context, and integration of specific variables like a demo URL and a defined call-to-action.
Where it fails
Both test outputs fail to preserve the required placeholder structure, substituting fixed values instead. Furthermore, Output A lacks a closing sign-off, and Output B introduces politeness padding ('It was great speaking with you'), an unsupported positive tone word ('great'), and an unverified outcome statement ('keep your schedule full').
Customisation tips
Ensure variable keys such as {{prospect_name}}, {{company_name}}, {{pain_point}}, {{demo_url}}, and {{call_to_action}} are strictly injected as placeholders into the final output text rather than hardcoded with fictional example data during execution.
Watch-outs
- Avoid introducing politeness padding or undefined positive tone words like 'great' in the opening sentence.
- Do not include unsupported outcome claims or exaggerated product benefits not explicitly supported by the context.
- Ensure the email contains a proper closing and sender placeholder rather than abruptly ending after the call-to-action.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Want to make AI useful across your team? Explore Atul's training.