The Maturity of an Outsourcing Contract: Five Levels, One Range of Loss

Nov 11, 2026 | Sourcing, Vendor Management

La madurez de un contrato de outsourcing: cinco niveles, un rango de pérdida
The health of an outsourcing contract can be measured. The five maturity levels, the seven dimensions through which value leaks and how to move from one level to the next.

Few conversations in technology leadership are as misleading as the one that starts with “our outsourcing contract is going well”. In thirty years reviewing contracts from the client’s side, I have learned that this phrase almost always means nobody is looking closely enough. And what nobody looks at closely gets paid for.

The good news is that the health of an outsourcing contract is not a matter of intuition: it can be measured. According to outsourcing market studies, between 9% and 20% of a contract’s annual value is lost after signing, silently and, most importantly, recoverably. The difference between losing 3% and losing 20% has a name: maturity. This guide explains the five maturity levels of an outsourcing contract, the seven dimensions through which value leaks, and how to move from one level to the next. For the cost of each dimension, see Value Leakage in IT contracts.

What is outsourcing contract maturity?

Maturity does not describe how old the contract is or how good the vendor is. It describes the client organization’s ability to govern the relationship: measure what matters, claim what it is owed and adjust the agreement as the business and technology change. A mature contract is not one without problems; it is one where problems are detected and corrected before they turn into leakage.

The idea is not new. Recognized governance and capability frameworks, such as COBIT (ISACA), Carnegie Mellon’s eSCM-CL , designed specifically for client-side sourcing capability, and the contract management maturity models of WorldCC , converge on the same five-level structure. What follows adapts that consensus to the concrete reality of an IT outsourcing contract.

The five maturity levels

From lowest to highest, each level describes how the contract behaves, and how much value leakage it corresponds to, based on the ranges the industry associates with each degree of maturity.

  • Level 1 · Reactive (12–20% leakage). The contract was signed, filed and bills itself. Nobody watches SLAs, capacity or scope. All seven leakage dimensions are open.
  • Level 2 · Repeatable (8–12%). There is reporting, but it is the vendor’s: green, technical, not translated into business terms. Invoices are reviewed, not results.
  • Level 3 · Defined (5–8%). There is an active governance function that claims the obvious: penalties, adjusting capacity to real consumption, renegotiating scale.
  • Level 4 · Managed (3–5%). Prices follow the market through benchmarking; the model pays for outcomes; exit clauses are negotiated.
  • Level 5 · Optimized (less than 3%). The contract captures the productivity of automation: when the vendor automates, the savings are passed on or shared.

Levels 1 to 3 are defensive: stop losing the obvious. Levels 4 and 5 are offensive: capture value proactively. The jump from 3 to 4 is not a technical change but a change of mindset, from policing the vendor to governing the relationship. To be candid: none of these levels requires an outside advisor. Many organizations reach Level 4 on their own. The value of an outside view is not “raising the level” but shortening the path and seeing the blind spots the green dashboard hides. From Level 4 upward, governance means looking past the Watermelon Effect of green dashboards and capturing the AI Dividend instead of leaving it with the vendor.

The seven dimensions of value leakage

A contract does not mature evenly. It can be at Level 4 in one dimension and at Level 1 in another. That is why it helps to understand each one separately: they are the seven fronts through which value leaks.

1 · Unadjusted scope

This is the leakage that happens when service volume grows but the unit price does not fall. You contracted a certain scope; over time you consume more (more users, more transactions, more tickets) and keep paying the same rate per unit, without capturing the economies of scale that higher volume should give you.

Warning sign: if the contract has grown in volume but prices per consumption tier were never renegotiated, you are overpaying for every additional unit.

2 · Unused capacity

This is capital tied up in digital inventory that creates no value: licenses assigned to people who have left, infrastructure provisioned for peaks that never come, FTEs contracted for demand that has dropped. You pay for it in full every month, whether you use it or not.

Warning sign: if nobody in your organization can tell you with data what percentage of contracted capacity is actually used, you are almost certainly paying for idle capacity.

