The B2B Buying Committee: What It Is and Why It Makes Deals Stall

Most B2B purchases involve six to ten stakeholders, each with different priorities, different levels of familiarity with the solution, and different criteria for what a good decision looks like. Understanding how buying committees work is one of the most practical things a revenue team can do.

Key takeaways

• A buying committee is the group of stakeholders within an organisation who are involved in a B2B purchase decision. Modern committees typically include six to ten people across multiple roles.
• Gartner research found that 74% of B2B buying teams demonstrate unhealthy conflict during the decision process. That conflict is the primary reason deals stall.
• Buying committees do not fail because individual stakeholders are unreasonable. They fail because each stakeholder is working from a different and often incompatible understanding of the problem and the solution.
• The champion is the person most invested in the decision. Equipping the champion is necessary but not sufficient. Every other stakeholder also needs access to accurate information on their own terms.
• Buyer enablement addresses buying committee dynamics directly: it provides the governed, accurate, role-specific information that each stakeholder needs to form a consistent and sufficient understanding.

B2B sales training has long focused on finding the champion: the internal advocate who wants the solution, has influence over the decision, and will carry the deal forward. That focus is reasonable. The champion matters.

But the champion is one person in a buying group that typically includes five to nine others. Each of those others has opinions, concerns, and the ability to slow or stop a decision. The champion who cannot bring the buying committee with them is not, in practice, very useful.

Understanding how buying committees form and where they break down is not an advanced topic in B2B sales. It is a foundational one. And the research on what happens to buying committees is sobering. Gartner found that 74% of B2B buying teams demonstrate unhealthy conflict during the decision process. That figure is not a marginal exception. It describes the majority of complex B2B purchases.

This article explains what a buying committee is, why conflict within it is so common, and what it means for how sales teams approach deals.

What is a buying committee?

A buying committee is the group of stakeholders within a buying organisation who are involved in a purchase decision. Gartner defines the group broadly: it includes everyone who has a formal or informal role in evaluating, approving, or influencing the outcome. In practice, that typically means six to ten people across multiple functions, seniority levels, and areas of the business. Research from Intentsify tracking how buying groups have evolved found that the average buying group for enterprise software decisions has grown steadily over the past decade, with more stakeholders involved at earlier stages of the process than was typical five years ago.

The composition varies by organisation and deal type, but the common roles present in most complex B2B purchases include:

• An economic buyer, typically a CFO or VP of Finance, who controls budget and needs commercial justification.
• A technical buyer, such as an IT lead or solution architect, who evaluates integration, security, and implementation requirements.
• End-user representatives, often operational leads or team managers, who assess practical usability and workflow impact.
• An executive sponsor, who provides strategic sign-off and whose support is often required for final approval.
• A champion, the internal advocate who has identified the problem, wants the solution, and is managing the internal process.

The challenge is not the size of the group. It is that each member of the group approaches the evaluation from a different starting point, with different prior knowledge, different concerns, and different criteria for what a satisfactory answer looks like.

Why buying committees create conflict

The 74% conflict figure from Gartner is striking, but it should not be surprising. The conditions that produce buying committee conflict are structural, not incidental.

Different stakeholders research independently

McKinsey’s B2B Pulse research found that buyers now use an average of 10.2 channels across their buying journey, up from 5 in 2016. Those channels include vendor websites, third-party review platforms, analyst reports, peer communities, AI-assisted search, and informal conversations with colleagues in other organisations. Different stakeholders consult different sources and form different impressions.

A CFO who reads an analyst report on total cost of ownership for a software category will form a view of what reasonable pricing looks like. An IT lead who consults a peer community about implementation timelines will form a view of what a realistic deployment looks like. Neither of those views may be accurate in relation to the specific vendor under consideration. And they will almost certainly be different from each other.

When those stakeholders arrive at the same internal discussion, they are not evaluating the same thing. They are each defending a mental model formed from different sources, and the discussion that follows is as much about reconciling those models as it is about evaluating the vendor.

