When a major programme needs outside help, most boards think they are choosing a firm. They are not. They are choosing a delivery model, and the model decides more about the outcome than the logo on the invoice does.
In the consulting market, team augmentation is the practice of hiring external people to work inside your organisation under your own management, charged by the day, to add capacity you do not currently have. The supplier provides resource. You provide the direction, the plan and the accountability. When the engagement ends, the people leave and what they learned leaves with them.
By contrast, embedded change is a delivery model in which the supplier holds accountability for delivery rather than advising on it, transfers capability into your permanent team while the work is under way, and specifies the conditions of its own exit at the start. Both models are legitimate. They are not interchangeable, and confusing them is expensive, because day rates look comparable and the difference only shows up eighteen months later in whether your organisation can run the thing you paid to build.
The four things you can actually buy
Strip away the brand language and there are four distinct models in this market. Every proposal you receive is one of them, whatever it is called.
| Model | What you are buying | Who is accountable | What you keep afterwards |
|---|---|---|---|
| Advisory | An opinion | Nobody. The report is the deliverable | A document |
| Team augmentation | Capacity, by the day | You. They work to your direction | Nothing, once they leave |
| Managed service or outcome contract | A defined output | The supplier, contractually | The output, plus a dependency |
| Embedded change | Capability, transferred | Shared, with the supplier holding delivery roles | A team that can run it without help |
Each is right for something. Augmentation is right when you know exactly what needs doing, you have the leadership to direct it, and you are simply short of people. That is a real and common situation, and paying a day rate to solve it is sensible.
It is the wrong answer when the problem is that nobody can say with confidence what needs doing, or when the people who could say it have no standing to make it happen. Adding capacity to a programme with a judgement problem makes the programme larger and no more likely to deliver.
Why augmentation quietly fails on troubled programmes
Three mechanics, all of them structural rather than anybody's fault.
The supplier has no mandate to disagree with you. Augmented resource works to your direction. If your direction is the thing that is wrong, the model contains nothing that will surface it. People on a day rate, extendable at your discretion, are poorly placed to tell you your plan is undeliverable, and most will not.
The commercial incentive runs the wrong way. Revenue is a function of days billed. Nobody is acting in bad faith, but a model that pays more for longer engagement and nothing for early exit will not naturally produce early exit. Over a long programme this compounds quietly.
Capability leaves when the invoice stops. Knowledge accumulates in the contractors, not in your team, because nothing in the arrangement requires otherwise. Two years later the people who understand the system you depend on are working somewhere else, and you are re-procuring the same capacity to maintain what you already own.
The CFO test: what each model does to your cost base
Four questions worth asking before signing anything, in roughly this order.
- What is the total cost over the full life, not the day rate? A lower day rate over a longer engagement is not a saving. Model the whole thing, including the maintenance years after go-live.
- What happens to run costs when the engagement ends? If the answer is a support contract with the same supplier, you have not bought delivery, you have bought an annuity and you are the one paying it.
- What proportion of this spend can be capitalised, and does the model put that at risk? Capacity spent on rework and re-planning is harder to defend as capitalisable than spend against a stable delivery plan, and auditors increasingly ask.
- What is the exit cost? Not the notice period. The cost of the capability gap on the day they stop, which is the number most business cases omit entirely.
These four questions separate the models faster than any comparison of rate cards, because they price the thing rate cards hide.
What embedded change commits to
The Embedded Change Model™ is our answer to the same problem, and it rests on a commitment the other three models do not make: the engagement is designed to end, and the exit is specified in week one.
In practice that means three things.
Related Resource
Find out more our Embedded Change Model™
intology.co
We hold delivery roles, not advisory ones. Where a programme needs someone to own delivery while the permanent structure is rebuilt, we take that accountability. Advisory-only intervention rarely works on a difficult programme, because the hard part is not knowing what to do, it is having the standing to make it happen.
Capability transfers as the work proceeds, not at the end. Knowledge transfer scheduled for the final phase is knowledge transfer that gets cut when the final phase is under pressure, which it always is. It has to be continuous or it does not happen.
We are independent by construction. Intology does not implement software, does not resell licences and takes no commission from any systems integrator or vendor. There is no downstream revenue that a longer engagement protects, which is what makes an honest recommendation to stop possible. We apply the same logic when advising whether to recover or write off a failing programme.
The private equity lens: dependency is a valuation problem
For a sponsor, the choice of delivery model is not an operational detail, it is a diligence exposure.
A portfolio company that cannot run its own core systems without a standing contractor bench has a cost line a buyer will normalise, a key-person risk a buyer will price, and a management team whose capability a buyer will question. None of that appears in the model at the point the day rate is agreed. All of it appears in the data room.
The test a sponsor should apply is simple: if the external team left tomorrow, what breaks? If the honest answer is "quite a lot", the business has been buying capacity for years and calling it transformation. That sits alongside the wider technology levers in private equity value creation, and it is usually the cheapest thing to fix early and the most expensive to discover late.
How to tell a real embedded model from a relabelled one
"Embedded" has become a popular word, and some of what is sold under it is augmentation with a better cover page. Five questions will separate them, and they are worth asking of us as readily as of anyone else.
- What is the exit criterion, and when was it written? A genuine embedded engagement can tell you in week one what has to be true for it to end. If exit is vague or deferred, you are buying capacity.
- Who holds the delivery role? If the supplier advises and your people deliver, that is advisory. If the supplier delivers and your people watch, that is outsourcing. Embedded means the supplier holds the role while your successor is built into it.
- How does the supplier fare commercially if the engagement ends early? Badly, in revenue terms. The question is whether the model treats that as a success or a loss, and the answer is usually visible in how the commercials are structured.
- What does the supplier sell downstream? Licences, implementation, managed service. Any of these means a commercial reason to prefer some recommendations over others.
- Who actually turns up? Ask whether the people in the pitch are the people on the engagement. Pyramid models cannot answer this honestly.
A firm with a real model will answer all five without hesitating. A firm that has adopted the vocabulary will struggle on at least three, and usually on the first.
Frequently asked questions
What is the difference between team augmentation and embedded consulting?
Augmentation supplies people who work under your direction to add capacity, charged by the day, and the capability leaves when the engagement ends. Embedded consulting supplies people who hold delivery accountability and transfer capability to your team as the work proceeds, with the exit specified at the start. One solves a shortage of hands; the other solves a shortage of capability and accountability.
When is augmentation the right choice?
When you know precisely what needs doing, you have the internal leadership to direct it, and you are simply short of people to do it. It is a sound and cost-effective answer to a capacity problem. It is the wrong instrument when the programme's direction itself is in doubt.
How should a CFO compare the models commercially?
Compare total cost across the full life rather than day rates, establish what happens to run costs when the engagement ends, check whether the model puts capitalisation of the spend at risk, and price the capability gap on the day the supplier stops. Day rates are the least informative number in the comparison.
Why does the delivery model matter to a private equity sponsor?
Because dependency is priced at exit. A portfolio company that cannot operate its core systems without a standing external bench carries a cost line a buyer will normalise, a key-person risk a buyer will price, and a question about management capability. The test is what breaks if the external team leaves tomorrow.
How can a buyer tell a genuine embedded model from a relabelled one?
Ask when the exit criterion was written, who holds the delivery role, how the supplier fares commercially if the engagement ends early, what the supplier sells downstream, and whether the people in the pitch are the people on the engagement. A firm with a real model answers all five without hesitation.
Talk to us
If you are comparing proposals and cannot tell which model you are being offered, that is worth half an hour of someone's time before it is worth a signature. Arrange a confidential conversation with a senior Intology consultant, or read how the model applies on programmes already in difficulty.