Skip to content
Log in
← Glossary

buying committee

Also called: buying group, decision-making unit

The group of people inside a company who influence or approve a purchase: the users, a champion, the budget owner, procurement, legal and IT security. Each of them can stop the deal, and each is guarding against a different risk.

A buying committee is everyone inside a company who can shape or stop a purchase. In a typical B2B deal that means the users who will live with the product, a champion who wants it, the economic buyer who owns the budget, and the gatekeepers: procurement (price and terms against other suppliers), legal (liability and contract clauses) and IT security (where data lives and who can see it). Bigger or riskier purchases add more people; a small purchase may collapse several roles into one person.

The committee matters because a yes from one member is not a yes from the company. Each role guards against a different loss: users their time, the champion their reputation, the budget owner the money, procurement the terms, legal the liability, security the data. A proposal that answers only the enthusiastic contact can still be stopped late by someone the seller never met, which is why many deals that "looked closed" quietly die in procurement or legal review.

The practical tool is a committee map: for each role, who it is, what worries them, what they will need and when they enter the process. Job titles are only a first guess, because the same budget sits with HR in one company and with a department head in another. The reliable way to fill the map is to ask an insider how the last similar purchase was approved, then treat every blank cell as the next question rather than a guess.

Example

Klasna for Teams sells corporate English at 800 UAH a lesson. After a demo, Pavlo, HR and learning manager at the logistics company Veloria, says: "This is exactly what our people need." Asked how Veloria bought its last training, he describes the path: he found the provider, the finance director approved the money, procurement compared three quotes, and legal got the contract last and took three weeks.

Role
Who at Veloria
What they guard
Users
Dispatchers, client managers
Their shifts
Champion
Pavlo
His name on the idea
Economic buyer
Finance director
The budget
Procurement
Unknown yet
Price and terms vs three quotes
Legal
Unknown yet
Liability, data clauses
IT security
Unknown yet
Employee data, recordings

Six roles, one conversation. The timing check shows why the map matters: the pilot is evaluated on 10 February and the target signature date is 26 February, only 16 days later. If legal again starts at the end and needs 21 days, the earliest signature is 3 March and the 1 March start is lost. Sending the contract draft to legal in the first week of the pilot wins those three weeks back.

Common mistakes

  • Taking the champion's yes for the company's yes. Enthusiasm after a demo says nothing about the budget, the signature or the checks.
  • Mapping by job title. Titles are a first guess; ask how the last similar purchase was approved.
  • Asking "are you the decision-maker?" It puts the contact on the spot; ask about the process and next steps instead.
  • Meeting the gatekeepers last. Procurement, legal and security that join at the end add weeks; bring them in early with written answers.
  • Treating the map as finished. People change roles and budgets move; update it after every meeting.

Learn it in the course