The most expensive consulting engagement is one you didn't need. Even good consultants can spend 4–6 weeks at the front of a project producing a diagnosis your team could have written in an afternoon — if someone had asked the right questions. Before you put out an RFP or book a discovery call, run the following seven-question audit internally. If you come out the other side and the answers are clear, you may not need outside help at all. If they aren't, you'll brief whoever you do hire about ten times better.
1. What does “better” actually look like?
“We want to improve our operations” isn't a problem statement; it's a feeling. A useful problem statement names the observable thing that will be different in six months.
Examples of useful answers:
- Quote-to-cash cycle drops from 18 days to 7 for our top three product lines.
- Customer onboarding completes in 2 weeks rather than the current 6 — measured by time from contract signature to first value moment.
- One person can run the close cycle instead of three.
If you can't name an observable thing, you're not ready to hire a consultant. You're ready to spend a week defining the thing.
2. Whose problem is this?
Every operating-model change has a champion (the person who will own the new way of working when the dust settles) and a sponsor (the executive whose neck is on the line for the outcome). If those two people aren't named — or worse, are the same person without explicit acknowledgement — the engagement will end with a beautiful report and no behavioural change.
Identify them now. If the champion is unwilling or unable to take ownership of the new state, the project is going to fail no matter who runs it.
3. What have you already tried?
Make a list. Be specific about what you tried, when, and why it didn't stick. Three quarters of the “new” ideas a consultant will propose are things you've already tried in some form — the value they add is usually in execution discipline, not ideation. Knowing what you've tried saves everyone weeks.
4. What data do you have, and where does it live?
Operating-model work depends on numbers: cycle times, error rates, cost-per-transaction, volume by segment. If those numbers exist somewhere (a CRM, an ERP, a finance system) you're miles ahead. If they don't — if the answer to “how long does X take?” is “we'd have to ask Janet” — that's a discovery finding before you even start.
Spend a week gathering whatever you can. A back-of-envelope number with a date next to it beats a perfect number that takes a month to produce.
5. What's your real appetite for change?
Be honest. Are you prepared to:
- Change reporting lines?
- Move budget between teams?
- Retire processes that have a long-time owner attached to them?
- Be unpopular for a quarter while the new model settles in?
If the answer to most of those is “not really,” you're looking for a workshop, not a transformation. That's a legitimate ask — just price it as such. A workshop is one to two weeks and a few thousand dollars. A transformation is months and orders of magnitude more.
6. What's the cost of doing nothing?
Quantify it. “We lose deals because onboarding is slow” becomes “we forecast losing $1.2M in expansion revenue this year based on three named accounts at risk.” If you can't produce a number — even a sloppy one — your sponsor will struggle to justify the consulting spend, and your team will struggle to prioritise the work alongside their day jobs.
7. When would “done” be?
Consulting engagements rot when they have no end state. Define what being done looks like — a specific operating model documented and in use, a specific tool deployed and adopted, a specific metric hit and held for two quarters. Tie payment terms to that, not to hours.
So, do you need outside help?
After running this exercise, three patterns emerge:
- You can do this yourself. The problem is well-defined, someone internal has the bandwidth and authority, and the change is contained. Save the money.
- You need a specific skill for a specific window.E.g. someone who's done five Asana implementations, or who knows NetSuite forwards and backwards. Buy that skill on a defined scope — not a generalist transformation engagement.
- You need outside perspective and execution capacity at the same time.The problem cuts across functions, has political edges your internal team can't navigate without scars, and the status quo has strong gravity. This is when a consulting engagement earns its keep.
If you land in (3), your seven answers become the brief. Hand them to whoever you talk to — us or anyone else — and you'll get a much better proposal because of it.
One final filter
Ask any prospective consultant: “Walk me through the last engagement you ran where the answer turned out to be ‘you don't need us.’” If they can't name one, you're dealing with a sales process, not a diagnosis. The good ones happily talk visitors out of work; they know the return business and the referrals more than make up for the engagement they walked away from.