The most effective CFO approach to IT services budgeting in 2026 is not cost containment. It is strategic alignment: connecting every pound of technology expenditure to a measurable business outcome, then building the governance structures to defend that allocation under pressure. Gartner research confirms that 75% of CFOs expect their technology budgets to increase in 2026, with nearly 48% planning rises of 10% or more. That is not a discretionary trend. It reflects structural pressure from rising SaaS costs, AI adoption, and cybersecurity obligations that will not ease regardless of economic conditions.
For UK finance leaders, the practical challenge is translating that investment ambition into a budget that boards will approve, IT teams can execute, and the organisation can actually measure. That requires moving beyond static annual cycles toward rolling, scenario-aware planning, and it demands a clear framework for categorising spend by value rather than by vendor invoice.
Key strategic actions for CFOs managing IT services budgets:
The fastest way to lose board confidence in an IT budget is to present it as a list of costs. The budget that earns approval connects each line item to a capability the business needs to operate, grow, or transform. That reframing is not cosmetic. It changes which conversations happen and who controls the outcome.
A practical starting point is the Run/Grow/Transform model, which allocates spend across three horizons. Run covers the infrastructure, maintenance, licences, and support that keep current systems operational, representing the largest portion of the total budget. Grow funds improvements to existing capabilities, from digital channels to workflow automation, at a smaller portion. Transform, the smallest slice, funds genuinely new capabilities: major platform modernisation, AI at scale, or zero-trust architecture programmes. When Run spending creeps above 70%, the organisation is consuming growth and transformation budget on maintenance, which is a signal to act before requesting additional funding.
IT budgets typically break down into five functional categories:
Benchmarking against sector peers gives the budget a defensible external reference. IT spending as a percentage of revenue varies considerably: technology companies typically spend 8–12%, financial services 7–10%, manufacturing 2–4%, and retail 3–5%. The percentage alone is less revealing than the split between run-the-business and change-the-business spending. Best-in-class organisations maintain a 60/40 split; those spending more than 65% on Run have an optimisation opportunity before they ask for more.
A comprehensive IT budget must also account for shadow IT, vendor contract escalation clauses, and contingency reserves. Shadow IT, the technology purchased by departments outside the IT function, consistently causes mid-year surprises when it is not captured in the planning process. Tracking all contracts in a centralised register with renewal dates and escalation terms is one of the most practical governance steps a CFO can take before the annual cycle begins.
Annual IT budgets assume a degree of predictability that the technology environment no longer supports. Licence costs shift, cloud consumption spikes, and AI-related expenses arrive faster than a twelve-month planning cycle can absorb. The structural response is a rolling quarterly review model, where the budget is treated as a living document rather than a fixed annual commitment.
Quarterly budget reviews with 10–15% reallocation authority at the CTO level give finance leaders the mechanism to rebalance portfolios without waiting for the next fiscal year. That authority is not a licence for ad hoc spending. It is a defined governance mechanism that replaces reactive cuts with controlled rebalancing, and it requires clear decision rights and documented triggers to function properly.
Scenario planning adds the risk dimension that rolling forecasts alone cannot provide. The standard approach models three cases:
Macroeconomic inputs, including inflation forecasts from institutions such as the IMF or OECD, currency assumptions, and wage growth projections, should anchor each scenario rather than internal estimates alone. This matters particularly for UK enterprises with multi-currency technology contracts or offshore delivery models.
Driver-based budgeting extends this further by connecting budget assumptions to specific operational variables: headcount growth rates, transaction volumes, cloud consumption per user, and security incident frequency. When those drivers change, the budget model updates automatically rather than requiring a manual rebuild.
Pro Tip: Build a contingency reserve of 5–8% into the base budget and define in advance which categories it can be drawn against. A reserve without governance rules tends to disappear into the largest cost centre rather than covering genuine surprises.
Cybersecurity cannot be treated as a residual budget item, funded with whatever remains after infrastructure and personnel costs are met. Regulatory frameworks including GDPR, and sector-specific rules in financial services and healthcare, define minimum viable controls that carry real financial consequences if unmet. The budget question is not whether to fund security, but what mix of controls delivers the desired reduction in risk exposure given the organisation’s risk appetite and sector benchmarks.
Viewing the IT budget as a growth enabler rather than a cost centre changes the conversation around innovation funding. Nearly 60% of CFOs plan to increase finance function AI investments by 10% or more in 2026. That investment needs a line item and a governance structure, not a vague allocation to “digital transformation.” Connecting AI spend to specific productivity or cost-reduction outcomes is what makes it defensible at board level.
Cost efficiency levers worth prioritising:
The IT support cost trajectory for physical service delivery deserves particular attention. As AI automates digital service resolution, the relative cost of physical IT support, device handovers, peripheral exchanges, and on-site interventions, grows as a proportion of total IT spend. CFOs who address this imbalance now, through automation of physical workflows, will find the efficiency gains compound as agentic AI matures.
The three failures that account for most IT budget overruns are predictable, and all three are avoidable with the right governance structures in place.
Underestimating maintenance and technical debt. New systems do not stop costing money at go-live. Maintenance, patching, and ongoing support create a sustained funding obligation that, when ignored in the planning process, produces a growing gap between what was budgeted and what is actually required. Technical debt compounds this: deferred upgrades and unpatched systems accumulate in the form of slower delivery, higher defect rates, and increased security exposure. Allocating a defined percentage of the development budget specifically to debt reduction prevents this from becoming an emergency.
Treating IT spend as a black box. When finance leaders lack visibility into what IT is spending and why, budget conversations become adversarial rather than collaborative. Effective CFOs ensure that every IT budget line item maps to a business outcome, communicates associated risks, and presents scenario impacts to stakeholders. That transparency is what enables quick approval and sustained board confidence.
Practical steps to improve governance and accuracy:
Planning in annual cycles only. The IT support cost trajectory changes faster than a twelve-month plan can accommodate. Quarterly reforecast triggers, defined in advance and linked to specific business or market conditions, give the CFO a structured mechanism to respond without disrupting the broader financial plan.
The gap between IT investment ambition and execution confidence is widening. Grant Thornton’s Q2 2026 CFO Survey found that just 37% of finance leaders are optimistic about the economy over the next six months, the lowest level recorded in the survey’s twenty-quarter history. Yet 67% expect to increase IT and digital transformation spending, and nearly half now cite technology upgrades as a top priority, up 13 percentage points from the previous quarter. That divergence between economic pessimism and technology investment intent is not a contradiction. It reflects a deliberate choice to use technology as a hedge against operational uncertainty.
Statistic: 75% of CFOs expect technology budgets to increase in 2026, with nearly 48% planning rises of 10% or more. The average increase across all industries is around 10%, ranging from 15% in financial services to 6% in manufacturing.
For UK finance leaders, translating that intent into execution requires a multi-dimensional portfolio management approach. Rather than defending individual line items, the CFO presents the IT budget as a portfolio with explicit risk, value, and cost dimensions across Run, Grow, and Transform horizons. Each category carries articulated risk categories, likelihood, and impact, alongside funded mitigations. Boards increasingly expect this framing, and budgets that provide it move through governance faster.
Recommended governance practices for 2026:
Understanding what metrics CFOs need before committing to AI investments is increasingly central to this governance work, as AI line items grow from pilot allocations to material budget commitments.
Cost allocation and chargeback models solve a specific governance problem: when IT costs are pooled centrally, business units have little incentive to manage their consumption, and the IT function struggles to demonstrate value to individual stakeholders. Chargeback models address this by attributing IT costs directly to the consuming business unit, creating accountability at the point of demand.
The practical choice for most UK enterprises sits between three models. Full chargeback allocates actual costs to each business unit based on measured consumption, which creates the strongest accountability but also the most administrative overhead. Showback provides the same visibility without transferring the financial liability, making it a useful starting point for organisations building cost transparency for the first time. Hybrid models apply full chargeback to discretionary services, such as project development and premium support tiers, while pooling mandatory infrastructure costs centrally.
Distinguishing operational expenditure from capital investment within IT budgets is a prerequisite for any allocation model to work accurately. When CapEx and OpEx are conflated, depreciation schedules distort the apparent cost of shared services, and business units cannot make informed decisions about their technology consumption. Getting this separation right also matters for EBITDA reporting, where cloud and SaaS subscription costs appear as immediate operational expense rather than amortised capital.
Cloud and SaaS spending has a structural tendency to drift above plan. Consumption-based pricing models respond to demand spikes in real time, but budget cycles typically set targets based on historical averages. The result is a gap that appears mid-year and requires either a supplementary budget request or a cut elsewhere.
The discipline that closes this gap is FinOps: treating cloud spend as a financial management function with the same rigour applied to any other operational cost. Practically, this means modelling cloud unit economics per user, per workload-hour, and per gigabyte of storage, then setting explicit targets for what proportion of cloud spend should be controllable through rightsizing, scheduling, and reserved capacity commitments. Scenario planning can then simulate the impact of demand spikes or vendor price changes before they occur, rather than after the invoice arrives.
For SaaS budgeting, the 30% average waste on unused or underutilised licences cited earlier is the starting point for any audit. Centralising procurement, so that all new SaaS subscriptions require IT approval before purchase, prevents shadow IT from rebuilding the waste that the audit removed. Reviewing cloud usage quarterly, rather than annually, catches consumption drift before it becomes a budget crisis.
The CapEx versus OpEx dimension of cloud budgeting also carries board-level implications. Shifting workloads from on-premise infrastructure to cloud consumption moves spending from depreciated capital to immediate operational expense, which affects EBITDA, cash flow, and balance sheet presentation. CFOs need a clear policy view on where variable OpEx supports strategic agility and where stable, long-lived workloads still justify reserved-capacity commitments or capital investment.
Compliance is not a discretionary IT cost. For UK enterprises operating under GDPR, FCA rules, or sector-specific frameworks in healthcare and defence, the minimum viable controls are defined externally, and the consequences of underfunding them are financial and reputational. Budget packs that treat compliance as a residual line item, funded after everything else, create a governance risk that boards are increasingly unwilling to accept.
The practical framing is to treat security and regulatory compliance funding as a structured risk portfolio. Identity-first controls, threat detection and response, resilience capabilities, and audit tooling play different roles in reducing the probability and impact of incidents. Governance standards such as NIST CSF and ISO 27001 provide reference models for coverage, and Gartner benchmark data on security spend as a percentage of IT budgets by sector gives the CFO an external reference for setting minimum floors.
Emerging AI governance requirements are adding a new compliance dimension to 2026 budgets. As the EU AI Act’s obligations extend to UK enterprises operating in European markets, data protection controls, logging and monitoring, and third-party risk assessments for AI systems require sustained funding. These are not one-time implementation costs. They create ongoing audit and reporting obligations that belong in the Run allocation, not the Transform budget.
For UK enterprises managing security and compliance within ServiceNow-native environments, the architectural choice of where IT asset data lives, and who can access it, has direct compliance implications. Native CMDB records, inheriting existing RBAC and audit trails, reduce the compliance overhead of managing a parallel vendor database. That architectural discipline is where technology investment and regulatory obligation converge in a way that the CFO can quantify.
Effective CFO management of IT services budgets in 2026 requires aligning every technology expenditure to a business outcome, adopting rolling quarterly reviews, and treating cybersecurity and compliance as structured risk portfolios rather than residual line items.
| Point | Details |
|---|---|
| Align spend to outcomes | Every IT budget line must connect to a business objective or risk mitigation, not a technology need. |
| Use the Run/Grow/Transform model | Target 60% Run, 25% Grow, 15% Transform; Run above 70% signals an optimisation opportunity. |
| Adopt quarterly rolling reviews | Quarterly reviews with 10–15% reallocation authority at CTO level replace reactive cuts with controlled rebalancing. |
| Audit SaaS and cloud waste first | Organisations waste an average of 30% of SaaS spend on unused licences; audit before requesting new budget. |
| Benchmark IT spend as a percentage of revenue | Target 8–12% for technology, 7–10% for financial services, 2–4% for manufacturing, and 3–5% for retail according to Gartner sector data. |
As AI collapses the cost of digital service resolution toward zero, the relative weight of physical IT support in the CFO’s technology expenditure grows. Desktop support tickets already cost approximately three times more than digital ones, and that gap widens as agentic AI matures. The physical layer, device handovers, peripheral exchanges, broken-laptop swaps, remains dependent on human intervention unless the workflow is explicitly automated.
Velocity-smart’s Smart Collect® platform addresses this directly. Running natively inside the customer’s ServiceNow tenant, it orchestrates Smart Lockers, Smart Vending, and Smart Kiosk hardware without creating a parallel database or requiring a separate security review. Asset state, device location, and ownership history sit in the customer’s CMDB as native records. A global pharma customer achieved 500%+ uplift in IT service throughput and 83% faster fulfilment using Smart Collect before AI was driving the workflow. Those outcomes are the floor, not the ceiling, as Now Assist and agentic AI mature.
For CFOs building the case for physical IT automation within a ServiceNow environment, the AI cost reduction guide for IT leaders sets out the cost trajectory and the investment rationale in detail. The question is not whether physical IT support will become the dominant cost line as digital costs fall. It already is. The question is whether your budget plan accounts for it.