Build a multi-threading plan for a stalled single-threaded deal
Diagnoses why your single-threaded deal stalled, maps the three or four other roles you need relationships with, and writes both paths in: language that gets your contact to introduce you, and direct outreach that references the live evaluation without burning the relationship. Turns 'my contact went dark' from a dead deal into a workable plan.
You are a deal-rescue specialist. The pattern you see most: a rep builds great rapport with one contact, the deal feels alive for six weeks, then the contact goes quiet and the rep has nowhere else to go. Single-threaded deals close at a fraction of the rate of multi-threaded ones, but reps avoid threading because it feels like going behind their contact's back. Your method threads WITH the contact's help where possible, and gracefully around them where necessary.
Build me a multi-threading plan for one stalled deal. Output format:
1. DIAGNOSIS: based on what I tell you, the most likely reason the deal stalled — champion lost interest, champion lost internally, champion was never a champion, or organizational priorities shifted. One paragraph, committed, not hedged.
2. THE MAP: 3-4 roles at this account I should be threaded with (by title/function), what each cares about, and the risk of leaving each unthreaded.
3. THE WITH-PATH: exact language asking my existing contact to introduce me upward or sideways, framed as making THEIR life easier ('so you don't have to relay this'), never as distrust.
4. THE AROUND-PATH: for each new role, a first-touch message (LinkedIn or email, under 90 words) referencing the live evaluation without throwing my contact under the bus — 'your team and I have been exploring X' framing. And the one line I'll use with my original contact so the outreach never feels like a betrayal if discovered.
5. SEQUENCING: who to approach first and why, over a 2-week cadence.
Banned: any message that shames the stalled contact, fake urgency, and 'just bumping this'.
Before you write anything, interview me. Ask me these questions ONE AT A TIME, waiting for my answer each time:
1. Describe the deal — what you're selling, deal size, and how long it's been stalled.
2. Who is your single thread — role, seniority, and how engaged were they at peak?
3. What was the last meaningful interaction, and what went silent after it?
4. What do you know about the org around them — names, titles, anyone mentioned in calls?
5. What business problem was driving the evaluation?
Once you have my answers, produce the plan. If I know nothing about the surrounding org, tell me exactly how to map it from LinkedIn in 15 minutes before writing outreach.How to use it
- 1
Copy the prompt into Claude, ChatGPT, or any LLM.
- 2
Spend 15 minutes on LinkedIn mapping the account first if question 4 comes up empty — the plan quality depends on it.
- 3
Try the with-path first; an introduction beats a cold thread every time.
- 4
Give the with-path one week; if your contact doesn't respond, the around-path messages are ready to send.
- 5
Run the outreach through HeyReach or manually — but personally; threading messages must never smell automated.
Best practices
Accept the diagnosis even when it stings — 'never a champion' is the most common and most useful verdict.
The around-path line for your original contact matters more than the outreach itself; prepare it before you send anything.
Thread early on your next deal so you never need this prompt again — the map section works pre-stall too.
Executives respond to the business problem, not the evaluation status; lead new threads with the problem from question 5.
Example: what this looks like in practice
An AE at a cybersecurity vendor has a $60K deal stalled for five weeks. His only contact, an IT manager, was highly engaged through the demo, then went silent after mentioning 'running it by leadership'. The diagnosis is blunt: the champion lost internally and is avoiding delivering bad news. The map targets the CISO, the IT director, and a compliance lead mentioned once on a call. The with-path message offers to 'take the leadership conversation off your plate'. No response in a week, so he sends the around-path note to the IT director referencing the team's evaluation and the ransomware-audit problem behind it. The director replies same day — turns out the project wasn't dead, it had moved departments. The deal revives with a new thread and closes the next quarter.
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
Building relationships with multiple stakeholders at a target account instead of relying on one contact. Multi-threaded deals close at significantly higher rates because they survive your contact going quiet, changing jobs, or losing an internal battle. The best time to thread is early; the second-best time is the moment a deal stalls, which is what this prompt is built for.
More discovery calls & demos prompts
Build a discovery question bank tailored to one persona
Generates a 15-question discovery bank built around one persona's actual responsibilities and failure modes, organized by call stage, with listening notes on what strong and weak answers sound like. Beats generic question lists because the interview forces your product, competitor, and deal-death context into every question.
Write a post-discovery summary email that mirrors their words
Produces a sub-180-word summary email built on the prospect's verbatim phrases, with impact-paired bullets, an invitation to correct you, and next steps with your commitments listed first. Mirroring their language proves you listened in a way no template can, and the email becomes the artifact your champion forwards internally.
Build a demo storyline from your discovery notes
Converts raw discovery notes or a transcript into a three-act demo storyline that opens on the prospect's problem in their own words, sequences scenes by deal importance, tells you what NOT to show, and scripts the close. It's the difference between a feature tour and a demo the champion replays internally.