The deal was going well. The champion was engaged, responsive, pushing things forward internally. The demo went great. The proposal was sent. Then it went quiet for three weeks, followed by an email saying the company had decided to go a different direction.

Nobody on your sales team ever spoke to the CFO who killed it.

That's the defining failure mode in B2B sales right now: deals that were genuinely progressing with one person, dead at the hands of someone your team never identified, never contacted, and never had a chance to influence. The champion wasn't lying about their enthusiasm. They just couldn't close the room on their own.

The buying group got bigger and nobody told your sales process

A decade ago the average B2B purchase involved two or three stakeholders. Today it's six or more on most mid-market and enterprise deals, and that number keeps climbing as companies get more deliberate about procurement risk and cross-functional buy-in.

Most sales motions haven't caught up. They're still built around one relationship — find the champion, qualify through the champion, present to the champion, close the champion. That model made sense when it matched how deals actually got done. It doesn't anymore, and it's a big part of why win rates keep sliding even as outbound volume goes up.

The deals that close in a consensus environment aren't won by better champions. They're won by teams that mapped the full buying group early and gave every person with influence a reason to say yes, or at least no reason to say no.

The stakeholder map most teams skip

A real stakeholder map isn't a list of everyone your rep has met. It's everyone with influence over the decision — their role, their likely concerns, their relationship to the champion, and whether your team has actually talked to them. The blank cells on that map are where deals go to die.

Most reps skip this because it means asking the champion an uncomfortable question. "Who else will be involved in this decision?" can sound like you're questioning whether their support is enough. Reframe it instead: "Who else should we make sure is set up for success as we roll this out?" Same question, but now it reads as service instead of skepticism.

Do this early enough and you'll almost always find someone the champion forgot to mention — the CFO who has to sign off above a certain threshold, the security team that gates new software, the VP whose quiet resistance can kill a deal without ever becoming an explicit objection. Finding them in week two is useful. Finding them in week eight, after the proposal's already in, usually isn't.

What multi-threading actually looks like

Multi-threading isn't blasting the same outreach at everyone in the account — that just irritates your champion and signals your team has no coordination discipline. It's deliberate: identify the two or three stakeholders whose buy-in matters most, and find a real reason to engage them directly rather than relaying everything through the champion.

For a CFO, that might mean proactively building an ROI model that speaks to their concerns and offering to walk them through it. For IT or security, it's your solutions engineer reaching out to cover the questions the champion can't answer. For an end-user team lead, it's a demo scoped to their workflow instead of the executive overview the champion sat through.

Not every champion welcomes this — some see it as going around them, some just prefer to run point the way they always have. Push through it anyway. A champion who won't allow multi-threading is usually overestimating their own internal pull, and deals that stay single-threaded at their request close at a noticeably lower rate. The line that tends to work: "Deals go smoother when the people most affected get a chance to weigh in early. Can we grab 20 minutes with [stakeholder] on [topic]? It usually heads off the questions that slow things down later." That's a pitch about reducing risk for the champion, not about distrusting them.

What this means for coaching your team

Here's a diagnostic worth running this week: pull your last 20 closed-lost deals and count how many stakeholders your team had a real conversation with in each one. Do the same for your last 20 closed-won deals.

The gap between those two numbers will tell you more about your win rate than any amount of call recording review. Teams that win in consensus environments have more relationships per deal, earlier in the cycle. Teams that lose are still running single-threaded and blaming price or timing.

So change what you inspect in deal reviews. Instead of "what did the champion say," ask "who else is involved," "have we spoken to them directly," and "what are their concerns and do we have a plan for them." Ask it every review and reps start paying attention to it during the deal — because what gets inspected gets managed.