$250M in Cost Gaps: What Post-Signing Outsourcing Really Looks Like

In 2020 I was tasked with a specific and uncomfortable mandate: find out why IBM's outsourcing contracts were generating substantial cost gaps after signature, and fix the underlying system. Not individual contracts — the system. The gaps were not random. They were structural, and they were recurring.

What I found when I started the analysis was that the cost gaps were not primarily caused by poor delivery. They were caused by the gap between what was priced at deal signature and what was actually required to deliver the contracted service in the operating environment that emerged after signature. That gap — between the priced model and the delivery reality — is the core dynamic that most outsourcing relationships struggle to manage, on both sides of the table.

Where the gaps actually come from

The most common assumption about outsourcing cost gaps is that they come from underpricing — the service provider bids aggressively to win and then discovers the contract is not profitable. That happens. But it was not the primary driver of the gaps I was asked to address.

The more significant drivers were structural:

Scope that was assumed rather than specified. Large outsourcing contracts are complex documents negotiated over months, often with multiple teams on both sides and significant commercial pressure to close. In that environment, assumptions accumulate. The delivery team prices what they understand the scope to be; the client team assumes certain activities are included; the contract language is ambiguous enough to support both interpretations. The gap does not surface until service commencement, when the delivery team starts running the actual operating environment and discovers that the priced model did not account for it accurately.

The environment that exists at transition is not the environment that was assessed during pricing. In a typical large IT outsourcing deal, there is a gap of six to eighteen months between the initial assessment of the client environment and the point at which the service provider takes over delivery. In that period, the client environment changes — applications are added or modified, infrastructure ages, technical debt accumulates. The delivery team inherits a different environment from the one that was priced. If the contract does not have adequate mechanisms for adjusting the commercial model to reflect this, the cost gap is baked in from day one of delivery.

Management system failures that prevent early detection. Cost gaps that are identified at month two of a contract are manageable. Cost gaps that are identified at month eighteen — after they have compounded across multiple service towers, multiple geographies, and multiple client relationships — are crises. A consistent finding in the contracts I reviewed was that the management systems in place were not capable of providing early warning. Data was siloed, reporting was lagged, and the metrics being tracked were the wrong ones to surface financial variance early.

Why clients should care as much as providers

Cost gaps in outsourcing contracts are typically framed as a service provider problem. They are not. They are a relationship problem, and the consequences fall on both sides.

When a service provider is running a contract at a cost gap, the first thing that happens is invisible to the client: the delivery team starts making resource decisions based on financial pressure rather than service quality. The experienced engineers get moved to more profitable contracts. The investment in tooling and automation that was committed in the deal is deferred. The governance meetings become more defensive. None of this is announced. The SLAs may continue to be met — for a time — while the underlying delivery quality degrades.

The second thing that happens is also invisible until it is not: the commercial relationship deteriorates. Contract renegotiations become adversarial. Change requests that should be straightforward become protracted. The client finds that the service provider is technically compliant but not genuinely engaged. The relationship that was sold as a partnership becomes a transaction, and a difficult one.

Clients who understand this dynamic — who recognise that a service provider operating at a significant cost gap is a risk to their own service quality, not just a commercial problem for the provider — are in a position to manage it proactively. Clients who do not understand it tend to discover the problem at a point where the options are limited and expensive.

What fixing it actually required

The corrective programme I led was not primarily a financial exercise. It was a management system redesign. The financial gaps were a symptom; the management system was the root cause.

The three changes that had the most material impact were:

Trusted data repositories with single versions of cost truth. The first finding was that different parts of the organisation had different versions of the cost position on the same contracts. The delivery team had one view; the finance team had another; the client management team had a third. Decisions were being made on incomplete or inconsistent data. Establishing a single trusted data source — and making it non-negotiable that decisions were made from that source — sounds straightforward. In practice it required significant organisational change and, in some cases, difficult conversations about whose data was right.

Leading indicators rather than lagging ones. The management system had been built around lagging financial metrics — monthly cost versus plan, quarterly variance analysis. By the time a gap showed up in these metrics, it had been building for weeks or months. We rebuilt the reporting framework around leading indicators: staffing model versus actuals in week two of a new contract, scope consumption versus forecast in month one, early signals from the transition assessment that suggested the priced environment was not what was delivered. This shifted the conversation from explaining past variance to preventing future variance.

Structural changes to the solutioning process. The permanent fix was upstream of delivery: changing how contracts were priced and what assumptions were documented and validated before signature. This meant investment in better assessment tooling, clearer scope definition standards, and — critically — a governance gate before commercial commitment that required the delivery team to validate the pricing model, not just the deal team. Contracts priced with delivery team sign-off had materially lower cost gaps than contracts priced without it.

What this means if you are on the client side

If you are a CIO or technology leader managing a significant outsourcing relationship, three questions are worth asking regardless of how well the relationship appears to be performing:

First, do you know your service provider's cost position on your contract? Not the headline margin — the actual cost variance against the delivery model they priced. If the answer is no, you are managing the relationship without complete information.

Second, what is the mechanism by which scope changes are assessed and commercially reflected? In most contracts, this mechanism is underused. Change requests are expensive and slow, so delivery teams absorb scope creep rather than raising it. That absorption has a cost, and it accumulates.

Third, how old is the transition assessment on which your contract was priced? If the answer is more than a year, the environment that was priced and the environment being delivered are almost certainly different. Whether that difference is material, and who bears the cost of it, is worth understanding before it becomes a renegotiation conversation.

The outsourcing relationships that work well over a five or ten year term are not the ones where the initial contract was priced perfectly. They are the ones where both sides have the data, the governance, and the commercial honesty to surface problems when they are small and address them before they compound.

← All Articles