Gartner says the average B2B purchase involves 6 to 10 stakeholders. The average account plan in your CRM probably names three.
That gap is where most deals die. A rep who maps three names and missed the security review, the procurement gate, and the skeptical VP who never showed up to a demo is going to lose to a rep who mapped all ten.
This post covers who sits on a modern buying committee, how to map them, the data on committee growth, and how to build coverage when you cannot reach everyone directly.
What a buying committee is
A buying committee is the group of people inside a company who collectively decide on a purchase. Some buying committees are formal, with a charter and a budget. Most are informal, with shifting members and unspoken authority.
The committee is sometimes called the buying group, the decision making unit, or the DMU. The terms are interchangeable.
The committee is not the same as your champion's team. It is everyone who can say no, slow the deal down, or change the scope.
Who is on a typical buying committee
Most buying committees include some version of the following nine roles. One person can hold multiple roles. Multiple people can hold the same role.
The economic buyer
The person who controls the budget and signs the contract. In smaller deals, this might be a director. In enterprise deals, it is often a VP or the C suite.
Economic buyers care about ROI, risk, and strategic fit. They rarely care about features.
The technical buyer
The person who validates that the product works and meets technical requirements. In software deals, this is often an architect or a senior engineer. In services deals, it might be a domain expert.
Technical buyers can veto a deal. They rarely advocate for one. Your job is to remove their objections.
The user
The person or team who will actually use the product daily. Users care about workflow, time saved, and how the product compares to their current tool.
Users are powerful in adoption decisions. They are weaker in budget decisions, but their resistance can kill a deal during implementation.
The champion
Your internal advocate. The champion sells for you when you are not in the room. They know the political landscape, who matters, and what objections will surface.
A champion is not the same as a friend. A friend likes you. A champion has skin in the game and is willing to spend political capital to push the deal forward.
For more on champion development, see our stakeholder analysis guide.
The coach
A coach gives you intel without sponsoring the deal publicly. They tell you who is for and against. They warn you about budget shifts. They are often outside the buying committee but adjacent to it.
You usually have multiple coaches in a complex deal. You typically have only one champion.
The blocker
The person who actively opposes the deal. Sometimes the blocker has a substantive concern. Sometimes the blocker is protecting a competitor relationship or an internal initiative.
A blocker who stays unnamed is a deal killer. A blocker you have mapped can be neutralized, isolated, or converted.
Legal
The legal reviewer who marks up the MSA, the DPA, and the order form. Legal will not advocate for the deal, but they can stall it indefinitely.
Engage legal early. The deals that fall apart in legal at quarter end usually had legal show up two weeks before close.
Security and IT
Security review is now table stakes for any B2B software deal of meaningful size. Expect a SIG, a CAIQ, a SOC 2 review, and likely a separate vendor risk assessment.
In larger enterprises, this is its own team with its own queue. The queue is your enemy. Surface security review at the start, not the end.
Procurement
Procurement enters at the contract phase. Their job is to extract a discount, lengthen payment terms, and standardize the agreement. They are evaluated on savings.
You will not avoid procurement. You can prepare for them by establishing value early with the economic buyer, so when procurement compresses price, the buyer pushes back.
The data on committee size
The Gartner number is 6 to 10 stakeholders. That is an average across deal sizes.
Forrester research has shown the same trend over time. Buying groups have grown roughly 20 percent over the last decade as products get more cross functional and risk reviews get more rigorous.
For deals over 100K ACV, expect 8 to 14 stakeholders. For deals over 500K ACV, expect 12 to 20.
The growth is real and structural. Software is harder to deprovision than it used to be. Data security is harder to assess. Vendor sprawl is a board level concern. All of that adds bodies to the committee.
Why most plans only map three names
Three names is what fits in a CRM contact field. Three names is what reps can remember without a tool. Three names is what shows up in the discovery call.
It is also wildly insufficient. Three names misses the security reviewer who has not been introduced yet. Three names misses the VP who heard about the deal in a leadership meeting. Three names misses the procurement lead who will appear two weeks before close.
The reps who map ten names early are the reps who close. The mapping is the work.
How to map the committee
Mapping is a sequence, not a snapshot. Run it across the deal lifecycle.
Step 1: Ask the champion
In the second or third call, ask the champion who else needs to weigh in. Ask specifically about budget owner, technical owner, security review, and procurement.
Champions almost always undercount. They tell you who they have talked to. Push for who they have not talked to yet.
Step 2: Pull the org chart
LinkedIn, ZoomInfo, and your CRM history together can tell you who reports to whom. Build the org chart for the relevant department and the adjacent functions.
You want to know not just the committee but the committee's bosses. The VP who does not show up to demos still influences the decision in the leadership meeting.
Step 3: Identify gaps
Compare your map to the typical committee structure. Do you have a name for every role? If not, that is your gap.
A deal with no named technical buyer is not a real deal. A deal with no procurement contact is going to slip on contract.
Step 4: Build coverage
Coverage means you have a path to every named role. Either direct contact, a champion who covers them, or a multithread plan to reach them.
Map the relationships. Who has met whom. Who has talked. What they said. The map should answer those questions for every committee member.
For tactics on multithreading, see our relationship mapping playbook.
Common committee mapping mistakes
Five mistakes kill committee maps.
Mistake 1: Treating the org chart as the committee
The org chart shows reporting relationships. The committee shows decision dynamics. They overlap but are not identical.
A senior engineer with no direct reports can be the technical buyer. The CTO might not show up to a single call. Map decisions, not titles.
Mistake 2: Confusing coach with champion
A coach gives you intel. A champion takes a risk for you. Reps over count champions because every nice contact feels like a champion.
If a contact has not done something specific to advance your deal, they are not a champion yet. They might be a coach, or they might just be polite.
Mistake 3: Ignoring the blocker
Reps avoid blockers because blockers are uncomfortable. Avoiding them does not make them go away. It just means they show up at close instead of mid cycle.
Map the blocker. Understand the objection. Decide whether to convert, isolate, or accept the loss.
Mistake 4: Single threading
A single threaded deal lives or dies on one relationship. If your champion leaves, gets reorganized, or loses political capital, the deal evaporates.
Multithread early. The cost is a few extra meetings. The benefit is a deal that survives normal organizational chaos.
Mistake 5: No update rhythm
The committee changes during the deal. Members get added. Members get reorganized. The map you built in week two is not the map at week eight.
Update the map weekly during active deals. The 30 seconds it takes to add a new name pays back ten times.
Building coverage when you cannot reach everyone
You will not get a meeting with every member of a 12 person committee. That is fine. Coverage is not the same as direct contact.
Coverage means three things are true. You know the name. You know the position the person will likely take. You have someone inside the account who will represent your case to that person.
If you have all three, you have coverage. Even if you never get a call with the person.
For deals where direct access is impossible, lean on your champion to deliver materials. Build a one pager that addresses the specific objection the absent stakeholder is likely to have. Make it easy for the champion to forward.
This is also where account mapping becomes critical. The map is the artifact your champion uses to navigate the rest of the org.
Related reading
Bring this into Salesforce with CRUSH
A buying committee map is a relationship map. CRUSH puts the map in Salesforce, next to the account record where the rep already works. Stakeholders, roles, sentiment, and influence lines are all visible. When the committee changes, the map updates. When the team reviews the deal, the gaps in coverage are visible at a glance.
The reps who map ten names instead of three are the reps who close. CRUSH makes the mapping part fast enough that they actually do it.
See how CRUSH visualizes the buying committee inside Salesforce.