The champion cannot be everywhere

The champion typically has the most complete understanding of the solution being evaluated. They have attended demonstrations, asked questions, and formed a reasonably accurate view of what the product does and how it compares to alternatives.

They cannot replicate that understanding for every stakeholder. Internal briefings are compressed. Presentations cover the headline points but not the depth of detail that each stakeholder’s specific questions require. The CFO who needs to understand the pricing model in detail will not get that from a fifteen-minute summary prepared by a project manager.

What the champion can share is their own understanding. And if their own understanding has gaps, those gaps propagate into the wider buying committee’s view of the solution.

Confident misunderstanding compounds the problem

The most difficult version of the buying committee problem is not when stakeholders say they do not have enough information. It is when they believe they do. The glossary on this site defines confident misunderstanding as the state in which a buyer holds an incorrect view of a solution based on incomplete or inaccurate research, without being aware that their view is wrong.

Confident misunderstanding is harder to address than a simple information gap. A stakeholder who says they have a question can be given an answer. A stakeholder who believes they already understand, but is mistaken, will interpret new information as a contradiction rather than a correction. That interpretation produces resistance, which looks to the selling team like a late-stage objection but is actually a consequence of how the evaluation was conducted.

What the data says about buying committee outcomes

The Gartner research on buying committee conflict published in May 2025 found two things that belong together. The first is that 74% of buying teams demonstrate unhealthy conflict during the decision process. The second is that buying teams which achieve alignment before making a decision are 2.5 times more likely to rate the quality of their decision as high.

That second finding is as important as the first. The buying committee conflict problem is not just a sales problem. It is a buyer decision-quality problem. Organisations that make purchase decisions under conditions of unresolved conflict arrive at worse outcomes, are less satisfied with what they chose, and are more likely to struggle with adoption and realisation of value after the contract is signed.

Forrester’s State of Business Buying research supports this from a different angle. It found that 86% of B2B purchases stall during the process and that 81% of buyers are dissatisfied with their chosen provider even after completing a purchase. Both figures are consistent with an environment in which buying decisions are made under conditions of inadequate shared understanding.

The implication is not only that unresolved conflict damages the vendor’s chance of winning a deal. It also damages the buyer’s outcome when they do make a decision. The problem is symmetrical.

Why the standard response is not sufficient

The most common sales response to buying committee complexity is multi-threading: building relationships with multiple stakeholders simultaneously, rather than depending on the champion to carry the deal. Multi-threading is a sensible practice and a genuine improvement on single-threaded selling.

It does not, on its own, solve the problem.

Multi-threading ensures that the selling team has contact with multiple stakeholders. It does not ensure that those stakeholders have a consistent, accurate understanding of the solution. A sales representative who speaks separately to the CFO, the IT lead, and the executive sponsor may conduct three excellent individual conversations and still leave each stakeholder with a slightly different understanding of what they evaluated.

The problem is not the quality of the conversations. It is what happens between them. Stakeholders return to their own research, discuss the solution with colleagues the sales team has not spoken to, and continue forming views from sources the selling organisation has no visibility into. The next internal discussion picks up from whatever those individual stakeholders have concluded in the interim.

Addressing buying committee dynamics properly requires more than frequent contact. It requires giving each stakeholder the ability to access accurate, governed information independently, on their own timeline, in response to their own specific questions. What buyer enablement looks like in practice works through how this is implemented across the four stages of the buying journey.

What effective buying committee support looks like

The organisations that navigate buying committee complexity most effectively share a common approach. They treat each stakeholder as a distinct audience with distinct needs, rather than assuming that the champion’s understanding will be sufficient to bring the group along.

Role-specific information

Each stakeholder type has a predictable set of concerns. A reference table is below. The practical implication is that a single deck or proposal will not adequately serve all of them. The CFO’s questions about total cost of ownership are not the same as the IT lead’s questions about data architecture. Providing role-specific information is not a luxury for large deals; it is a prerequisite for well-supported buying committee decisions.

