B2B buying committee: how to map who decides and who blocks

The B2B buying committee is the group of people at the buying company who influence, approve or veto a purchase, and a deal tends to die on the desk of one of them whom your salesperson never met. The contact liked the proposal, said they would take it to the director, and the answer that came back was “let’s leave it for next year”. If you lead sales or a portfolio of accounts, the map of that committee needs to exist before the proposal, with each person’s role recorded in the CRM and a plan for whoever is not yet in the conversation. Mapping who decides and who blocks is a skill the team learns by practicing on its own accounts, and it is up to leadership to define that a deal without a mapped decision maker does not go into the quarter’s number.

When I open a client’s funnel at the proposal stage, the picture repeats: most deals have a single associated contact, the same one from the first form. The decision maker field, when it exists, holds the contact’s name. Among losses, the most used reasons are “no response” and “internal decision”, and no record says who decided against it, or why. Leadership sees a full funnel and a forecast that slips at the end of every quarter.

What is a B2B buying committee?

A buying committee brings together everyone who takes part in the decision on a complex purchase, with or without a formal role in the process. Some of these people show up in meetings, like the manager of the user area. Others stay outside the room and weigh more on the decision, like the director who approves the budget, the IT team that assesses security and the legal team that reviews the contract. In consultative selling, finding out who takes part in the decision is part of discovery from the first meeting.

The size and friction of this group explain a good share of the deals that stall at the finish line. In a survey of 632 B2B buyers conducted from August through September 2024, Gartner, in 2025, found unhealthy conflict in 74% of buyer teams, with members holding conflicting objectives, disagreeing on the best course of action or being overruled by external decision makers. The same survey describes groups of five to 16 people across as many as four functions, and shows that groups that reach consensus are 2.5 times more likely to report that their deal was high quality. For your team, this means that convincing the contact solves a small part of the problem.

What are the roles in a buying committee?

I work with seven roles. One person can hold two of them, like the director who uses the solution and approves the budget, and a role can stay empty in a smaller purchase. For each deal, the salesperson needs to know who holds each role, what that person wants, what they fear and what question they will ask in the internal meeting.

Role	What they want	What they fear	What they ask
User	Less rework and a simpler routine	More work during the transition and losing control of what they do today	“What does my day look like in the first week?”
Economic buyer	Return within the year’s timeline and budget	Approving an investment that does not deliver and answering for it to the board	“How much does it cost, how long until it pays back and what happens if we don’t do it?”
Technical or IT	Integration with current systems, security and support	Inheriting a troubled project after signature	“How does it integrate, where does the data live and who provides support?”
Legal or procurement	A contract within policy and a fair comparison between vendors	Non-standard clauses and a vendor without approved registration	“What are the terms and liabilities, and who else quoted?”
Influencer	Seeing their own experience reflected in the choice	Being held responsible for a decision they had no say in	“Why this option, and not the one we already know?”
Internal champion	Solving the problem and getting credit for it	Backing the project and losing, left exposed	“What do I take to convince the director?”
Blocker	Protecting the budget, their own project or the current way of working	Losing ground or budget with the change	“Why now?”, and risk questions the salesperson cannot answer yet

The blocker nobody invited to the meeting

The blocker rarely introduces themselves. It can be the manager of another area competing for the same budget, the owner of the system your solution replaces or the IT analyst who heard about the project after it was ready. In meetings they look neutral, and the veto arrives through a risk question asked to the decision maker in the hallway or through a technical review that takes three weeks. The salesperson who mapped the committee looks for this person early, because an objection heard during discovery still fits into the design of the proposal, and the same objection on the eve of signature becomes a reason to postpone.

How do you map the buying committee?

The map starts in discovery, with questions the salesperson asks the contact in the first meetings. They fit into a normal conversation and reveal roles the org chart does not show.

Discovery question	Role it reveals
“How did you decide the last purchase of this size, and who took part?”	The decision ritual and the roles that repeat
“Up to what amount do you approve on your own, and who approves above that?”	Economic buyer and the contact’s approval limit
“Who will feel this change in their daily work?”	Users and influencers
“Does any area need to assess security, integration, the contract or vendor registration?”	Technical, legal and procurement
“Who benefits from the way things work today?”	Possible blocker
“If this project stops halfway, where does it usually stop in your company?”	Veto point and the history of similar projects

