You built the thing. You know what it does, you know why it's good, and on a call with someone who might buy it, that knowledge is exactly what gets in your way. The pitch arrives in minute two because you're excited and because silence before you've said anything about the product feels like wasted time. It isn't wasted. It's the only part of the call where you learn something you didn't already know, and once you start talking, that part is over.
The arithmetic of a discovery call, checked against a clock
Set a timer on your next call and look at it afterward, honestly. A thirty-minute call is 1,800 seconds. If you're talking for twenty of those thirty minutes, you've used two-thirds of the room on information the prospect already had, which is what you think, and left one-third for information you didn't have, which is what they think. That ratio is backwards for a call whose entire purpose is finding out whether there's a real problem worth solving. Flip it, on purpose, and the pitch you eventually give lands better anyway, because it's aimed at something specific instead of everything.
Five questions, and why each one earns its place
"What are you doing about this today?" Not "do you have this problem," which almost everyone answers yes to out of politeness. Ask what they're currently doing, specifically, and you find out whether the problem is severe enough that they've already built a workaround, however bad. A workaround, even a terrible one, is a much stronger signal than an admitted problem with no workaround, because it means they've already spent effort on it.
"What does it cost you when this goes wrong?" Push for a number, even a rough one, and let them do the arithmetic out loud. "We lose about a day a week to this across the team" is worth more than any adjective they could use to describe how much the problem bothers them, because a day a week is a number you can both do something with later — multiply it by a rate, compare it to your price, and the case for buying starts building itself in front of them rather than being argued by you.
"Why is this the month you're dealing with it, rather than last month or next month?" This is the question that separates a real prospect from someone being polite on a call they agreed to out of courtesy rather than urgency. If there's a real answer — a deadline, a new hire, a bad month that finally broke the workaround — you're talking to someone who might actually buy soon. If the honest answer is "no particular reason," you've just learned the timeline is fictional, and you can stop planning around a close date that was never real.
"Who else needs to agree before you can say yes?" Ask this before you've pitched anything, while it's just a logistics question and not yet a sign you think the deal is close enough to worry about closing mechanics. People answer it more honestly early than late, when a late-stage version of the same question can read as pressure. Knowing there's a co-founder, a finance approval, or a procurement step changes what "yes" from this person on this call is actually worth.
"What happens if you do nothing?" Most founders skip this because it feels like talking someone out of buying. It's the opposite. If the honest answer is "not much," you've learned the problem isn't urgent and no pitch fixes that — better to know now than after a demo. If the honest answer involves a real cost, you've just heard the prospect state their own case for buying, in their own words, which will do more work in the pitch than anything you could have said yourself.
What changes once you actually have the answers
A pitch built on five real answers is short, because it only has to cover the parts that matter to this specific person. Instead of walking through the product, you say: "You told me this costs you a day a week and there's no real workaround beyond patching it manually — here's the part of what we built that removes that day." That's one sentence with a demo attached to it, not fifteen minutes of features arranged in the order you built them. The discovery call did the hard work. The pitch is just reading the answer back.
The trap of asking well and then not listening to the answer
Asking these five questions and then pitching anyway, on schedule, regardless of what came back, is worse than not asking them, because it teaches the prospect that the questions were theater. If the answer to "why now" is genuinely "no reason," say that out loud and ask if it's worth continuing the conversation at all, rather than pretending you didn't hear it. A prospect who watches you act on their honest answer, even when the honest action is ending the call early, trusts the next thing you say far more than one who watched you ask good questions and ignore every answer.
Where the record of the answers actually matters
The value of these five answers doesn't end when the call does. Three weeks later, on the call where you're actually trying to close, you'll want the exact number they gave you for what the problem costs them, not your memory of roughly what they said. A transcript of the discovery call, sitting on their record rather than in your head, means you can quote their own number back to them instead of paraphrasing it into something vaguer. That's a small mechanical thing — Rocketship keeps the recording and the transcript attached to the person, so it's there to check rather than remembered approximately — and it's worth having for exactly this reason. It doesn't ask the questions for you, and it doesn't know which ones matter for this particular prospect. That part is still entirely on you, on the call, before you say a single word about what you built.