A buying committee is the group of people who influence or approve a B2B purchase: usually a champion, an approver, the users, and people from finance, IT and procurement. Running discovery with one means holding one call where several stakeholders each describe the problem, its cost and the decision from where they sit, and finding where those accounts disagree. The account executive runs it, often with a champion's help setting it up. It needs 45 to 60 minutes and about thirty minutes of preparation.
The glossary entry has the short definition. One-to-one discovery is covered in our discovery call guide. This piece is about the call where five people join, the senior one arrives late, and the rep's instinct is to present.
The job
A committee discovery call has two jobs. The first is the usual one: get the buyer's own words on the problem, the cost and the decision. The second is specific to a group: find out where the stakeholders see the problem differently, while there is still time to deal with it.
- 01Map the committee with your champion
- 02Send an agenda that names each person
- 03A round on the problemMost junior person first
- 04Log the differences on screen
- 05Ask the approver directly
- 06Close with an action per personEach with a date
Committees rarely stall on price. They stall because finance thinks the problem is cost, operations thinks it is process, and the approver thinks it is a vendor relationship nobody has mentioned. A rep who demos to that room gets five polite nods and a decision that never comes. A rep who asks each person how the problem shows up for them gets the disagreement on the table in the first twenty minutes.
The roles on a buying committee
Titles differ from company to company, so map roles before names. Most committees include some version of these:
| Role | What they care about | What to ask them in discovery |
|---|---|---|
| Champion | Getting the problem fixed, and looking good for pushing it | Who else feels this problem, and how would they describe it? |
| Approver (economic buyer) | Whether the spend is worth it against everything else they could fund | What would need to be true for this to be worth doing this year? |
| User | Whether their day gets easier or harder | Walk me through what happens today when this goes wrong. |
| Technical evaluator (often IT) | Fit, risk, security and the work to set it up | What would make this hard to put in place here? |
| Finance | Cost, timing and where the money comes from | Which budget would this come from, and when is it set? |
| Procurement or legal | Terms, risk and process | What does your process need from us, and how long does it usually take? |
One person can hold several roles in a smaller company. The role nobody has named yet is usually the risk: a blocker who has not been met, or an approver the champion assumes will say yes.
The procedure
1. Map the committee with your champion before the call
Ask your contact who else would be involved in a decision like this, and what each of them cares about. Write a line per person: role, what they are measured on, what they likely think the problem is.
Good looks like a list your champion corrects. "Procurement will want in early" is the useful sentence. If your contact cannot name anyone else, you have a fan, and the discovery call questions piece has the approval questions to ask next.
2. Send an agenda that names each person
Draft the invite for your champion to send, or send it yourself with their name on it. Name each attendee and the one question you would like their view on.
Say (in the agenda): "Priya: how contract delays show up for sales. Tom: what they cost in finance terms. Ruth: what a decision like this needs from your side."
Good looks like nobody arriving cold. People prepare when they have been asked a specific question in writing.
3. Open with the frame and a round on the problem
After a two-minute frame, ask each person in turn the same question about how the problem shows up for them. Start with the most junior person in the room, so the senior voices do not set the answer for everyone.
Say: "Before I say anything about us, I'd like to hear how this looks from each seat. Priya, can we start with you?"
Good looks like three different answers. Identical answers usually mean one person has briefed the others, and the real views are somewhere else.
4. Log the differences where everyone can see them
Share a simple table on screen: each person's account of the problem and its cost, in their words. Read it back and ask the room which version is closest.
Say: "Priya says the delay costs deals at quarter end. Tom says it's outside counsel fees. Are those the same problem or two?"
Good looks like the committee arguing with each other for a few minutes. Disagreement about the root cause is what you are looking for, and a visible log makes it safe to have.
5. Ask the approver about the decision directly
If the person who signs is on the call, ask them what the decision needs: criteria, other options, timing, and what happened the last time they bought something like this.
Say: "Ruth, the last time the team bought a tool at this size, what did you need to see before you signed?"
Good looks like an answer with names and steps. If the approver is not on the call, ask the room who would brief them, and offer to write the summary for that person.
6. Handle the late arrival with a recap
When a senior stakeholder joins late, stop, recap the log in the attendees' words, and ask which version matches their view.
Say: "Welcome, Ruth. Two views so far: Priya sees lost deals at quarter end, Tom sees outside counsel fees. Which is closer to how you'd put it?"
Good looks like the latecomer joining the discussion on the committee's terms. A fresh pitch for their benefit resets the room to presentation mode.
7. Close with an action per person
Before the call ends, give each person something to do, with a date. One sends a number, one books the next call, one names who else should join.
Good looks like a follow-up email that lists each person's action, sent within the hour. The how to prepare for a sales call procedure applies to the next call, now with a committee's evidence to start from.
The stakeholder evidence table
Fill this in on the call, share it in the follow-up, and keep it in the deal record.
| Stakeholder | Role | The problem, in their words | The cost, in their words | What they need to decide | Their action and date |
|---|---|---|---|---|---|
Two empty cells in the cost column after the call is normal. Two people describing different problems with nobody noticing is the risk this table exists to catch.
Worked example (illustrative)
This deal is invented to show the procedure. Kofi sells a contract management product to a 1,200-person manufacturer. His champion, Priya in sales operations, sets up a call with Tom (finance), Ruth (general counsel, the approver) and Dev (IT).
Before. Kofi maps the four with Priya, who adds that Ruth signed a document-storage contract last year that "nobody uses." He writes the agenda with a question per person and sends it through Priya.
The round. Priya: quarter-end deals wait on legal review. Tom: outside counsel spend is up and he cannot see why. Dev: three tools already store contracts. Ruth is late.
The log. Kofi puts the three views on screen. Tom says, "That's the same problem. Legal sends overflow to outside counsel at quarter end." Dev disagrees: the problem is that nobody can find the existing contracts, so legal re-reviews them. The room spends six minutes on this. Kofi says nothing about his product.
The late arrival. Ruth joins at minute 22. Kofi recaps both views in their words and asks which is closer. Ruth says Dev's, and that she will not buy another storage tool. That is the most important sentence of the call: a decision criterion, stated by the approver, before any demo.
The close. Tom sends last year's outside counsel spend by Friday. Dev lists the three existing tools. Ruth agrees to a 30-minute call on how existing contracts would be found and reused. Kofi's next demo starts from retrieval, the part Ruth cares about.
Where it goes wrong
Presenting to the crowd. The rep demos because a group feels like an audience. People rarely disclose much in front of colleagues to a stranger who is presenting.
The champion speaks for everyone. The champion answers every question and the others stay quiet. Fix: the round in step three, starting with someone else.
Disagreement goes unspoken. Different views come out in separate side calls after the meeting, when the rep is not there to work through them. Fix: the visible log.
No owner per action. "We'll get back to you" from a group means nobody will. Fix: one named action per person, in the follow-up email.
Briefing every committee call
A committee call is the call a manager most wants to brief, because there are more ways for it to go wrong. Few managers have the hour per deal it takes.
With Replicate Labs, the rep calls Caty before the committee call and walks through the map. Caty asks who is missing, what each person likely thinks the problem is, and how the rep will handle the approver's question about the last purchase. She builds a roleplay with the late approver in it, and the rep runs it until the recap sounds natural, with a debrief after each run.
After the call the rep talks Caty through the log, and she flags who has not yet spoken about cost and what that means for the next step, in the team's methodology. Typing works when a call is not possible. See preparing for sales conversations for how it works, or talk to us about checking the skills on your team's recordings. If the committee pushes back on price or an incumbent, objection handling covers the response.
Draw the map for your next committee call tonight, with an empty seat for anyone you have not met. If the approver's seat is empty, talk to us about how Caty would prep that seat.
FAQ
What is a buying committee in B2B sales?
A buying committee is the group of people who influence or approve a B2B purchase. It usually includes the person with the problem, a budget owner, an approver and people from functions such as IT, legal or procurement. Each sees the problem from a different seat, and the deal moves when they agree on what the problem is.
How do you run a discovery call with multiple stakeholders?
Send an agenda that names each attendee and the question you want their view on. Open with a short frame, then ask each person in turn how the problem shows up for them, starting with the most junior. Log their answers on screen, ask the room to reconcile differences, and close with a dated action for each person.
How do you multi-thread a deal during discovery?
Ask your contact who else would be involved in a decision and what each cares about, then invite them to a discovery call with a named question each. Draft the invite for your champion to send. On the call, get each person's own account of the problem, so the deal no longer depends on one person's view.
What do you do when the decision maker joins a call late?
Pause, welcome them, and recap what the others have said, in their words and attributed. Then ask which view is closest to theirs. That brings them into the discussion without restarting it. Avoid re-pitching for the latecomer, which turns the call back into a presentation and loses the room's momentum.
How many people are on a typical buying committee?
Buying committee size varies with deal size and company: a small purchase may involve two or three people, and a large enterprise deal many more. The count matters less than coverage, so map your own committee with your champion: who has the problem, who pays, who approves, who could block it.