A B2B buying decision is rarely made alone: six to ten people take part, each with a different criterion, and several of them will never meet you. Selling to a committee therefore means mapping the roles, arming someone able to carry the case in your absence, and seeking agreement between members rather than individual conviction.
We regularly work with sales teams that lose deals without ever understanding why. The opportunity was well qualified, the demo landed, the contact was enthusiastic, and then nothing: the project stopped at a level of the organisation the salesperson had no access to.
This is the most consistent feature of B2B selling today. The decision is no longer made in the room you are in. It is made in your absence, between several people who do not share the same criteria, some of whom have never met you. As long as a team sells to an individual, it is betting a deal on a conversation. Selling to a committee is a different job.
Six roles, and a seventh nobody names
Committee composition varies from one company to the next, but the roles themselves are stable. In a smaller business one person often holds three of them; in a large account, each sits in a different department.
The user will live with the solution every day. They judge on usage and on what happens to their workload. They rarely have the power to say yes, and almost always the power to sink a project they did not want.
The initiator identified the need and started the search. They are often your first contact, and mistaking them for the decision maker is the classic error.
The economic buyer commits the budget. They care neither about your features nor your interface, but about what the problem costs today and what changes if nothing is done. This is the role salespeople meet least often, and the one that decides.
Procurement comes in late, once the choice is settled, to improve terms and secure the supplier. Their arrival is not a bad sign: it means the technical decision has been made.
The technical or security function validates feasibility, data hosting, integration. It cannot say yes on its own, it can say no on its own. That asymmetry is better handled early.
Legal reviews the contract, usually at the end, sometimes over three weeks nobody had put in the plan.
Then there is the seventh role, which appears on no org chart: whoever would rather nothing changed. They are not necessarily against your solution. They may have built the current system, have no room for another project, or stand to lose something in the move. Ignoring them does not make them disappear, it only removes your chance to answer them.
What actually changes between one person and a committee
The difficulty is not the number. It is that each member judges on a different criterion, and those criteria do not rank in the same order.
An operations director and a finance director can agree that the problem is real and disagree completely about when it should be dealt with. A sale addressed to only one of them earns a convinced ally and a silent blocker. The question to ask about a deal is therefore not “are we convincing”, but “what does each person need to hear in order to say yes in front of the others”.
That shift has a second, less comfortable consequence. The wider a committee grows, the more likely the do-nothing option becomes, because it is the only one everybody can agree on without effort. Your main competitor is almost never another vendor, it is next quarter, a point we also approach from the cycle angle in shortening your B2B sales cycle.
Map it, with three columns
Mapping a committee does not require a tool. Three columns are enough, kept current on every significant deal.
Who. Name, job title, and above all their real role in this decision, which does not follow from the title. An operations manager who has been listened to for fifteen years often weighs more than a director who arrived six months ago.
Their criterion. One sentence, in their own words, on what will determine their view. If you cannot write it down, you have not asked, and a guess is worth nothing here.
Their position. Supportive, neutral, opposed, unknown. The most useful value in this column is “unknown”: it counts the people your team has never met, and that number predicts a late surprise better than anything else.
One rule is worth stating in deal reviews: a significant deal with only one known contact is not an advanced deal. It is one of the checks we recommend making systematically in a pipeline review, alongside the dated next step.
Arm someone, because you will not be there
Since the decision happens without you, the only question that matters is who will speak for you. That role, the champion, is neither the initiator nor the budget sponsor: it is the person willing to spend some internal credit on your case.
You do not guess who it is, you test it, with two concrete requests. Ask them to set up a conversation with someone they have not yet introduced you to: a champion opens doors. Ask them to produce something, an internal number, a review of your business case: someone who invests work in your deal has started to treat it as theirs.
Arming them then means writing what they will have to say. One page, not a brochure: the problem in their company’s vocabulary, what it costs every month using their figures rather than your market averages, what the solution costs, when it pays back, and one-sentence answers to the three objections that will come. The test is a single request: ask them to tell you the story in ten minutes. Whatever they forget is exactly what needs rewriting.
One message per role, one promise
Adapting the message to each person is necessary, and it is also the door to inconsistency. The rule we apply is never to change the promise, and to change only the proof.
The user needs to see what happens to their day. The economic buyer needs a number on the cost of inaction. Security needs to know what happens in an incident and where the data lives. Procurement needs to know what is negotiable. Those are four different proofs of one promise, not four promises.
Consistency is not a matter of commercial ethics, it is a matter of effectiveness: committee members talk to each other, and a contradiction between two meetings will be spotted. The method for adapting a message without breaking it is covered in adapting your message by persona.
Make the decision happen, rather than waiting for it
A committee does not meet for your benefit. Between two meetings, your case lives in the inboxes of people with other things to do. Three practices clearly change the outcome.
The first is to write the decision plan with the customer: the remaining steps, who validates what, by when, and what each person needs in order to do it. The document is drafted together and corrected by the customer, which makes it their plan rather than yours.
The second is to price the waiting. As long as doing nothing is free, doing nothing wins. The monthly cost of the problem, built from their data, is the only argument that moves a decision without manufacturing urgency.
The third is to welcome the objections. An opponent identified early costs infinitely less than one discovered at the final committee. Asking your champion who will push back, and why, is the highest-return question of the whole cycle.
Frequently asked questions
- Who sits on a B2B buying committee?
- Six roles come up almost every time, sometimes held by the same person in a smaller company: the user who will live with the solution, the initiator who identified the need, the economic buyer who commits the budget, the procurement lead who negotiates terms, the technical or security function that validates feasibility, and legal, who reviews the contract. A seventh role is rarely named and often decisive: whoever would rather nothing changed.
- Why is a single-contact deal risky?
- Because it rests on one person who can change jobs, lose an internal argument or move on to another priority, and because you only see the deal through one point of view. A deal with a single contact is not an advanced deal, it is a deal where you are missing most of what matters.
- How do you adapt your message to each committee member?
- Keep one promise and change the proof. The user wants to know what happens to their day, the economic buyer what inaction costs, security what happens in an incident, procurement what is negotiable. Contradictions between two meetings always surface, and they cost more than a lack of personalisation ever would.
- How do you move a committee that will not decide?
- Treat no decision as the default outcome rather than an accident. Three levers work: price the cost of each month of delay using their own numbers, tie the decision to a deadline that belongs to them, and write a plan with dated steps and named owners that the customer validates themselves.