Good discovery questions create a path. Each answer should point to the next question, moving from the prospect's situation to the problem, its cause, its importance, and how a decision would happen. Decide the target before writing the question: choose the problem to surface and what you want the prospect to say. That keeps discovery specific and deep. Curiosity alone can leave you collecting facts; a planned sequence gives every question a job.
Design the path
Write the route before the wording. Decide what answer each question should earn and where it should take the conversation.
Choose the problem you want to surface before you choose the question.1 Write down what you want the prospect to say before creating probing questions.2 A question earns its place in discovery when its reason is about the prospect.3
For each question, note the answer that would show the problem is present, the next question that would deepen it, and why that information matters to the prospect. Prepare enough context to be curious about the account without trying to predict every answer.4 This lets you ask directly while showing why the question belongs.
Start with the situation
Start with lightweight questions so you can understand the prospect's situation.5 These questions can also show that you researched the account.6 Try:
"What's on your whiteboard right now?".7
"What's red on your dashboard right now?".8
After the opening answer, do not collect several unrelated facts. Choose the part with the most tension and stay with it.
Turn the situation into a problem
The first answer usually describes a condition. Find what happened, what caused it, or what it affects.
Ask what prompted the stated need before discussing a solution.9 When you have a prospect-specific observation, check whether it explains the call:
"I'm curious, is that what's driving this conversation?".10
Ask when the prospect realized the problem existed.11 Asking this almost always produces a painful story.12 Then ask:
"Why do you think that is?".13
Stay with the thread until the prospect gives a specific account of what happened and why it matters. A label such as "visibility" or "efficiency" is only a starting point. The useful answer contains an event, a consequence, or a reason the issue has gained attention.
Go deeper on the same thread
Keep each next question attached to the prospect's last answer. Depth comes from narrowing the problem instead of opening a fresh topic.
Building each discovery question on the previous answer can reach one or two deep problems in 10 minutes before you move to the demo.14 Keep your questions focused on the prospect's world and priorities.15
When the prospect asks you a question, investigate the picture behind it. Ask what led them to ask, because the goal is to get them to describe the mental picture that caused the question.16 The answer often shows what they are comparing, fearing, or trying to make possible.
Test relevance and assumptions
Treat your interpretation as a working hypothesis and give the prospect an easy way to correct it before you build the rest of the call around it.
Ask whether the problems under discussion are relevant to the prospect.17 Check an assumption with a short question:
"Is that right?".18
Keep a reason for every question.19 Test it by asking whether you could explain why you needed the information if the prospect asked.20 If you cannot, remove the question or connect it to something they have already said.
Move into buying conditions
A problem can be real and still fail to create a decision. Once the prospect confirms that the issue matters, ask about the conditions that would allow the business to act.
A qualification drill checks whether the buyer has a problem, when implementation is planned, and how the buyer will purchase.21 Ask about competitive differences when the prospect has mentioned another approach. Those questions can reveal the competitors, what they propose, and what the customer prefers or dislikes.22
Ask what matters to the procurement contact and the economic buyer.23 If a champion may introduce you to a power stakeholder, ask what that stakeholder cares about before making the request.24 The answer tells you which part of the problem belongs in the next conversation and which part still needs work.
Change the question shape as the call moves
Let the prospect explain early, then use tighter checks when you need to confirm a detail or keep the exchange moving.
On cold calls, stop using close-ended questions as your default.25 In a live conversation, close-ended discovery can create conversational back-and-forth while you answer the buyer's question.26 Make the question easy for the prospect to answer.27
Before a demo, ask each stakeholder an individualized one-to-one discovery question.28 When you show a component, ask how it fits into the prospect's existing workflow:
"Could you explain to me how that fits into your existing workflow?".29
That keeps the conversation attached to their process while you learn what the product would need to change.
What not to do
These mistakes can make discovery feel like an interrogation or leave you with facts that do not guide the next step.
- Do not open with "what's your biggest problem?" or "what keeps you up at night?" as stock wording. The first question should address the concern without sounding clichéd.30
- Do not force substantive questions before the prospect is engaged. Prospects are much more open to those questions after they are excited and leaning in.31
- Do not treat a pricing question as the end of discovery. Use it as an opportunity to discover.32
Once the prospect gives a concrete account of the problem and its buying conditions, take the agreed next step.