What a discovery call is actually for

Ask a technical founder how the first call went and you will often hear "really well, they loved the demo." Ask what the buyer's current process costs them and you get a pause.

That pause is the whole problem. The call went well as a presentation and did nothing as a sale.

The job of the first real conversation

A discovery call has one job: to end with the buyer holding a number they did not have when the call started, about their own business, that they believe.

Everything else - rapport, product fit, next steps - follows from that. Without it you are asking someone to spend money to fix a problem they have never sized, which is why the price feels big later.

You are not there to explain your product. You are there to help someone add up a number they have never added up.

Why founders demo instead

Because the product is the part you are confident about. You built it. When a conversation gets uncertain, you steer toward the thing you know, and the demo is right there.

There is also a politeness trap. The buyer asks "so what does it do?" in the first two minutes, and it feels rude not to answer. So you answer for thirty-five minutes.

A reasonable escape: "I can show you, and I will. Can I ask you three things first so I only show you the parts that matter?" Almost nobody says no.

The arithmetic, in four questions

Ask these in order, and write the answers down where the buyer can see them.

• Walk me through what happens today. Step by step, with the person who actually does it. Not the manager's version.
• How often does that happen? Per week, per site, per customer, per claim. Get a real number, even a rough one.
• What does it cost you each time it goes wrong? Time, rework, a lost customer, a missed deadline, a fine.
• What have you already tried? Failed attempts are cost, and they are usually the most vivid part of the story.

Then do the multiplication out loud and check it: "So on your numbers that is roughly X a year. Does that feel about right, or is it higher?"

Asking whether it is higher is deliberate. It usually is, and now they are the one arguing the problem up.

The three answers that should change your behaviour

• "I'd have to check." Good. That is a second meeting with a reason, and probably a second person.
• "It's not really costing us anything." Believe them. This is not a deal, it is a nice conversation. Disqualify early and thank them properly.
• "We tried that two years ago and it failed." Stop and dig. Whatever killed it last time will be waiting for you, and knowing it now is worth more than anything on your slides.

Silence is a technique, not an accident

The single most common thing I fix in a founder's discovery is that they answer their own questions. They ask something good, leave a two-second gap, feel the discomfort, and fill it with a helpful suggestion.

The buyer was about to say something more interesting than your suggestion. Count to four in your head. It feels much longer to you than to them.

How to close a discovery call

Not with "I'll send some information over." Close it three ways:

• Play back the number. "So this is costing you roughly X, and the bit that hurts most is Y." Let them correct you. Corrections are gold.
• Name the next step and who else needs to be in it. The person who was not on the call is usually the person who decides.
• Book it now. A date in a calendar, not a promise to find one.

What this does to your pricing conversation

Everything, and this is the real payoff. When the number exists, your price stops being an announcement and becomes a comparison. The same figure that would have caused a flinch in week one is easy in week three, and nothing about the product changed.

Only the order of the conversation did.

So think about your last first call: at the end of it, could your buyer have told a colleague what their problem costs them - in their own numbers, without you in the room?