Verified against ChatGPT · 2026-07-26
Turn a single-threaded deal into a multi-threaded one before it stalls
Maps who else in the buying org likely needs to be involved, ranks them by risk of being missed, and drafts the specific ask to your current contact for a warm path to each one — for a deal currently riding on one relationship.
The prompt
Ready to copy — highlighted parts are example details you can swap.
This deal is riding on one relationship and I need to fix that before it stalls or dies quietly. Deal: Brightwell Insurance Group, third call, verbal interest, no other stakeholders looped in yet, deal value roughly $54,000 ACV. Current contact: Wendy Zhao, Senior Claims Operations Manager — this is the only person I've actually spoken with so far. What I know about the org structure or team, even secondhand: she mentioned reporting to a VP of Claims and has said "IT would need to sign off" once in passing. Why this matters now: Wendy went quiet for eight days after our last call with no explanation, and there's no one else who could tell me why.
STAKEHOLDER MAP
Based on she mentioned reporting to a VP of Claims and has said "IT would need to sign off" once in passing and the nature of {{product_or_service}}, list the likely additional people who plausibly need to be involved before this can close — an economic buyer if not already identified, anyone whose workflow the product actually touches day to day, anyone in procurement, security, or IT who could gate the deal at the finish line, and anyone with a plausible reason to be skeptical of a purchase like this. For each, state their likely role in the decision and, honestly, whether this is a confident inference from what's known or a reasonable guess that needs to be checked directly on the next call rather than assumed.
RISK RANKING
Rank the missing stakeholders by how much risk their absence adds to the deal specifically — not a generic ranking, but one grounded in third call, verbal interest, no other stakeholders looped in yet and she mentioned reporting to a VP of Claims and has said "IT would need to sign off" once in passing. Someone who could block the deal at the very end (security review, procurement sign-off) but hasn't been engaged yet is a different risk than someone who's merely nice to have looped in for buy-in.
THE ASK TO Wendy Zhao
Write the actual message or talking point to ask Wendy Zhao for a path to the highest-risk missing stakeholder — framed as something that helps them too, not as a request that implies distrust in their ability to carry the deal alone. Never phrase it as "can I talk to your boss" or anything that could read as going around them; frame it around a legitimate reason the other person's involvement helps the deal move faster or get evaluated more fairly, and let Wendy Zhao be the one who looks good for making the connection.
FALLBACK IF Wendy Zhao RESISTS
Give me one alternate path to the same stakeholder that doesn't depend on Wendy Zhao's cooperation — LinkedIn outreach, a mutual connection, an event, a different internal referral — for the specific case where the ask above doesn't work or gets a soft no, since a multi-threading plan with no fallback is really a single-threading plan with extra analysis attached.
HONESTY CHECK
Tell me plainly if she mentioned reporting to a VP of Claims and has said "IT would need to sign off" once in passing is too thin to build a real stakeholder map from, versus enough to work with — don't manufacture a confident-sounding org chart from information that's really just a guess, and say explicitly which names on the list are informed inference rather than something actually confirmed.Customize
Optional — swap in your own details for the highlighted parts above.
Why this works
Single-threading — a deal running through exactly one point of contact with no other relationship inside the buying org — is one of the most consistently cited reasons enterprise deals go dark without warning, because the entire deal's survival depends on one person's continued availability, motivation, and internal standing, all three of which can change for reasons that have nothing to do with the deal itself: a reorg, a change in priorities, or simply someone getting busy on something unrelated. Separating the stakeholder map from a confidence label on each entry — confident inference versus a guess to check directly — matters because org charts built entirely from secondhand fragments are exactly the kind of output an LLM will otherwise present with uniform, unearned confidence, and a rep who acts on a guessed name as if it were confirmed can walk into a next call referencing a stakeholder who turns out to be the wrong person or doesn't exist in the role assumed, which damages credibility with the very contact being asked to make the introduction. Framing the ask to the current contact around a benefit to them, rather than as a request that implies they can't carry the deal alone, targets a real relational risk in multi-threading: a contact who feels bypassed or distrusted becomes a worse champion, not a better one, so the exact same request phrased two different ways can either strengthen or damage the one relationship the deal currently has. Requiring a fallback path that doesn't depend on the current contact's cooperation is what actually makes this a risk-mitigation plan rather than a single-threaded plan with an extra step added on top — if the only path to every other stakeholder still runs entirely through the one relationship already identified as a point of failure, nothing about the deal's structural risk has actually changed, it has just been described more thoroughly.
What you get back
Highest risk missing stakeholder: whoever in IT signs off on new tools — Wendy mentioned this once in passing and it was never followed up on, and a late-stage IT block after verbal interest is one of the most common ways a deal at this stage stalls without an obvious cause. Ask to Wendy: "Since IT sign-off will come up eventually, would it help to get someone from that team looped in early so there's no surprise at the finish line? Happy to keep it a quick, low-key intro call."
Verified against
ChatGPT GPT-5.1 · 2026-07-26
Claude Sonnet 4.5 · 2026-07-27
Changelog
- 2026-07-27 — Initial publish, verified against ChatGPT (GPT-5.1) and Claude (Sonnet 4.5).
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
