Reopening a deal that went quiet after a good product demo
Writes the follow-up messages for a prospect who liked the product demo and then stopped replying: one built on what they said in the demo, one that helps them sell it inside their company, and a final respectful close-the-file note. Each message gives them an easy reason to reply. Use it one to three weeks after a demo that ended with "this looks great, let me check internally".
The output this prompt produced, unedited.
The prompt
Fill in these first
Product and what it solves: [one line]
Prospect's name, role and company: [e.g. Head of Operations at a 200-person logistics firm]
What they said in the demo, in their words: [pain points, the feature that got a reaction, any number they shared]
Who else decides: [e.g. finance head, IT, unknown]
What was promised after the demo: [e.g. pricing sent, trial offered, nothing]
Days since the last reply: [e.g. 12]
One useful asset you can share: [e.g. a one-page ROI summary, a case study from a similar firm, a security document]
Write
Email 1, send now: recall one thing they said in the demo, connect it to one result, and ask a yes or no question about the next step.
Email 2, send 5 to 7 days later: offer the asset as something they can forward to the other decision maker, with a two-line summary they can paste.
Email 3, send 7 to 10 days after that: a short note that you will close the file for now, with an open door and no guilt.
A LinkedIn message under 300 characters for use between emails 1 and 2.
For each email
A subject line under 45 characters that is not "Following up".
A body under 100 words, written to one person.
One question that can be answered in a word.
Rules
Use only details from the inputs; never invent results, clients or deadlines.
No fake urgency, no discounts unless given, no "just checking in".
follow up after demosales follow up emailprospect went silentb2b sales emaildemo follow upre engage prospect
How to run this
Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.
The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.