Buying Committee
A buying committee is the group of people inside an organization who collectively research, evaluate, and approve a B2B purchase, rather than a single individual deciding alone.
Key takeaways
- Committees exist as separate conversations and forwarded documents, rarely as a single meeting.
- Size grows with contract value, departments touched, regulation and memory of a failed rollout.
- More reviewers reduce single-objection risk but raise the chance of death by inaction.
- A quiz can ask which functions will weigh in and structure the result accordingly.
- Below a certain deal size the committee is one person with a company card.
In depth
A buying committee forms because the risk of a purchase is spread across functions. Someone owns the problem, someone owns the systems the tool will touch, someone owns the money, and someone owns the contract language. Each of them can slow a deal down and only one or two can speed it up. The committee rarely convenes as a group. It exists as a chain of separate conversations, internal documents and forwarded links, most of which the vendor never sees and cannot influence directly.
Committee size grows with contract value, with the number of departments the tool touches, and with regulatory exposure. It also grows after a bad prior purchase, because organisations answer a failed rollout by adding reviewers. Larger committees reduce the chance that a single objection kills the deal, but raise the chance that the deal simply expires through inaction. Every additional member brings a criterion, a calendar and a veto, which is why cycle length tends to rise faster than headcount on the committee.
Practically the work is mapping the committee and then arming it. You ask early which functions will weigh in, you produce a different artefact for each role, and you give your contact material designed to be forwarded rather than read alone. A scorecard funnel supports this directly: the quiz can ask which departments will be involved, and the result page can be built so that one section speaks to each named function, giving the respondent something circulate-ready without rewriting it.
The concept can be over-applied. Below a certain deal size the committee is one person with a company card, and building multi-threaded campaigns for those deals adds coordination cost without changing the outcome. Committee maps also decay quickly, since people move, reorganisations reshuffle ownership, and a map drawn at the first call is often wrong by the time a proposal goes out. A committee that is broad but disengaged is not a committee, only a list of names recited on request.
Example in practice
How to measure it
Count distinct contacts engaged per open opportunity, then compare that count between deals that closed and deals that stalled. A single-threaded pipeline shows up as a healthy-looking forecast that slips again and again. Also check whether the functions actually engaged match the functions your contact originally named, because the gap between those two lists is the part of the committee you are not reaching.
Watch timing as well as count. Record how far into the cycle each new function first appears, since a finance or security contact who shows up only after the proposal is the pattern that produces late-stage surprises. A shortening interval between first contact and first engagement from a second function is direct evidence that the multi-threading effort is doing something.
Common mistakes
The first mistake is asking who else is involved and then doing nothing with the answer. Contacts routinely name three colleagues and receive exactly the same follow-up email as before, so the information decays inside a CRM field. If the answer names finance, send something a finance person can use within the same week. Unused stakeholder data is worse than none, because it creates a false sense of coverage.
The second is treating multi-threading as sending one pitch to more people. Copying a champion's manager into a thread with no reason to be there irritates both and can cost you the champion's goodwill. Reach each member with content that answers the question their own role owns, and where possible let the champion make the introduction, since an internal forward carries credibility a cold email never will.
Frequently asked questions
Who is typically on a buying committee?
Most committees include a champion, end users, technical or security evaluators, an economic buyer who controls budget, and often procurement or legal. The exact mix depends on deal size, with larger purchases pulling in more stakeholders.
How is a buying committee different from a single decision maker?
A single decision maker can approve a purchase alone, whereas a buying committee shares that responsibility across several people with veto power. Treating a committee deal as if one person decides usually leads to late-stage stalls.
How can a quiz help me map the buying committee?
A quiz can ask how decisions are made and who else is involved, capturing roles and team size as structured data. That lets you trigger role-specific nurture so finance, IT, and the champion each receive relevant material.
How many people are usually on a B2B buying committee?
It varies with deal size and with how many departments the tool touches, so no single number is worth planning around. A useful rule of thumb: a purchase requiring a security review, a budget approval and a workflow change involves at least one person for each, plus whoever raised the problem. Count functions rather than heads.
How do I find out who else is involved without seeming pushy?
Ask it as a process question rather than a power question. Asking how purchases like this normally get approved invites a description of the path, which names roles without forcing anyone to admit they lack authority. A quiz question offering the functions as checkboxes collects the same information with even less friction.
What is multi-threading and is it always worth doing?
Multi-threading means holding live relationships with several committee members instead of one. It pays when the deal is large enough that losing a single contact would reset the cycle, and when the purchase crosses departments. For small, fast, single-department deals it adds coordination cost and can slow a decision one person was already ready to make.
What should we send to a committee member we have never spoken to?
Something that stands alone and answers the question their role owns, delivered through the champion where possible. A security summary, a pricing rationale or an implementation outline should make sense with no prior context and no sales narrative wrapped around it. Anything that needs a meeting to be understood will not travel through the committee.
How do we keep a committee moving when it goes quiet?
Give the group a decision to make rather than more information to absorb. Silence usually means the purchase lost its place among competing priorities, not that someone objected. A short summary of what is agreed, what is outstanding and what happens next gives the champion something to circulate, and a named date turns intention into a calendar item.
Does a buying committee exist in self-serve purchases?
Often a smaller one exists invisibly. Even a card-swipe subscription may need a manager's approval on an expense report or a security check before it is allowed on company devices. Those reviewers never contact you, so the practical response is publishing what they need, such as a plain security page and clear pricing, where they can find it alone.