25 Discovery Questions for Consultants That Uncover the Real Problem

Why discovery matters more now

When clients arrive with a specification or a prototype from an AI tool, your instinct may be to comply. But specifications are often symptoms. Discovery is where you show the judgment they are really paying for. Use these inside a diagnostic-first sales call.

Pick five to eight per conversation. Do not read them like a checklist.

The problem behind the request

1. What's the problem behind this request?
2. What prompted you to look at this now?
3. What happens if nothing changes in six months?
4. When did you first notice it?
5. What have you assumed about the cause?

The cost of the problem

1. How is this affecting revenue, costs or time today?
2. Who feels this most, and how?
3. What is it costing you each month, roughly?
4. What opportunities are you missing because of it?
5. What would fixing it be worth to you?

What has been tried

1. What have you already tried?
2. What did you learn from that?
3. Have you used AI tools on this? What did they get right and wrong?
4. Why do you think earlier attempts fell short?

The decision

1. Who else is involved in this decision?
2. Who owns the result if this works or fails?
3. What does the approval process look like?
4. What are the criteria you'll use to choose?

Success and constraints

1. What would a great outcome look like in ninety days?
2. How will you measure it?
3. What constraints should I know about: budget, timing, systems, people?
4. What would make you regret this project?

Testing fit and honesty

1. What worries you most about working with an outside adviser?
2. Is there anything you haven't told me because it feels awkward?
3. If I could change one thing about how you're approaching this, what do you think it would be?

How to listen

• Note their exact words. Use them when you recommend.
• Ask "what do you mean by that?" once more than feels natural.
• Pause after the answer; the useful detail often comes in the silence.
• Reflect back: "So the real issue is X, not Y. Is that right?"

What to do with the answers

Turn them into a short written summary: the problem as you heard it, the cost, what has been tried, the decision and your recommendation. Then propose the next step. If the problem is unclear, offer a paid diagnostic. The answers about cost let you price against value, as explained in how to stop competing on price.

Reveal your stance

Consistently asking these signals an authority stance. Compare it with the vendor's default "What do you need?" The audit can show how often your conversations start with a problem rather than a specification.

How to use the questions in real conversations

A list of questions is only useful if you can weave it into a natural conversation. Here is how to do that without sounding like an interrogation.

Start with permission and purpose

"I'd like to ask a few questions to understand your situation properly, so I don't waste your time with generic advice. Is that all right?" People almost always say yes, and it frames you as careful rather than nosy.

Follow the answer, not the list

If a client mentions something interesting, follow it. "You said the last vendor disappeared after launch. Tell me more." The best insight often comes from an unplanned follow-up. Treat the list as a map, not a script.

Use the "three whys" technique

When a client states a need, ask why three times, gently.

• "We need a new website." Why? "Because the old one looks dated."
• Why does that matter now? "We're losing tenders to competitors."
• Why do you think that is? "Procurement teams look us up online and don't see proof of our work."

The real problem, proof of credibility, is different from the original request. The answer may be a portfolio page and case notes, not a redesign.

Reflect back

Summarise what you heard in one sentence and check it: "So the core issue is that decision-makers can't see evidence of your track record. Is that right?" This shows you understand and gives the client a chance to correct you.

Take notes visibly

Writing signals that their words matter. Later, quoting their phrases back in your recommendation builds trust.

Questions for specific situations

The 25 questions above are general. These are tuned to common consulting scenarios.

When a client brings a specification

• What led you to this particular solution?
• What alternatives did you consider?
• What would happen if we did nothing for six months?
• Who else has an opinion about how this should be done?

When a client wants "something like a competitor's"

• What is it about theirs that appeals to you?
• What result do you think it delivers for them?
• How different is your business from theirs?
• What would you change about it?

When the client is a team, not one person

• Who will use this every day?
• Who will be affected but is not in this conversation?
• Where do you expect resistance?
• Who decides if this succeeded?

When the client is overwhelmed

• If you could fix just one thing this quarter, what would it be?
• What is the most urgent thing and what is the most important?
• What has been tried and abandoned?
• What would make next month easier?

When the client has been let down before

• What happened last time?
• What did you learn about what to do differently?
• What would you need to see to trust a new provider?
• How can I make sure the same doesn't happen?

Red flags to listen for

Discovery is also a filter. Some answers signal a poor fit.

• No one owns the outcome. Projects without an owner tend to drift.
• Unclear success measures. If they cannot say what good looks like, you cannot deliver it.
• A history of many failed providers. It may be the client's process, not the providers.
• Refusal to share information. You cannot diagnose what you cannot see.
• Unrealistic timelines and budgets together. You will be blamed.
• Pressure to skip the diagnosis. It signals a vendor relationship.

You can still choose to work with such clients, but price the extra risk and set clear boundaries, or decline politely.

Turning answers into a written summary

Within a day of the call, send a short summary the client can forward. Use this structure:

1. The problem as I understand it (in their words).
2. What it is costing (their figures).
3. What has been tried and what we learned.
4. Who decides and by when.
5. What success looks like at ninety days.
6. My recommendation and next step, with fee and dates.

The summary shows accountability, gives the client something to share with colleagues and protects against misunderstanding. It also positions you as an adviser, not a supplier.

Practising discovery

Skills improve with practice.

• Record calls (with permission) and listen for how much you talked.
• Role-play with a colleague, taking turns as client and consultant.
• Set a goal per call, such as asking two follow-up questions or using a pause.
• Review after each call. Write down one thing you would ask differently.
• Collect great questions. Keep a list from clients, books and peers.

Using AI to prepare, not to replace

An AI assistant can help you prepare by suggesting questions for a sector or by summarising background documents. It cannot replace listening. The value of discovery lies in the unrehearsed detail a client shares when they feel heard. Use AI before the call and your own attention during it.

Where discovery fits in your sales process

Discovery is the second step in a diagnostic-first sales call. It feeds the cost estimate that supports value-based pricing (see how to stop competing on price), and it is the foundation of a good paid diagnostic. If you want to see how often your conversations start with a problem instead of a specification, take the free Vendor-or-Authority Audit. Question 2 asks exactly that. The book covers the approach across Chapters 2, 3 and 8, with a tool at the end of each.