What each part of the prompt does
- Written to be forwarded
- The role line and the "colleague who missed the demo" rule shape the email for the real reader: the budget holder who was not on the call and needs the whole story in one message.
- Their words, not ours
- Restating the problem the way the prospect described it shows you listened and makes the email easy for them to agree with when they pass it on internally.
- Concerns answered, not skipped
- Follow-ups often skip the awkward questions. Requiring an answer, or a date for one, keeps an unresolved objection from quietly stalling the deal.
- A concrete next step
- Two specific time options get a faster reply than "let me know when works". The ban on discounts and on clichés keeps the email confident instead of pushy.
Variations to try
Same idea, one thing changed.
No reply after a week You are a sales rep who writes follow-ups that buyers forward to their boss. Task: Write a second follow-up to [PROSPECT NAME] at [COMPANY], who has not replied for a week since our demo and first follow-up. Context: - What we sell: [PRODUCT] - The problem they described: [PROBLEM] - What we showed in the demo: [DEMO POINTS] - Questions or concerns they raised: [CONCERNS] - Agreed next step, if any: [NEXT STEP] - Pricing or terms we discussed: [PRICING] Requirements: - Open by thanking them in a few words and restating their problem in their own words. - Add one new, useful thing instead of repeating the recap: a short example, a relevant answer or a resource tied to their problem. - Answer each concern directly. If we did not have an answer on the call, say when they will get it. - Write it so a colleague who missed the demo understands it without any other context. - Propose one next step with two specific date and time options. - Mention pricing only as discussed in the context. Do not offer discounts. - Under 100 words. Friendly and plain, no phrases such as "just checking in" or "touching base". Output: - Subject line. - Email body in plain text. - A one-line note for my CRM on where the deal stands.
Recap for their team You are a sales rep who writes follow-ups that buyers forward to their boss. Task: Write a follow-up email after a product demo with [PROSPECT NAME] at [COMPANY]. Context: - What we sell: [PRODUCT] - The problem they described: [PROBLEM] - What we showed in the demo: [DEMO POINTS] - Questions or concerns they raised: [CONCERNS] - Agreed next step, if any: [NEXT STEP] - Pricing or terms we discussed: [PRICING] Requirements: - Open by thanking them in a few words and restating their problem in their own words. - Recap the two or three parts of the demo that solve that problem, one sentence each. - Answer each concern directly. If we did not have an answer on the call, say when they will get it. - Write it so a colleague who missed the demo understands it without any other context. - Propose one next step with two specific date and time options. - Mention pricing only as discussed in the context. Do not offer discounts. - Add a short section they can paste straight to their team, titled "Summary for your team", in three bullets. - Under 250 words. Friendly and plain, no phrases such as "just checking in" or "touching base". Output: - Subject line. - Email body in plain text. - A one-line note for my CRM on where the deal stands.
If the result isn't right
- Write [PROBLEM] in the prospect's own words straight from your call notes; it is the line they are most likely to quote internally.
- If you promised an answer you do not have yet, put the date you will have it in [CONCERNS] so the email commits to it.
- Paste the CRM note into the deal record right away; it becomes the history the next person on the account reads first.