Consultant Questions to Ask Client
For a consultant's first discovery call with a prospective client, when you are still working out what the problem is and whether the work is worth taking. Twenty questions on why the request has surfaced now, what has already been tried, who owns the budget and how approval really works, who inside the organization will resist, and what would cause the engagement to be stopped early.
The questions
Open any question for the note
What made you get in touch this month rather than last year?
Why ask it
The trigger tells you more than the brief does: a board question, a lost customer, a regulator's letter, a new arrival wanting a visible win. Work that has no trigger tends to stay unfunded no matter how well you scope it.
How would you describe the problem in one sentence to someone outside your team?
Why ask it
Forces the brief down to something a sponsor can repeat. If the sentence comes out full of internal project names, the problem has not been defined yet, and defining it may be the more useful first piece of work.
Who first said you needed outside help, and was anyone against it?
Why ask it
You need to know whose idea you are. Being the sponsor's initiative means the people you will interview may already resent the exercise, and knowing that before day one changes how you introduce yourself.
What happens if you do nothing for another six months?
Why ask it
Establishes whether there is a real cost of delay or only a stated intention. If the honest answer is that things continue much as they are, expect the project to be deferred at the next budget review, whatever anyone says today.
What have you already tried, and how far did it get?
Why ask it
Almost every problem that reaches a consultant has survived at least one internal attempt. Ask what stopped it: the answer, usually a person, a system or a competing priority, is the same thing that will stop you if it is left in place.
Who here knows the most about this, and are they involved?
Why ask it
There is normally one person who could describe the whole problem in an hour. If they are not in the project, find out why: they may have been the author of the failed attempt, or they may simply be too busy to be released.
Twelve months from now, what number would have to move for this to have been worth it?
Why ask it
Insist on a measure they already report, not one you would have to build. Metrics invented for a project have no history and no owner, and they are quietly dropped the moment the results are ambiguous.
How would you know it was working after four weeks?
Why ask it
Long-term measures do not protect the engagement in month two, when patience runs out. An early signal you both agree on, even a soft one, is what buys you time. Not being able to name one is a warning about how the work will be judged.
Who signs the invoice, and are they part of this conversation?
Why ask it
The gap between the person with the problem and the person with the budget is where proposals die. If they are different people, your next question is how to get twenty minutes with the second one before you write anything.
What have you budgeted, or what range are you working within?
Why ask it
Asking directly is normal, and reluctance is itself an answer. A client who genuinely cannot indicate a range usually has no allocation yet, which means you are helping build a business case rather than responding to a funded need.
How does spend like this get approved here, and how long does that take?
Why ask it
You are asking about thresholds, procurement, preferred supplier lists and committee dates. Work that needs a quarterly board slot cannot start next month, and knowing that now saves you from writing a proposal against a fantasy timeline.
Are you speaking to other firms, and what will decide between us?
Why ask it
A straightforward question that most clients answer honestly. Listen for whether the criteria are about approach and people or about price and format, and for signs that a preferred supplier is already chosen and you are making up the numbers.
What is the deadline, and where does it come from?
Why ask it
Separate dates that come from outside, such as a filing, an audit or a contract ending, from dates chosen for internal comfort. Only the first kind survives contact with delay, and the second kind is where scope gets cut without the deadline moving.
Who would be my counterpart day to day, and how much of their week can they actually give this?
Why ask it
Get a name and a number of hours. A named counterpart at two hours a week is a serious constraint on any design that assumes internal participation, and it is far better discovered now than in week three.
Whose job gets harder if this works?
Why ask it
There is nearly always someone: a team losing headcount, a manager losing a decision right, a supplier losing a contract. Naming them early is the difference between managing resistance and being surprised by it in a steering meeting.
What was the last piece of outside work you commissioned, and what happened to it?
Why ask it
The answer predicts your own fate more reliably than anything in the brief. If the last report is still cited, good. If nobody can remember what it recommended, ask what would be different this time and listen carefully to whether anything is.
What would make you stop this early?
Why ask it
Puts the cancellation conditions on the table while the relationship is still cordial. Answers tend to be specific and useful: a change of leadership, a bad quarter, an acquisition. You can then design phases that survive those events.
What are you not willing to change, whatever we find?
Why ask it
Every organization has protected ground: a product line, a founder's structure, an office, a supplier relationship. Knowing the boundary keeps you from spending the engagement on a recommendation that was never going to be accepted.
Who else needs to be brought along that we have not mentioned?
Why ask it
Draws out the finance controller, the works council, the clinical lead, the IT security team, the person who owns the data you need. Each one adds weeks. Better to learn their names now than to have your access blocked mid-project.
What have I not asked that I should have?
Why ask it
Reliably produces the thing they were waiting to see whether you would notice: a reorganisation coming, a system being replaced, a previous consultant who left badly. It also shows whether they are treating this as a conversation or as a procurement exercise.
Running a first discovery call
Practical guidance for the conversation itself
Before the call
- Read their last annual report or public filings, recent press, and the section of their website aimed at customers rather than investors. Twenty minutes of this changes the quality of your questions noticeably.
- Find out who is on the call and what each of them does. A finance person on a first call usually means the budget is real; a room of eight people usually means nobody has decided anything.
- Write down the four things you must know by the end: the trigger, the measure, the budget owner, the internal owner. Everything else is optional.
- Decide in advance what would make you decline. It is far easier to walk away from work you have already defined limits for than from work you have started imagining.
During the call
Do not solve it in the room
The urge to demonstrate expertise by proposing an answer in minute fifteen is the most expensive habit in consulting. You give away the analysis, you anchor on the wrong problem, and you stop learning. Ask one more question instead.
Follow every abstraction with "can you give me an example?"
"Our processes are inconsistent" becomes a specific handover between two teams that fails on Fridays. Only the second version can be scoped, priced or fixed, and the client often has not articulated it before either.
Write down their words, not your summary
Verbatim phrases from a discovery call are the most persuasive material available to you when you write the proposal. Using their language back to them is also how they recognise that they were heard.
Ask the money and politics questions in the same calm register
Budget, approval routes and who objects are ordinary operational facts. If you drop your voice or apologise before asking, you signal that these are awkward, and you will get vaguer answers as a result.
Leave the last five minutes for what you have missed
Summarise what you heard in three sentences, ask what you got wrong, then ask what you should have asked. Both corrections are usually more valuable than anything in the middle of the call.
Signals worth taking seriously
No named internal owner
Work with no one inside the organization accountable for the outcome ends as a document. If nobody can be named, propose a smaller piece whose deliverable is a decision rather than an implementation.
The brief is already a solution
When you are asked to deliver a specific tool, structure or framework, ask what problem it was chosen to solve. Sometimes the answer is sound. Often someone has committed publicly and needs external cover, which is a different engagement and you should price the risk.
Everyone is enthusiastic and nobody is accountable
Unanimous warmth on a first call usually means the work has not yet been tested against anyone's budget or headcount. Ask who will have to give something up, and watch how quickly the mood changes.
Free thinking is being requested at length
A request for a detailed plan, diagnostic or benchmark before there is a contract is a request for unpaid work. Offer a short paid scoping phase instead, and note how they respond, because it tells you how they will treat change requests later.
You are the third bidder
If procurement needs three quotes and the incumbent has already been chosen, you are supplying paperwork. Ask directly who else is bidding and how long the incumbent has been in place, then decide whether the relationship is worth the loss.
After the call
Within a day
- 1Send a short recap: the problem in one sentence in their words, the measure of success, the constraints you heard, and what you agreed to do next. Ask them to correct anything you got wrong.
- 2Ask for the one or two things you need before you can write anything sensible: a conversation with the budget owner, a report, access to a number. Willingness here is the best test of whether the work is real.
- 3Write your own private note on the risks: who resists, what the last engagement produced, what would stop it. This is the note you will reread when you decide on your price and your phasing.
- 4Only then write the proposal, and make the first phase small enough that both sides can stop cleanly if the diagnosis turns out to be wrong.
If they go quiet
Silence after a good discovery call usually means an internal priority shifted, not that you did badly. One short message referencing the trigger they described, sent a fortnight later, is worth more than a follow-up asking whether they had thoughts on your proposal.