IT Financial Management — framework & methodology

The IT Budget Lifecycle: framework before the tool

Why an IT budget needs more than one reading, and the frameworks (ITFM, TBM Taxonomy v4.0, Run/Grow/Transform) that the simulator is built on.

Why an IT budget needs more than one reading

The same pool of spend, three legitimately different questions.

IT Financial Management (ITFM) treats the budget as a conversation, not a spreadsheet: the same pool of spend has to satisfy a board asking whether the number is under control, a CFO (Chief Financial Officer) asking whether it's the right kind of spend, and a CIO (Chief Information Officer) asking what it's actually buying, tower by tower. Technology Business Management (TBM) — the discipline's most widely adopted taxonomy — formalises this by tracing every dollar through cost pools (labour, hardware, software, external services) into IT towers (applications, infrastructure, security and so on) and finally into the business capabilities they fund.

TBM's own taxonomy also draws a sharper line than most internal budgets do: business units are split into revenue-generating units (which run their own P&L, or Profit & Loss) and non-revenue-generating support units. Global IT is one of the latter, alongside other central functions such as HR, Marketing and Finance — not a label for the whole group, and its cost-pool/tower detail (below) is Global IT's own budget alone, never a wider or company-wide total.

Global IT spend crossed an estimated $6.37 trillion in 2026, up 14.2% year-on-year, and Gartner's own 2026 CIO research found 52% of CIOs naming cost reduction an increasingly important priority over the next two years — even as budgets grow. That tension, cut costs and keep funding growth, is exactly why Gartner frames cost optimisation as a discipline rather than an event: assess and prove the baseline, align spend to reinvestment, then mature it into a standing capability, rather than a one-off exercise that lapses the moment the pressure eases.

General Ledger Finance's raw spend data 9 TBM Cost Pools Labour, hardware, software... "what kind of cost" 11 IT Towers Application, Network, Security... "what it funds" Global IT's budget One figure, one department — used everywhere in the simulator Other Central Functions & Business Units CAPEX/OPEX only — no cost pool or tower breakdown tracked

Every dollar starts in the same General Ledger. Only Global IT's spend is classified further, by cost pool and tower — that's a scoping choice most organisations make in practice, not a TBM rule.

The IT budget lifecycle

Plan Build the budget Track actuals Analyse variance Reforecast Report

The simulator sits at the last step. It doesn't build a budget from scratch — it takes a completed one (yours or the sample) and re-projects it through the three views that matter once the numbers exist: is it in control, is it the right shape of spend, and what is it actually funding.

Three frameworks doing the real work underneath

TBM cost taxonomy

Every dollar in Global IT's own budget — the IT department alone, not other central functions — is traced from a cost pool (9 standard TBM pools: internal labour, external labour, outside services, hardware, software, facilities & power, telecom, other, internal services) into an IT tower (11 standard towers) — two alternate lenses on the same Global IT budget, reconciled to the same total.

Revenue vs. non-revenue business units

TBM's own Business Unit layer splits into units that maintain their own P&L (revenue-generating) and units that exist to support them (non-revenue-generating). Global IT is one such unit, shown separately from other central functions like HR, Marketing and Finance. Consumption and cost logic run one way: support funds delivery, not the reverse.

Run / Grow / Transform

The standard split for judging portfolio balance: spend that keeps the lights on, spend that expands existing capability, and spend that changes the business. A commonly cited industry range puts Run at roughly 60–80% of total spend.

Why three lenses

Same numbers. Three legitimately different questions, asked by three people who each need a different answer.

One dataset this simulator's numbers Board / CXO "Are we in control of the number?" CFO "Is it the right kind of spend?" CIO "What's it actually buying, tower by tower?" Total, variance, Global IT vs. Business Units Cost pools, CAPEX/OPEX, Run/Grow/Transform IT towers, planned vs. actual, by owner

Same underlying numbers, sliced three ways. None of the three is "more correct" — the discipline is keeping all three honestly derived from one dataset, not three separately-massaged ones.

Lens one

Board / CXO

Answers: "Are we in control of the number, and is it moving the right way?" Cares about the total, the split between Global IT and the revenue-generating business units, and whether variance is improving or worsening.

  • Headline totals and utilisation
  • CAPEX and OPEX by business area, quarter-phased
  • Global IT vs. Business Units, side by side

Lens two

CFO

Answers: "Where is the money going, and is it the right kind of spend?" Cares about Global IT's own composition — the nine TBM cost pools — and whether the portfolio is weighted towards running or building the business.

  • Global IT spend by TBM cost pool
  • Run / Grow / Transform split
  • Tech spend as a share of revenue, benchmarked

Lens three

CIO

Answers: "What's actually consuming the budget, tower by tower?" Cares about operational detail — the 11 standard TBM IT towers within Global IT — which are over plan, and which business area is driving demand.

  • Global IT spend by IT tower, planned vs actual
  • Business-area demand, full detail
  • Towers currently over plan, flagged

A board that only sees tower-level detail drowns in noise it can't act on; a CIO who only sees the headline number can't run the department. Each lens is right for its audience, not a simplification of the "real" one.

Ready to see it in numbers?

Open the Simulator →