The complaint appears almost word-for-word across consulting firms of very different sizes and specialisms: "Clients keep pulling us in directions we didn't plan for."
Scope creep, shifting priorities, or sprawling engagements. Most management and IT consultancies treat it as a delivery problem to be managed, usually with change requests, sometimes with stricter SOWs, occasionally with a frank conversation. It works, up to a point. Change request fees recover some of the margin. Tighter contracts slow the bleeding.
But the cycle never breaks. The next engagement creeps too. And the one after that.
Scope creep is rarely just a delivery problem. More often, it is the commercial consequence of how the consulting firm defines, packages, and structures its expertise.
Most consultancies build their engagements around a menu of services. They have a data engineering practice, a transformation practice, an architecture practice, or a change practice. They tell clients what they can do, agree on a generic objective like "enable the digital transformation," and start the work.
The consulting firm has defined capabilities but has not clearly articulated how value is created, sequenced, and measured. What is missing in that setup is a prescription:
No specific outcome.
No defined milestones.
No methodology that says: “Here is the path from the issue to the result, and here is how we know we have arrived.”
That absence is not neutral. It creates a vacuum. And clients - quite reasonably - fill it themselves. Not because they are difficult, but because they have a problem that needs solving and nobody has told them what the path looks like, so they start improvising it in real time.
"Can we also look at this?" "While you're at it, can you check why X is doing Y?" "Can you prioritise tasks 4 and 5?"
Each request is reasonable in isolation. In aggregate, they fragment the engagement.
Most firms account for scope creep in commercial terms: hours lost, margin compressed, and change requests negotiated. Those are real, but they understate the damage.
The deeper cost is structural. Over time, the consulting firm loses the ability to compound expertise, codify delivery knowledge, strengthen pricing confidence, and build scalable commercial leverage across engagements.
Every engagement that goes off-path becomes a bespoke piece of work. Bespoke work cannot be turned into a playbook, used to train juniors, or inform the next proposal. The firm builds the same expertise from scratch on every engagement rather than compounding it across many engagements.
This is the complexity tax: the cumulative drag of a vague proposition felt as bespoke delivery, inefficient proposals, weak IP, and pricing power and value monetisation that struggle to strengthen because every engagement remains too different from the last to create scalable expertise economics.
In our experience (from working with mid-sized and larger firms) the symptoms are predictable:
Utilisation looks fine, but the margin doesn't.
Senior people are stretched across too many half-defined engagements.
The pipeline grows, but each deal is harder to scope than the one before.
New hires take longer to become productive because there is no established way of working to learn from.
None of this looks like a crisis. It looks like consulting. That is what makes it so corrosive.
A 250-person data and analytics consultancy we worked with had what appeared to be a healthy book of business. Fourteen partners. A broad capability menu spanning data strategy, engineering, advanced analytics, and AI. Roughly £45m in revenue, and growing.
But the same patterns kept showing up. Win rates around 25%. Average deal sizes flat. Almost every engagement spawned at least one change request, and roughly a third sprawled badly enough that the partner running them had to step back in to renegotiate scope. Margin had been sliding two points a year for three years.
When we mapped their last forty engagements against the original SOW, the pattern was unambiguous: the engagements that creeped were the ones sold as capability bundles rather than as a prescribed path to a defined outcome - often as bids against client-shaped RFPs where proper diagnosis hadn’t been scoped and budgeted correctly (stuff for a different post, for sure!).
Eighteen months after redesigning around a sharper consulting proposition - one specific issue, one defined client success journey, modules (incl. for diagnosis!) and full programs replacing “raw” services - the numbers told a different story. Win rates climbed past 40%. Average deal sizes moved up by almost half (!). And change requests dropped sharply, not because clients stopped asking, but because the firm had something concrete to point to in its answers. And the engagements that continue to sprawl? Tended to sprawl in the same predictable ways, which meant the firm could finally standardize its responses.
The capability menu had not changed much. What changed was the order of operations: the proposition came first, and the services followed it. The consulting firm stopped commercialising broad capabilities and started commercialising a designed path to client value.
Recommended reading: Every Consulting Firm Needs a Discovery Service
The phrase "proposition-led" can sound abstract. In practice, it means one specific shift in design sequence. In practice, proposition-led consulting is a way of structuring expertise commercially before services are defined operationally.
Capability-led firms design their service menu first and then try to wrap a proposition around it. Proposition-led firms do the opposite. Before defining a single service, they work through a sequence of questions:
What specific issue are we resolving, for whom, and in what specific context?
What does success look like at the end of the engagement, in outcome language that the client would recognise?
What are the milestones between starting and finishing - the recognisable points where progress can be checked?
What needs to be true at each milestone before moving to the next?
What access, decisions, and inputs do we need from the client at each stage?
That sequence produces what we call a client success journey: a staged path from issue to outcome, described as milestones the client recognises, not as delivery phases the firm runs internally.
The journey is the artefact that makes the engagement defensible. When a client asks to add something mid-stream, the firm has a precise reference point: does this request move us toward the next milestone, or sideways from it? The conversation stops being a negotiation about hours and starts being a conversation about outcomes.
Services come after. Each one earns its place by answering a single question: what does the client need in order to reach the next milestone? That tends to produce fewer, more sharply scoped offerings - what we'd call programs rather than services - with defined "done" criteria and prices anchored to outcomes rather than day rates.
This matters far beyond delivery efficiency. Consulting firms that continuously reshape engagements around client-driven scope expansion often remain economically dependent on labour effort, senior intervention, and (costly) bespoke execution. Firms that structure expertise around repeatable client success journeys gradually build stronger pricing power, scalable expertise, reusable IP, and more resilient consulting economics.
The most common objection we hear when we describe this is a commercial one: “If we say no to scope additions, clients will go elsewhere.”
The pattern is reliably the opposite. Clients who hear: "No, that's outside our usual path-to-success, and it will delay your result; here is what our method says to do instead", tend to gain confidence in the consulting firm, not lose it. The firms that say yes to everything end up looking interchangeable with the next vendor. The firms that hold the line on a designed path to success look like specialists.
This is also where capability-led firms most often misread their own market. They believe they are losing deals on price or scope flexibility. In reality, they are losing them because there is no clearly prescribed path from problem to result, and the buyer cannot tell what they are actually buying.
Think about it: Would you trust a doctor who continuously asks you what to check and do next - or would you prefer a specialist who calmly and confidently explains which three things they’ll do next before making a specific decision?
If your firm is worn down by constant change request battles, there is one question worth sitting with:
Does your service design follow your proposition, or does your proposition try to wrap around your services?
If it is the latter, scope creep is not the problem to solve. It is a symptom of a deeper design choice that, until it changes, will keep generating the same pattern, engagement after engagement.
Proposition design is the foundation. Everything that follows - how the firm governs itself, how it goes to market, how it prices, how it scales - depends on getting this part right. It is not about piecing services together. It is about taking clients through milestones of a designed, disciplined client success journey, one that the firm built before the engagement started, not one that the client assembles as they go.
The future advantage in consulting may increasingly belong to firms that commercialise expertise through designed client success journeys, enabling stronger value monetisation, scalable expertise, and less dependence on customised service delivery.
So, perhaps: Time to get more prescriptive?
Interested in receiving all our learnings to build a better consulting firm?
Subscribe to our newsletter.