3 · Outdated rates

Technology prices fall over time; those in many outsourcing contracts do not. A rate that was competitive at signing now funds the vendor’s historical costs, not its current ones. On top of that, cost-of-living adjustment (COLA) clauses raise the price every year without anyone checking whether it is still at market level.

Warning sign: if your rate has not been compared with the market in the last 12–24 months, you are probably paying prices from another era.

4 · Unenforced SLAs

Every breach penalty that is not claimed is, in practice, a hidden price increase. But the deeper problem is design: many SLAs measure technical availability instead of business outcomes. The vendor meets the indicator while the business suffers. It is the Watermelon Effect: green on the outside, red on the inside.

Warning sign: if, when something really fails, you find out the vendor complied “technically”, your SLAs are measuring the wrong thing.

5 · Paying for effort, not outcomes

When the payment model is based on hours, tickets or people, the vendor earns more the more it works, which means the less efficient it is. The incentive is inverted: solving things quickly and well reduces its billing. The result is a relationship where slowness is quietly rewarded.

Warning sign: ask yourself whether your vendor earns more by being efficient or by working more. If it is the latter, the model works against you.

6 · Automation arbitrage (the AI Dividend)

This is the fastest-growing dimension. The vendor brings AI and automation into the operation it bills you for, sharply cuts its delivery cost, and keeps charging you the same. The productivity gain, the AI dividend, is kept silently by the vendor. You pay for work that now costs a fraction to produce.

Warning sign: if your vendor automated half of the work it bills you for tomorrow, would you find out, and would anything change in what you pay? If the answer is no, this arbitrage is already happening.

7 · The exit trap

It is not a direct leak, but the loss of the negotiating power that holds up all the others. When leaving the vendor costs more than tolerating inefficiency (because of rigid clauses, proprietary platforms or lack of data portability), the vendor controls the relationship. And a vendor without competitive pressure has little reason to give you value.

Warning sign: if this vendor failed you seriously tomorrow, could you leave in an orderly way, or are you tied down by the cost of leaving?

The AI Dividend: the fastest-growing front

Of the seven dimensions, three (outdated rates, paying for effort and automation arbitrage) account for more than half of all value leakage in the contracts I have assessed. And all three point to the same underlying phenomenon: the automation the vendor is already introducing into the operation.

Most vendors today automate the work they bill. Automation creates real savings, and the underlying question is who keeps them. In a Level 4 or lower contract, the vendor keeps them silently. I will not present this as simple: it is the hardest of the five jumps, because no vendor gives up without resistance the margin that automation hands it. It is won not at the renegotiation table through willpower, but with clauses built into the contract design: periodic benchmarking, prices tied to outcome units and review mechanisms when the way the service is produced changes.

When the vendor automates and you pay the same, the efficiency did not disappear: it changed owners.

How to move up a level

Placing the contract on the scale is only the assessment. The next question is how to move forward. Each jump has concrete levers:

From Level 1–2 to Level 3 (from reactive to defined)

The foundational jump. It requires creating a governance function, even if it is one person with dedicated time, that does three things: read and summarize the contract’s real obligations, set up systematic penalty claims, and review contracted capacity against real consumption. This closes the most visible leakage and, almost always, the one with the fastest return.

From Level 3 to Level 4 (from defensive to offensive)

The change of mindset. It means benchmarking rates against the market, moving the payment model from effort to outcomes, and negotiating exit and reversibility clauses that give negotiating power back to the client. It stops being about “not losing” and starts being about “capturing”.

From Level 4 to Level 5 (capturing the AI Dividend)

The front with the highest return today. It requires clauses that explicitly define what happens to the savings when the vendor automates, and a pricing model tied to the autonomy with which the service is delivered, not to the hours it takes. It is the hardest and the most valuable.

A real case, from the scale to the result

