Discovery Questions by Buying Committee Role: What to Ask Each Seat

Most discovery advice assumes one buyer on the other end of the call. Real deals have a group, and the group does not share one set of worries. A question that works on the person who asked for the demo lands badly on the person who has to sign the contract. Discovery questions by buying committee role fix that by treating every seat as its own short discovery call with its own goal.

Here is the question set I would run seat by seat, in the order most deals open up, with the answer that should make you slow down.

One discovery call cannot cover a committee

Every enterprise deal carries more people than the one who answered your form. Harvard Business Review has written about the growing number of stakeholders involved in each purchase. The common mistake on these deals is a habit: reps run one good discovery call with the first person who replied, then treat that person's answers as the whole deal.

That person is usually your champion. They are useful, and they are also one view of the deal. What they believe about budget, timing and who objects is a hypothesis until someone in that seat says it too.

The fix is to split discovery into short, role-specific conversations. In the C.A.L.L.S. Framework, Ask is the second step: Confirm the reason you are speaking, Ask, Listen and take CRM notes, Lay out a plan, Secure the bag. The C.A.L.L.S. Framework tells reps to keep five to eight go-to questions ready for every call. On a committee deal, you keep that set ready for each seat, and each set is a little different. The general technique for asking a good question is covered in how to ask better sales questions. This post is about who gets which question.

What do you ask the economic buyer?

The economic buyer owns the budget and can say yes without asking anyone else. You rarely get long with them, so the questions are short and about outcomes, not features.

• "What would have to be true six months from now for you to call this a good decision?" This tells you their definition of a win, which is almost never the feature list.
• "Where does this sit against the other things competing for the same budget this year?" Your real competitor is often another project, not another vendor.
• "What has to happen before you can approve it?" You are asking for the path, not the amount.

Listen for the cost of doing nothing in their words. If they cannot name one, the project is a nice-to-have, and nice-to-haves lose to everything else.

What do you ask the technical evaluator?

The technical evaluator is checking fit and risk. Their job is to find the reasons it will not work, so do not be surprised when the conversation feels like an examination. Give them room.

• "What would make you say this is not a fit?" Ask it directly. You want the objection now, while you can still do something about it.
• "What does the current setup do well that we should not break?" This shows you respect what exists, and it surfaces the integration points that cause delays later.
• "Who else needs to sign off on the technical side?" Technical approval is often a second or third person you have not met.

What do you ask procurement and the end users?

These are two different seats that tend to show up late. Procurement owns process and timing. The end users own daily reality. Reps who skip either one get surprised in the last month.

For procurement, ask about the steps, not the price.

• "Walk me through what happens between a yes and a signed agreement." Write down every step and every named reviewer.
• "What documents do you need from us, and how long does each step usually take?" You are looking for the date your timeline really starts.

For the end users, ask what the work looks like today.

• "Talk me through the last time this went wrong for you." A specific story beats an opinion.
• "What would you need this to do on a normal Tuesday for you to use it without being told to?" Adoption lives in this answer.

What do you ask your champion?

Your champion is the one person on the committee who wants this to happen. Ask them for access and honesty, not enthusiasm.

• "Who else is weighing in on this, and what will each of them care about?" Use the answer to plan the other four conversations.
• "Which of them will you be able to introduce me to, and which will be hard to reach?" The second half matters more than the first.
• "Who on this committee is likely to be unsure about it?" People will often tell you the name before they will tell you the objection.

A champion who cannot get you in front of the economic buyer is giving you information. Treat it as such.

In what order should you run the conversations?

Start with the champion, because they open the doors. Go next to whichever seat is most likely to say no, which is usually the technical evaluator. An early objection is cheap to handle. The same objection in the last week of the quarter is not.

Take the economic buyer third, and take them with something in hand: what you learned from the champion about their goals and what the technical seat confirmed about fit. A budget owner who hears their own priorities repeated back accurately will give you more time than one who hears a feature tour. Procurement and the end users come last in most deals, but ask about procurement's steps earlier than feels natural. The date their process starts is rarely the date your proposal lands.

After every conversation, do three things in the CRM before you close the tab: the person's name and seat, their answer to the win question in their own words, and the next step with a date. That record is what lets a second rep, or a manager in a deal review, see the committee without asking you.

The seat-by-seat question sheet

Print this and keep it next to the CRM record. It is the same set of questions in one place, with the answer that should make you slow down.

Seat	What they own	Two questions to ask	The answer that should worry you
Economic buyer	The budget and the yes	What would make this a good decision in six months? What has to happen before you can approve it?	They cannot name a cost of doing nothing
Technical evaluator	Fit, risk and integration	What would make this not a fit? Who else signs off on the technical side?	A vague "it looks fine" with no named concern
Procurement	Process and timing	What happens between a yes and a signed agreement? What do you need from us, and how long does each step take?	Steps they cannot describe, or reviewers they will not name
End users	Daily use and adoption	When did this last go wrong for you? What would it have to do on a normal Tuesday?	They have never heard of the project
Champion	Access and the internal story	Who else is weighing in? Who can you introduce me to?	They cannot or will not open the budget owner's door

If you are building the full picture of who sits where, enterprise sales training from Drewbie takes reps through committee mapping and multithreading on the open deals in their own pipeline, so the question sheet gets used on real accounts and not a case study. For deals where the problem sits in the process underneath the selling, sales consulting looks at the sales process, the follow-up and the pipeline together.

When better questions will not save the deal

The second thing that does not help is asking all five sets of questions on a single call. Each seat gets its own conversation, and each conversation ends with a booked next step. For the basics of discovery before you split it by seat, Call The Damn Leads has a guide to the discovery sales process that covers the foundation this post builds on.

Sources: Harvard Business Review, The New Sales Imperative · Call The Damn Leads, the discovery sales process · Call The Damn Leads, the C.A.L.L.S. sales framework