The B2B buying committee: map veto power, not job titles

Enterprise deals rarely die in front of you. They die in a meeting you were not in, killed by someone you never spoke to, for a reason nobody ever tells you.

That person almost never has "decision maker" in their title. They are frequently mid-level. They frequently do not want the product either way. What they have is the ability to say no in a way nobody overrules.

Mapping a buying committee by seniority finds the people who can say yes. Mapping by veto power finds the people who can say no. The second list is shorter, less obvious, and decides more deals.

The six functions in every committee

Committees vary in size and title. The functions are remarkably consistent.

The last one is the most dangerous and the least mapped. Someone in the organisation has a project that your purchase makes redundant, or reveals as behind schedule. They will not oppose you openly. They will raise reasonable concerns at the right moments until the deal loses momentum.

Ask your champion directly: who internally would prefer this did not happen, and why. Champions almost always know. They are rarely asked, because the question feels adversarial. It is the single highest-yield question in enterprise discovery.

Veto power is not seniority

The two most common mapping errors:

Assuming the most senior person decides. A VP can approve a purchase and still be stopped by a security review. Seniority determines who signs, not who blocks.

Assuming a blocker can be routed around. Security, legal and procurement are usually absolute. No amount of executive enthusiasm overrides a failed review. These functions should be engaged early precisely because they cannot be overruled late, and every week you delay is a week the deal spends discovering an obstacle you could have found in the first call.

The practical reframe: map who can stop this, then map who can start it. Most teams do it in the opposite order and meet the blockers at the worst possible moment, when momentum is highest and there is no time left to solve.

How many people, realistically

Enterprise B2B software purchases typically involve somewhere between six and ten people, and the number grows with deal size and with anything touching data, security or compliance.

Two numbers matter more than the headcount:

How many you have reached. Account penetration. Reaching one person at an eight-person committee is a 12% conversation.

How many functions you have reached. Spread. Four contacts all sitting in marketing is one interested department. Three contacts across marketing, finance and security is a process forming.

Spread predicts far better than depth. Why that distinction drives ABM reporting is covered in ABM metrics.

Different people need different things

The reason a single generic asset underperforms across a committee: they are not asking the same question.

• Champion needs ammunition. Something they can forward that argues the case without you present.
• Economic buyer needs the cost of inaction and a defensible reason this quarter.
• Technical evaluator needs specifics, honestly stated. Overclaiming here is fatal, because they will test it.
• End user needs to know their day gets better, not just different.
• Security and legal need documentation, early. Not persuasion.
• The skeptic needs their concern acknowledged before they raise it publicly.

One document cannot serve six questions well. That is precisely the structural argument for personalized microsites, where navigation is built around role rather than around your product's feature list.

Arm the champion above all

Your champion has the hardest job in the deal. They have to re-explain your value to five colleagues, in rooms you will never enter, without your help, while also doing their actual job.

Most vendors make this harder than it needs to be. They send material designed to persuade the champion, who is already persuaded, and nothing designed for the champion to *use*.

What actually helps:

• A forwardable artifact that carries its own argument with no narration. If it only makes sense with someone presenting it, it is useless the moment it leaves the room.
• The internal case, pre-made. The cost of the status quo, phrased for their CFO rather than for them.
• Answers to the objections they will face, including the ones about you. A champion blindsided in a meeting loses credibility, and a champion without credibility cannot help you.
• Something short. They are forwarding this to busy people. A forty-page document does not get read and reflects badly on the person who sent it.

Treat the champion as a colleague running an internal campaign, not as a prospect being sold to. It changes what you send, and it is the highest-leverage shift available in enterprise deals.

Mapping it in practice

Build the map as an artifact, not as knowledge in one rep's head.

For each account, record: name, function, whether they can block, whether they have been reached, what they need, and what they have engaged with. Attach it to the account record so it survives a rep changing.

Sources worth combining: enrichment data for the org structure, engagement data for who is actually reading, the champion for internal politics no dataset contains, and public signals like job postings that reveal team shape and priorities. What those signals can and cannot tell you is in B2B buying signals.

Update it when something changes, not on a schedule. Committee maps go stale fastest exactly when the deal is moving fastest.

Frequently asked questions

What is a B2B buying committee?

The group of people inside a company who collectively decide on a purchase. In enterprise software it typically includes a champion, an economic buyer, a technical evaluator, end users, and approval functions like security, legal and procurement, usually six to ten people in total.

How many people are in a B2B buying committee?

Typically six to ten for enterprise software, growing with deal size and with anything touching data, security or compliance. The more useful measures are how many you have reached and how many distinct functions you have reached, since functional spread predicts outcomes better than raw contact count.

Who actually blocks B2B deals?

Most often security, legal or procurement on a policy issue that cannot be overruled, or an unnamed internal skeptic who owns a competing initiative. Neither usually appears on a seniority-based stakeholder map, which is why mapping by veto power outperforms mapping by title.

How do you map a buying committee?

Record every known participant with their function, whether they can block, whether they have been reached, and what they need. Combine enrichment data, engagement data and direct input from your champion, who knows the internal politics no dataset contains. Store it on the account record, not in a rep's head.

How do you support a champion in an enterprise deal?

Give them something forwardable that argues the case without you present, the cost of inaction phrased for their CFO, and answers to the objections they will face internally. Treat them as a colleague running an internal campaign rather than as a prospect to persuade.

---

*NomiOS is RZLT's GTM and ABM engine. Point it at a target and get back finished, branded work built on a real read of that company.*

[See how NomiOS works →](https://nomios.rzlt.io)