From Cost Cutting to a Framework
An IT cost optimization framework exists to make savings repeatable. One-off cost cutting produces a number once and then erodes; a framework produces a standing capability that finds and captures savings every cycle. This guide is the operating model that sits beneath the strategy in our enterprise IT cost optimization pillar — where the pillar explains what to do, this explains how to run it as a programme.
A practical 2026 framework has three moving parts: a classification scheme to decide where spend belongs, a value model to connect cost to outcomes, and an execution engine to capture savings continuously. Each maps to a well-established discipline — Run/Grow/Transform, Technology Business Management (TBM), and FinOps — and the three are designed to interlock.
Classify Every Dollar: Run/Grow/Transform
The first move is to classify every dollar of IT spend by strategic purpose. Run is the cost of keeping existing systems operational — infrastructure, licence renewals, the service desk. Grow is investment in scaling existing capabilities. Transform is strategic investment in new technology and business capability. Most enterprises sit at 60–70% Run and 30–40% Grow plus Transform, and the central aim of optimisation is to shrink Run as a share so more can be redirected into Grow and Transform without raising the total.
This classification is what keeps cost work honest. A cut to Run that funds Transform is reallocation toward growth; a cut to Transform to protect Run is mortgaging the future to defend legacy. Licence renewals — a large Run component — are exactly where independent negotiation shrinks Run without touching capability, which is why this framework and our contract work are two halves of the same programme.
TBM: Connecting Spend to Outcomes
Classification tells you where spend sits; TBM tells you what it produces. Technology Business Management is a value discipline that allocates cost from raw spend through to business outcomes, giving finance, IT, and the business one shared view of cost, consumption, ownership, and performance. Without it, optimisation decisions are made on cost alone — and cost alone cannot distinguish the expensive system that drives revenue from the cheap one that drives nothing.
TBM depends on the visibility layer described in the pillar. The data foundation comes from IT spend analytics, and the value model only works once the estate is fully mapped — including the shadow purchases covered in our guide to shadow IT licensing risks. Build the model once, and every subsequent investment trade-off is made against outcomes rather than line items.
FinOps tells you where the money is being wasted. TBM tells you what the recovered money should fund. Run one without the other and you either cut blindly or measure endlessly.
The FinOps Quick-Win Stack
Execution begins with the quick wins, because demonstrating stewardship early buys the credibility to do the harder structural work. Cloud is the richest seam: around 30–35% of cloud spend is wasted on overprovisioning and idle resources, and teams in the FinOps "Run" maturity phase achieve average reductions of 20–30%, many realising a 30% cut within six weeks. The moves stack.
| Quick Win | Typical Saving | Effort |
|---|---|---|
| Reserved instances / savings plans | 30–72% off on-demand | Low (commitment) |
| Right-sizing instances | 15–25% | Low–Medium |
| Schedule non-production | 10–20% | Low |
| Eliminate idle resources | Recovers ~30–35% waste | Low |
An Azure one-year reservation saves roughly 30–40% and a three-year reservation 55–72%, with leading teams targeting 60–80% commitment coverage of steady-state workloads. The software equivalent of these moves is right-sizing licences and editions, covered in our guide to right-sizing enterprise software, and reclaiming unused seats per our licence rationalisation guide.
Making It Continuous
The framework only delivers if it runs continuously rather than as an annual project. The 2026 best practice is to run TBM and FinOps together on a shared operating model where cost, usage, ownership, forecast, unit economics, and outcomes all live in one decision flow — FinOps finding the waste, TBM steering the reinvestment. The organisational signal is clear: 78% of FinOps practices now report into the CTO or CIO, making cost a standing engineering and architecture concern rather than a periodic finance review. The harder structural savings — contract consolidation and ELA restructuring — are where this programme connects to negotiation, detailed in our contract consolidation playbook.
The 90-Day Rollout
Stand the framework up in three phases. Days 1–30: establish the baseline and run external benchmarks, classifying spend Run/Grow/Transform and instrumenting the FinOps data feeds. Days 31–60: capture the quick wins — commitments, right-sizing, idle-resource elimination — and publish the first savings to build credibility. Days 61–90: stand up the TBM value model and the governance that makes the cuts stick, sequencing service-affecting decisions last in line with our guide to cutting costs without cutting capability. To accelerate the rollout, or to bring independent benchmarks to the baseline, request a confidential briefing, or download our CIO contract governance white paper.