Discovery Calls

Frameworks, question banks, active listening, next steps.

What discovery really is

Discovery is not "questions before the demo." It is the entire deal in miniature. Done well, you leave a first discovery call knowing whether this is a real opportunity, who else needs to be involved, what "success" means to the buyer in numbers, and when a decision must be made. Done poorly, you leave with a demo scheduled and nothing else.

The four goals of a discovery call

1. Diagnose the pain — root cause, not symptom.
2. Quantify the impact — in hours, dollars, or risk.
3. Map the buying process — who, when, how.
4. Earn a real next step — with a specific date.

Structure of a great discovery call

Question frameworks

SPIN (Situation, Problem, Implication, Need-Payoff) is the most reliable skeleton. Layer MEDDIC on top when the deal grows.

• Situation — how things work today.
• Problem — what's broken.
• Implication — what happens if it isn't fixed.
• Need-Payoff — what fixing it would unlock.

The two most under-used are Implication and Need-Payoff. They create the emotional case for change. See SPIN Selling.

A discovery call question bank

Warm-up

• "What does your day-to-day look like right now?"
• "What was the trigger for taking this call?"
• "What have you already looked at in this space?"

Pain diagnosis

• "Walk me through how [process] works today, from start to finish."
• "Where does that break down most often?"
• "How often does that happen, and who's affected when it does?"
• "What's the workaround your team uses when it breaks?"

Impact / implication

• "If I ran the math on that, roughly what would it cost you in a quarter?"
• "What does your boss say when that happens?"
• "If nothing changes in the next 6 months, what breaks?"
• "How much of your week does this eat?"

Future state

• "What would 'solved' look like — in one sentence?"
• "If we could hand you [outcome] in 90 days, what would that free you up to do?"

Buying process

• "Who else typically weighs in on decisions like this?"
• "How does your team usually evaluate and buy a new tool?"
• "Is there a timeline you're working toward — a board meeting, quarter end, launch?"
• "What could get in the way of moving forward, even if you loved it?"

Active listening — how to do it

• 3-second pause after they finish. Almost always they add the most important sentence.
• Label emotions: "It sounds like this has been frustrating for a while." (Chris Voss's mirroring.)
• Echo the last 2–3 words of what they said to prompt elaboration.
• Take notes visibly. Say "let me make sure I got that" as you write.
• Never interrupt. Ever. Even to answer a good question.

Setting a real next step

"I'll send over some info" is not a next step. A real next step has:

• A specific meeting on both calendars.
• A named attendee list (with any missing stakeholders identified).
• An agreed agenda — usually a tailored demo focused on their top 2 pains.
• A shared success criterion: "If [X] works the way we described, we'll move to a pilot."

Sample discovery call arc

You: Thanks for making time. What I'd love to do — spend the first 20 minutes understanding your world and where things are painful, then use the last 10 to figure out if it makes sense to go deeper. Cool?

Buyer: Sounds good.

You: Perfect — take me through how pipeline reviews work today, top to bottom.

[Buyer explains messy spreadsheet process.]

You: Got it. And when the numbers are wrong on Monday morning — what happens?

Buyer: Honestly it's the worst hour of my week. The VP grills me and I can never fully defend the number.

You: That sounds really frustrating. If we could get that hour back and hand you a defensible number, what would that unlock for you?

Notice: no product mentions yet. The buyer is doing 80% of the talking. This is the standard to aim for.