The rule that separates them
Anything that cannot be measured in a system the client owns does not go in the report. That single rule produces almost every other difference between the two, so it is worth sitting with before comparing anything else.
It rules out benchmark comparisons, because a benchmark is a fact about other companies. It rules out figures derived from interviews, because an interview is evidence about where to look rather than evidence of magnitude. It rules out market sizing, strategic options and organisational design, all of which are legitimate work and none of which can be measured in a CRM. What it leaves is a narrow class of finding: demand that entered a system, did not convert, and can be priced against that company’s own rates.
Interviews still happen — four to six of them, thirty minutes each, across sales, operations and service. Their purpose is specific: to find the gap between what the system records and what people actually do. That gap tells you where to go and measure. It never becomes a number on its own.
What each one is actually good at
Management consulting is the right instrument when the question is what to do. Which markets, which products, what the operating model should look like, whether to build or buy, how to structure the organisation after an acquisition. These are judgement questions where the value is in framing and experience, and no amount of system access answers them.
Operational diligence of this kind is the right instrument when the question is where the money is going and how much. It is a measurement exercise with a narrow scope and a specific output, and it is deliberately not strategic. Nobody should commission it expecting a view on their market.
The failure mode in both directions is buying one and expecting the other. A strategy engagement will not hand you a defensible leakage figure. A leakage diagnostic will not tell you whether to enter Texas.
Cost, and why the gap is so large
A fixed $5,000, credited in full against implementation, against a scoped consulting engagement that is normally a multiple of that. The gap is not a discount and it is not a comment on anyone’s value. It is a function of three structural things.
- Scope. Ten business days from systems access, on a known list of failure modes, in a known order. Narrowness is what makes a fixed price possible at all.
- Pattern recognition instead of discovery. A thousand engagements since 2021 means the work is checking a known list against a specific estate rather than starting from first principles, which is what a consulting engagement must do because its questions are genuinely open.
- The follow-on. The fee is credited against a build the same firm would do. The diagnostic does not have to carry the firm’s margin on its own, which a standalone advisory product does.
That third point cuts both ways and should be named rather than glossed. A credited fee creates an incentive to find something buildable. The counterweight has to be structural: if the leakage is immaterial the report says so in its first paragraph and the firm says do not hire us, and implementation is approved one phase at a time rather than as a committed total. A firm with the credit and neither counterweight has a sales funnel with a report attached.
How to tell which one you are being sold
- 01Ask whether every figure in the deliverable will name the system it was measured in and the period it covers. This is the fastest question and it separates the two categories immediately.
- 02Ask what happens if nothing material is found. A measurement exercise has an answer and it is a null result. An advisory engagement structurally cannot return nothing — there is always a recommendation.
- 03Ask whether benchmarks appear in the output. Not a criticism: benchmarks are useful and they are a different epistemic object from a measurement of your business.
- 04Ask who is in your systems and for how long. If the answer is nobody, you are buying analysis of what you tell them rather than of what is there.
- 05Ask whether another firm could execute the roadmap. A plan you cannot take elsewhere is a dependency dressed as a deliverable.
The audit-firm comparison, which is closer
Operational diligence has more in common with an audit than with strategy work, and the comparison is instructive. Both measure rather than advise, both name their evidence, both can return a clean result. The difference is that an audit is testing compliance against a standard, and this is testing conversion against the company’s own potential — so there is no external standard, only the company’s own fast-response population as the counterfactual.
That is also why the recoverability haircut matters so much and why a stated one is a mark of seriousness. An audit either finds a misstatement or does not. A leakage figure is an estimate of what could be recovered, and an estimate without an explicit haircut is implicitly claiming that every lost enquiry was winnable, which nobody believes and which invalidates the rest of the report.
When you need both, and in which order
Measure first, almost always. A leakage figure is cheap, fast and it changes the strategic conversation: knowing that $3M a year is leaking out of the existing funnel is materially relevant to whether the answer is a new market or a fixed operation. The reverse sequence — strategy first, then measurement — routinely produces a strategy that assumes the operation converts better than it does.
The exception is a genuine inflection: a pending acquisition, a new product line, an imminent change of model. There, the operation you would measure is about to stop existing, and measuring it carefully is a way of answering a question that will be obsolete by the time the answer arrives.