I lost a $200,000 deal because I put all my eggs in one basket.
My champion was enthusiastic. Senior enough. Well-connected. We had a great relationship. I felt confident.
Then he left the company.
Two weeks before we were supposed to sign, he took a job at a competitor. Nobody else in the organisation knew me. Nobody else understood the project. The deal died within a month.
If I'd built relationships with two or three other people, I would have had continuity. I had one relationship, and it walked out the door.
The Data on Multi-Threading
Sales research analysing thousands of deals found a clear pattern:
- Deals with 1 contact: 27% win rate
- Deals with 3+ contacts: 45% win rate
That's not a marginal difference. That's nearly double.
LinkedIn's State of Sales report confirms the pattern: deals involving multiple stakeholders are more likely to close, close faster, and renew at higher rates.
The message is clear: single-threaded deals are fragile. Multi-threaded deals are resilient.
Why Multi-Threading Works
Champions leave or get distracted
The average tenure for a VP-level role is about two years. Even if they stay, priorities shift. A champion who was focused on your project in Q1 might be pulled into a crisis in Q2.
When you have relationships with three people, one going dark doesn't kill you.
Buying is a group sport
Enterprise decisions are rarely made by one person. Industry research shows 6-10 people are typically involved in B2B purchases.
If you're only talking to one of them, you're missing information about what the others think, what concerns they have, and what would make them supportive.
Different perspectives give you intelligence
Your champion sees the project one way. A technical evaluator sees it differently. An end user has another perspective entirely.
Each contact gives you information the others can't or won't share. The more threads, the more complete your picture of the deal.
Internal selling is easier with allies
Your champion has to sell your solution internally. That's easier when other people are already familiar with you and supportive.
If your champion walks into a meeting and three people already know the vendor and like the approach, that's different than walking in alone to convince everyone from scratch.
How to Multi-Thread
Start with your champion
Don't go around them. Go through them.
"Sarah, I want to make sure we build a solution that works for everyone. Who else on your team should I be talking to? I'd love to understand their perspective."
Most champions appreciate this. It shows you're thorough and takes burden off them.
Identify the buying committee
In any significant purchase, multiple roles are involved:
The economic buyer controls the budget and has final approval. User buyers will use your product daily and care about functionality. Technical buyers evaluate integration, security, and scalability. And there are coaches who may not have formal authority but still influence decisions.
Map who's who. Then work to connect with each category.
Create reasons to meet others
You need legitimate reasons to meet multiple people, not just "networking."
Good reasons:
- "I'd love to understand how your team would use this day-to-day."
- "Can I do a technical deep-dive with your IT security team?"
- "Would it help if I presented directly to the executive sponsor?"
- "I'd like to include your implementation team in planning."
Each meeting has a purpose beyond just adding a contact. Good discovery questions help surface what each stakeholder uniquely cares about.
Different value for different stakeholders
What resonates with the CFO is different from what resonates with end users.
Tailor your messaging. Executives care about ROI, strategic alignment, and risk. Users want to hear about ease of use, workflow improvement, and support. Technical teams focus on integration, security, and scalability. Your champions want to know you'll make them look good and support their initiative.
One pitch doesn't fit all stakeholders.
Document your contacts
Track everyone you've met, what they care about, and their role in the decision.
In your CRM, note:
- Name and title
- Their specific priorities
- Their sentiment toward the deal
- Last meaningful interaction
- Next planned engagement
This discipline keeps multi-threading organised as deals get complex.
The Balance: Enough but Not Too Many
There's a line between multi-threading and annoying everyone.
You don't need to meet the entire organisation. Focus on people with meaningful influence on the decision. Usually that's 3-5 people for a mid-market deal, 5-8 for enterprise.
And always be transparent. If someone asks "have you been talking to others in our organisation?" the answer should be yes, and you should be able to explain why in terms of serving them better.
What Happens When You Don't
Single-threaded deals are at risk every day.
If your champion leaves, the deal dies. If they get busy, it stalls. If they lose influence internally, same outcome. If they have blind spots about the buying process, you miss important information. And if they face internal opposition you don't know about, you won't find out until it's too late.
I've seen countless deals fail because the seller had one relationship and that relationship couldn't carry the deal across the finish line alone.
Making It Habitual
For every qualified deal, ask yourself:
- How many active relationships do I have?
- Which stakeholder categories am I missing?
- What's my plan to add another thread this week?
Build multi-threading into your deal management discipline. Review stakeholder maps regularly. Identify gaps and fill them.
The deals that close are the ones with a web of relationships, not a single strand.
For more on navigating complex stakeholder situations, see what enterprise buyers actually care about.