The best SaaS discovery call questions do one job: they get the prospect to describe their problem, their current workaround, and what it costs them, in their own words, before you say anything about your product. A good discovery call is mostly the prospect talking. If you're doing more than about a third of the talking, it's a pitch, not a discovery call, and pitches convert worse.
This guide gives you the questions, organized by the stage of the call where they belong, plus the part most question lists skip: how to actually run the call so it ends in a decision instead of a polite "let me think about it."
What a discovery call is actually for
A discovery call has two real purposes, and closing the deal isn't one of them.
The first purpose is qualification: figuring out whether this prospect is someone you can genuinely help and who can genuinely buy. The second is understanding: learning their situation well enough that, if there's a fit, you can show them exactly how you solve their specific problem rather than delivering a generic demo.
Notice what's missing. You're not there to convince, pitch, or persuade on a discovery call. You're there to find out. The selling, if it happens, comes later and is far easier because you'll know exactly what they care about. Founders who treat the discovery call as a pitch skip the finding-out and end up presenting a product to someone whose problem they never actually understood. That's the call that goes well and then ghosts.
Discovery call questions by stage
Good questions are sequenced. You open by understanding their world, move to the problem and its cost, check how they're solving it now, and only then explore fit. Here are the questions that work, in the order they belong.
Opening: understand their situation
Start broad. Let them set the scene before you narrow in. The goal here is context and rapport, and to get them talking.
- Walk me through how your team currently handles [the area your product touches].
- What does a typical week look like for you around [relevant process]?
- How is your team structured around this? Who owns what?
- What made you take this call? What's going on right now that made this feel worth 30 minutes?
That last question is one of the most useful in the whole call. The answer tells you what triggered them to look, which is the single strongest signal of whether this is a real opportunity or idle curiosity.
Problem: find the real pain
Now go after the problem itself. You're looking for the specific, concrete version, not the abstract one. Push gently for detail.
- What's the hardest part of [process] right now?
- Can you give me a specific recent example of when that was a problem?
- When does this actually come up? How often?
- Who on the team feels this most?
- What happens if this just stays the way it is?
The specific-example question is where discovery calls earn their value. "We struggle with reporting" is abstract and tells you nothing. "Last Tuesday my ops lead spent four hours rebuilding a report by hand because the export broke" is concrete, and now you understand the real problem. Always push from the general to the specific.
Cost: quantify what the problem is worth
A problem the prospect can't or won't quantify usually isn't painful enough to pay to solve. These questions surface whether the pain is real.
- Roughly how much time does this cost your team in a week?
- Have you tried to fix this before? What happened?
- What's the downstream effect when this goes wrong?
- Is this something you're actively trying to solve this quarter, or more of a someday thing?
The "have you tried to fix this before" question is quietly one of the most revealing. If they've tried three tools and hired a contractor, the pain is real and expensive. If they've never done anything about it, it's probably not urgent enough to buy for, no matter how much they nod along.
Current solution: understand the alternative
Whatever they're doing now, even if it's a spreadsheet or nothing, is your real competition. Understand it.
- How are you handling this today?
- What do you like about the current way? What's frustrating?
- If you could wave a wand and change one thing about how this works now, what would it be?
The "what do you like about it" question matters more than it looks. Whatever they like about the current solution is something yours needs to preserve or beat. Founders skip this and then wonder why a technically superior product lost to a spreadsheet the buyer was comfortable with.
Decision: understand how a purchase would actually happen
Before the call ends, you need to know whether this person can buy and what buying would involve. Skipping this is why deals stall.
- If you decided this was worth doing, what would the next steps look like on your side?
- Who else would be involved in a decision like this?
- What would need to be true for you to move forward?
- Is there a budget for solving this, or would one need to be created?
"What would need to be true for you to move forward" is the most important question in the entire call, and the one founders most often skip because it feels confrontational. It isn't. It's the question that converts a vague good feeling into a concrete, testable condition. Their answer is your roadmap to the close.
How to run the call so it converts
The questions only work if the call is run well around them. A few principles matter more than any individual question.
Talk less than the prospect. Aim to talk about a third of the time or less. The prospect should be doing most of the talking, because every minute they talk, you learn. Every minute you talk, you don't. If you catch yourself explaining your product for five straight minutes on a discovery call, you've lost the thread.
Ask follow-ups instead of moving to the next question. The gold is usually in the second and third layer, not the first answer. When they say something interesting, don't move on. Ask "can you say more about that" or "why is that." The best discovery isn't a checklist run top to bottom; it's a genuine conversation that follows the interesting threads.
Get comfortable with silence. After you ask a real question, stop talking and let them think. Founders rush to fill silence and end up answering their own question or softening it. The pause is where the honest answer comes from.
Do not pitch mid-discovery. When a prospect describes a problem your product solves, the urge to jump in with "oh, we do exactly that" is enormous. Resist it until you've fully understood the problem. Pitching early cuts off the discovery and moves you into selling before you've earned it.
Always end with a concrete next step. This is the one that most affects conversion. Never end a discovery call with "I'll follow up" or "let me know what you think." End with a specific next action and a date attached: a scheduled follow-up, a scoped trial with a check-in booked, a proposal by a certain day. A discovery call that ends without a defined next step is a call you'll probably never hear about again. I wrote more about why warm calls that lack a next step quietly die in why getting more discovery calls can make your startup worse.
Common discovery call mistakes to avoid
A few patterns that consistently sink otherwise good calls:
- Talking too much. The single most common one. If you leave a call having talked more than the prospect, you ran a pitch.
- Accepting abstract answers. "We struggle with X" is not an answer. Push for the specific, recent, concrete example every time.
- Skipping the cost questions. Without understanding what the problem costs, you can't tell a real opportunity from a polite one.
- Never asking who else decides. You have a great call with someone who turns out to have no authority to buy, and you find out three weeks later.
- Ending without a next step. The warm feeling at the end of a good call evaporates within days if nothing concrete was scheduled.
The bottom line
The best SaaS discovery call questions move from understanding their situation, to the specific problem, to what it costs, to how they solve it now, to how a decision would actually get made. But the questions are only half of it. Run the call so the prospect talks most of the time, follow the interesting threads, resist pitching until you understand the problem, and always end with a concrete next step and a date.
Done well, a discovery call qualifies the prospect and sets up an easy, specific sale later. Done as a pitch, it produces the call that feels great and then goes silent. If your discovery calls keep going well and then ghosting, the problem is usually in how the call is structured, and it's fixable. That's the kind of thing a diagnostic call is for: half an hour, no pitch, and a clear read on what to change.
