Anatomy of a Buying Committee

Enterprise buying decisions are not made by individuals. They are made by committees — often informal, rarely documented, and almost never represented by the org chart. The person who signs the contract is frequently not the person who made the decision. The person who made the decision is frequently not the person who initiated the evaluation. Understanding who is actually on the buying committee and what role each person plays is the difference between selling to the decision and selling to the org chart.

A typical enterprise buying committee has six to ten members across four functional roles. The economic buyer controls the budget and has final sign-off authority. The technical evaluators assess whether the solution meets requirements. The user champions will live with the solution daily and their enthusiasm or resistance determines adoption. The coaches are internal advocates who guide you through the organization. And then there are the veto holders — people who cannot say yes but can say no, often in risk, legal, procurement, or security functions.

1. Identify the Economic Buyer The person who controls the budget. Not the person who "manages" the budget but the person who can approve spending without escalation. In mid-market, this is often a VP or C-level. In enterprise, it may be a committee itself. Ask directly: "Who needs to approve the budget for this initiative?" The answer is often not who you think.
2. Map the Technical Evaluators The people who will assess your solution against requirements. They rarely have buying authority but their recommendation carries enormous weight. Technical evaluators want proof: demos, trials, reference architectures, integration documentation. Winning them requires competence, not charm.
3. Find the User Champions The people who will use your solution daily. Their enthusiasm drives adoption. Their resistance kills it — slowly, quietly, after the contract is signed. User champions care about usability, workflow impact, and change management. A solution the user champion endorses survives. A solution they tolerate fails.
4. Identify the Veto Holders The people who cannot say yes but can say no. Legal, security, procurement, compliance. They evaluate risk, not value. They are incentivized to reject, not approve. A veto holder who learns about your solution for the first time during contract review is a veto holder who says no. Engage them early, on your terms, not theirs.