The last question tends to produce the most useful answer, because the contact has seen other projects die and knows on which desk. After the questions, the salesperson asks for access: twenty minutes with the director, a technical meeting with IT before the proposal, the procurement contact to get registration moving. The contact’s reaction to that request also tells you whether they are a champion.

Recording contacts and roles in the CRM

The map needs to live in the CRM, associated with the deal, because the salesperson’s memory does not show up in the pipeline meeting or in the handoff to CS. Each committee member is associated with the opportunity with three fields: role in the committee, from a closed list, relationship level and position on the project. The team records professional data only, within the company’s privacy policy.

The relationship level uses a short scale that two salespeople apply the same way. At level 0, the salesperson knows who the person is and has never spoken to them. At level 1, there was contact by email or in a meeting with other people. At level 2, the salesperson talked with them about the problem and knows what they want and what they fear. At level 3, the person shares internal information and agrees to talk outside formal meetings. Position has four values, supports, neutral, against and unknown, and a decision maker with an unknown position is the alert leadership looks for.

How do you prepare the internal champion?

The purchase decision happens in a meeting your salesperson will not attend, and the internal champion is the person who defends the project in that room. Many salespeople call the contact who likes them and replies fast a champion. A champion passes a practical test: they give access to the decision maker, share what happens in internal meetings and defend the project when you are not there. A friendly contact who opens no doors is a favorable influencer, and the salesperson who confuses the two finds out in the week of the decision.

The salesperson prepares the champion the way they would prepare themselves. Together they build a one-page summary in the buyer’s words, with the problem, the cost the customer attributed to it, the decision being requested and what happens if the company waits another six months. Then they review the questions each role will ask and the answers the champion can give alone, and the unanswered ones become supporting material or a request for the salesperson to join part of the meeting. Many of the objections I describe in B2B sales objections are born in that internal meeting, when the CFO asks about the return and the champion does not have the number.

Action plan by committee role

With the map filled in, the salesperson builds a plan for each role, with an action, a piece of material and someone from your company joining when the role calls for it. In larger accounts, the KAM coordinates this plan with their own company’s technical team, executives and legal.

Role	Salesperson’s action	Supporting material	Who from your company joins
User	Demo based on their current process and a transition plan	First week of use roadmap	Implementation specialist
Economic buyer	Short conversation about the problem and the return, with the discovery numbers	One-page summary and return calculation validated by the champion	Sales director or manager
Technical or IT	Technical meeting before the proposal, without waiting for the formal review	Integration and security documentation	Presales or solution architect
Legal or procurement	Get vendor registration and the draft contract moving early	Standard contract and answers to common clauses	Your company’s legal or finance
Influencer	Listen to their experience and include it in the solution design	Honest comparison with the alternative they know	Salesperson
Internal champion	Prepare the internal meeting and keep weekly contact	Champion kit	Salesperson and manager
Blocker	Talk early, understand what they lose and address the risk they raise	Written answer to the risk objection	Manager or director, depending on their level

If the economic buyer row has no dated action, the deal depends on a meeting the salesperson does not control, and the manager learns this before the forecast.

What does leadership enforce in the pipeline?

The rule that changes team behavior the most fits in one sentence: a deal without a mapped economic buyer does not go into the quarter’s commit. The opportunity at proposal stage needs the decision maker associated, with relationship level 2 or higher and a known position. A deal that does not meet the rule stays in the funnel, in the best case category, and returns to the commit when the salesperson completes the map. The rule protects the forecast and teaches, because the salesperson starts asking for access to the decision maker to get the deal into their number.

In the pipeline meeting, the manager swaps “when does it close?” for questions about the committee. Who on the committee have you not met yet? From whose mouth did the decision maker hear about the problem? When do legal and procurement come in? Has the champion rehearsed what they will say in the internal meeting? Within a few weeks, these questions show which salespeople map by habit and which need coaching.

The metrics come from the CRM the company already uses. The first is the percentage of proposal-stage deals with an associated decision maker and a known position. The second compares the average number of contacts associated with won deals against lost ones, and shows the team, with its own operation’s data, the difference between selling to one person and selling to the committee. It is also worth tracking the share of “no response” and “internal decision” among loss reasons.

A roadmap for leadership

