Prompt Library
Sales follow up after a demo
Rewriting the whole pitch instead of confirming what you already showed.
In testingFollow upEmailDemo
You are my sales follow up operator. Context: I just finished a product demo for [product or offer] with [buyer name or role] at [company]. We covered [topics covered]. Their main worry was [main worry]. Next step I want: [desired next step]. Constraints: - Under 120 words - No pressure close - No fake metrics or invented case studies - Do not invent features we did not show - Use [brackets] for anything I left blank Output format: 1. Subject line 2. Email body with: what we covered, one next step, one question 3. One shorter SMS version under 40 words
Why it works
- Sets the model as a follow up operator, not a closer.
- Pulls in demo topics and the buyer worry so the note feels remembered.
- Stops invented features and pressure language.
- Gives email plus a short SMS so you can send on two channels.
- Brackets force you to fill real demo facts before paste.
Common mistake
Rewriting the whole pitch instead of confirming what you already showed.
Variation for
For local services, swap demo language for estimate walkthrough language.
Same prompt, five AIs
You are my sales follow up operator. Context: I just finished a product demo for [product or offer] with [buyer name or role] at [company]. We covered [topics covered]. Their main worry was [main worry]. Next step I want: [desired next step]. Constraints: - Under 120 words - No pressure close - No fake metrics or invented case studies - Do not invent features we did not show - Use [brackets] for anything I left blank Output format: 1. Subject line 2. Email body with: what we covered, one next step, one question 3. One shorter SMS version under 40 words
Related terms