Why IT budgets lose credibility
Most IT budgets are last year's numbers plus a percentage, presented as a list of cost centres. The CFO cannot see what drives the cost, which part keeps the lights on and which part buys change, or why the forecast moved in March. So the conversation becomes a negotiation over a percentage, and IT loses it.
A budget the CFO will approve does three things: it shows the whole of IT spend on one page, in categories finance recognises; it explains every movement from last year; and it builds the run cost from drivers, so that a change in the business shows up as a change in the number.
The IT budget on one page
Two views carry most of the conversation. What the money is spent on (cost types, which finance sees in the ledger) and what it is for (run the business, grow it, transform it). Put both on one page, with capital and operating expense alongside. The view below is a spend view: what will be paid out in the year, capital and operating, without depreciation. An illustrative budget, in thousands:
| Cost type | Run | Grow | Transform | Total |
|---|---|---|---|---|
| Internal staff | 4,200 | 600 | 400 | 5,200 |
| External staff and services | 900 | 700 | 1,100 | 2,700 |
| Software and SaaS | 2,600 | 300 | 200 | 3,100 |
| Infrastructure and cloud | 1,800 | 150 | 100 | 2,050 |
| Telecoms and network | 700 | 50 | 0 | 750 |
| Other | 200 | 0 | 0 | 200 |
| Total | 10,400 | 1,800 | 1,800 | 14,000 |
| Share | 74% | 13% | 13% | 100% |
| of which capital | 300 | 400 | 1,000 | 1,700 |
| of which operating | 10,100 | 1,400 | 800 | 12,300 |
- Run: keeping current services working: operations, support, maintenance, licences, hosting.
- Grow: improving or extending what exists: enhancements, more users, new sites on existing systems.
- Transform: new capabilities that change how the business works: new platforms, new business models, major replacements.
Agree the definitions with finance once, write them down, and apply them every year. A run share that moves because the definitions moved tells the CFO nothing.
The bridge: explain every movement
The CFO's first question is why the number changed. Answer it before it is asked, with a bridge from last year to this year. Each line has an owner and evidence.
| In thousands | Amount | Evidence |
|---|---|---|
| Last year's budget | 13,300 | Approved budget |
| Price increases on existing contracts | +300 | Indexation clauses and renewal quotes |
| Pay review and staff changes | +200 | HR pay assumptions and the position list |
| Volume growth: users, data, cloud usage | +250 | Business plan headcount and usage trends |
| Run cost of projects that went live | +300 | Business cases of those projects |
| Savings: contracts ended, licences removed | −450 | Savings pipeline, confirmed by finance |
| Change projects completed | −1,200 | Portfolio |
| New change portfolio | +1,300 | Ranked demand, approved by the steering committee |
| This year's budget | 14,000 |
The first five lines are run: they take it from 9,800 to 10,400. The last two are change: from 3,500 to 3,600. CFOs often ask for the same bridge from last year's forecast outturn as well as from last year's budget; prepare both. The bridge separates what IT cannot avoid (prices, volume, the run cost of past decisions) from what the business chooses (the change portfolio). It moves the conversation from "IT costs more" to "these are the choices that cost more".
Build the run budget from drivers
Run costs follow a small number of drivers. Build them that way, and the budget updates itself when the business plan changes.
| Cost | Driver | Ask for |
|---|---|---|
| Workplace licences and devices | Number of employees and contractors | Headcount plan from HR |
| Business application licences | Named or concurrent users, revenue or transactions | Contract metrics and the business plan |
| Cloud and hosting | Usage: compute, storage, data transfer | Last 12 months of bills and the growth plan |
| Contracts and support | Contract terms, indexation, renewal dates | Contract register with key dates |
| IT staff | Approved positions, pay review, vacancies | HR position list and pay assumptions |
Two checks keep the run budget honest. The run rate check: take the last three months of actual run spend, adjust for annual payments and seasonal items, annualise it, and compare it with the budget. If the gap cannot be explained by known changes, the budget is wrong. The contract check: every contract that renews during the year has a line, with the renewal price, not today's.
The change budget: fund decisions, not wishes
- Start from the ranked portfolio. Approved projects carry their approved budgets; new demand is ranked against capacity and funded in order until the envelope is used.
- Release money in stages. Fund each project to its next decision point rather than in full at the start of the year.
- Keep a small unallocated reserve for what the year will bring, released only by the steering committee.
- Add the run cost tail. Every project that goes live adds run cost. Show it in the year it starts, not as a surprise the year after.
Capital or operating: decide with finance, early
The split between capital and operating expense changes the profit and loss account, which is often what executives are measured on. Three points cause most surprises:
- Software-as-a-service is operating expense. The cost of configuring it is often expensed too under IFRS, while US GAAP usually spreads it over the contract term. Moving from owned software to subscriptions shifts cost from capitalised software, whose amortisation sits below EBITDA, into operating expense above it: EBITDA falls even if total cost does not.
- Capitalised spend comes back as depreciation and amortisation for years. The profit and loss view of the budget replaces this year's capital spend with the depreciation and amortisation of past and current investments; show it as a reconciliation line under the spend view.
- Internal staff time can be capitalised only in the build phase of qualifying projects, when the accounting criteria are met, and only if it is recorded. Without timesheets, it stays in operating expense.
Agree the rules with your controller before the budget is built, not after it is approved.
Forecast every month, from one version
An approved budget is a starting point. What the CFO trusts is a forecast that moves early and explains itself. Each month, update the full-year forecast, explain the variances above a threshold agreed with finance, and list the risks and opportunities not yet in the numbers. Keep one version of the forecast, owned by IT and reconciled with finance. Two spreadsheets that do not agree destroy more credibility than an overrun.
Ten questions the CFO will ask
- What does the whole of IT cost, including IT spend in the business units?
- How much is run, and why is it growing?
- What did we get for last year's change budget?
- Which contracts renew this year, and at what price?
- What run cost will this year's projects add next year?
- Which savings are already in the numbers, and who confirmed them?
- What is capital, what is operating, and what is the depreciation tail?
- What happens to the budget if headcount grows, or falls, by 10%?
- How does our spend compare with others, and how reliable is the comparison?
- What would you stop if the budget were cut by 5%?
If you can answer each one with a number and a source, the budget will be approved on its merits.
Questions
What share of the IT budget should be run versus change?
There is no right share for every company: it depends on the industry, the age of the systems and the strategy. What matters is the trend and the reason. A run share that rises every year without a decision behind it means past projects are adding run cost faster than savings remove it.
Should business-unit IT spend be in the IT budget?
It should be visible, even if it is not managed by IT. Show the whole of technology spend, with the part managed by IT and the part managed in the business units, so that the CFO and the board see the real total.
When should the IT budget process start?
Three to four months before the budget is due. Start with the run baseline and the contract register, then the demand for change, then the bridge. Leave the last month for the conversation with finance.
How do I handle a budget cut?
Show the choices, not a percentage. List what would stop or slow down for each level of cut, with the risk and the business impact, and let the executive committee choose. Cuts to run without a change in service usually come back as incidents.