How to present IT cost to a CFO on one page

In brief

What a CFO wants to know about technology spend, the TBM views that answer each question, the language to use, and a sample one-page structure to copy.

Steve Elliott

Steve Elliott · · 5 min read


On this page
  1. What does a CFO want to know about IT spend?
  2. Which views answer each question?
  3. What does the one-page structure look like?
  4. How do you explain variance and the P&L effect?
  5. What language should you use and avoid?
  6. What should you prepare before the meeting?
  7. Sources

Give a CFO five answers about technology spend: what you are spending, on what, whether it is going up and why, what you are getting for it, and where it could be cut or moved. Put them on one page, in that order, built on the TBM Taxonomy's Finance View and finished with a decision the CFO can make.

The TBM Council's May 2026 guides for CFOs and CIOs explain which layers of the taxonomy a finance leader relies on. Neither shows what to put in front of a CFO, in what order. This post does, with illustrative numbers you can replace with your own.

What does a CFO want to know about IT spend?

The TBM Council's CFO guide says finance leaders struggle to answer "What are we actually spending?" It also argues that governing the technology budget and tracking variances is no longer enough. Boards expect defensible returns, and CFOs are expected to make strategic trade-offs rather than simply enforce cost controls.

In a Gartner survey of more than 300 CFOs and finance leaders, run in October 2025 and published in February 2026, technology budgets were set to rise in 2026 for 75% of CFOs, and 48% planned increases of 10% or more. A separate Gartner survey of more than 200 CFOs in August 2025 found that 56% ranked enterprise-wide cost optimization targets in their top five priorities for 2026.

So technology spend is growing while the CFO is pressed to show cost under control. In our view, five questions turn that tension into an agenda.

  1. What are we spending? One total, actual and forecast, against budget.
  2. On what? By what was bought and by what it does.
  3. Is it going up, and why? Variance explained by cause, not by account.
  4. What are we getting? Unit costs tied to things the business counts.
  5. Where can we cut or shift? Specific options with amounts and dates.

Which views answer each question?

The TBM Council describes views as lenses on one taxonomy. Its CFO guide says the Finance View focuses mainly on cost pools and resource towers, and that it supports budgeting, planning, variance tracking and chargeback. The CIO guide describes the same view as focused on accounting and budget variance, while the CIO works mainly in the Technology View of towers and solutions.

In our view, the CFO's anchor is the ledger, so start there and move up the layers only as far as the question needs.

CFO questionView or measure that answers itWhere it comes from
What are we spending?Total actual and forecast vs budget, prior yearGeneral ledger, forecast
On what?Cost pools (Staffing, Cloud Services, Software, Hardware) and resource towersFinance View of the TBM Taxonomy
Is it going up, and why?Budget vs actual and forecast variance, by causeVariance analysis
What are we getting?Unit costs against business volumes; solution TCOTBM model, business volume data
Where can we cut or shift?Run vs change split; fixed vs variable; named optionsPortfolio and contract data
What hits the P&L?Capex vs opex, depreciation and amortizationFixed asset register, capitalization records

Two details from the CFO guide help. The cost pool layer separates operating from capital spend, which lets a CFO see how much of the estate is fixed versus variable. And towers are where benchmarking becomes possible, because they let finance compare labor intensity and infrastructure ratios with peers.

The guide frames run versus grow as a trade-off between maintaining legacy systems and funding innovation. It doesn't give a formula for the split, so state your own definition on the page. We use "change" for what the TBM Council calls grow (some models split it into grow and transform).

What does the one-page structure look like?

The numbers are illustrative: take a company with a $118 million technology budget, capital and operating combined. Each block answers one question.

#BlockWhat to showIllustrative content
1HeadlineOne sentence: total, variance, the reason, the askForecast $120.0M vs $118.0M budget (+$2.0M, 1.7%), driven by orders running 18% above plan. We propose cutting $3.0M of run cost next year and moving it to change.
2What we spendActual, forecast, budget, prior yearForecast $120.0M; budget $118.0M; prior year $112.0M (+7.1%)
3On whatTop cost pools, then top towersStaffing $46M; Software $24M; Cloud Services $18M; Hardware $10M; all other $22M
4Why it movedTwo or three variance drivers, by causeCloud +$2.6M, with orders 18% above plan (not all cloud cost moves with volume); contractors -$0.6M from roles converted to employees
5Run vs changeSplit, trend, definition usedRun $84M (70%); change $36M (30%)
6What we getTwo or three unit costs tied to business volumesTotal technology cost per order $3.00, down from $3.40 last year as orders grew faster than cost; cost per employee supported, flat
7P&L effectOpex, capex, and depreciation and amortization (D&A) this year and nextOpex $96M and capex $24M. P&L charge is opex plus D&A: D&A $14M this year, about $17M next as new releases go live
8OptionsWays to cut or shift, each with full-year amount and dateNext year's run reductions: retire a legacy order system, $1.8M (exit by January); consolidate two monitoring contracts, $0.6M at the January renewal; drop unused SaaS licenses, $0.6M at the January renewal. Total $3.0M
9DecisionWhat you are asking the CFO to approveApprove moving the $3.0M from run to change in next year's plan

