The best discovery call questions do three things at once: they qualify the opportunity, they help the prospect articulate their own pain, and they surface the information you need to close the deal. Not all questions do all three. The 47 below are the ones I’ve used across €4M+ in B2B SaaS revenue, organized so you can pick the right ones for your stage and deal size.
Before we get into the list: don’t ask all 47. Pick 8-12 that fit your product and the conversation. A discovery call is a conversation, not an interrogation. The questions are prompts to get the prospect talking - what they say in response matters more than how many boxes you tick.
Situation Questions (Map the Landscape)
These go first. They’re low-threat, context-building questions that help you understand the current state before you probe for pain. Start here and you’ll earn the right to ask harder questions later.
- ”Walk me through how your team currently handles [area your product addresses]."
- "What tools or software are you using today to manage this?"
- "How long have you been doing it this way?"
- "How many people in your organization are involved in this process?"
- "How did this process get set up originally? Was it intentional or did it just evolve?"
- "What does a typical week look like for the team managing this?"
- "Are there other teams or departments that depend on this process working well?"
- "Have you tried to improve or change this process before? What happened?”
Problem Questions (Find the Pain)
Once you’ve mapped the landscape, go looking for what’s broken. These questions help prospects articulate frustrations they may have normalized. The goal is to get them talking about pain in their own words - not yours.
- ”What’s the most frustrating part of that process right now?"
- "If you could change one thing about how this works, what would it be?"
- "When does this process typically break down or cause problems?"
- "What’s falling through the cracks that shouldn’t be?"
- "How much time per week does your team spend on [manual or inefficient activity]?"
- "What do you have to do manually that you wish were automated?"
- "What does a bad week look like when this process isn’t working?"
- "Are there things your competitors do in this area that you wish you could do?"
- "If I asked your team what they hate most about this process, what would they say?"
- "What’s the workaround people use when the official process doesn’t work?”
Impact Questions (Make the Pain Real)
This is where most founders leave money on the table. They find the pain and jump straight to the solution. Don’t. These questions help prospects feel the full cost of their problem - which is what creates urgency. Without urgency, there’s no deal.
- ”If you don’t solve this in the next 6 months, what happens to [their main goal]?"
- "What’s the business cost of this problem - in revenue lost, time wasted, or deals missed?"
- "How does this affect the team’s ability to hit their targets?"
- "What’s happened to deals or customers because of this problem?"
- "How much is this costing you in employee time per month, roughly?"
- "Who else in the organization feels the pain from this?"
- "What’s the most expensive thing that’s gone wrong because of this issue?"
- "If this keeps going unresolved for another year, where does that leave you?"
- "How is this affecting team morale or retention?"
- "What’s the opportunity cost - what could your team be doing instead of dealing with this?”
Decision and Qualification Questions (Map the Buying Process)
You need to understand who decides, how they decide, and on what timeline - before you invest in a proposal or demo. These questions are about mapping the buying landscape, not interrogating the prospect. Ask them conversationally, late in the call.
- ”Besides yourself, who else would be involved in evaluating a solution like this?"
- "Who would be the main user of something like this day-to-day?"
- "What does your decision-making process look like for software this size?"
- "Have you budgeted for solving this problem? Is there a range you’re working within?"
- "What’s your timeline for having something in place?"
- "Is there a specific event or deadline that’s driving the timeline?"
- "Have you evaluated other solutions? What did you like or not like about them?"
- "What would need to be true for you to feel confident moving forward?"
- "What would make you say no to a solution, even if it technically fit your needs?"
- "What does success look like for you 90 days after implementing something?”
Competitive and Context Questions (Understand the Market Position)
These help you understand what you’re competing against - including the “do nothing” option, which is your most common competitor in early-stage B2B SaaS.
- ”Are you looking at other solutions right now, or is this early exploration?"
- "What made you start looking now? Was there a specific trigger?"
- "What’s your current thinking on build vs buy? Have you considered solving this internally?"
- "If you don’t find a good solution, what’s the default plan?"
- "What do you like about how you’re handling this today that you’d want to preserve?”
Closing Questions (Set Up the Next Step)
Never end a discovery call without a clear next step. These questions help you transition from discovery to the next stage without it feeling abrupt.
- ”Based on what we’ve talked about, does it make sense to go deeper?"
- "What would you want to see in a demo to feel like this is worth exploring further?"
- "Who else should be on the demo call to make it worth their time?"
- "I have [specific times] available - which works better for you?”
How to Use These Questions in Practice
Don’t read from this list on the call. Instead, build your own call guide with 3-4 questions from each category that are most relevant to your specific product and ICP. Then use that guide as a mental map, not a script.
The flow should feel like this:
- Open with framing (set expectations, get permission to ask questions)
- 2-3 situation questions to build context
- 3-4 problem questions to find the pain
- 2-3 impact questions to make the pain feel real
- 2-3 decision questions to qualify the opportunity
- Close by booking the next step
Total call time: 25-30 minutes. If you’re running longer, you’re probably talking too much between questions.
Enough to qualify — not so many it feels like an interrogation
Longer usually means the founder is talking too much
Prospect talks 60% of the time on great calls
The One Question That Changes Everything
If I had to pick one question from this entire list, it’s question 19: “If you don’t solve this in the next 6 months, what happens?”
Here’s why it’s so powerful. Most prospects enter a discovery call in “exploration mode.” They’re curious about your product but not necessarily committed to solving the problem. This question forces them to think about what happens if they do nothing. And when they answer it out loud - “Well, we’d probably miss our growth targets,” or “Our team would keep burning out,” or “We’d lose another enterprise client” - they’re doing your selling for you.
Urgency you create for a prospect is weak. Urgency they articulate themselves is real. This question is the most reliable way I know to make the second happen.
The Questions Not to Ask
A few question types consistently hurt discovery calls. Avoid them.
| Question type | Wrong approach | Right approach |
|---|---|---|
| Budget | ”Do you have a budget?" | "How are you thinking about budget for solving this?” |
| Pain | ”You’re probably finding that [X], right?" | "What’s the most frustrating part of that process right now?” |
| Multiple | ”What’s your timeline, who’s involved, and do you have budget?” | One question at a time — let the answer guide the next |
| Research | ”So what does your company do?” | Show you’ve done homework; ask about specifics only you’d know |
Yes/no questions. “Do you have a budget?” gets a defensive yes or no. “How are you thinking about budget for solving this?” gets a real answer.
Leading questions. “You’re probably finding that [problem], right?” You’re putting words in their mouth. Let them describe the problem in their own language - that language is more valuable to you than your assumptions.
Multiple questions at once. “What’s your timeline, who’s involved, and do you have budget set aside?” Prospects will answer the easiest one and you’ll lose the thread. One question at a time.
Questions that signal you haven’t done basic research. “So what does your company do?” If you couldn’t spend 10 minutes on their website before the call, you’re telling them this isn’t important to you.
Building Your Own Discovery Call Guide
The best discovery call guides are built from this list but customized to your specific product, market, and deal size. Here’s how to build yours:
First, go through your last 10 deals - won and lost. What did you learn in discovery that turned out to be decisive? Build questions that surface that information earlier.
Second, look at deals you lost. Where did the conversation go wrong? What did you not understand about the prospect that you should have? Add questions that would have surfaced that.
Third, talk to your best customers. Ask them what their situation looked like before they bought from you. The language they use to describe that situation - the pain, the trigger, the desired outcome - should feed directly into your discovery questions.
This is the approach I use when working with founders on their sales process. The discovery guide that results is built from their specific customer reality, not a generic framework. That specificity is what makes it work.
If you want to build a discovery guide tailored to your product and ICP, or want to sharpen how your current process handles discovery, start with understanding what discovery is meant to achieve - then come back to this list and pick the questions that fit your motion. For a deeper conversation about your specific situation, book a sales audit.
Want this run on your pipeline?
€500, 90 minutes. Credited against any Build.