1. Take a baseline. Count how many proposal-stage deals have more than one contact and an identified decision maker, and do the same for won and lost deals from the last six months.
2. Write down the roles and the scale. Define the seven roles, the relationship scale and the position values, with examples from your market, and put them in the playbook.
3. Configure the CRM after the text is approved. Create the fields on the contact to deal association and make the decision maker mandatory for the proposal stage.
4. Map real accounts with the team. In a working session, each salesperson presents the committee for two open deals, and colleagues point out the empty roles.
5. Change the commit rule. Announce the date from which a deal without a mapped decision maker leaves the quarter’s commit.
6. Review every week. Read the metrics in the pipeline meeting and compare them with the baseline at quarter end.

The buying committee is also a marketing and post-sale matter

Marketing: content by committee role

The salesperson can only deliver material for each role if someone produces it. Marketing that receives from the CRM the roles in won deals learns who takes part in the purchase in your market, and that feeds the ideal customer profile and the personas. The content agenda comes from the roles table: security documentation for IT, a return calculation template for the decision maker, answers to common clauses for procurement and customer cases told from the user’s point of view. The material that helps most shows each area what the others gain, and that reduces the internal dispute Gartner measured.

Post-sale and Customer Success: the committee changes after the sale

The committee that signed the contract is almost never the one that decides the renewal. The champion may be promoted or leave the company, the economic buyer changes with the year’s restructuring, and users, who carried little weight in the purchase, become the main voice on the value delivered. If the map reaches CS at handoff, the post-sale team starts out knowing whom to talk to and what each person expected, and then reviews roles and positions at kickoff and at every account review, as I detail in B2B post-sale. The renewal lost because the new director never heard of the project repeats the problem of the sale.

Mapping the committee is a skill: what HR and L&D need to assess

A new CRM field, on its own, produces a map with the contact’s name in every role. The salesperson who has never asked “up to what amount do you approve on your own?” needs to practice the question, hear the evasive answer and push without making the customer uncomfortable. This behavior forms through practice on real accounts, with the manager sustaining the follow-up afterwards, a principle I discuss in sales training that changes behavior. In the consultative selling program I run, the committee exercise uses each participant’s open deals, and the salesperson leaves the room with the map of two accounts and the champion rehearsal scheduled for the following week.

The signs of the need show up in the CRM: proposal-stage deals with a single contact, losses concentrated in “no response” and “internal decision” and proposals approved by the contact and vetoed above them. When these signs appear together, HR and L&D have a case for proposing the training. The group brings together salespeople and KAMs, the managers who will enforce the map in the pipeline and the CS people who handle renewal and expansion, with SDRs when they run the first qualification. To measure, take a baseline beforehand, with the percentage of proposal-stage deals with a mapped decision maker, the average number of contacts per deal and the proposal to win conversion rate, and compare after one sales cycle.

If your team loses deals to people it never met, that is the work of the in-company Consultative Selling training. I run the program on the open accounts of your operation, with salespeople, KAMs and managers in the same room, and the group leaves with the consultative selling playbook, which includes the committee map and the relationship scale, and with the needs discovery framework, where the questions about who decides and who can block live.

Frequently asked questions

What is a B2B buying committee?

It is the group of people at the buying company who influence, approve or veto a complex purchase. It includes those who use the solution, whoever approves the budget, the technical and legal areas, the internal champion and whoever can block the project, often outside the meetings with the salesperson.

How many people are on a buying committee?

It depends on the size of the purchase and the company. The Gartner survey published in 2025 describes groups of five to 16 people across as many as four functions. To find your operation’s number, compare in the CRM the contacts associated with won deals against lost ones.

How do you identify the economic buyer in a B2B sale?

Ask the contact up to what amount they approve on their own, who approves above that and how the company decided the last purchase of a similar size. Then ask for a short conversation with that person, with the champion’s support.

How do you record the buying committee in the CRM?

Associate each contact with the opportunity using three fields: role in the committee, relationship level from 0 to 3 and position on the project. Make the decision maker mandatory for the proposal stage and review the map in the pipeline meeting.

What should you do when a blocker shows up late in the negotiation?

Talk with them to understand what they lose with the project and what risk they are raising, answer the risk in writing and bring in someone from your company at their level. Adjust the close date in the forecast and add the question about who benefits from the current way of working to future discovery calls.

How do you train the team to map the buying committee?

Use the team’s own open accounts: each salesperson presents the committee for their deals, colleagues point out the empty roles and the group practices the discovery questions and the champion rehearsal in role-play. Afterwards, the manager sustains the habit in the pipeline meeting with the mapped decision maker rule.