Multi-Threading Discovery Framework

The Problem This Solves

Single-threaded deals — where your only relationship is with one friendly, engaged contact — are the single biggest predictor of a stalled or lost complex deal. The contact who took your call is rarely the only person with a vote.

Step 1 — Map the 6 Roles

Step 2 — Discovery Questions That Surface Each Role

• "Besides you, who else would need to sign off before this could move forward?" (Economic Buyer + Procurement)
• "Who on the technical side would need to weigh in on something like this?" (Technical Evaluator)
• "Who's actually going to be using this day to day?" (End User)
• "Has anyone tried to bring in something like this before — what happened?" (Influencer/Skeptic history)
• "When something like this has been approved before, who's typically in the room?" (whole committee, indirectly)
• "Who would be the hardest person in the building to convince?" (Skeptic, directly)

Step 3 — Score Every Stakeholder: Influence × Support

Plot each identified stakeholder:

• Influence: High / Medium / Low — how much their opinion moves the final decision
• Support: Champion / Neutral / Skeptic / Blocker

Priority order for your time:

1. High Influence + Skeptic/Blocker → address directly and early, don't avoid
2. High Influence + Neutral → invest the most discovery time here
3. High Influence + Champion → arm them with what they need to sell internally
4. Low Influence + any → maintain lightweight touch, don't over-invest

Step 4 — Stakeholder Map Template

Step 5 — Multi-Threading Trigger Points (force a new thread when...)

• Deal has been "in discovery" more than 30 days with only one named contact
• Your single contact can't answer a budget or process question ("I'll have to check")
• Deal size crosses a threshold that structurally requires committee approval
• Your contact goes quiet for more than 5 business days at Proposal stage or later

Red Flags Indicating Single-Threading Risk

• You've never had a live call with anyone above your contact's level
• Your contact answers "I think so" more than once to a budget/authority/timeline question
• No one else has been copied on email or attended a call in 3+ weeks
• Your contact discourages you from reaching out to others ("Let me handle that internally")

Get-Introduced Script

Through your champion:

"[Champion name], to make sure this lands well with [target stakeholder], would it make sense to loop them in directly — a quick three-way call, or I can send something short they can review on their own time? Whichever's easier for you."

Direct outreach once introduced (or independently):

"Hi [Name], [Champion] suggested I loop you in given your role in [function]. I don't want to waste your time repeating everything from scratch — happy to send a 2-minute summary of where things stand, or grab 15 minutes if that's easier. What's more useful for you?"