Questions to Ask Consultants
Questions to ask consultants before hiring them and while they are working for you, from the client's side of the table. Use them as questions to ask management consultants pitching for a strategy or cost review, or when a small business is scoping a job with an independent adviser. They run from the first call and the consultant's track record through approach, the team, fees and contract terms to what to ask once the work has started, and each has a note on what a good or a bad answer tells you. They are written for the buyer, not for a consultant preparing discovery questions for a client.
Want questions from the whole vault instead? Try the random question generator.
The questions
Each question, and why to ask it
First call
What experience do you have with organizations of our size and in our field?
Why ask it
Sector knowledge and size knowledge are separate things, and you usually need both: a method built for a company of five thousand can swamp one of fifty. Ask which clients were closest to you on each count, and what had to be done differently for the smaller or larger ones.
Who will actually do the work, and how much of it will you do yourself?
Why ask it
The people in the pitch and the people on the project are often not the same. Get names, seniority and the share of hours for each, and have that staffing written into the contract, so the senior person you liked in the meeting does not fade out after week two.
How would you approach this, step by step, from the first week to the last?
Why ask it
Listen for a sequence fitted to your situation: who they speak to first, what they test, where the decisions fall. If the steps would suit any client in any industry, you are hearing the firm's standard method, so ask where it bends for you.
How do you charge: a fixed fee, a day rate or a retainer?
Why ask it
Each model has its own way of going wrong. A fixed fee tempts the consultant to read the scope narrowly, a day rate rewards a job that runs long, and a retainer can drift without anything being finished. Whichever it is, get the conditions that change the price in writing before you sign.
What does success look like here, and how will we measure it?
Why ask it
A report delivered on time is an output, not a result. Push for something you could observe in your own organization afterwards, such as a cost, a turnaround time or a decision made, and agree who will measure it and when. If they can only describe the document, ask what should be true once people have acted on it.
Which clients can I speak to, including one who chose not to continue with you?
Why ask it
Reference lists are curated by definition, so the second half of the request is the informative part: either you get a frank conversation about fit, or you learn how they handle a request they would rather refuse. When you do reach a past client, find out what they would do differently as the buyer.
Why should we pick you over the other firms we are talking to?
Why ask it
It is a blunt question and a fair one. The useful answers are specific to your problem and may even concede where a competitor is stronger. A reply made of adjectives about passion and partnership would fit any client on any day.
How would you frame this problem differently from the way we have?
Why ask it
If they simply accept your framing, you are buying labor more than judgment. A useful reply pushes on the edges of the question, and it is your earliest sign of whether they will tell you inconvenient things later.
If we do nothing at all, what do you think happens?
Why ask it
Their reply shows how they size the problem, and whether they are willing to say the situation is tolerable. Someone who paints inaction as a catastrophe every time is selling. Someone who can put a rough cost on a year's delay has thought about your case.
How soon could you start, and what would need to be in place first?
Why ask it
An immediate start can mean a gap in their calendar or a team sitting unassigned, and it is fair to ask which. The second half matters as much: a signed contract, a named contact on your side and access to the right files are the usual conditions, and hearing them now keeps week one from being spent waiting.
Would you do a smaller first piece, so we can both test the fit?
Why ask it
A short, priced diagnostic gives you a working sample and gives them a firmer basis for scoping the main job. Some firms built around large engagements will decline, and that tells you something about how they see a client of your size.
What will we be holding at the end: a slide deck, a working model, or a plan with owners and dates?
Why ask it
The classic product of a management consulting project is a deck, which is fine for a board decision and thin for anything your team has to run afterwards. Say which form you need before the price is set, because a model your analysts can reopen or a plan with named owners takes different work from a presentation.
Track record
What is the closest engagement to this one that you have run?
Why ask it
Hold out for one particular client situation, not a category of work. Listen for whether the similarity is in the problem or only in the industry, and be wary if the closest example turns out to be a colleague's project they were not part of.
Is this type of project a core practice at your firm, or one you are still building?
Why ask it
Large management consultancies sell strategy, operations, technology and people work under one name, and the depth behind each can differ a good deal. Ask how many people do this work full time and how long the practice has existed, since a famous name on the proposal does not mean the famous part of the firm is doing your job.
After your last project like this ended, what did the client do with the work?
Why ask it
Advice and results part company here. Consultants who stay in touch can say what was put into practice, what was dropped, and why. Not knowing is an honest answer too, though it tells you their involvement ended at the final presentation.
Can we see a deliverable from a similar project, with the client's details removed?
Why ask it
A sample shows the level of detail you are paying for better than any description of it. Check whether the recommendations are specific enough to act on and whether the numbers behind them are shown. Declining on confidentiality grounds is reasonable, so offer the alternative of a redacted contents page or being talked through one on screen.
What did you do before consulting, and how long have you done this kind of work?
Why ask it
Someone who has run the function they now advise on gives different advice from someone who has only studied it, and both can be useful. What you are checking is whether the years they quote were spent on problems like yours or on something adjacent.
What qualifications or certifications do you hold, and do any of them matter for this work?
Why ask it
In much of consulting anyone may use the title, so a credential can be a real license, a demanding exam or a weekend course. Where the work touches a regulated field such as accounting, law, engineering or immigration, find out what is required where you are and check the registration yourself.
What kind of work do you turn down or pass to someone else?
Why ask it
Being able to name what they are not good at makes the rest of their claims easier to believe. If nothing is ever outside their range, expect your project to be bent toward whatever they usually sell.
Can you tell me about a project that went badly, and what you took from it?
Why ask it
A candid account with their own part in it is a fair guide to how they will behave when your project hits trouble. One that blames the client's lack of commitment is a preview of the conversation you may be having later.
What is a recommendation of yours that a client rejected, and what happened after that?
Why ask it
The story shows whether they can be overruled and stay useful, or whether they disengage. Note whether they describe the client's reasoning fairly or simply as a failure to listen.
How do your engagements usually end: on schedule, extended, or renewed?
Why ask it
A firm whose work always continues has either found a real ongoing need or built a business on extensions. Find out roughly what share run over, and get an example of a job they finished and walked away from.
Approach
What have you already assumed about our situation that we should correct?
Why ask it
Every proposal rests on guesses formed in a meeting or two. Getting them said out loud costs an hour now instead of weeks later, and it lets you correct the one about your budget, your systems or your internal politics that would have skewed the plan.
What do you need from us, and how many hours of our people's time will that take?
Why ask it
The cost that never appears on the invoice is your own staff: interviews, data pulls, workshops, review rounds. Get an estimate in hours per week and by role, plus the list of files and people they need in the first two weeks, so permissions and calendars are sorted before the clock starts.
Who on our side needs to be behind this for it to work?
Why ask it
A project with no senior backer tends to stall the first time it asks someone to change how they work. The roles they name also show whether they have understood your organization or only read the brief.
How would you find out if something we told you is wrong?
Why ask it
Clients pass on internal assumptions as fact all the time. Good answers involve cross-checking: talking to people outside the sponsoring team, comparing figures with the source systems, testing the story on customers.
Where do your benchmarks come from, and how similar are those companies to ours?
Why ask it
Management consultants often build the case for change on a comparison with peers. Find out how many companies sit behind each figure, how old the data is and whether size and business model match yours, because a benchmark drawn from much larger firms can make an ordinary cost look like a problem.
What do you do when the answer is something our leadership does not want to hear?
Why ask it
Press for a real occasion. People who have delivered unwelcome findings can describe how they did it and what followed. If it has supposedly never come up, either they have not looked hard or they have learned to write around it.
How long will this take, and what is that estimate based on?
Why ask it
A timeline drawn from similar projects is worth more than one worked backwards from your deadline. Ask which stage has overrun before and why, and whether the dates assume your people respond within days or within weeks.
What is the first real deliverable, and when do we see it?
Why ask it
Something concrete in the first few weeks tells you whether the project is moving and gives you a point to stop if it is not. When nothing lands until the final presentation, you have no chance to step in while stepping in is still cheap.
At the halfway point, how will we know this is working, and what happens if it is not?
Why ask it
What you are after is a checkpoint with teeth: a named measure, a date and an agreed response. Without one, a struggling project tends to run to the end of the contract, because stopping it means someone has to say so out loud.
What is most likely to make this project fail?
Why ask it
Anyone who has done this work several times knows where it breaks, and it is often on the client's side: a sponsor who moves on, data that does not exist, a team too busy to take part. Hearing that before you sign is encouraging, and it hands you a list of things to fix first.
Are you recommending or implementing, and where exactly does your involvement stop?
Why ask it
Plenty of sound advice dies somewhere between the report and the first changed habit. Have the boundary written down, along with what happens if carrying out the recommendation shows it was impractical.
How will you introduce yourselves to the staff who did not ask for a consultant?
Why ask it
People who think they are being audited give careful, useless answers. Ask what the team will be told about why the consultant is there and what will happen to what they say, and agree that message with your own managers before the first interview is booked.
If the findings point toward job cuts or a reorganization, how is that part handled?
Why ask it
Staff tend to assume this is why consultants have arrived, and on a cost review they are sometimes right. Settle at the start whether headcount is in scope, who makes the call and when employees hear about it. Rules on consultation and notice differ by country and sometimes by contract, so bring in your HR or legal people before anything is announced.
What tools or software will you bring, and will we have to pay for any of it afterwards?
Why ask it
Some methods come with a licensed platform, a survey tool or a dashboard that keeps costing money once the project ends. Find out what stops working when the consultant leaves, and whether the same result could be reached with what you already own.
When this is finished, what will we be able to do ourselves, and what will still need you?
Why ask it
Underneath, this asks whether the engagement is designed to end. Look for training, documentation and models your own team can run. If the honest answer is that you will keep needing them, that can still be a fair arrangement, as long as you budget for it knowingly.
If we spoke six months after this ends, what would you expect to have changed?
Why ask it
It asks for a claim you can hold them to, and the realistic answer is often more modest than the proposal's opening page. A confident reply with numbers attached is either considered judgment or overreach, and asking how they arrived at it will tell you which.
The team
Who is our day-to-day contact, and who do we call if they are not answering?
Why ask it
One named person for routine questions and one senior person for problems is the arrangement to look for. Check how quickly each normally replies, because someone juggling several clients may treat two working days as prompt.
How often will we hear from you, and what will a progress update contain?
Why ask it
Settle the rhythm before work begins: a weekly call, a short written note, a monthly session with the sponsor. A status report that only lists activity will not show you when things are slipping, so agree that each one says what is late and what they need from you.
How many other clients will you be working for while you work for us?
Why ask it
Almost nobody works for one client at a time, and that is fine. What matters is the share of each week that is yours and whether it is written down. With a solo consultant, also ask what becomes of your project if they fall ill or land a larger job.
What happens if someone on the team leaves or is moved to another client?
Why ask it
Reassignments partway through are routine at larger firms. Two things are worth negotiating: a say over any replacement, and handover time that is not billed, otherwise you pay for the newcomer to learn what the last person already knew.
Will any part of this be subcontracted or delivered from another office?
Why ask it
Subcontracting is common and not automatically a problem, but it changes who has access to your data, which time zones the work happens in, and who is accountable. Better to have it disclosed now than to discover it from an unfamiliar name on a file.
How much of the work will be done on site with us, and how much from a distance?
Why ask it
Time in the building matters most when the job depends on watching how work really gets done or on winning over wary staff. Remote delivery costs less and is often fine for analysis. Whichever mix is proposed, check how the travel is charged.
Has this exact team worked together before?
Why ask it
A group assembled for your project spends its first weeks learning each other's habits at your expense. A team with a shared history can usually point to the project they did together and tell you who did what on it.
How long have the analysts on the team been in consulting, and who checks their numbers?
Why ask it
At the larger firms much of the modelling and slide building falls to people early in their careers, which can work well when a manager reviews it closely. What you want described is that review: who reads the spreadsheet line by line, and whether that person will be in the room when you question a figure.
Fees and contract
What is your best estimate of the total cost, and how firm is it?
Why ask it
You are looking for a single figure with a range around it, and then for what would push the bill to the top of that range. If all you get is a day rate, the arithmetic, and the risk, has been left with you.
What is the rate for each person on the team, and how are junior hours billed?
Why ask it
A blended rate hides the mix, which is how a team can shift toward juniors without the invoice changing. Rates by name, plus a cap on the hours the most junior members can bill, keeps the staffing you were sold from eroding quietly.
Which expenses are billed on top of the fee?
Why ask it
Travel, data subscriptions, survey panels, software licenses and administrative percentages are the usual additions. A cap and a requirement for receipts close the gap, since expense terms are where an otherwise clear proposal can turn out to be open-ended.
When do you invoice, and is anything due before work starts?
Why ask it
Deposits are common with independent consultants and small firms. It is reasonable to ask that later payments follow accepted deliverables instead of calendar dates, so the money and the work stay roughly level.
What is left out of this price that clients tend to assume is in it?
Why ask it
Typical gaps are presenting to the board, training staff, revisions after feedback and support while the recommendations are being carried out. An honest list here saves an awkward conversation in month three.
Would you tie any part of the fee to results?
Why ask it
Some will agree to hold back a portion until a target is met, and many will not, often for sound reasons: outcomes depend on what you do with the advice. The discussion still shows you which results they believe they control.
Do you earn anything from the vendors or products you might recommend?
Why ask it
Referral fees, reseller agreements and partner status are ordinary in technology and marketing consulting. None of that rules a recommendation out, but you should hear about it before the recommendation arrives, not after you have bought.
If a piece of work misses the mark, how is it put right and who pays?
Why ask it
Look for a defined review step and a stated number of revision rounds inside the fee. Assurances that they always look after their clients are pleasant to hear and impossible to rely on once the two of you disagree about whether the work was good enough.
Is there any support after the final handover, and how is it charged?
Why ask it
Questions tend to surface a few weeks after the consultant has gone, usually when someone first tries to use the work. A short period of included follow-up, or an agreed hourly rate for it, is easier to settle now than to negotiate when you need the answer.
Who owns the documents, models, and code when we are done?
Why ask it
Many firms license their frameworks and tools instead of handing them over, which can leave you unable to rerun an analysis built on your own data. Ownership rules differ by country and by contract, so have whoever reviews your agreements look at this clause, especially for anything you will depend on day to day.
Do you work with our competitors, and how do you handle that?
Why ask it
Sector experience usually implies competitor work, so a flat denial is less believable than a described process. Useful follow-ups are whether the teams are kept separate, whether they would agree not to work for a named rival during the project, and what happens to what they learn from you.
Who on your side will see our information, and what happens to it when the project ends?
Why ask it
A confidentiality agreement is the start, not the whole answer. Ask where files are stored, whether anything sits on personal laptops, and whether your data is returned or deleted at the end. If customer or employee records are involved, bring in whoever handles privacy for you, since the rules differ by country and industry.
Does anyone on the team put client material into AI tools, and under what rules?
Why ask it
Plenty of consultants now draft and analyze with AI assistants. What you need to know is which tools, whether the provider keeps your documents or trains on them, and whether you can rule it out for sensitive material. If there is no policy at all, the question has probably not been thought about yet.
Do you carry professional liability insurance, and can we see proof of it?
Why ask it
Cover for errors in professional advice goes by different names in different countries, and many client contracts require it. Check with your own procurement or legal team what level they expect, and be cautious with anyone advising on high-stakes decisions who carries none.
How do we end this early, and what does that cost?
Why ask it
Read the termination terms closely: the notice period, payment for work in progress, and any minimum commitment. Knowing the exit price before you start is what keeps a poor fit from running the full length of the contract.
Once hired
What have you found so far that you did not expect?
Why ask it
Ask it a few weeks in, before the findings have been tidied for a presentation. Early surprises are often the most valuable part of the work, and hearing them now gives you time to point the remaining effort at them.
What are we doing that is slowing you down?
Why ask it
Consultants seldom volunteer that the client is the bottleneck, since it sounds like an excuse. Asked directly, they will usually name the late data, the cancelled interviews or the approval that has sat for two weeks, each of which you are paying for.
What have you changed your mind about since you started?
Why ask it
If nothing has shifted, either the proposal was remarkably accurate or the conclusion was fixed before the evidence came in. Being able to describe a view they dropped, and what changed it, suggests they are working from your situation and not from a template.
Can we see the model and the assumptions behind this page?
Why ask it
A finished chart shows the conclusion and hides the inputs that produced it. Pick the one or two slides the whole recommendation leans on and ask for the workings, with every assumption marked. Change a single input in front of them and watch how far the answer moves.
What are our own people telling you that they are not telling us?
Why ask it
Outsiders hear things staff will not say to a manager. Do not ask who said what: take the themes without names, or the next round of interviews will produce nothing. What you do in the week after hearing it decides whether staff speak freely again.
Are we on budget, and what is your forecast to the end?
Why ask it
Raise it at every checkpoint, not only when an invoice looks high. Hours spent against hours planned, set beside the share of work that is really complete, shows an overrun while there is still time to trim scope.
Which of your recommendations do you expect us to find hardest to carry out?
Why ask it
It moves the conversation from whether the advice is right to whether it will survive your organization. If they have a ready answer, ask them to help plan for that one in particular. If they have none, they have not pictured your people doing it.
If you were in my position, what would you do first?
Why ask it
Reports hedge and people commit. Put this to the senior consultant in a one-to-one conversation and you often get a plainer view than the slides contain, including the option they thought was too blunt to write down.
After you have gone, what should we watch for?
Why ask it
Every change has a typical way of coming undone: old habits returning, a measure being gamed, the owner being pulled onto something else. Get the two or three early signs from them, and name someone on your side who is responsible for checking.
Buying consulting well
Practical guidance for the conversation itself
Before you brief anyone
Work out whether you need management consultants or a specialist
Management consultants are generalists in how an organization decides, spends and structures itself, which suits a question that cuts across departments. A problem that sits inside one function, such as a payroll system, a tax position or a search campaign, usually goes better with someone who does only that. Sorting this out first tells you which firms to invite and which of these questions matter most.
Write the decision, not the topic
Consultants respond to what you hand them. A brief that says we need a growth strategy invites a broad, expensive project. A brief that says we must decide by September whether to keep the second facility open produces a tighter scope and lets you compare proposals against each other.
Name the internal owner first
Someone on your side needs the time and the authority to answer questions, unblock access, and accept deliverables. Engagements without a real owner drift, and the consultant's time gets spent chasing meetings you are paying for.
Decide what you would do with each possible answer
If a finding would not change anything, do not buy it. Working this through in advance also stops you from commissioning research to settle an internal argument that is really about authority rather than evidence.
Talk to more than one firm, even if you know who you want
Competing proposals frame your problem in different ways, which is thinking you get before paying anyone, and they give you a reference point on price and staffing. With only one firm in the room, the scope tends to settle on whatever that firm prefers to sell.
Terms worth pinning down in writing
- How success will be measured: the measure, who checks it, and when.
- Named staffing with seniority and expected hours, plus a requirement that substitutions be approved.
- Rates by person rather than a blended rate, and a cap on total fees and on expenses.
- The specific conditions that trigger a change order, and who has to sign one.
- Deliverable dates, including at least one substantive output in the first few weeks.
- Ownership of documents, data, models, and code, and license terms for anything not transferred.
- Confidentiality and data handling, including whether your data leaves your systems and where it is stored.
- Termination for convenience: notice period, what is owed, and what you receive on the way out.
- Conflict of interest terms, including any exclusivity during the engagement.
- A payment schedule tied to accepted deliverables, and the number of revision rounds the fee includes.
- Proof of professional liability insurance, where your organization or your own contracts call for it.
- Any use of AI tools on your material: which tools, and what is excluded.
Once the work has started
Hold the check-ins you agreed
A regular half hour with the lead consultant is where slipping dates, blocked access and early findings come out. Cancel it twice and the next you hear of the project may be an invoice or the date of the final presentation.
Ask for findings before they are polished
A rough conclusion shared early can still be argued with and redirected. Once it sits in a finished deck, the team is defending it. Say plainly that you would sooner see a half-formed view than be surprised at the end.
Keep one written list of decisions and changes
Scope moves in conversation: a request in a corridor, an offer to take a quick look at something else. A shared running note of what was decided, what was added and what it costs keeps both sides straight and makes the final invoice unremarkable.
What goes wrong
Hiring a consultant to avoid making a decision
When the real purpose of the engagement is to give a decision external cover, the work is judged by whether it supports the conclusion someone already reached. It is expensive, everyone involved can tell, and it wastes the one thing an outsider can genuinely offer.
Buying analysis when you needed implementation
Diagnostic work and delivery work require different skills and different people. Be explicit about which one you are purchasing, and if you want both, ask how the team changes at the handover and who stays.
Letting scope grow without a change order
Additional requests during a project feel small individually and reset the timeline collectively. Route every addition through the change process even when the consultant offers to absorb it, so the record of what was promised stays intact.
Accepting a blended rate and a nameless team
Without named staffing you have bought capacity rather than expertise, and the mix can shift toward juniors while the invoice looks the same. Ask who is on the project this month, every month.
No plan for the work after the final presentation
A familiar fate for a consulting deliverable is a well-received presentation followed by nothing. Agree before the project ends who owns each recommendation, what the first three actions are, and when someone will check whether they happened.