Nudge a quiet internal champion without burning goodwill
Builds a 3-touch sequence for the champion who went quiet: arm them with a forwardable tool, reduce their internal risk, then release the pressure gracefully — with a read on what each possible reply says about deal health. Every touch makes their internal job easier instead of reminding them they owe you an update.
You are a complex-deal advisor who has coached hundreds of AEs through the hardest silence in sales: the internal champion who was enthusiastic, promised to talk to their boss, and went quiet. You know the champion is usually not ignoring you; they're stuck, embarrassed, or deprioritized. Every touch must make their internal job EASIER, never remind them they owe you. Build me a 3-touch champion nudge sequence: - Touch 1 (4 to 6 days after they went quiet): under 80 words. Hand them a tool for their internal conversation — a one-paragraph summary they can forward, a data point for their boss's likely objection, an answer to a question procurement will ask. Frame: 'thought this might be useful for your conversation with X', never 'any update?'. - Touch 2 (a week later): under 80 words. Reduce their risk: offer to join their internal meeting, take a stakeholder question directly, or shrink the decision (pilot, phase one). Give them a graceful, cheap way to admit it's stalled. - Touch 3 (a week after that): under 70 words. The pressure-release: name the possibility that priorities shifted, offer to pause cleanly with a restart trigger, and thank them for the championing they did. No guilt, no disappointment, no 'I thought we had momentum'. - Banned everywhere: 'any update?', 'did you get a chance to talk to', 'checking in on this', deadlines invented to force motion, and going over their head without telling them. Output: three emails with timing, plus a one-line note on the signal each reply type sends about the deal's real health. Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time: 1. Who's the champion, who do they need to convince, and what's the org dynamic between them? 2. What happened in your last interaction, and how long has the silence been? 3. What does your solution cost, roughly, and what outcome does it deliver for THEIR company? 4. What internal obstacle is most likely — budget, a skeptical boss, procurement, competing priority? 5. What assets do you have that could arm them — one-pagers, ROI data, security docs, references? Once you have my answers, write the sequence. If the obstacle in question 4 is a skeptical boss, make touch 1 a forwardable aimed at that boss's objection, written so the champion can send it without any editing.
How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Map the org honestly at question 1 — the sequence is built around who the champion must convince, not around you.
- 3
Name the likeliest obstacle at question 4; a budget stall and a skeptical boss need different touch 1 tools.
- 4
Space the touches as directed and resist compressing them — champion pressure compounds faster than prospect pressure.
- 5
Read replies against the signal notes: 'still working on it' with no specifics usually means stalled, and the notes tell you what to probe.
Best practices
Arm before you ask, always — a champion with a forwardable answer to their boss's objection moves deals that ten status checks won't.
Never go around a champion silently; if you must widen the deal, propose it to them first as making their life easier.
The graceful-pause offer in touch 3 is a probe, not a surrender — how they respond to 'should we park this?' tells you the truth 'any update?' never surfaces.
Keep every touch forwardable-clean: assume anything you send the champion may be read by their boss verbatim.
Example: what this looks like in practice
An AE at a 30-person analytics company has a Director of Ops champion who loved the pilot proposal, promised to raise it with her CFO, then went silent for two weeks. In the interview he flags the obstacle: a CFO skeptical of new tools mid-budget-cycle. Touch 1 delivers a forwardable paragraph framing the pilot as $4K against a documented $60K annual reporting cost, written for CFO eyes. Silence. Touch 2 offers to join her CFO conversation directly or answer questions async, and adds 'if this has slipped down the stack, tell me straight — genuinely fine'. She replies within a day: 'CFO meeting is Thursday, that paragraph helped, can you be on standby?'. The deal closes as a phased pilot; touch 3 never sends.
Best fit
This prompt is one gear in a bigger machine. We orchestrate 20+ tools into outbound systems our clients own — and guarantee the results.
Apply for a Pilot Spot → →Frequently asked questions
Assume stuck, not gone — champions go quiet because their internal push stalled, and 'any update?' only adds to their burden. Instead, send something that makes their job easier: a forwardable summary for their boss, data for the objection they're facing, or an offer to join the internal conversation. Then give them a cheap way to admit it's stalled; honesty you make easy is intelligence you can act on.
More follow-ups & sequences prompts
Build a complete 4-touch cold email sequence from scratch
Generates a launch-ready 4-touch sequence where each email plays a defined role — opener, proof, angle shift, close — with word caps, subject lines, and send delays included. The interview extracts your offer, segment, and proof first, so the sequence reads like one coherent argument instead of four disconnected pitches.
Write value-add bump emails that never say 'just following up'
Produces touch 2 and touch 3 bump emails that each introduce a new angle — proof, insight, or resource — instead of re-asking for attention. It bans every nagging cliché that kills reply rates and caps each touch at 75 words, so your follow-ups earn the reply the first email didn't get.
Ask for a referral in a follow-up without making it awkward
Produces a complete referral kit: a specific, well-timed ask email, a forwardable third-person blurb your contact can paste without writing anything, and a pressure-free bump. It engineers out the two reasons referral asks fail — vagueness and effort — and refuses to let you ask at a bad moment.