15 Discovery Call Questions That Surface Real Problems

Why Most Discovery Calls Feel Like Interrogations

You hop on a call with a potential client, work through your list of questions, and thirty minutes later you have a page of notes but no real sense of what they actually need. Sound familiar?

The problem usually isn't the questions themselves. It's asking too many of them, or asking them in the wrong order, or forgetting that a discovery call is a conversation, not a form you're filling out together.

This post gives you a working set of discovery call questions organized by what you're trying to learn. Use it as a reference, not a script.

Before You Ask Anything: Set the Frame

Spend the first two minutes telling the other person how the call will go. Something like: "I'll ask you a few questions to understand your situation, and then we can figure out together if there's something worth exploring." This small thing changes the dynamic completely.

People answer more honestly when they don't feel like they're being sold to. And you'll get better information when they're relaxed.

Situation Questions (Ask 2-3, Not All of Them)

Situation questions establish context. They're the least valuable category because the answers are often things you could have found out beforehand. Do your homework first, then confirm or fill gaps on the call.

"How long have you been running this side of the business?" Useful when tenure affects how deeply rooted a problem is.
"How are you currently handling [the thing you help with]?" This is the one situation question worth almost always asking. It tells you what they're comparing you to.
"Who else is involved in this area day to day?" Helps you understand whether you're talking to the person who feels the pain or the person who'll sign off on fixing it.

Skip situation questions you can answer from their website, LinkedIn, or a quick Google search. Asking someone to explain their own business to you when you haven't done basic research signals that you're not serious.

Pain Questions (This Is Where the Real Work Happens)

These are the discovery call questions that actually matter. You're trying to understand what's broken, what's frustrating, and what they've already tried.

"What's the biggest friction point in how you're doing this right now?" Open-ended, and gives them room to tell you what actually bothers them rather than what they think you want to hear.
"What have you already tried to fix this?" Critical. If they've tried three things that didn't work, you need to know that before you suggest a fourth.
"What does a bad week look like because of this problem?" Gets them out of abstract problem-description and into lived experience. The answers are almost always more vivid and honest.
"Is this a new problem or something you've been working around for a while?" Duration tells you a lot about how urgent they actually feel it is, versus how urgent they say it is.

Resist the urge to jump in with solutions here. When someone describes their pain, the instinct is to say "oh, I can help with that." Wait. You don't know enough yet.

Impact Questions (Make the Cost Visible)

Pain questions surface the problem. Impact questions help the person connect that problem to something they care about: time, money, relationships, reputation, or just their own stress levels.

"What does this cost you in a typical week?" You're not fishing for a number to justify your price. You're helping them articulate something they may have normalized.
"How is this affecting other parts of the business?" Problems rarely stay contained. This question often surfaces secondary problems that are actually more painful than the original one.
"What happens if this doesn't get resolved in the next six months?" This is one of the most useful discovery call questions because it separates real urgency from vague dissatisfaction. Some people are fine coasting. Others are genuinely stuck.

Listen for what they don't say here too. If someone can't articulate any real impact, the problem might not be painful enough for them to act on it, no matter how good your solution is.

Decision Process Questions (Know Before You Propose)

Solopreneurs often skip this category because it feels awkward. It isn't. You need to know how decisions actually get made, or you'll spend time building a proposal for someone who can't say yes.

"When you've brought in outside help before, how did that decision usually work?" Asking about past decisions is less confrontational than asking "who makes the call here." You get the same information with less friction.
"Is there anyone else who'd need to be part of this conversation before you move forward?" Simple, direct, and saves you from being ghosted after a great call because you forgot there was a business partner involved.
"What would need to be true for you to feel confident moving ahead?" This one is underused. It lets them tell you exactly what they need to see, rather than you guessing.

Timeline Questions (Separate Real Deadlines from Wishful Thinking)

"As soon as possible" usually means something different to each person. These questions help you figure out whether there's a real forcing function or just a vague preference.

"Is there a specific date or event driving when you need this solved?" A product launch, a conference, a contract renewal: these are real deadlines. "I'd like to get started soon" is not.
"What's your process from here to making a decision?" This tells you whether they're shopping around, whether they need internal sign-off, or whether they're ready to move fast. All of those require different follow-ups from you.

The Questions You Should Skip (or Save)

Some questions have a place, but not in a first discovery call.

Budget questions up front. Asking "what's your budget for this?" in the first ten minutes puts people on the defensive before they trust you. You'll get a low number or a non-answer. Wait until you've established the impact of the problem, then have the budget conversation.

Questions you can answer yourself. "How many employees do you have?" "What industry are you in?" Do the research.

Leading questions. "You're probably frustrated with how long this takes, right?" You're not gathering information, you're looking for validation. It feels good but it doesn't help you understand the real situation.

Listening More Than You Talk: What This Actually Means

You've probably heard the advice to "listen more than you talk" on discovery calls. It's true, but vague. Here's what it looks like in practice.

When someone finishes answering, pause for two or three seconds before you respond. Most people fill silence. What they say in that pause is often more honest than their initial answer.

Reflect back what you heard before moving to the next question. "So it sounds like the main issue is X, and you've already tried Y, is that right?" This does two things: it confirms your understanding, and it shows the person they've been heard. Both matter.

Take notes on their exact words, not your interpretation of them. When you follow up or write a proposal, using their language builds trust in a way that paraphrasing doesn't.

What to Do With the Answers After the Call

This is where most discovery calls fall apart. You have good notes, the conversation went well, and then... you write a generic proposal or send a vague follow-up email that doesn't reference anything specific they said.

Right after the call, while it's fresh, write down the three most important things you learned. Not a full transcript. Just the three things that would change how you'd approach working with this person.

Your follow-up should reference specific things they said. "You mentioned that the current process breaks down when you're juggling more than three clients at once" is more compelling than "I think I can help with your workflow challenges."

If you're running a lot of calls, keeping track of what was said becomes its own problem. This is one of the reasons tools like Ungrind exist: the AI bot joins your Google Meet or Teams call, transcribes it, and automatically creates follow-up tasks and a meeting summary so you're not relying on hastily scribbled notes. For solopreneurs doing their own sales, that kind of automatic capture makes a real difference when you're trying to personalize a proposal two days later.

Putting It Together: A Simple Call Structure

You don't need to ask all fifteen of these questions. A good discovery call usually involves five to eight questions total, with plenty of space for the conversation to go where it needs to go.

A rough structure that works:

Frame the call (1-2 minutes)
One or two situation questions to confirm context
Two or three pain questions, with real listening between them
One or two impact questions to understand what's at stake
One decision process question
One timeline question
Ask if there's anything they expected you to ask that you didn't

That last one is a gift. It catches everything you missed and often surfaces the thing they most wanted to say but didn't know how to bring up.

The Goal Isn't to Qualify. It's to Understand.

The best discovery call questions aren't tricks to move someone through a funnel. They're genuine attempts to understand whether you can actually help someone, and whether they're ready to be helped.

If you go into a call trying to qualify or close, people feel it. If you go in trying to understand, you'll ask better follow-ups, give more honest assessments, and end up working with clients who are actually a good fit.

That's a better use of everyone's time, including yours. For more practical posts on running a solo business without burning out, check out the Ungrind blog.

If you're doing a lot of discovery calls and want to stop losing track of what was said, Ungrind offers a 30-day free trial with no credit card required. It won't run your calls for you, but it will make sure you remember everything that happened in them.