How to take real cost out of an IT estate without leaving the organisation exposed in twelve months' time.
Cost optimisation is one of the most popular reasons organisations engage external advisory. It is also one of the most common ways organisations damage themselves in ways they do not notice until it is too late. The savings are visible. The lost capability is invisible — until a project fails, a security incident happens, or a regulator asks an awkward question.
This article describes how to take real cost out of an IT estate without leaving the organisation exposed. It draws on cost optimisation engagements we have led or reviewed across financial services, manufacturing, public sector and retail.
The most common cost optimisation methodology is broken before it begins. An executive decides that IT spend needs to come down by a percentage. The percentage is set externally — by a board, by a budget cycle, by a competitor benchmark. The target becomes the brief. The brief becomes the scope. The cost optimisation programme is designed to deliver the number, not to make the estate healthier.
The right starting point is the cost base itself. What is the IT estate costing, by category, by capability, by business outcome? What is genuinely essential to the operating model of the business? What is "nice to have" that has accreted over the years? What is actively harmful? Until the executive team has a clear view of the base, the target is meaningless. A target without a base is a wish.
In our experience every IT cost falls into one of three categories, and each category requires a different conversation.
The most expensive cost optimisation programmes are the ones that succeed. The savings appear on the spreadsheet. The lost capability does not, until much later.
Before any discretionary or historical cost is removed, we require the executive team to map the capabilities the organisation depends on. Capability mapping is not architecture. It is not a process model. It is the explicit, business-owned description of what the organisation needs to be able to do, day to day, in order to serve its customers and meet its obligations.
Capability mapping sounds bureaucratic. In practice it is the most powerful defence against accidental capability loss. The conversation moves from "this is expensive, can we cut it" to "this capability costs this much; here is what we lose if we remove it; here is the alternative." Most of the time the alternative is acceptable. Sometimes it is not. The decision becomes a conscious trade-off rather than an accidental one.
Vendor renegotiation is often the single largest source of savings in a cost optimisation programme. It is also the area where organisations are most likely to leave money on the table because of the asymmetry of expertise between the client and the vendor.
The defence is to approach renegotiation as a discipline rather than as a conversation. The discipline has three parts. First, understand what you are actually buying — workload by workload, unit by unit, not aggregated. Second, understand what comparable vendors charge for equivalent capability. Third, be prepared to walk away — even if the walk-away cost is high, the cost of a bad renegotiation is usually higher.
Shared service centres, managed service providers, internal shared platforms — all of these arrangements promise cost reduction through consolidation. Some deliver. Many do not. The reason is usually that the consolidation is pursued without the underlying process redesign that would have made it work. The result is a shared service centre that runs at higher cost than the disaggregated services it replaced, with less agility and weaker accountability.
The honest question to ask before any consolidation is: what would this look like if we redesigned the underlying process first? If the answer to that question is materially different from the consolidation proposal, the consolidation is probably premature.
Capability protection sounds like an oxymoron in a cost optimisation programme. It is not. The most successful cost optimisation programmes we have led have been the ones where the executive team explicitly listed the capabilities the organisation could not afford to lose, and used that list as a constraint on every cost reduction proposal.
This sounds obvious. It is surprisingly rare. Most cost optimisation programmes are designed around the savings target, with capability protection as an afterthought. The right order is the reverse. The capabilities that must be preserved define the constraint. The savings are then found within that constraint.
A successful cost optimisation programme delivers savings that are durable, capability that is preserved, and an executive team that understands which trade-offs were made. A successful programme is one the organisation can defend two years later when the savings have been absorbed and the consequences have emerged.
An unsuccessful cost optimisation programme delivers short-term savings that look impressive, capability that has been quietly damaged, and an executive team that has lost the institutional knowledge to recognise what has been lost. We have been asked to lead the recovery from both kinds of programmes. The unsuccessful ones are much harder to recover from.
Cost optimisation is one of the most valuable things independent advisory can help an organisation with — and one of the most dangerous when done badly. The organisations that get it right are the ones that treat capability as the constraint and cost as the outcome, not the other way around. If you are planning a cost optimisation programme and would value a sounding board on methodology or trade-offs, we are happy to talk.