The reason you’re hunting for discovery call questions is probably that you’re scared of the silence. Someone agreed to a call, the call is tomorrow, and you can already picture the moment where you’ve said your piece and there’s nothing left and it gets awkward. So you want a list to hold onto. Fair. But the goal of a discovery call isn’t to fill the time. It’s to find out, fast, whether you should even be talking to this person.
That reframe changes which questions matter. You’re not there to perform or to pitch. You’re there to disqualify quickly if it’s a bad fit, and to understand deeply if it’s a good one. Good discovery call questions do one of those two jobs. Everything else is filler that makes the call longer without making it better.
Start with the problem, not the product
Your first questions should be about their world, before yours ever comes up. How are they handling this today? What made them take the call now, of all weeks? What’s the actual cost of the thing being broken? You’re listening for whether the pain is real and loud, or vague and someday. A vague problem is a polite no wearing a maybe.
The “why now” question is the one most founders forget, and it’s the most useful. Someone who can’t articulate why they’re looking right now usually isn’t really looking. Someone who says “our old tool broke last week and we’re bleeding hours” just handed you the timing half of a real opportunity.
Discovery call questions that actually qualify
A short set does more than a long one. These are the discovery call questions worth memorizing, because each one is built to surface fit or kill it fast:
- “Walk me through how you handle this right now.” Surfaces the real workflow and the real pain.
- “What made you look into this this week?” Surfaces timing, the half everyone skips.
- “If you don’t fix this, what happens?” Tells you whether the pain is expensive or just annoying.
- “Who else cares about this getting solved?” Tells you if the person on the call can actually decide.
- “What would make this an easy no for you?” Pulls the real objection out before it kills the deal silently.
Listen more than you talk
The most common discovery call mistake is talking too much. You’re nervous, so you fill space with features. Resist it. The rough rule is that they should be talking most of the time and you should be the one going quiet. Every minute you spend pitching is a minute you don’t spend learning whether they’re worth pitching to at all.
When you do talk, ask the follow-up. Someone says “it’s a hassle,” and the lazy move is to nod and move on. The good move is “say more about that, what part’s the hassle?” The gold is always in the second answer, not the first. If the whole idea of running one of these still feels foreign, here’s what a discovery call is and why the founder is better at it than a hired rep.
End it early when it’s a no
If ten minutes in it’s clearly not a fit, say so kindly and give them their time back. “Honestly, I’m not sure we’re the right thing for this, and I’d rather tell you now than waste your week.” People remember that. It costs you a deal that was never real and earns you a reputation that brings you the ones that are. A call that ends in a clean no is a success, not a failure.
The whole thing gets easier when you walk in already knowing the person has a real, recent reason to talk. That’s the part we built Unbound Compute to handle: finding the people who show the problem out loud, with the context behind it, so your discovery calls start with someone who actually needs you. You still run the call. You just stop wasting them on people who were never going to say yes.