Champion enablement

The champion needs specific support to run the internal process effectively. They need materials they can share that will hold up under scrutiny from stakeholders who were not in the original sales conversations. They need answers to the objections they know will arise. They need a way to brief executive sponsors that does not require them to become product experts.

What the champion does not need is more sales collateral designed for external audiences. Internal briefing materials have different requirements: they need to be honest about trade-offs, specific about implementation detail, and credible to a sceptical colleague rather than persuasive to an interested prospect.

Asynchronous access to accurate answers

Much of what buying committees need to resolve their differences cannot be scheduled. A CFO who has a question after reading a proposal at 8pm cannot wait for the next sales call. A security architect who needs to understand how a platform handles a specific compliance requirement before an internal review needs that answer before the review, not after. The buyer enablement tools landscape covers the platforms that have emerged to support this kind of asynchronous, role-specific access.

Frequently asked questions

How many people are typically in a B2B buying committee?

Most research points to six to ten stakeholders for complex B2B purchases, though the figure varies significantly by organisation size, deal value, and industry. Gartner’s buying committee research consistently identifies groups of this size across enterprise software decisions. Smaller organisations with less formal procurement processes may involve fewer people; highly regulated industries or large public-sector organisations may involve more. The relevant number is not the total headcount but the number of people with a meaningful ability to slow or stop the decision.

What causes buying committee conflict?

The most common cause is not disagreement about objectives. Most members of a buying committee share broadly similar goals: they want a solution that works, is affordable, is implementable, and reduces rather than creates risk. The conflict arises from different understandings of whether a specific solution meets those criteria. Those different understandings come from different sources of information: different research, different conversations, different prior experiences with similar solutions, and different interpretations of the same vendor materials. When stakeholders arrive at internal discussions having formed different mental models from different inputs, the discussion that follows is as much about reconciling those models as it is about making a decision.

What is the difference between a buyer champion and an economic buyer?

The champion is the stakeholder who is most invested in solving the problem and most actively managing the internal evaluation process. They are typically the person who initiated the search for a solution and who will benefit most directly from its success. The economic buyer controls the budget and must approve the commercial commitment. In some organisations the champion and the economic buyer are the same person; in many they are not. The distinction matters because the champion may have the most complete understanding of the solution but the least authority to approve the purchase, while the economic buyer may have the authority but the least detailed knowledge. Both need to be convinced, and they need different information to get there.

What is multi-threading in B2B sales?

Multi-threading is the practice of building relationships with multiple stakeholders within a buying organisation simultaneously, rather than relying on a single champion to carry the deal. It reduces the risk of a deal collapsing because a champion leaves the organisation, loses internal support, or is unable to answer questions raised by other stakeholders. Multi-threading is a sound practice and a genuine improvement on single-threaded selling. It does not, on its own, ensure that the multiple stakeholders the selling team is now speaking to have a consistent and accurate understanding of what they are evaluating.

Why do deals go dark after appearing to have momentum?

Deals go dark most often because the champion has encountered an internal barrier they cannot resolve on their own. That barrier is typically one of three things: a stakeholder objection they cannot adequately answer, a misconception that has taken hold among decision-makers and that the champion cannot correct without appearing to undermine their own advocacy, or an alignment conversation between committee members that has stalled. In all three cases, the underlying cause is a gap between what some stakeholders believe about the solution and what the solution actually does.

How does buyer enablement address buying committee dynamics?

Buyer enablement addresses buying committee dynamics by ensuring that the governed, accurate explanation of a solution is accessible to every stakeholder, not just the one who attended the initial sales call. It means a CFO can explore financial implications independently. A CISO can assess security architecture without routing every question through a sales representative. A project manager can understand what implementation actually involves before the internal approval process begins. When each stakeholder can access accurate, role-specific information on their own terms, the understanding they bring to internal committee discussions is more consistent and more complete.

Sources