A contract of about 20 million dollars a year was losing close to 9.25% of its value: barely Level 2 of 5. Its radar, however, was not flat: it was particularly weak in the SLA dimension. The dashboard showed 99.9% availability, and yet the business lost money at every month-end close, because the 0.1% of failures always happened during the accounting close, when all users connected at once.

The intervention was not to negotiate harder but to redesign what was measured: from “server uptime” to “concurrent users without degradation during month-end close”. The vendor adjusted its architecture within 60 days and the problem disappeared. In that single dimension, the contract went from Level 2 to Level 4, and the full journey, dimension by dimension, meant recovering more than half of the leakage without renegotiating the contract from scratch.

What level is your contract at?

Your contract does not have one level: it has seven. Each dimension matures separately, which is why the assessment does not return a number but a radar that shows where the contract is solid and where value leaks. We have prepared a free 5-minute self-assessment that places your contract on the scale and gives you your maturity radar by dimension, with the estimated leakage range for your level. To put a dollar figure on it, use the Value Leakage Calculator.

If the result exposes significant leakage, the next step is a 30-minute assessment session, at no cost and with no commitment, that estimates your contract’s exact figure and the recovery levers available for its phase. You can take the self-assessment here.

Frequently asked questions

What is value leakage in an outsourcing contract?

It is the share of the contract’s value lost after signing because of immature management: unclaimed penalties, capacity paid for and not used, outdated rates, automation savings kept by the vendor, among others. According to outsourcing market studies, it ranges from 9% to 20% of the contract’s annual value.

How do I know what maturity level my contract is at?

You can place it with a self-assessment that evaluates the seven leakage dimensions and translates them into one of five levels, from Reactive to Optimized. A quick test: if your team cannot answer in under ten minutes what the vendor is obliged to deliver, in what form and by when, the contract is usually at the low end of the scale.

How much value can be recovered?

It depends on the starting level. A contract at Level 1 or 2 (with 8–20% leakage) that moves up to Level 4 can recover most of that loss, usually without renegotiating the contract from scratch, just by managing it with more maturity.

What is the AI Dividend?

It is the productivity saving created by the automation the vendor introduces into the operation it bills you for. The key question is who captures it: in immature contracts the vendor keeps it; in mature contracts, that saving is passed on to or shared with the client.

Do I need an outside advisor to move up a level?

Not necessarily. Many organizations reach Level 4 with internal discipline and a good vendor management team. The value of an outside, independent view is not “raising the level” but shortening the path and revealing the blind spots the vendor’s green dashboard hides.

Doesn’t better contract governance cost money?

Yes: it requires people, tracking tools and management time. But that cost is usually a fraction of the leakage it prevents. When a contract loses 9% of its value and the governance to recover it costs a tenth of that, the investment pays for itself.

 

Is your IT contract leaking value right now?

We run a 30-minute Governance Maturity Assessment to identify your critical leakage points and quantify the value that is being left on the table today.

No cost. No commitment. Just evidence.

→ Book a free assessment

 

About the author

William D. López is an independent IT consultant with more than 30 years of experience negotiating and governing technology contracts in Latin America. Founder of IT Experts Consultoría, he has led optimization processes in more than 8 countries with cost reductions of 10% to 35%. He publishes weekly analyses on Value Leakage, strategic sourcing and AI for CFOs and CIOs on LinkedIn.

Consultoría de TI

¿Le interesa aplicar esto en su empresa? Conozca nuestros servicios:

CONTENIDO SEMANAL

¿Le resultó útil este artículo?

En LinkedIn publico semanalmente contenido sobre optimización de contratos de TI, Value Leakage y estrategias de abastecimiento para CFOs y CIOs en América Latina.

¿Lo que acaba de leer le genera preguntas sobre sus contratos de TI?
Conversemos 30 minutos. Sin costo. Sin compromiso.

Contenido Relacionado

Subscríbete a nuestra lista de Publicaciones

Subscríbete a nuestra lista de Publicaciones

Únete a nuestra lista de correo para recibir las últimas noticias y actualizaciones de nuestro equipo.

¡Te has suscrito exitosamente!

WhatsApp chat