How B2B buying committees actually decide, and what it means for the way you sell
Most enterprise deals are decided in meetings you're not invited to. How buying groups research, build consensus and kill deals, and how to sell to that.
, 4 min read, B2B buyers
Key takeaways
- Buyers spend most of the purchase process researching independently and aligning internally. Time with any single vendor is a small slice of the whole.
- Deals are lost more often to indecision and internal disagreement than to a competitor. The seller's job is to reduce the group's risk of being wrong.
- Multithreading is not optional. A single champion, however enthusiastic, cannot carry a decision through a committee they do not control.
- The most valuable thing you can hand a champion is material they can forward: a one-page business case, a security summary, a rollout plan.
Ask a seller why a deal was lost and you will hear about price, a competitor's feature or a champion who "went dark". Ask the buyer and you get a different story: the group could not agree, the risk felt too high, or nobody wanted to own the decision. Both accounts are honest. They describe different meetings.
Understanding how a buying committee works is the difference between selling to a person and selling to a decision. This article describes the process from the buyer's side and draws out what it means for the way you run a deal.
The process from the inside
Research happens before you are contacted
By the time a prospect fills in a form or takes a call, they have typically already read review sites, asked peers, watched a demo video and formed a shortlist. Gartner's research on B2B buying has for years pointed out that buyers spend only a small share of their total buying time with any one vendor's sales team. Most of the time goes to independent research and internal meetings.
Two consequences follow. First, the seller often meets a buyer who is further along than they let on. Second, the content on your website, your reviews and your community presence are doing a large part of the selling before a rep is involved.
The group forms around a problem, not a product
A buying committee rarely starts as "we need to buy category X". It starts as an operational pain that someone escalates, a budget line that opens up, or a mandate from above. The people who assemble around it have different jobs to do:
| Role | What they care about | What kills the deal for them |
|---|---|---|
| End users | Will this make my day easier | A tool that adds steps or looks hard to learn |
| Champion | Career credit for solving the problem | Looking naive for backing the wrong option |
| Budget owner | Return relative to alternatives, including doing nothing | An unclear business case |
| IT and security | Integration, data handling, support burden | An unanswered security questionnaire |
| Procurement | Terms, pricing benchmarks, vendor risk | A contract that departs from their template |
| Legal | Liability, data protection, exit terms | Non-standard clauses with no explanation |
Each of these people can slow the deal. Only a few can approve it. Almost all of them can veto it. Selling to the champion alone means betting that one person can win six internal arguments you will never hear.
Consensus is the real product
The committee is not really evaluating vendors. It is evaluating its own ability to make a defensible decision. Research from CEB and later Gartner has repeatedly found that buying groups struggle most with reaching agreement, not with understanding options, and that the larger the group, the more likely the outcome is "no decision".
This is why deals stall late without a competitor in sight. The buyer has learned everything they need and still cannot get the group to commit, because committing means someone owns the risk.
What this means for how you sell
Reduce the group's risk, not only the champion's
The most persuasive thing a seller can offer a committee is evidence that the decision is safe: reference customers in the same industry, a clear implementation plan with named responsibilities, security documentation ready before it is asked for, and honest answers about where the product is weak. Every one of these lowers the personal cost for a member of the group to say yes.
Arm the champion with things they can forward
Your champion will present your solution in meetings you never attend. What they have to work with is whatever you gave them. A one-page business case written in the buyer's language, a short security and compliance summary, and a proposed rollout timeline are worth more than a 40-slide deck. If it cannot be forwarded and understood in two minutes, it will not be.
Multithread early, on purpose
Ask, in the first or second meeting, who else will be involved in the decision and how they usually evaluate tools. Then ask for introductions. Contact with IT, finance and procurement early in the process is not a sign of weakness; it is how you find the veto before the veto finds you.
Sell the decision process, not only the outcome
Buyers often do not know how to buy your category. Offering a structured evaluation plan with milestones, a mutual action plan with dates, and clear criteria for the pilot gives the group a shared map. It also gives you a legitimate reason to check in that is not "just following up".
Treat "no decision" as your main competitor
Your forecast should assume that inertia, not the rival vendor, is the most likely reason a deal does not close. Build the case for change explicitly: what the cost of the current situation is, what happens in twelve months if nothing changes, and who inside the company will feel it. If the buyer cannot articulate this, the deal is not real yet, however warm the champion.
A short diagnostic
Before you forecast a deal as likely to close, answer these five questions honestly:
- Have you spoken to the person who controls the budget, not just the person who wants the tool?
- Has security or IT seen documentation, and have they raised objections you have addressed?
- Does the champion have a business case they could present without you in the room?
- Do you know how the group will actually make the decision: a vote, a sign-off chain, a single executive?
- Has procurement or legal seen your paper?
If two or more answers are no, the deal is earlier than it feels, whatever the stage says in the CRM.
Frequently asked questions
- How many people are involved in a typical B2B purchase?
- Research from firms such as Gartner has for years put the typical enterprise buying group at somewhere between six and ten people, spanning the end users, the budget owner, IT or security, procurement and legal. The exact number varies by deal size, but the pattern of a group rather than an individual holds across almost every category.
- What is multithreading in sales?
- Building relationships with several stakeholders inside the same account instead of relying on one contact. It reduces the risk that a deal dies when one person goes quiet, and it gives the seller a fuller picture of how the group will decide.
- Why do deals stall at the end of the process?
- Usually because the group has not reached consensus, not because they prefer a competitor. Late-stage stalls are often a sign that someone with veto power was never engaged, or that the buyer is unsure how to justify the decision internally.