Consulting Questions to Ask a Client
Consulting questions to ask a client between the first discovery call and the proposal, whether you are a business consultant with a corporate sponsor or doing small business consulting for an owner who signs the checks. The 70 questions follow the order the conversation usually takes: the problem and why it matters now, what success would be worth, what a business wanting to grow means by growth, who decides and who will resist, where the boundary of the work sits, which data, people and systems you will actually get access to, and the budget, the proposal, the contracting steps and what happens next. On a first discovery call, start with the Problem group, which holds the first questions consultants ask clients before anything is scoped or priced, and treat ten questions as plenty for one meeting.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
Problem
What problem do you want this work to solve?
Why ask it
Start here and let them finish before you say anything. A first answer is often a solution in disguise ("we need a new CRM"), so ask what the new CRM would fix, and keep going until you reach something the business actually feels.
Why has this become a priority now?
Why ask it
Problems are usually tolerated for a long time before anyone calls a consultant. Find out what ended the tolerance, because that event sets the real deadline and the mood you will be working in. If the honest answer is "nothing in particular", be careful how much unpaid proposal effort you put in.
What have you tried so far, and why do you think it fell short?
Why ask it
Their explanation matters as much as the history. A client who says the last attempt lacked time or backing is describing conditions you will inherit, and one who blames the people involved may say the same about you in a year.
What is this costing the business while it stays unsolved?
Why ask it
Ask for it in their units: hours lost, orders delayed, staff leaving, revenue not billed. A rough figure they worked out themselves gives the fee something to stand against, and a shrug suggests the problem is an irritation and not yet a priority.
What do you think is causing the problem?
Why ask it
Take the theory seriously without adopting it. They have lived with the problem far longer than you have, but the cause a client names is frequently the one that is most comfortable to name, and your diagnosis should be free to test it.
How does this work today, and where exactly does it break?
Why ask it
Have them trace one real case from start to finish, an order or a hire or a month-end close, on a whiteboard if there is one. The gap between how the manager describes the process and how the person doing it describes it is often the finding.
Who feels this problem most from day to day?
Why ask it
The person who commissions the work is often not the person living with it. Get names and ask to speak to one or two of them before you propose anything, since they know details the sponsor has never been told.
What is working well that we should be careful not to break?
Why ask it
Clients arrive ready to list faults, so this one usually takes them a moment. The answer marks out what people there are proud of, and a recommendation that tramples it will be resisted however sound it is. If nobody can name anything, ask how the team is doing before you ask about the process.
How would you put the problem in one sentence to someone outside your team?
Why ask it
Save it for when the detail is on the table. If what comes back is plain enough for the finance director to repeat, you have something to scope against. If it leans on project code names and acronyms, nobody has pinned the problem down yet, and pinning it down may be the first thing worth paying you for.
Goals
What does success look like a year after we finish?
Why ask it
Setting the picture a year out moves the answer past "the report was delivered" to what is different in the business. Write down their exact words and use them in the proposal, since that is the language the result will be judged in.
How will you measure that, and where does the number stand today?
Why ask it
A target without a baseline cannot be shown to have moved. If nobody knows the current figure, measuring it becomes the first task in the scope, and it is better for both sides to learn that before a fee is attached to an improvement.
What would tell you in the first month that this is working?
Why ask it
A measure set for a year out is no help in week three, when the sponsor gets asked how the consultants are getting on. Agree on one early sign, even a soft one such as fewer escalations or a first clean data pull, so there is something to report before the main number can move. A client who cannot think of one may end up judging the work on mood.
What would solving this be worth to the business?
Why ask it
The answer is what makes value-based pricing possible, a fee set against the result instead of the days. Let the client do the arithmetic aloud and do not supply the number yourself: an estimate they built is one they will defend when the proposal reaches finance.
Would the gain from solving this come once, or would it repeat every year?
Why ask it
A saving that returns every year supports a different fee from a single windfall, and clients tend to count only the first year until asked. Have them say how long they expect the benefit to last before something else in the business changes it.
What are the business's main goals for the next two years, and where does this project fit?
Why ask it
Work tied to a stated company goal has a better chance of keeping its funding when budgets tighten. If the link takes a long explanation, you are probably looking at one person's project, which can still be good work but calls for a smaller first phase.
When you say you want to grow, which do you mean: revenue, profit, customers, locations or headcount?
Why ask it
A business wanting to grow has often not chosen, and the choices pull against each other: chasing revenue can thin the margin, and adding locations can starve the first one of attention. Get one measure and a figure for it before anyone discusses how.
Where has your growth come from over the last two or three years?
Why ask it
Ask for the split between new customers, existing customers buying more, and price rises. The owner's story and the sales records do not always agree, and the source that did most of the work is the first place to look before you propose anything new.
What is holding growth back right now: demand, capacity, cash or people?
Why ask it
Each answer points to a different engagement. A firm turning work away needs help with delivery, while one with idle staff needs help selling, and proposing the wrong one wastes the first month. If they name all four, ask which ran out first in their last strong quarter.
If sales doubled next year, what would break first?
Why ask it
It is a quick test of whether the growth they want is feasible with the business they have. Delivery, hiring, cash tied up in stock or unpaid invoices, and the owner's own hours are the usual answers, and whichever they pick may need work before any push for more sales.
What would have to be true for expanding into a new market, product or location to be worth it?
Why ask it
This turns the feasibility of expanding into a short list of assumptions you can test: how many customers, at what price, what it costs to set up and how long before it pays back. Agree with the client in advance which result would mean no, since a study that can only say yes is not worth commissioning.
How would the growth be paid for, and how much could you afford to lose finding out whether it works?
Why ask it
Expansion tends to cost money before it brings any in. Whether the plan rests on retained profit, borrowing or an investor tells you how fast it can move and whose approval it needs, and the second half of the answer sets the size of a sensible first trial.
If we could only fix one thing, what should it be?
Why ask it
Useful when the brief has grown into a list of everything that annoys the leadership team. The answer gives you the core of a first phase, and it shows whether the people in the room agree with each other. Quite often they find out that they do not.
What would a disappointing result look like to you?
Why ask it
People are often more exact about failure than about success. You may hear about a past report that sat unread or a recommendation nobody could afford, and each of those is a design constraint you would not otherwise have been given.
What is riding on this for you personally?
Why ask it
Ask it one to one, never in front of the client's colleagues. A sponsor whose reputation depends on the outcome will clear obstacles for you. One who was handed the project will not, and you should plan your escalation route with that in mind.
People
Who makes the final decision to go ahead, and who else has a say?
Why ask it
You need the whole chain: the person who signs, the people who advise them and anyone who can veto. If the decision maker is not in the conversation, ask how to include them before the proposal goes in, because a proposal relayed secondhand loses most of its argument.
Who is sponsoring this, and how much of their time will it get?
Why ask it
A sponsor in name only cannot unblock anything. Ask what they will personally show up for, half an hour every two weeks or only the final presentation, and size your ambitions to match.
How much of the business runs through you personally, and what happens when you are away for two weeks?
Why ask it
In small business consulting the owner is usually the sponsor, the decision maker and the bottleneck all at once. If quotes, key customers and approvals each wait for them, your recommendations will wait too, so plan the work around the hours they can really give.
Who is our day-to-day contact, and what can they decide without checking upward?
Why ask it
Authority matters more than seniority here. A contact who must refer every question to someone else adds days to each one, so settle in advance which calls are theirs to make: interview schedules, data requests, minor changes to the plan.
Who inside the business understands this problem best, and will they be part of the work?
Why ask it
In many organizations one person could walk you through the whole thing in an afternoon, and that person is not always a senior one. If they have been left out, ask why before you assume it was an oversight: they may be too stretched to release, or they may have run the attempt that stalled.
How do you want progress reported, to whom, and how often?
Why ask it
Also ask what happens between reports if something is going wrong. A client who wants only a formal monthly update has no route to hear bad news early, so settle who you may call on the day a problem appears.
Whose work will change if this goes ahead, and what have they been told?
Why ask it
If the answer is "nothing yet", your first interviews will double as the announcement and people will be guarded. Ask the client to tell them before you arrive, in the client's own words, what the project is and what it is not.
Where do you expect resistance, and what is behind it?
Why ask it
Push for the why as well as the who. Objections usually have a fair core, such as a team that was burned by the last change or a manager who stands to lose budget, and knowing it lets you answer the concern instead of working around the person.
Have you worked with consultants before, and what would you repeat or avoid?
Why ask it
A direct route to their expectations of you. Complaints about consultants who vanished after the kickoff or handed over a generic deck tell you which habits to make visible early, and praise tells you the standard you are being measured against.
What worries you about bringing in an outside consultant?
Why ask it
Invite the objection while you can still answer it. Cost, disruption, confidentiality and "they will tell us what we already know" are the usual ones, and a client who has voiced a worry is much easier to reassure than one who is quietly holding it.
Why bring in someone external for this instead of handling it in-house?
Why ask it
The reason defines your role. Missing expertise, missing capacity and the need for an independent voice call for three different engagements, and the third means part of your job is to say what insiders cannot.
Whose idea was it to hire a consultant, and did anyone argue against it?
Why ask it
You are walking in as somebody's proposal, and it helps to know whose. If the sponsor pushed for it over a colleague's objection, that colleague's team may greet your interviews coolly, so ask how you should be introduced to them. If the idea came from a board or an investor, find out how the sponsor feels about having you there.
Scope
What is in scope, and just as importantly, what should we leave alone?
Why ask it
Exclusions are the useful half and clients rarely volunteer them. Written down, "we are not reviewing the operating model" prevents the slow expansion that turns a six-week job into four months at the same fee.
Which decisions do you want from us, and which will you make yourselves?
Why ask it
Some clients want a single recommendation to approve, and others want options with the trade-offs laid out. Hand the first kind a menu and it reads as fence-sitting. Hand the second kind a verdict and it reads as presumption.
Do you want us to stop at the recommendation or stay through implementation?
Why ask it
Advice and delivery are different jobs with different staffing, fees and exposure. Clients often assume one and consultants the other, and the mismatch surfaces at the final presentation when someone asks who is going to do all this.
What do you want to have in your hands at the end: a report, a working model, a trained team?
Why ask it
Ask what became of the last report someone wrote for them. Clients sometimes request one because that is what consultants are known to produce, when what they need is a spreadsheet their own analyst can maintain after you have gone.
Who will read the output, and what do they need to be able to do with it?
Why ask it
A board paper, an implementation plan and a submission to a regulator are different documents, and one file cannot be all three. Knowing the reader also tells you how much of the reasoning has to be visible and how much can sit in an appendix.
What decisions have already been made that are not open for review?
Why ask it
There is usually a committed vendor, structure or announcement somewhere in the background. Learning it now lets you scope around it honestly. Learning it in a steering meeting, after you have recommended the opposite, costs you credibility that is hard to win back.
Which other projects touch this one, and who runs them?
Why ask it
Overlapping initiatives compete for the same people and can undo your recommendations partway through. Ask to be introduced to those leads early, because their cooperation is a dependency whether or not anyone writes it down.
How much change can your team take on while still doing their normal jobs?
Why ask it
The answer decides whether you design something people can adopt alongside their work or something that needs cover for their roles. Check a confident answer against what the organization has been through lately: a team still absorbing a restructure or a new system may have less room than its leaders assume.
Who signs off each phase, and what has to be true for them to sign?
Why ask it
Ask for the acceptance test in plain words. "Sign-off when the sponsor is satisfied" is not a criterion, it is an open invitation to rework, and it leaves you nothing to point to if the final invoice is questioned.
If the diagnosis changes what we think you should do, how do we handle that?
Why ask it
Settling the mechanism before you need it keeps a real finding from turning into an argument about the contract. You want a named person to take a change of scope to, a rough turnaround, and permission to raise it early instead of at the end of a phase.
What would make you stop this work early?
Why ask it
It is an easier thing to ask before the contract than after a bad quarter. A change of leadership, a spending freeze and an acquisition are common answers, and each is a reason to break the work into phases that leave something usable behind if the next one never starts.
Who takes this over when we leave, and what will they need from us?
Why ask it
Hold out for a person, not a team. Handover planned from the start looks like documentation, working side by side and shadowing along the way. Handover arranged in the final week is a folder nobody opens.
Access
Which data will we need, who owns it, and how long does access usually take?
Why ask it
Waiting for data can eat weeks of a short engagement. Check who grants access, whether a security review is involved, and whether the data has ever been pulled before. "It should be straightforward" from someone who does not own the system is a hope, not an answer.
Who can we interview, and does the list need approval?
Why ask it
You are testing for filtering. A curated list of enthusiasts produces a comfortable, useless picture, and being told you may not speak to frontline staff tells you what the sponsor is worried about hearing. Both change how you design the work.
Who already advises you, such as an accountant, a bookkeeper or a lawyer, and may I speak to them?
Why ask it
A smaller client's accountant often knows the numbers better than the owner does. An introduction saves you rebuilding figures that already exist, and it stops you contradicting advice the owner trusts without knowing you have done it.
What has already been written about this: earlier reports, audits, process maps?
Why ask it
Reading what exists before the first interview saves the client from paying you to rediscover it. It also shows you which conclusions were reached before and then ignored, which is worth raising with the sponsor before you reach them again.
Which systems and tools does this touch, and who looks after each one?
Why ask it
On an IT or data engagement this is half the scope. Ask about versions, custom changes, vendor contracts and whether a test environment exists, and note any system whose only expert is one employee or a supplier who is no longer under contract.
How much of your team's time can you commit, and whose?
Why ask it
Have the people and their hours a week written into the scope instead of offered verbally. Every engagement design assumes some client effort, and when that effort does not appear the work either stops or you absorb it, which is how a consulting firm quietly loses money on a job.
What is happening in the next quarter that we should schedule around?
Why ask it
Year end, a system upgrade, an audit, the busiest season, a reorganization, school vacations for the key people. Any of these can make a perfectly reasonable timeline impossible, and clients often do not think to mention them until asked.
What regulatory, security or contractual limits apply to how we work?
Why ask it
This covers how personal data is handled, where information may be stored, background checks, site access, and clauses in the client's own contracts with third parties. The rules differ by country and industry, so ask their legal or compliance contact how it works there, and build the answer into your staffing and timeline.
Where do you want us working, and how often on site?
Why ask it
Being in the building buys you hallway conversations that no interview schedule replaces, but three days a week of travel changes your costs. Settle it explicitly, including who pays the expenses, so that neither side drifts into an arrangement it did not price.
Budget and proposal
Has a budget been set for this, and what range should the proposal fit?
Why ask it
Asked plainly after the conversation about value, it rarely offends. A range lets you offer two or three sizes of engagement instead of guessing, and "send us a proposal and we will see" often means the money has not been found yet.
Which budget would this come out of, and when does that budget year end?
Why ask it
Operating money, a capital request and a department's unspent funds each come with their own rules and approvers. The year end matters too, and it is not the same month everywhere: money that has to be spent before it calls for a different phasing from money that only becomes available after it.
When do you need this finished, and what happens if it runs a month late?
Why ask it
The consequence shows which dates are real. A contract renewal or a board meeting will not move, while a date picked to sound decisive will. Plan backward from the fixed ones and say early if the time allowed does not fit the scope.
Who else are you considering, and what will you compare us on?
Why ask it
Many clients will tell you, at least in outline. If the comparison is mainly on day rate, decide now whether you want to compete on those terms. If doing the work internally is one of the options, treat that as your strongest competitor.
What made you get in touch with us in particular?
Why ask it
A referral, a talk you gave and one piece of past work each set a different expectation of you. If a former client sent them, ask what was said, since that story is the result they are hoping to have repeated. If they found you by searching, expect to be compared with whoever else the search turned up.
What does the proposal need to contain for it to be approved?
Why ask it
Some clients need a one-page letter and others a formal response with references, proof of insurance and a priced plan. Find out who reads it besides your contact: the finance or procurement reader was not in the room and needs the reasoning spelled out.
Would it help to see the proposal as two or three options at different prices?
Why ask it
Options change the client's decision from whether to hire you into which version to buy. The smallest one they would accept shows what they consider essential. If they ask for a single figure instead, find out what it has to cover before you write it.
Would you go through a draft of the proposal with me before I send the final version?
Why ask it
Objections raised over a draft can still be fixed, while a finished proposal arriving cold by email tends to be judged on its last page. Notice who they bring to that call, because those are the people whose approval it needs.
How do you prefer to pay for work like this: a fixed fee, by the day, or in phases?
Why ask it
Follow up with what has to happen for an invoice to be approved and how long payment takes after that, since both vary a lot between organizations. A fixed fee leans on a tight scope and clear exclusions, and day rates lean on a spending cap the client trusts, so match the model to how much is still unknown.
What are your contracting and procurement steps, and how long do they take?
Why ask it
Master agreements, supplier onboarding, insurance evidence, security questionnaires and purchase orders can add weeks between a yes and a start date. Find out now who owns each step, so the start date in your proposal is one you can meet.
Who owns the material we produce, and what may either of us say publicly afterward?
Why ask it
Cover the deliverables themselves, your right to reuse your own methods and templates, and whether you may name them as a client. Ownership depends on the contract and on the law where you work, so get it written into the agreement at this stage and have someone qualified read the clause if much rides on it.
Is there anything I have not asked about that I ought to know?
Why ask it
Leave a proper silence after it and resist filling it. Clients often hold back the awkward fact, such as a skeptical head of finance or a budget that is not yet confirmed, until they have decided you are worth telling.
What happens next on your side, and when should we speak again?
Why ask it
Try not to leave a client meeting without a dated next step. Offer one yourself if they hesitate, such as a written summary by Friday and a call the following week, and notice whether they commit to it. Reluctance to fix a date says something about how interested they are.
Turning a conversation into a scope
Practical guidance for the conversation itself
Using the list across two or three conversations
Before the first discovery call
Give twenty minutes to what the client publishes about itself: the pages written for its customers, recent news, an annual report if there is one. Find out who will be on the call and what each person does. Then write down the four facts you want to leave with: what triggered the request, how success will be measured, who holds the budget and who inside the business will own the result.
First call: problem, goals, people
Nobody gets through a list this long in one meeting, and nobody should try. A first call has room for eight to ten: most of the Problem group, two or three from Goals, who decides, the budget range and the next step. Leave scope and access until the client has agreed that the problem is worth solving.
Scoping meeting: scope, access, budget
Once the problem is agreed, the Scope and Access groups turn it into something you can price. Send the access questions ahead of the meeting so the client can bring the person who owns the data or the system. The questions on payment, procurement and ownership can often go by email to whoever handles suppliers.
For value-based pricing, ask about value before budget
Cover what the problem costs, what solving it would be worth and whether that gain repeats before any figure for the work is mentioned. In that order, the budget question is a comparison between a cost and a return, which is the footing a fee priced on value needs. In the reverse order it is only a price check.
Do not solve it in the room
The first call is for the client's account of the problem, and an answer offered twenty minutes in cuts that account short. It also fixes both of you on the first version of the problem, which is seldom the last. When you feel a recommendation forming, ask for an example instead: "our handovers are inconsistent" turns into one named handover between two teams, and that is the version you can scope and price.
Ask about money and approvals in an ordinary voice
Budget, sign-off routes and who objects are operational facts, the same as headcount or the reporting calendar. Asked in the tone you use for everything else, they tend to get plain answers. An apology in front of the question tells the client it is an awkward one.
Say it back before you leave
Close each conversation by summarizing the problem, the goal and the next step in two or three sentences and asking what you got wrong. Corrections made out loud at this point are far cheaper than corrections made to a proposal.
On IT and systems work
The same questions apply, with more weight on the Access group. Ask early about the systems involved, who administers them, what a change request involves and whether there is somewhere safe to test. Requirements gathered only from managers tend to miss how the system is used in practice, so ask to watch someone do the task.
When the client is a business wanting to grow
The growth run in the Goals group comes before any talk of tactics. Settle which measure they mean and what is holding it back, then use the doubling question and the expansion question to judge whether the plan is feasible before you offer to help carry it out. A short feasibility study that ends in a go or no-go is often the honest first phase.
Small business consulting
With an owner-run client several roles collapse into one person: the sponsor, the decision maker and the day-to-day contact are usually the owner. Leave out the procurement questions, ask how much of the business runs through them and who advises them already, and size the first phase to what the owner says the business can comfortably pay for.
Writing the scope
- Define the work by its exclusions as well as its inclusions. A list of what you are not doing is the cheapest protection against expanding scope, and it gives the client something concrete to push back on before the work starts.
- Make the first phase small and its deliverable a decision. Diagnosis, then a go or no-go, lets both sides stop cleanly if the problem turns out to be different from the brief.
- Write the client's obligations in the same detail as your own: named people, hours, data by date, decisions by date. If their side of the scope is vague, every delay becomes your fault.
- State your assumptions explicitly, each with what happens if it proves wrong. Assumptions are how a fixed fee stays honest.
- Put a review point at roughly a third of the way through, with the explicit option to change direction. The first weeks often turn up something that should change the plan, and a planned review gives it somewhere to go.
What the answers tell you
Access commitments are the real test
Enthusiasm is free. Agreeing to grant a data extract by a named date, or to release a named analyst for a day a week, costs something internally. A client who will not commit to access is telling you how much priority the work really has.
Listen for who is missing from the scoping conversation
If the people whose work will change are absent from scoping, they will hear about the project from a slide deck. Ask to include one of them, even briefly, and treat refusal as a risk to note rather than a detail.
Ask what the last engagement's scope got wrong
Clients can often say precisely where a previous consulting scope was unrealistic: too many interviews, too little time for approvals, a report nobody had a slot to receive. Use the answer to calibrate yours before you put dates on anything.
Check the timeline against their own calendar
Take the milestones and lay them against the committee dates, the audit, year end and holidays. A timeline can fail simply because an approval could only happen on a date nobody checked.
Where scoping goes wrong
Fixed fee on an unfixed problem
If you cannot yet describe the deliverable in a sentence, a fixed price transfers all the uncertainty to you. One way out is to scope the diagnosis for a fixed fee and price the rest once you know what you are dealing with.
"Just a couple of extra interviews"
Additions arrive as small favors from people you want to keep happy. Log each one with its cost in days, even when you decide to absorb it, and show the accumulated list at the review point rather than at the end.
Designing around client effort that does not exist
Workshops, data pulls and co-authored outputs all assume availability. If the named counterpart has two hours a week, build something that works at two hours a week rather than something that needs eight.
Sign-off with no criteria
Acceptance defined as satisfaction gives an unhappy sponsor unlimited rework and gives a happy one no way to defend the invoice internally. Write down what the deliverable must contain and let that be the test.
A detailed plan requested before any contract
A client who wants a full diagnostic, a benchmark or a worked plan as part of the pitch is asking for the first phase free. Offer a short paid scoping phase in its place. How they take that offer is a fair preview of how they will treat a change request later.
Writing the third quote
Some buying rules call for several quotes even when the choice has been made. If the question about who else is being considered gets a vague answer, ask whether the current adviser is bidding and how long they have been in place, then decide whether this proposal is worth your week.
Leaving handover to the end
A team that first sees the work in the closing presentation will not maintain it. If nobody can be named as the receiver, say so in the proposal and price a shorter, narrower piece rather than pretending the problem will be solved.
A workable sequence
From scoping call to signed scope
- 1Send a one-page summary within a day: problem, boundary, deliverable, what you need from them, and the assumptions. Ask for corrections in writing.
- 2Get the two or three access commitments confirmed by the people who actually control them, before the proposal is finalized. It is an easy step to skip and an expensive one to have skipped.
- 3Write the proposal with phases, exclusions, client obligations and acceptance criteria, and put the change mechanism on the same page as the fee rather than in the terms at the back.
- 4Walk the sponsor through the assumptions and exclusions out loud before signature. If any of them make the sponsor uncomfortable, you need to hear it now.
- 5At kickoff, restate the boundary and the review point to everyone who will be involved, including the people who were not in scoping.
If scoping keeps stalling
Repeated delays at this stage are not always administrative. Often a decision is unresolved somewhere above your sponsor. Ask directly what has to happen internally before this can be signed, and offer a smaller first phase that fits under whatever approval threshold is blocking it.
If the client goes quiet after the first call
Silence after a good first conversation does not have to mean the call went badly: something else may simply have taken priority on their side. Give it a week or two, then send one short note that refers to the event that prompted them to get in touch. That gives them more reason to reply than a message asking whether they have had time to think it over.