How do you run a discovery call that closes?

A discovery call closes when the prospect feels genuinely understood before you say a single word about your product. The structure that achieves this is diagnostic, not promotional: you identify the specific pain, quantify its cost, and let the prospect talk themselves into urgency. Done right, the 'close' is simply confirming what the conversation already made obvious.

Set the agenda before the call starts

Most discovery calls fail in the first ninety seconds because neither side is clear on what a successful outcome looks like. Send a one-paragraph pre-call note: state the three things you want to cover, ask the prospect to add anything they care about, and name what you'll both decide at the end. This small act signals competence, reduces the prospect's anxiety, and stops you from running a demo when you should still be asking questions.

When the call opens, reinforce this frame out loud. Something like: 'I want to spend most of our time understanding your situation before I show you anything — that way I won't waste your time on features that don't apply.' Prospects almost always agree. This framing also gives you legitimate permission to delay the product pitch, which is where most salespeople self-sabotage by rushing.

Diagnose before you prescribe

The core discipline of a discovery call is the same one Paul Graham identifies as essential to doing work that matters: an obsessive interest in the specific problem in front of you, not a rehearsed solution you're trying to force onto it. Graham's point about independent-mindedness — the willingness to question assumptions rather than accept conventional framings — applies directly here. The best discovery questions challenge the prospect's own framing: 'You mentioned this is a Q4 priority — what makes it more urgent now than it was six months ago?' forces real thinking instead of polished talking-points.

The practical sequence is: situation (what's true today), complication (what's breaking or costly), implication (what happens if nothing changes), and desired outcome (what good looks like). This is not a script — it's a diagnostic logic. You go deeper on whichever layer reveals the most tension. If a prospect says 'our reporting is slow,' the situation question is answered. The complication question is: 'What decisions are you making slower because of that?' The implication is: 'What did that cost you last quarter?' The outcome is: 'If reporting was instant, what would you do differently?' Each question multiplies urgency without you manufacturing it artificially.

Control silence and avoid the feature trap

After a strong diagnostic question, most salespeople fill the silence immediately — either answering their own question or pivoting to a feature. Neither works. Silence after a question is productive; the prospect is doing the work of connecting your question to their real situation. Let it run. Count to seven in your head if you have to. The answers that come after a pause are almost always more honest and more useful than the first instinctive response.

The feature trap is the other common failure: a prospect mentions a symptom and you immediately map it to your product's capability. This is premature. You have not yet established that their symptom is actually the root problem, that solving it is a genuine priority, or that they have the budget and authority to act. A discovery call that turns into an impromptu demo is almost always dead on arrival — you've handed over control and signaled that you can be led off-topic. Stay in diagnostic mode until you have enough to make a credible case, then and only then show anything.

Qualify on power, priority, and path — not just pain

Pain is necessary but not sufficient. Countless deals die not because the prospect didn't have a problem, but because the person on the call couldn't act on solving it. You need to know: who actually owns the budget decision, whether this problem is ranked high enough to get resources in the next 90 days, and what the internal approval process looks like. These are uncomfortable questions for many founders and early sales reps, but asking them directly is a sign of respect — it tells the prospect you take their time seriously and won't put them through a six-week evaluation only to stall at procurement.

A clean way to surface this without sounding transactional: 'Assuming this conversation goes well and you think we're a fit, walk me through how a decision like this would actually get made on your side.' This question reveals authority structures, potential blockers, procurement timelines, and competing priorities in one move. The prospect's answer also tells you how sophisticated their buying process is — which affects how much discovery you still need to do.

Close the call on a specific next step, not vague interest

The close of a discovery call is not a contract — it's a committed next step that both sides are willing to put on a calendar before you hang up. 'I'll send over some information' is not a next step. 'Let's schedule a 30-minute technical review with your CTO on Thursday' is a next step. The specificity signals that the discovery actually surfaced something worth acting on.

Before closing, do a brief verbal summary: 'Based on what you've told me, the core problem is X, it's costing you roughly Y, and the reason it hasn't been solved yet is Z — does that feel accurate?' This accomplishes three things: it confirms you listened, it lets the prospect correct any misunderstanding, and it re-anchors the urgency in their own words rather than yours. If they confirm your summary and agree to a next step, you have a qualified opportunity. If they hedge, you've discovered a gap in your diagnosis — which is valuable information you'd rather have now than three calls later.

The one thing to do

Before your next discovery call, write down the three diagnostic questions you'll ask to surface pain, cost, and urgency — and commit to not showing the product until all three are answered.

Frequently asked questions

How long should a discovery call be?

30–45 minutes is the practical ceiling for most early-stage deals. Beyond that, you're either going too deep without enough trust built, or you've wandered off-topic. If you still don't have enough information after 45 minutes, book a second discovery session rather than padding the first.

When should you share pricing on a discovery call?

Only after you've confirmed the pain is real, the priority is high enough to act on, and the decision-maker is either on the call or explicitly bought in. Sharing pricing before those three conditions are met invites sticker shock without context — and context is what converts price from an obstacle into an investment.

What if the prospect wants a demo immediately?

Acknowledge it and redirect: 'I'll absolutely show you the product — I just want to spend 10 minutes understanding your setup first so I can make the demo actually relevant to you.' Almost every prospect will accept this. If they refuse, that's diagnostic data about how they buy.

How do you handle a prospect who gives only one-word answers?

Switch from open-ended to hypothetical questions. Instead of 'What are your main challenges?', try 'If you could change one thing about how your team handles this today, what would it be?' Hypotheticals lower the stakes and tend to unlock more specific, honest answers from guarded buyers.

Sources

More playbook answers · Growth Prophet home