Verified against ChatGPT · 2026-08-13
Turn a proposal that's gone quiet into a follow-up sequence the buyer actually answers
Builds a short, escalating follow-up sequence for a proposal stuck in silence — each message tied to a specific signal from the deal instead of a generic "just checking in" nudge, so it reads as informed rather than needy.
The prompt
Ready to copy — highlighted parts are example details you can swap.
You are writing a follow-up message sequence for a sales proposal that has gone quiet — the prospect has not responded since it was sent, and a generic "just following up" email would read as either desperate or as filler the buyer has seen a hundred times before. Use the details below to write messages that only make sense for this specific deal.
PROPOSAL SUMMARY
A 12-month contract for our mid-tier analytics plan at $850/month, including onboarding and a dedicated Slack channel, sent with a comparison against their current spreadsheet-based process.
DAYS SINCE SENT AND PRIOR CONTACT
Sent 9 days ago. One reply the day after ("looks good, reviewing internally") and nothing since.
STAKEHOLDER SITUATION
Sent to the Head of Ops, who mentioned needing sign-off from the CFO before committing to anything over $500/month.
LAST SIGNAL FROM THE BUYER
Asked in the intro call whether the plan supports exporting data to their existing BI tool.
DESIRED NEXT STEP
A 15-minute call with the CFO to walk through the ROI comparison, or a straight yes/no on moving to a contract.
RULES FOR THE SEQUENCE
Write exactly three messages, spaced for escalating urgency but never impatience: a light check-in, a value-add nudge, and a final "close the loop" message. Every message must reference something specific and real about this deal — a detail from the proposal, a date, a stakeholder's stated concern, or the last thing the buyer actually said — never a placeholder like "I wanted to touch base" that could be sent to any prospect. Do not open any message with "just checking in," "following up," "circling back," or "wanted to see if you had a chance" — these signal a message with no new information and buyers skim past them. Each message must give the recipient a reason to respond that isn't just guilt or politeness: new information, a genuine question tied to their stated concern, or a low-effort binary choice (a yes/no, a pick-one-of-two). If the stakeholder situation suggests the proposal may be stuck with a different person than the one who received it (a champion who's gone quiet, a committee decision, budget approval pending), address that possibility directly in at least one message rather than assuming the original recipient is the blocker. The final message in the sequence must include a graceful, low-pressure way for the buyer to signal "not now" or "not interested" without it feeling like a breakup email — closing a dead deal cleanly is more useful than one more unanswered message sitting in a pipeline.
WHAT NOT TO DO
Do not manufacture false urgency (fake limited-time pricing, invented deadlines) if none was actually given in the proposal. Do not repeat the entire proposal pitch again — assume the reader already read it once and needs a reason to re-engage, not a recap.
OUTPUT FORMAT
1. Message 1 (light check-in) — subject line and body, 3-5 sentences.
2. Message 2 (value-add nudge, sent if no reply to Message 1) — subject line and body.
3. Message 3 (close the loop) — subject line and body, including the low-pressure opt-out.
4. A one-line note on the recommended spacing between each message given the deal size and stakeholder situation described above.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Most proposal follow-ups fail for a structural reason that has nothing to do with wording: they carry zero new information, so a busy buyer correctly infers that ignoring it costs nothing. Forcing every message to reference a specific proposal detail, stakeholder concern, or prior answer removes the option to write a content-free nudge, which is the actual mechanism that gets a message read instead of archived — a model asked to be "polite but persistent" without that constraint will default to exactly the templated opener the rules explicitly ban, because that phrasing is statistically the most common pattern in its training data for this exact scenario. Naming the possibility that the real blocker is a second stakeholder (a CFO sign-off, a committee) rather than the original recipient matters because a follow-up sequence that only ever escalates pressure on the same person silently assumes single-threaded buying, and in the B2B context this template targets, deals stall at exactly this multi-stakeholder friction point far more often than at simple disinterest — addressing it directly gives the seller a second lever the sequence would otherwise miss entirely. The requirement to end with a genuine low-pressure exit is a deliberate counterweight to a model's tendency to keep escalating urgency across a sequence when asked for one; a dead deal that gets a clean "no" in message three is more valuable to a real pipeline than a fourth unanswered message, and stating this explicitly stops the AI from writing a slightly-more-desperate version of message two by default. Finally, banning invented urgency (fake deadlines, fabricated scarcity) keeps the output usable as-is rather than something the seller has to first strip of claims that aren't true, which is the difference between a draft and a liability.
What you get back
Message 1 — Subject: "Quick one on the BI export question" — Hi [Name], you'd asked whether the analytics plan exports cleanly to your BI tool during our call — wanted to confirm it does, via a direct connector, no manual CSV step. Figured that might be sitting as an open question while you're reviewing internally. Happy to send a two-line technical confirmation if that's useful for whoever needs to sign off. — Message 2 references the CFO approval threshold directly and offers a 15-minute call. — Message 3 closes with: "If now isn't the right time, no worries at all — just let me know and I'll close this out on my end so I'm not cluttering your inbox."
Verified against
ChatGPT GPT-5.1 · 2026-08-13
Changelog
- 2026-08-13 — Initial publish, verified against ChatGPT GPT-5.1.
Need this built into your business?
If a prompt isn't enough — Google Ads management, built and maintained for you — that's Scult's day job.
EXPLORE GOOGLE ADS MANAGEMENT
