Qualification questions feel like an interrogation when they arrive in a list, in your order, with nothing in between. They stop feeling that way when each one follows from something the buyer just said. You can cover everything a framework like MEDDPICC asks for, pain, impact, buyer, process, timeline, competition, in a conversation the buyer enjoys, if you earn each question and let their story set the order. Here are the questions and how to sequence them.
Why discovery turns into an interrogation
Most discovery scripts are written as a list of things the seller needs to know: budget, authority, need, timeline, and whatever else the methodology adds. Reps then work down the list. The buyer experiences twelve questions in a row from someone who hasn't yet shown they understand the problem, and starts giving short answers. By question six, the rep has a filled-in form and a buyer who has stopped talking.
You still need the answers. What changes is the order and the trigger: every question is earned by the answer before it, and the buyer can tell why you're asking.
Three rules that keep it a conversation
- Ask about the situation before the stakes. Start with what they do today and what prompted the meeting. Impact and budget questions only land after the buyer has described a real problem.
- Follow the buyer's last sentence. If they mention a missed target, the next question is about the target, not the next item on your list. You'll get to your list; the order is theirs.
- Say why you're asking when the question is heavy. "I ask about the approval process because the deals that stall for us usually stall there" turns a qualification question into a helpful one.
The questions, in the order buyers tend to allow
These ten cover pain, impact, decision criteria, decision process, economic buyer, champion, timeline, and competition. Use them as follow-ups to what the buyer says, not as a sequence to read out.
- "What made you take this meeting now?" Opens on timing and the trigger event. The answer usually contains the pain and a deadline.
- "How are you handling that today?" Gets the current situation and the incumbent tools or workarounds, which is competition without asking about competition.
- "When that goes wrong, what does it cost you, in time or money or risk?" Impact. If they can't quantify it, help: "Rough numbers are fine. Is it a few hours a week, or a headcount?"
- "Who else feels this?" Starts the map of stakeholders and shows you who the champion's allies are.
- "If you fixed it this quarter, what would you do with the result?" A priority test. It separates a nice-to-have from a problem someone will fund.
- "How have you bought something like this before?" Decision process and paperwork, without the phrase "what's your process".
- "Who would need to sign off, and what do they care about most?" Economic buyer and their criteria, asked as a favor to the person in front of you.
- "What else are you considering, including doing nothing?" Competition, framed so an honest answer is easy.
- "What would need to be true for this to be done by then?" Timeline and the obstacles to it, using the date they gave you earlier.
- "Looking back a year from now, what would make this a bad decision?" Decision criteria and risks, in their own words.
Layering follow-ups so it stays a conversation
The difference between a good discovery call and a form is the second question. When the buyer gives you a headline, ask for the example. When they give you an example, ask what it cost. When they give you the cost, ask who else knows about it. Three layers on one topic tell you more than ten topics at one layer, and buyers tend to enjoy it, because someone is finally taking their problem seriously.
"You mentioned new reps are slow to ramp. Can you give me an example of what a new hire struggled with last quarter?" Then: "What did that cost you, roughly, in deals or in your own time?" Then: "Who else on the leadership team knows it's this bad?"
Notice that none of those three questions is on a qualification checklist, and all three produce qualification data: identified pain, quantified impact, and the beginnings of a stakeholder map.
Mapping the conversation back to your framework
After the call, not during it, map what you heard onto the framework. If you're using MEDDPICC, the questions above give you Metrics from the impact answers, the Economic buyer from question seven, Decision criteria and Decision process from six, seven, and ten, Identified pain from one through three, the Champion from four, and Competition from eight. Whatever is blank is your agenda for the next call, and by then you can ask for it directly, because you've earned it.
Doing the mapping afterwards is what keeps the call human. The buyer never sees the framework; it is for you and your manager after the call.
Ending the call so the qualification holds
A discovery call that ends with "I'll send over some information" hasn't qualified anything, because nothing has been tested. End by proposing a specific next step that requires the buyer to do something small: bring a colleague, share a number, confirm a date. If they agree, you have a real signal. If they hedge, you've learned more than any question on the list would have told you.
"It sounds like the ramp problem is costing you roughly two deals a quarter. The right next step is a thirty-minute session with you and whoever owns the enablement budget, so we can pressure-test that number together. Does the fourteenth work?"
Where this goes wrong
- Reading the list. If the buyer can hear the checklist, they answer it like a form.
- Skipping to budget. Asking about money before the problem is quantified gets you a defensive number or a polite deflection.
- Accepting the headline. "We need better forecasting" is a category, not a pain. Ask for the last time it hurt.
- Single-threading. If every answer comes from one person, you've qualified their opinion, not the deal.
- Filling in the framework live. Typing MEDDPICC fields during the call pulls your attention off the buyer, and they can tell.
Where Aircover fits
Aircover prepares reps before the call with account context and suggests the next follow-up question during it, based on what the buyer just said, so the layering above happens on the live call rather than in a debrief. Afterwards it maps the conversation to MEDDPICC, SPICED, or your own framework and shows which elements are still blank. The call prep page covers the pre-call side.