The first twenty discovery calls I ran were basically interrogations. I had a list of questions I wanted answered. I asked them in order. I typed notes. At the end I said I would send over some information and we would talk next week. Half the time there was no next week.
I thought I was doing discovery. I was actually doing a questionnaire with a stranger. Those are not the same thing.
The shift came when I stopped thinking about discovery as information-gathering and started thinking about it as helping the prospect articulate a problem they already have. The job is not to figure out whether you can help them. The job is to help them figure out whether they need to solve this problem at all, and why now. When you do that well, you do not close deals. They close themselves.
The actual goal of a discovery call
Most founders think the goal is qualification. They want to find out if this person can buy, whether the company is the right size, whether there is budget. Those things matter, but they are secondary. If you lead with qualification, you sound like you are screening someone rather than trying to help them.
The actual goal is urgency. By the end of the call, the prospect should understand the cost of their current situation better than they did before they got on with you. If they walk away thinking this is a problem they need to solve soon, you have done your job. If they walk away thinking it is vaguely interesting but not urgent, you have lost the deal even if they sounded enthusiastic.
The four-part structure
I use a four-part structure on every call: Situation, Problem, Impact, Vision. It is not a rigid script. It is a shape the conversation should move through.
Situation is quick. You want to understand how they currently handle the thing you help with. What does their workflow look like today? Who else is involved? How long have they been doing it this way? You need context, but do not linger here. People do not get emotional about their situation. They get emotional about their problems.
Problem is where you slow down. What is frustrating about the current approach? What breaks down when things get busy? What has to happen manually that should not have to? The goal is not to get a list of complaints. It is to find the one or two things that actually hurt. The way you know you have hit a real problem is the energy in their voice shifts. They start giving you more than you asked for.
Impact is where most founders skip ahead too fast. Before you move toward solutions, you need to understand what the problem is actually costing them. Not in theory. In specifics. How many hours a week does this take? What does the team have to do instead of fixing this? Has it cost you a customer? Has it slowed a hire? The answers to these questions are the reason anyone is going to sign a contract. If you do not surface them, you will lose to inertia.
Vision is the turn. Once the problem and its cost are clear, you ask them to describe what good looks like. If this were solved, what would be different? What would you be able to do that you cannot do now? This does two things. First, it lets you see if your solution actually delivers what they need. Second, it gets them to articulate the outcome in their own words, which is far more persuasive than anything you could say to them.
The question that moves every deal
The single most useful question I have found is some version of: what happens if this does not get solved in the next six months? This is not a trick. It is a genuine question about priority. The answer tells you whether this is a burning problem or a background annoyance.
If the answer is something like we keep doing what we are doing and it stays messy, that is a signal the urgency is low. You need to dig further into impact or be honest with yourself that this is not the right time. If the answer is we will miss our Q3 target, or we will have to hire two more people just to keep up, or we will lose another customer like the one we lost last month, you have real urgency to work with.
The mistake that kills otherwise good calls
The most common mistake I see founders make, and the one I made for the longest time, is pivoting to the product too early. The moment you hear a problem you can solve, you want to tell them about it. Resist that. Every time you shift into pitch mode during discovery, you give up information. You tip your hand about what you think the problem is before you have heard enough to know whether you are right. And you break the flow of a conversation where the prospect is opening up.
Save the product for after the call, or at least for the last ten minutes. The demo should be the natural response to the problem you just spent thirty minutes surfacing together. When you show them a feature that directly addresses the thing they just told you costs them two hours a week, it lands completely differently than showing them the same feature in a generic walkthrough.
How to end the call
Never end with I will send over some information. That is not a next step. That is a way of avoiding a next step while sounding polite.
Before the call ends, summarize what you heard in two or three sentences. Name the specific problem, the specific cost, and the specific outcome they described. Then ask a binary question: does that match what you were hoping to solve? If yes, propose a concrete next step with a date. If they want to think about it, that is fine, but ask what specifically they need to think through. That answer tells you what the real objection is.
The goal is not to pressure anyone. It is to get clarity. A clear no is better than a slow maybe. A slow maybe will drain your calendar and your morale for months.
What to do after the call
Send a follow-up email within an hour. Not a wall of text. Three or four sentences that reflect back what you heard: the problem they named, the cost they described, and the next step you agreed on. Write it in their language, not yours. If they said we are drowning in manual reconciliation every month-end, use that phrase. If they said it takes us three days to onboard a new customer when it should take one, use those words.
This does two things. It shows you were actually listening, which is rare enough to be memorable. And it gives them an artifact they can use to justify the next step internally. In B2B, most of your champions cannot approve a purchase on their own. The email you send them after a discovery call is often the thing they forward to their manager or CFO. Make it easy for them to make the case.
Discovery is not a step in a sales process. It is the whole game. If you get it right, everything that follows is easier. If you skip it or rush it, no amount of follow-up will recover the deal.