A single responsive champion can hide a fragile deal, and a bloated committee can sabotage one. Here's how to bring the right people into the decision, at the right stage, without going around your champion.
Multithreading in sales means building relationships with several people in a buying group, so the deal doesn't depend on one contact. Done well, it means bringing in the people the decision actually needs, at the stage it needs them, and connecting them with one message your champion can carry when you're not in the room.
Placeholder answer
Short, practical frameworks for executive messaging, business cases, multithreading, and sales enablement.
"My champion's running pricing up the flagpole, so we're at 50%."
That's something I've said about a lot of deals. Which subsequently exploded.
Your champion can be all-in on the project, but map the rest of the group against the buying process and you'll usually find a manager selecting a vendor, a VP still debating the approach, an operations team that hasn't committed to the problem, and an executive focused on a different priority altogether. All inside a single deal record, with one probability attached to it.
So the standard advice kicks in: multithread, which usually gets heard as "add more names to the CC line."
But in 1944, the OSS (the CIA's predecessor) wrote a field manual teaching ordinary people how to quietly sabotage enemy organizations from the inside, and one of its tips was to refer everything to committees "for further study and consideration," and to "make the committees as large as possible." Never less than five people. Which means adding people to a decision, by itself, is a documented sabotage tactic.
So which is it, is a single-threaded deal fragile or is a big committee dysfunctional? Both. The job is to add the people the decision actually needs, at the stage it needs them, and then stop.
Multithreading means building relationships with several people in a buying group, so your deal doesn't live or die with one contact. The way I'd put it: you're getting the right people into the conversation at the right stage, and tying them together with one message they can all repeat. If those threads never connect to each other, you've just opened more loops to follow up on.
So the question worth asking in your next deal review is whether this group can make a decision together, and what you can do to help them get there.
A few reasons:
Put those together and a responsive champion can hide a fragile deal. If your sale feels too smooth, there's a good chance your champion is sanding down the friction alone, settling every disagreement before you ever see it.
Yes. Every person you add is a relationship that has to stay aligned with every other person in the group. Fred Brooks did this math for software teams in The Mythical Man-Month back in 1975: n people = n × (n − 1) / 2 lines of communication. So six people = 15 handshakes to keep in sync, and twelve people = 66.
CEB (now part of Gartner) put numbers on what that does to a purchase. In their research, purchase likelihood fell from 81% with one decision-maker to 55% with two, and to 31% with six (Harvard Business Review, 2015). The data stops at six. I think they didn't want to scare us with what happens after that.
So why do committees keep growing? Usually because confidence is low, and unconfident groups do one of two things:
Both add people who can say no without adding anyone who can say yes. Pair that with the enterprise's favorite decision, doing nothing, and you can see why close rates fall as the circle swells. So treat an ever-growing committee as the canary in the coal mine, and aim for a minimally viable committee: just enough people to confirm the problem, build the use case, and clear the contract.
Start with who can say no. There's no such thing as one decision-maker: there may be one economic buyer who signs the contract, but everyone in the group who can say no is a decision-maker too, because "no" is just as clear a decision as "yes."
And influence rarely follows the org chart. It lives in social capital, internal reputation, and back-channel conversations more than in hierarchy and formal approvals. One of the best questions I know for surfacing it: "Is there someone you often turn to for advice on new projects?" It pulls people out of the shadow org chart and into your committee.
Then plot everyone on two axes, influence (can they change the direction of the decision?) and advocacy (are they for it?):
For each person, note the part of the decision they own or can veto, their #1 goal this year, and the stage where you'll need them. That last one is what keeps you from adding contacts at random.
Threading the needle between a dozen people's goals is tough stuff, and the simplest tool I've found for tying them together is two words, which means, linking each layer of the group to the next:
Reps spend more time prospecting than managing pipeline, which means... sales directors don't have the coverage to hit team quota, which means... the SVP misses their goal of returning 4x each seller's fully loaded cost.
Now the rep, the director, and the SVP can all see themselves in the same sentence, and a sharp 4-sentence soundbite is the version of that chain short enough to be retold in rooms you'll never enter.
Sequence your threads by what the decision needs at each stage. Adding a VP because your manager asked "are we multithreaded?" in pipeline review is how you end up with random threads. So ask: what's the gap at this stage, and who closes it?
The first row is the one most teams skip. Get high early, win later: surface the economic buyer in discovery, before you build any business case, instead of treating them as a prize at Propose.
The other row that bites late is Propose. In a recent pipeline review with an enterprise team, sellers kept protecting the deal from security, legal, IT, and procurement until they "had a yes," and those teams kept surfacing at Negotiate and adding weeks. So ask "What's your vendor onboarding process?" while you're still qualifying. Procurement isn't paperwork, it's a gate with a vote.
Work with them, not around them, whenever you can. In practice that's five moves:
Most of those moves happen in writing, which is why the forwardable email is the cheat code for multithreading. And once the group agrees on why to act, which is the job of a 1-page business case, a mutual action plan keeps every thread pointed at the same date.
Some conflict is healthy, it means people care enough to disagree. But when a right-fit deal keeps stalling, you're usually looking at two kinds of problems. Math problems have solutions: they're about what you're selling. Drama doesn't: it's about people, and the stories they tell themselves about their jobs. And math problems usually go unsolved because of the drama around them.
One case from Selling With: a retailer's customers couldn't find answers in their help content, so they kept asking for a human. The math problem was simple (more inquiries than staff), and a search tool that understood the intent behind a question fixed it. It still took forever, because:
Making sense? The drama was keeping each of them safe, needed, or blameless, and the deal moved once each one had a new story to believe, like the support manager finally being free to work on more meaningful projects. So when a deal with an obvious ROI keeps getting blocked, find the need the drama is meeting, and help your champion connect the fix to that same need. I totally learned this framework from my own therapist, by the way.
Here's a deal I've walked teams through in workshops, with the names taken out. The buyer was a fast-growing franchise restaurant brand with a couple hundred locations, a two-person customer experience team buried in more than ten thousand pieces of feedback a year, no budget, a CFO who'd already said no, and owners who almost never talked to sellers.
It closed after 23 meetings, with the group mapped by role instead of title. As one of the champions put it: "I don't find titles all that relevant. I do find ears really relevant."
The org chart said the gatekeeper was a lawyer. It was the champion who knew she was the gate, which is the whole case for mapping the group with your champion.
Run through these on your biggest open deal:
Multithreading isn't always the move. A few times it backfires:
Pick your biggest open deal and do three things before Friday:
Then use the multithreading email templates to open the threads you're missing.