The Eleven-Stakeholder Problem Nobody Mentions on the Sales Call

I had a deal sitting at late stage for six weeks. My champion was enthusiastic, the business case was tight, and every conversation went well. Then procurement went quiet. Then my champion stopped replying. Then a short email arrived: "We've decided to go a different direction."

Nobody mentioned the IT director who had built the existing solution. Nobody told me he sat on the vendor evaluation committee. I never spoke to him once.

That deal taught me more about buying committees than any training course. The problem was never the product or the price. The problem was that I had one thread in a rope that needed eleven.

The number that should change how you prospect

Gartner's research on B2B purchasing puts the average buying committee at six to ten people. More recent data from Forrester pushes that figure past eleven for mid-market and enterprise deals. Read that again. Eleven people with competing priorities, different definitions of success, and varying degrees of influence over a decision that affects all of them.

Most salespeople build one relationship and call it a pipeline. That is not a pipeline. That is a single point of failure dressed up as progress.

A champion who backs you is not the same thing as a deal that closes. One is an opinion. The other requires a committee.

Matthew Dixon and Brent Adamson documented this dynamic in The Challenger Sale. The most dangerous moment in a complex sale is when you mistake champion enthusiasm for organisational alignment. Your champion believes in you. The procurement lead has three other vendors. The CFO wants a two-year payback. The IT director thinks the integration will take eighteen months. These are not the same conversation.

Multi-threading is not a tactic. It is the baseline.

Multi-threading means engaging multiple stakeholders across multiple functions before the deal reaches its critical stage. Not bombarding people with emails. Not going around your champion. Mapping the committee, understanding each person's stake in the outcome, and building genuine relationships across the organisation.

The practical starting point is simple: ask your champion to draw the decision for you. Who signs the purchase order? Who has to live with the implementation? Who approved the last technology purchase of this size? Who could block this if they wanted to? That last question is the one most people skip.

In Never Split the Difference, Chris Voss writes about the importance of identifying decision-makers you have not yet met. His framing: assume there is always someone you have not spoken to who can kill the deal. In my experience, he is right every time.

The person behind the table

There is a concept in negotiation and sales strategy called the behind-the-table deal killer. This is the stakeholder whose autonomy, budget, or authority is threatened by your solution. Not because your solution is poor, but because it represents change they did not initiate.

They rarely appear on the formal org chart of decision-makers. They appear in the internal meeting after your presentation, the one you are not invited to. They say things like "the timing isn't right" or "we need to think about integration complexity" or "I'm not sure this aligns with the roadmap." These are not objections. They are the language of someone protecting their position.

The behind-the-table deal killer rarely objects to your face. They object in the room you never enter.

The only way to neutralise this is to find them early and make their concerns visible. Ask your champion directly: "Who in your organisation has built something we'd be replacing? Who owns the current process?" Then find a reason to involve that person in the evaluation, not as a threat to be managed but as a voice whose experience carries real weight.

What multi-threading looks like in practice

Start mapping the committee from the first discovery call. Not every name, but the stakeholder landscape. Who owns the budget? Who owns the problem? Who owns the infrastructure that has to support the solution? Who will be measured on the outcome twelve months after go-live?

Each of those people has a different version of success. The business owner wants speed and adoption. The CFO wants return on investment and risk mitigation. The IT director wants clean integration and minimal disruption. The end users want something that does not make their job harder. If you are only talking to one of these people, you are only solving for one definition of success, and the others will surface as late-stage objections.

The most underused tool here is the executive sponsor call. Ask your own leadership team to engage their peer at the prospect organisation. Senior-to-senior conversations carry a weight that peer-level calls cannot match, and they signal that your organisation takes this relationship seriously beyond the initial sale.

The thread that never breaks

None of this replaces a strong champion relationship. Your champion is the person who understands the internal politics, who can tell you when something has shifted, who advocates for you in the rooms you cannot enter. Protect that relationship. Build on it.

What multi-threading adds is resilience. Champions change roles. Reorganisations happen. Budget cycles shift. A deal built on eleven relationships survives disruptions that a single-threaded deal cannot.

The IT director who might have killed my deal six weeks in: with a different approach, he could have been one of the strongest voices in favour. He knew the existing system's limitations better than anyone. He had been asking for a replacement for two years. I just never asked him.

That is the eleven-stakeholder problem. Not that there are too many people involved. That most of us only talk to one of them.