Discovery Call Questions That Uncover Real Problems
- No invented stats
- Written for UK readers
- 5 min read
- Published 19 September 2026
Many discovery calls go wrong in the first few minutes, when the rep asks "so, what are your current challenges?" and accepts whatever comes back. The prospect gives a tidy, rehearsed answer — "we just want better visibility" — and the rep writes it down as a pain point. It isn't one. It's a summary of a problem the prospect hasn't examined closely either.
Good discovery questions do two things: they get a specific, concrete answer, and they make the prospect think about something they hadn't quite articulated. That second part is what earns you the right to a second meeting.
Start with how things work now, not what's wrong
Asking "what's the problem?" invites an abstraction. Asking someone to walk you through their actual process produces detail you can work with, and the problems surface on their own.
"Before we talk about whether we're a fit — can you walk me through what happens today when a new enquiry comes in? Start from the moment it lands and take me through to the point someone's been invoiced."
People are comfortable describing their own process. As they do it, you'll hear the workarounds: the spreadsheet someone maintains manually, the handover that always goes wrong, the report that takes a day to produce. Those are the real problems, and they came out unprompted — which means they're genuine rather than performed for your benefit.
Follow the workarounds rather than ignoring them:
- "You mentioned Dev rekeys that into the finance system — how long does that usually take?"
- "What happens if he's off that week?"
- "Has anything ever been missed because of that gap?"
Questions that reveal size and cost
A problem nobody has quantified is a problem nobody will fund. You don't need the prospect to produce a business case on the call, but you do need a rough sense of scale — and the act of asking often makes them realise they've been tolerating something expensive.
- "Roughly how many hours a week does that take across the team?"
- "How often does that go wrong — weekly, monthly, twice a year?"
- "When it does go wrong, who ends up fixing it, and what does that cost you?"
- "If this stayed exactly as it is for another twelve months, what's the impact?"
That last one is the most useful question in discovery, because the honest answer is sometimes "none, really." That's valuable. A prospect who can't describe any consequence of doing nothing is a prospect who will do nothing, no matter how good your product is.
Questions about the last time they tried to fix it
Almost every problem worth selling into has been attacked before. Understanding what happened tells you what you're up against.
- "Have you tried to solve this before? What did you try?"
- "What stopped it working?"
- "Was that a tool problem or a people problem?"
- "Who was involved in that decision last time?"
If a previous attempt failed because nobody adopted the new system, your deal has an adoption risk, not a feature risk — and your pitch should address it. If it failed because the budget got pulled at the last minute, you've learned something about their approvals process before you've written a proposal.
Questions about how a decision actually gets made
Asking "are you the decision maker?" is a bad question. It invites a yes from someone who wants to feel senior, and it's mildly insulting to someone who genuinely is. Ask about the process instead.
"Let's say in a few weeks you decide this is worth doing. Walk me through what happens next internally — who else would need to look at it, and is there a sign-off threshold at a certain spend?"
This is a normal, unthreatening question, and the answer is far more useful than a job title. It's worth reading our guide to finding the real decision maker alongside this, because the answer you get on a first call is often incomplete rather than dishonest.
How to handle a vague answer
The skill in discovery isn't the question list — it's what you do with a weak answer. When someone says "efficiency is a big focus for us this year," you have three options, and most reps pick the worst one.
- Accept it and move on. Learn nothing. Most common.
- Pitch at it. "Great, efficiency is exactly what we do." Now you're guessing.
- Ask for an example. "Where does that show up most? Give me a recent example of something that felt inefficient."
Asking for a specific recent example is the single highest-value follow-up in sales. Vague statements come from the part of the brain that produces corporate language; examples come from memory, and memory is specific. Two or three "can you give me an example?" follow-ups will tell you more than fifteen questions from a list.
Leave silence after the question
Reps talk too much on discovery calls, usually out of nerves. A three-second pause after a hard question feels like a minute to you and like nothing to them, and it is often when the useful part of the answer arrives. If you want to improve one thing on your next call, make it this — there's more on why in talking less as a sales skill.
When discovery tells you to stop
Discovery is qualification, not a formality on the way to a demo. You should be prepared to end the process on the strength of what you hear. Genuine disqualifying signals include:
- No consequence to inaction, described in any concrete way
- The problem is real but owned by a department your contact has no influence over
- They solved something similar internally last year and are happy with it
- The timeline depends entirely on an event outside their control, with no fallback
Saying "based on what you've described, I don't think we're the right fit right now — here's why" costs you a forecast entry and buys you a reputation. People remember the supplier who told them not to buy, and some of them come back with a budget eighteen months later.
What not to do with your notes
Don't turn the answers into a slide called "Your Challenges" and read them back. Prospects find it slightly eerie. Use the detail instead: reference their actual process in your proposal, use their words for the problem rather than your product category's words, and structure any later demo around the two or three things they said out loud. That's the part that separates discovery from an interrogation — see why combining discovery and demo kills deals for how to keep those two conversations apart.
Where this advice doesn't apply
If you sell a low-value, high-volume product with a short cycle, a twenty-minute structured discovery call is overkill and will cost you more deals than it saves. Two or three qualifying questions on a first call are enough. This depth of discovery earns its keep when the deal is large enough, or the implementation disruptive enough, that a wrong-fit customer costs both sides real money.
Spotted a mistake or a number we can't back up? Tell us and we'll fix it.