Why it is built this way, in our view:

  • Lead with the ask. If the CFO reads only one line, it should name the decision.
  • Variance by cause, not by account. "Cloud up $2.6 million because orders ran 18% above plan" is an answer. "Account 6420 over budget" is a question.
  • Unit costs only where the business counts the volume. Cost per order means something to a CFO who already tracks orders; cost per gigabyte stored usually does not.
  • Options that add up to the ask. Each with a full-year amount and date.

The CIO guide recommends structuring budget reviews by fully burdened solutions rather than legacy account groupings. We think the CFO's page should stay anchored in cost pools, with solution TCO as the drill-down behind block 8.

How do you explain variance and the P&L effect?

Explain variance in two layers: full-year forecast versus budget, which the CFO reports upward, then the causes, sorted by whether they track business volume. Cloud spend that rises with orders is a different conversation from a renewal that came in above plan.

Capital spend does not hit the income statement when it is incurred. Under GAAP, capitalized internal-use software is amortized over its estimated useful life once it is ready for its intended use, according to BDO. So this year's capex becomes future amortization. The P&L charge is opex plus D&A, not opex plus capex, and in our view a CFO will want to see that tail before approving more capital.

The capex/opex mix can also move under new rules. ASU 2025-06 changes when capitalization of internal-use software starts, and PKF O'Connor Davies notes it could mean more costs expensed rather than capitalized, with possible pressure on EBITDA-linked covenants. We cover that in ASU 2025-06 and your IT cost model. This is not accounting advice; confirm treatment with your controller and auditor.

What language should you use and avoid?

The CIO guide names the core problem: IT speaks in capabilities and services, while finance speaks in ledger lines like hardware or software. Its answer is to use standard TBM definitions in every technology finance discussion. In our view, a few habits help.

UseAvoidWhy
Dollars, with the period statedPercentages aloneA CFO will ask "of what?"
Forecast vs budget"We're tracking"Forecast is a number the CFO can test
Cost reduction, with the line it comes off"Savings" for avoided increasesLabel cost avoidance as avoidance, or the CFO will look for it in the budget
Employees and contractors, counted separately"Headcount" for bothThey flex differently when demand changes
Business volumes: orders, claims, policiesTechnical volumes: VMs, tickets, storageThe CFO can test business volumes against other reports
"We propose""We need"A proposal invites a decision; a need invites a challenge

The CIO guide also says optimization "is not reactive cost cutting; it is strategic reallocation." That is the framing for the options block.

What should you prepare before the meeting?

  1. Reconcile to the ledger. Your total must match the number finance reports, or the meeting will be about the gap.
  2. Write down your definitions. Run versus change, fixed versus variable and each unit cost need a one-line definition the CFO's team can check.
  3. Agree the volumes with the business owners. If your order count differs from the sales report, the unit cost loses credibility.
  4. Size each option. Amount, timing, one-off cost, owner and risk.

The CFO guide's next steps include agreeing a shared bill of IT, starting with mapping ledger categories to standard cost pools. That mapping is the foundation for this page. A cost model that doesn't feed decisions tends to stall, as we discuss in why IT cost transparency projects stall.

In our view, the page works best when the plan, the funding decision and the cost of the work sit in one operating model, so the numbers on it are current when the CFO reads them.

Sources

Frequently asked questions

What does a CFO want to see about IT spend?

In our view, five things: total spend against budget and forecast, what it is spent on, why it moved, what it buys in terms of unit costs, and where money could be cut or shifted. The TBM Council's CFO guide adds the split between fixed and variable spend and between operating and capital expenditure, both visible in the cost pool layer.

What is the Finance View in the TBM Taxonomy?

The Finance View is one of several lenses on the same TBM Taxonomy. According to the TBM Council's CFO guide, it focuses mainly on cost pools and resource towers and supports budgeting, planning, variance tracking and chargeback. The CIO works mainly in the Technology View, which emphasizes resource towers and solutions. Both draw on one shared model.

Which unit costs should you show a CFO?

We think you should show two or three unit costs tied to volumes the business already counts and reports, such as cost per order, per claim or per employee supported. Technical unit costs like cost per virtual machine are useful for IT but hard for a CFO to test against other reports. State each definition so finance can check it.

How should IT explain capex and opex to a CFO?

Show opex, capex, and the depreciation and amortization that capital spend creates in later years. Under GAAP, capitalized internal-use software is amortized over its estimated useful life once ready for use, so this year's capex becomes future P&L cost. Rules are changing under ASU 2025-06; confirm treatment with your controller and auditor.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.