Keeping-the-Lights-On vs Innovation Spend

Part 4 followed the maintenance drain through one engineering team. This part pulls back to the whole budget, where the same dynamic has a name every CIO and CFO already uses: keeping the lights on versus innovation. It is the most important ratio in enterprise IT, and the one a locked-in legacy estate quietly pushes in the wrong direction year after year — usually without anyone deciding to let it.

This is the part for the economic buyer, because the keep-the-lights-on ratio is the form in which the entire series finally lands on a budget. Lock-in raises the switching cost; maintenance collects it; and the ratio is where that collection shows up as the shape of your spending — how much of it points at the future, and how much at standing still.

The ratio that matters more than the budget

Most budget conversations fixate on the total: is IT spend going up or down, and by how much. The more revealing number is the split — what share of that spend runs existing systems versus what share builds new capability. The industry calls these “run-the-business” and “change-the-business,” or more bluntly, keeping the lights on versus innovation.

The split matters more than the total because it decides what the money can do. Two organizations with identical IT budgets can have completely different futures depending on the ratio: one spending most of its budget on the new, the other spending most of it standing still. A bigger budget tilted toward maintenance buys less future than a smaller one tilted toward change. The headline figure tells you how much you spend. The ratio tells you what you get for it.

What the ratio actually is

The most credible public anchor for this comes from Deloitte’s Global CIO surveys, which over several years put run-the-business spend at roughly 55–57% of the enterprise IT budget — the majority of most budgets goes to keeping existing systems operating rather than building anything new. (You may see a “70%” version of this figure attributed to Gartner; it is widely repeated but not traceable to a primary report, so the defensible number to cite is the Deloitte one, or the plain statement that the majority of IT budgets goes to running what already exists.)

Read that for what it says. Before a single new initiative is funded, more than half the budget is already committed to keeping yesterday running. Innovation does not compete on equal footing with maintenance; it competes for the minority share that maintenance leaves behind. And for an organization with a heavy, locked-in legacy estate, the run-the-business share runs higher than the survey average, because the maintenance buckets from Part 3 are larger and climbing. The reversal is uncomfortable and worth stating plainly: for most enterprises, the default setting of the IT budget is the past.

Why maintenance always wins the budget fight

The ratio does not drift toward maintenance by accident. It drifts because of an asymmetry in how the two kinds of spend are treated. Maintenance is non-negotiable: the system must run, so its costs are funded first, as a floor beneath the budget. Innovation is discretionary: it is what you do with whatever sits above the floor. When the two compete, maintenance wins by default, every cycle, because “the system has to keep running” is an argument innovation can never make about itself.

Lock-in turns this asymmetry into a ratchet. A locked-in system cannot be left, so its maintenance is permanently in the non-negotiable category — and as the system ages, that category grows. Rising licensing on capacity-based contracts, climbing specialist-labor costs as skills thin, an expanding integration tax, a swelling risk premium: each pushes the maintenance floor up, and every inch the floor rises is an inch the innovation ceiling falls. The ratio worsens on its own, with no one ever choosing to spend less on the future. They simply find, each year, that there is less of the future left to fund. This is the budget-level face of the cost of inaction: the ratio quietly tilting while everyone attends to the year’s emergencies.

You can’t cut your way out

The instinct when innovation gets squeezed is to attack the maintenance line — efficiency drives, vendor renegotiation, doing more with less. These help at the margin and change nothing structural, because the maintenance is non-negotiable for exactly the reason that makes it hard to cut: the system has to run. You cannot decide to stop maintaining a system you cannot leave. Cutting maintenance on a locked-in system is cutting the floor you are standing on.

The only durable way to shift the ratio is to lower what running the system costs — and that means changing the system, not the budget. When you modernize the workloads whose maintenance dominates the run-the-business side, the floor under your budget falls, and the space that opens up falls automatically to innovation, because innovation is whatever sits above the floor. You do not redirect money the maintenance bill has already claimed; you stop the maintenance bill from claiming it. This is why modernization is best argued to a CFO not as a cost but as a ratio intervention — the move that changes how much of every future dollar can point at the future. We make that argument in full in building a modernization business case; the ratio is the number it turns on.

Where the ratio argument stops

Three cautions keep this from becoming a slogan. First, not all run-the-business spend is waste to be eliminated — a healthy organization will always spend real money keeping systems running, and a ratio tilted toward maintenance is not automatically a problem. The question is whether the maintenance share is higher than it needs to be because of lock-in and aging, and whether it is climbing. A stable, reasonable ratio on a well-run estate needs no intervention.

Second, the Deloitte figure is an industry benchmark, not your number. It establishes that the majority of IT budgets goes to running existing systems in general; it does not tell you your split. Measure your own — the discipline from Part 4 applies at the budget level too — and present that, dated and with its assumptions, as the figure the case rests on.

Third, lowering the maintenance floor takes investment before it returns budget, and on the wrong system it may never pay back. The ratio argument is strongest where the maintenance being displaced is large, climbing, and attached to systems the business needs to keep. It is not a reason to modernize a quiet, cheap, stable system whose maintenance share is already small. The goal is a healthier ratio, not modernization for its own sake.

Where this leads

We have traced lock-in from a switching cost, through the maintenance bill, to the budget ratio that decides what your business can build. The diagnosis is complete. The rest of the series turns to the cure — and a cure begins with knowing what a system that doesn’t tilt the ratio looks like. Part 6, Open Standards & Portable Architecture, describes the architectural antidote to lock-in: the design choices that keep the switching cost low by construction, so the next system you build does not become the next system you cannot leave.