Discovery Call Question Generator

What a discovery call is for

A discovery call is where you find out whether there is a deal and what it would take to win it. Not a demo, not a pitch, not a rapport-building chat with a product slide at the end. If you leave a discovery call without knowing what the problem costs the buyer and who has to agree to fix it, you did not do discovery. You had a pleasant conversation that will stall in six weeks.

That sounds obvious, and most reps would say they do it. Then you listen to the recordings and the pattern is the same: ten minutes of situation questions, one pain question answered with "yeah, it is a bit of a headache", no attempt to quantify anything, and a demo offered before anyone asked who signs. The questions on this page are organised to stop that happening.

The generator above builds a question set for the call you are on. This guide is about how to run it: what to ask first, how to go deeper, which framework to borrow from, and how to tell afterwards whether the call was any good.

The five areas every discovery call has to cover

• Situation: how things work today. You need enough to understand their world, not a full process map. Two or three questions, then move on. Situation questions are easy for buyers to answer and easy for reps to hide in.
• Pain: where the current approach breaks. This is where "it is fine" has to be challenged gently, because "fine" is not something you can sell against. Ask where it breaks, how often, and what happens when it does.
• Impact: what the pain costs in hours, money, missed targets or headcount. Without a number here there is no business case, and without a business case there is no budget. Most reps skip this because it feels pushy. It is the most important part of the call.
• Decision: who else needs to agree, what the process looks like, whether budget exists or has to be created, and what happened last time they bought something like this. Deals die here, not on features.
• Next step: a specific commitment before the call ends. Not "I will send over some times", but "Thursday at 2pm with you and Sam from finance".

A discovery call question flow, worked example

Here is a qualification call for scheduling software, condensed to the questions and the transitions between them. The buyer is an operations manager at a field service company who took the call after a cold outreach.

BANT, MEDDIC, SPIN: which framework, and when

Every discovery framework is a checklist of what you must learn before you propose. They differ in depth and in how much they assume about the deal.

• SPIN tells you how to ask. BANT and MEDDIC tell you what you need to find out. Use SPIN's ladder inside each area, and use MEDDIC's checklist to decide whether the deal is qualified when the call ends.
• Whatever you pick, write the checklist on a sticky note, not a form you fill in live. The moment the buyer hears you typing answers into boxes, the conversation turns into an interview.

Mistakes that turn discovery into an interrogation

• Asking questions in a list. Twelve questions read from a doc with no follow-ups is a survey. The value is in the second question, the one that goes deeper into whatever they just said.
• Accepting the first answer. "It is a bit of a headache" is not pain. "How much of a headache? What happened last time?" is where pain gets specific.
• Skipping impact because it feels pushy. Asking what a problem costs is not pushy. It respects the fact that they will have to justify spending money. Do it gently, do it with "roughly", but do it.
• Demoing in the middle. The buyer asks "can it do X?" and you share your screen. Now it is a demo, discovery is over, and you never found out who decides.
• Talking more than 40 percent of the time. If you are explaining, you are not discovering. Count your own airtime on a recording. Most reps are surprised.
• Asking about budget in the first five minutes. Before pain and impact are established, a budget question gets a defensive non-answer. Ask it after the buyer has done the maths on the cost of the problem.
• Ending with "I will send some times over". That is an intention, not a next step. Book it on the call.

How to tell whether your discovery is working

The test for a discovery call is what you can write down afterwards. If you cannot fill in all five of these in one sentence each, something was missed: the problem in the buyer's words, what it costs per quarter, who else must agree, what happened last time they bought, and the date and attendees of the next step.

Over a month, the number to watch is the proportion of discovery calls that convert to a next meeting with a new stakeholder on it. A second call with the same person is pleasant but not progress. A second call with the finance director on it means your decision questions worked.

Listen to one of your own recordings a week with a single question in mind: where did I accept an answer I should have followed up? Mark those moments. After a few weeks the same spot will keep showing up, and that is the question you need to practise asking.

When good questions are not enough

A perfect question list does not survive contact with a buyer who answers the first question for six minutes, or who turns every pain question back on you with "well, what does your tool do about it?", or who is friendly, vague, and gives you nothing. The skill is not knowing the questions. It is getting to the fourth one without sounding like you are working through a form, redirecting without being rude, and holding the impact question steady while the buyer tries to skip past it.

That is only learned by running the call repeatedly against buyers who behave like real ones. Pavone gives you an AI buyer who talks too much, deflects, and goes vague on cost, so you can practise steering a discovery call to the number and the next step before you do it with a deal on the line.