Discovery questions that uncover a buyer’s actual priority

A buyer has given you thirty minutes. You have a list of questions and a product you want to discuss. The danger is finishing with a page of answers and little understanding of why anything needs to change. Useful discovery gives the buyer room to describe their work, then helps both sides make sense of it.

Start with a situation, rather than a product-shaped question

“Would better reporting help?” invites agreement with your proposed solution. “Walk me through how you prepare the weekly report” reveals the work. Ask about a recent instance so the conversation has something concrete to examine. A broad complaint such as “our reporting is painful” can mean unreliable data, slow preparation, awkward approvals or an audience that ignores the result.

Before the call, choose two or three areas relevant to this buyer’s role. Treat them as hypotheses. Tell the buyer what you hope to understand and check that the agenda fits their priorities. Their most pressing concern may differ from the reason you booked the meeting.

Follow the answer through work, consequence and priority

Use the buyer’s own words to choose the next question. If preparation takes time, ask which steps consume it. If errors occur, ask how they are detected and who deals with them. Then explore the consequence: delayed decisions, duplicated work or another effect the buyer identifies. Do not supply a dramatic financial cost because the answer sounds promising.

• Work: “What happened the last time you did this?”
• Difficulty: “Where did the process become harder?”
• Consequence: “What did that mean for the people relying on it?”
• Priority: “What would make this worth changing now?”

These prompts are a route through a conversation. Listen for answers already given, so you do not ask the buyer to repeat themselves.

Separate a useful signal from your own interpretation

An illustrative buyer says three managers spend Friday checking inconsistent forecasts. The seller assumes that automation is the priority. A follow-up reveals that the managers disagree about what counts as a qualified opportunity. A faster report could reproduce the same disagreement more quickly.

A useful summary would be: “You want the team to use a consistent definition before you improve the reporting process. Have I understood that?” The buyer can confirm, correct or add nuance. Only then explore what evidence would help them assess an approach. This avoids turning an early symptom into a premature recommendation.

Keep a discovery note you can actually use

Organise notes around meaning, rather than the order of your questions. Use four short fields:

1. Current situation: the workflow and people involved.
2. Buyer-stated difficulty: their words and a concrete example.
3. Desired change: what they want to do differently and why.
4. Open question: what remains uncertain, who can clarify it and when.

Mark assumptions explicitly. “Potential integration requirement; not yet validated” is more useful to a Sales Engineer than “needs integration”. Check which stakeholders would experience the proposed change and whose criteria are still missing. A single contact can describe their own view without representing every decision maker.

Rehearse the follow-up, not just the opening question

Ask a colleague to play a buyer who gives a plausible but incomplete answer. Your task is to uncover a specific instance, explore its significance and offer an accurate summary. The observer should note the follow-up that changed your understanding and any point where you introduced a solution too early.

Repeat the conversation using the feedback. At the close of a real meeting, summarise the priority and agree which remaining question deserves attention next. A shorter list of well-understood needs gives the next conversation a firmer purpose.

NewSkilz shapes discovery practice around your buyer roles, approved proposition and the answers your sellers find hardest to explore.