Situation First

sell

Discovery Without Interrogation

Published · 8 min read

Bad discovery feels like a job interview conducted by someone who already has a candidate in mind. Questions come rapid-fire. Each answer gets a perfunctory “great” before the next question arrives. At the end, the buyer has shared a lot of information and feels vaguely processed.

Good discovery feels like talking to someone who’s genuinely curious about a situation they don’t yet fully understand. Questions build on each other. There’s silence. The conversation produces clarity for both people — and the buyer ends it feeling like someone finally listened.

The difference is not technique. It’s intent. Before any framework, decide what you’re actually trying to learn: what does this person need to make a confident decision, and what would make them confidently say no? If you’re trying to qualify them for your pipeline rather than understand their reality, they’ll feel it.

Who it’s for

Anyone who needs information from another person in a way that preserves — or ideally builds — the relationship. Founders on early customer calls. AEs on first meetings. Consultants scoping an engagement. ICs trying to understand what a stakeholder actually wants before proposing a solution.

Why most discovery fails

Asking questions you can answer with research. If you ask what industry they’re in, what their company size is, or what tools they use — information available on their website — you’ve wasted their time and signaled you didn’t prepare. Do the research. Save the questions for things you can’t know.

Stackfiring. Three questions in a row, without pausing for the answers, produces worse information than one question followed by real listening. People give shorter, safer answers when they feel interrogated. They give longer, more honest answers when they feel heard.

Asking what you want to know instead of what they want to tell you. “What’s your budget?” is a question you want the answer to. “How have you funded changes like this in the past?” is a question that gets you the same information while also teaching you about their process, their authority level, and how long things take. Same information, completely different experience.

Not naming your intent. One of the most effective things you can do at the start of a discovery call is tell the person what you’re trying to figure out. “I want to understand your situation well enough to tell you honestly whether we can help — and if we can’t, I’d rather tell you now than waste your time.” This shifts the conversation from “me qualifying you” to “us figuring out together.”

Framework: seven questions that build on each other

These aren’t a script. They’re a sequence of investigative directions, ordered to move from opening to depth without jumping ahead.

1. What prompted this conversation now? The word “now” is doing real work. Not “why are you interested” — that’s abstract. “Now” asks what specifically shifted that made this a priority today rather than three months ago. The answer usually tells you the urgency, the triggering event, and implicitly who’s applying pressure internally.

Listen for: urgency signals, external pressure, internal frustration that’s been building.

2. If this went well in 90 days, what would be different? Ask for a specific picture of success — not what they want the solution to do, but what their world looks like if it works. This surfaces the outcome they actually care about, which is almost never the one stated in the original brief.

Listen for: the gap between what they say (“we’d have faster reporting”) and what they mean (“my team wouldn’t be scrambling to answer the CFO’s questions at 6pm”).

3. Walk me through how you handle this today. Don’t ask “what’s your current process.” Ask them to walk you through it — present tense, step by step, with them as the narrator. People reveal far more about friction, workarounds, and ownership when they’re narrating a workflow than when they’re summarizing it.

Listen for: the steps they skip because they’re too embarrassing, the tools they mention apologetically, the moments where they say “and then we have to manually…” — those are the real pain points.

4. What have you already tried? Every honest answer to this question tells you two things: what doesn’t work (which you might be about to propose), and what mattered enough to them to invest time in solving. It also signals whether you’re the first conversation or the fifth — which changes what they need from you.

Listen for: solutions that failed and why, which tells you what constraints are real versus preferences.

5. What would you need to see to feel confident — not just interested? “Interested” is free. Confidence requires evidence. Ask for the specific proof bar: a reference customer, a pilot, a technical review, a specific metric. This question does two things: it tells you exactly what to deliver, and it gently moves the conversation from exploration to evaluation.

Listen for: the difference between “I’d want a trial” (low trust, standard evaluation) and “I’d want to talk to your customer at [Company]” (high specificity — they’ve already researched you).

6. What would make you say no? This is the most important question most people skip. Asking what would make them say no gives you the actual veto criteria — the real concerns they’re managing — rather than the objections they’ll raise after you’ve invested weeks in a proposal. It also signals that you’re not desperate for the deal, which itself builds trust.

Listen for: process constraints (“we can only start after Q2 budget”) vs. fit concerns (“I’m not sure this works for our scale”) vs. political concerns (“there’s a competing internal initiative”). Each requires a different response.

7. Who else cares about this, even if they’re not in the room? Decisions are almost never made by the person you’re talking to alone. This question surfaces the full decision landscape without putting the person on the spot about their authority level.

Listen for: names of specific people, which tells you who to ask to meet; and vague gestures (“the team,” “leadership”) which tells you the decision criteria aren’t established yet.

Listening technique: the mirror

After each answer, repeat the last three to five words back as a question. It sounds like this:

Them: “The main issue is that our reporting takes two days instead of two hours.”

You: “Two days instead of two hours?”

Them: [explains further, often with the real detail they almost didn’t mention]

The mirror is not a trick. It signals that you heard the specific thing they said, and it creates a natural pause that almost always produces more information. Use it sparingly — every other answer, not every one.

What to do with the answers

Write them down. Actually write them down, in the call, in front of them. “I’m taking notes — tell me if I get anything wrong.” This does three things: it signals that you take their answers seriously; it creates a moment of shared accountability (they can correct your notes); and it gives you a reference for the proposal or follow-up that maps directly to their language.

When you send a follow-up, reflect their words back. Not your summary. Their words. “You mentioned the two-day reporting lag is what’s forcing the manual scramble at end of month — our pilot would address that in the first two weeks.”

Worked example

The interrogation version: “What’s your team size? What tools are you using? What’s your timeline? Do you have budget allocated?”

(None of these questions build on each other. None of them feel like curiosity. The buyer answers each one and feels like they’re filling out a form.)

The discovery version: “What made you decide to take this meeting now, versus three months ago?” → [Listen, mirror one detail.] → “You mentioned the finance team started flagging it — is that a new thing?” → [Listen.] → “Walk me through what happens from when a client asks for that report to when you get it to them.” → [Listen.] → “What’s the most painful step in that?” → [Listen, mirror.] → “If that one step didn’t exist — or took ten minutes instead of two days — what would that change for your team?”

This version takes longer. It also produces information you can actually use.

Practice prompt

Before your next discovery call, write seven questions — one for each direction above. Then remove any question you can answer with research. What you’re left with is your actual agenda. Run the call. After, note which question produced the most useful information you didn’t expect. That’s usually the one to lead with next time.

← All sell guides · Guide builder · Resources & checklists