Spend the first half of the call asking what they do today and what it costs them, not demoing. Show only the part of the product that addresses what they just described. Answer the price question directly the first time it is asked. End by agreeing a specific next step with a date, because a call that ends on a good feeling and no date is a call that produces nothing.
Someone agreed to a call. You have thirty minutes, a working product, and no idea what happens in the middle. So you do the thing that feels safe and demo for twenty-five minutes, and it ends warmly, and nothing happens afterwards.
The short answer is to ask for the first half and show for the second. A sales call is not a presentation of your product; it is finding out whether this person has the problem badly enough to change something, and then showing only the part that matters to them.
What a discovery call is for
A discovery call is a conversation whose purpose is to establish whether a problem exists, what it currently costs, and who decides. That is all. It is not a demo, not a pitch, and not a chance to prove the architecture is sound.
Engineers struggle with this for an understandable reason. In engineering, showing the work is how you establish credibility, and being asked to talk about something without demonstrating it feels like bluffing. On a sales call, showing the work before you know what the person needs is not credibility, it is guessing in public.
The four questions
You do not need a script. You need four things answered before you open the product, and they can be asked in any order that fits the conversation.
- What do you do about this today? Establishes whether the problem is real. If the answer is "nothing", it may not be a problem worth paying to fix.
- How long has that been the case, and what changed recently? Finds out whether anything is forcing a decision. Problems that have been tolerated for three years are usually tolerable for a fourth.
- What does it cost you, in money or hours? Gives you the anchor for price and tells you whether your number is going to sound large or trivial.
- If you decided to change this, who else would be involved? Tells you whether you are talking to a buyer or to an enthusiast who will need to convince someone else.
The fourth is the one founders skip because it feels presumptuous. It is the one that most often explains why a call that went brilliantly produced nothing: the person loved it and could never have bought it.
How to ask without sounding like a form
These are not questions to read out. The difference between discovery and an interrogation is whether the next question follows from the last answer, so ask one, then follow it wherever it goes, and only move on when you have the thing you needed.
The most useful follow-up in the language is "what do you mean by that". People describe problems in compressed shorthand, and the expanded version is where the specifics live. Someone says outreach is a nightmare; what they mean, three sentences later, is that they have no list and cannot face building one.
Then stop talking
Having asked, let the answer finish. The instinct after a short answer is to fill the silence, usually by explaining a feature. Resist it for three seconds and most people keep going, and the second half of what they say is more useful than the first.
The other discipline is to write down their exact words, not your summary. "It takes forever" and "I lose a day a week to it" mean the same thing and are worth very different amounts when you repeat one of them back in a proposal.
Taking notes without disappearing into them
Typing while someone talks reads as distraction on a video call, and not typing means losing the exact phrasing that makes a follow-up land. The compromise most founders settle on is to capture verbatim only the sentences that describe the problem or a number, and to paraphrase everything else afterwards from memory.
Saying what you are doing removes the awkwardness entirely. "I am going to write that down exactly as you said it" is flattering rather than rude, and it usually produces a slower, more careful version of the same sentence, which is the one you wanted.
Demo only what they described
Now open the product, and show only the part that addresses what they just told you. Not the tour. Not the feature you are proudest of. The thing that solves the sentence they said out loud four minutes ago.
The difference is not cosmetic. A tour asks the buyer to work out which parts apply to them, which is work, and a person doing work is not a person being persuaded. Showing one relevant thing does that work for them.
If you are showing something they did not ask about, you are demonstrating rather than selling, and demonstrating is a habit worth catching yourself in.
One more failure mode worth naming, because it is specific to founders who built the thing. When something does not work during a demo, the instinct is to explain why, in detail, from the architecture down. The buyer does not need that and the explanation makes a small glitch into the memorable part of the call.
"That is a bug, I will fix it this week" is a complete sentence and a better one. Technical audiences in particular respect the short version, because a founder who diagnoses live is a founder who will do that instead of shipping.
The price question
At some point they ask what it costs. Answer it. Immediately, plainly, with the number.
The instinct to defer, to say it depends, or to ask about their budget first, reads as evasion, and the trust it costs is worth more than the negotiating position it buys. You are a small company they have just met; the only advantage you have over a large one is being straightforward.
| What they say | What it usually means | What to do |
|---|---|---|
| "That's fine" | Too low, or they are not buying | Ask what they expected |
| "That's expensive" | Negotiating, or value not yet clear | Ask what they are comparing it to |
| "What's included?" | Interested, checking scope | Answer, then ask what they need included |
| "Is there a discount?" | Buying, testing the edges | Hold, or trade for something: a case study, an annual term |
| "Let me think about it" | No, said politely | Ask what would have to be true for it to be a yes |
The last row is the important one. "Let me think about it" is almost never someone going away to think. It is a decline that avoids the discomfort of declining, and the only useful response is a question that surfaces the real objection while you still have them.
When the objection is not really about price
Two objections come up constantly and neither is what it appears to be. "We already have something for this" is usually true and usually not an obstacle, because having a tool and having the problem solved are different states; the useful reply asks what it does not do.
"Now is not a good time" is either real or a soft decline, and one question separates them. Ask what would need to be different for the timing to work. A real timing problem produces a specific answer with a date attached. A decline produces a vague one, and you have saved yourself three follow-ups.
End with a date
The most common way a good call produces nothing is ending on warmth. Everyone enjoyed it, the founder says they will follow up, and the thread dies in a week.
Before you hang up, agree one specific thing that happens next, with a date and a named person. "I will send the trial link today, you will try it on the Tuesday data, and we will speak Thursday at four." If they will not agree to a next step, that is the answer, and it is better to have it now than after three unanswered follow-ups.
Write the summary while it is fresh, in their words, and send it the same day. The email is short: what you heard, what you agreed, when. That email is doing two jobs at once, confirming you listened and creating a written record of a commitment.
The calls that are worth losing quickly
Not every call should be saved. A person who has no budget, no authority and no urgency is not a prospect who needs better handling, and the most valuable thing a founder can learn is how to end that call at fifteen minutes rather than thirty-five.
The polite exit is honest: this does not sound like the right fit today, here is what would have to be true for it to be, do come back if that changes. People respect it, it occasionally produces a referral on the spot, and it returns twenty minutes to the only person in the company who can build the product.
Where this advice is wrong
The call is with a developer evaluating a technical product
If you are selling infrastructure to an engineer, the demo is the discovery. They want to see it work, and a founder who asks four questions before showing anything reads as sales process, which is the thing they were hoping to avoid. Show it early, then ask.
They came to you already convinced
If someone arrived from a referral with their card out, do not run discovery at them. Confirm the problem in one question, answer whatever they ask, and get out of the way. Over-qualifying a ready buyer is a real way to lose one.
You are still trying to find out if the product should exist
Early customer-development conversations are a different exercise with a different goal, and mixing them produces bad versions of both. If you are learning rather than selling, say so at the start, do not demo, and do not ask for the sale. People are generous with their time when they are not being sold to.
The part that gets easier
Founders assume that sales calls require a personality they do not have. Mostly they require a structure, and the structure is the thing above: ask, listen, show one thing, answer the price question, agree a date.
What does not get easier is the volume. Getting on the call is the hard part, and it is the part that runs on outreach rather than on charm. That half of the problem is covered in where your first 100 customers come from, and it is the half Operater's Sales agent is built to carry, because a founder who can run a good call is still stuck if nobody books one.
Key takeaways
- The person who asks the questions controls the call, and the demo is not a question.
- Every minute of demo before you understand their situation is a minute spent guessing.
- Dodging the price question costs more trust than any number you could name.
- "This is great, let me think about it" is a no that has not been said out loud yet.
- A call without an agreed next step and a date has not advanced anything, however well it went.