Enterprise FinOps AI cloud cost management has undergone a structural shift that most IT organizations have not yet caught up to. The FinOps Foundation released its State of FinOps 2026 report on February 19, drawing on responses from 1,192 practitioners who collectively account for more than $83 billion in annual cloud spend, and the headline finding is stark: AI spend is now in scope for 98% of FinOps teams, up from 63% in 2025 and just 31% the year before that. The cloud bill is no longer the center of gravity - total technology spend is.
FinOps Foundation, State of FinOps 2026 (February 2026), n=1,192
| Value (% of practitioners) | AI spend in scope |
|---|---|
| 2023-24 | 31 % of practitioners |
| 2025 | 63 % of practitioners |
| 2026 | 98 % of practitioners |
How fast AI spend entered the FinOps remit
Two years ago, fewer than one in three FinOps practitioners had any mandate over AI infrastructure costs. By the time the 2025 survey closed, that figure had reached 63%. The 2026 number - 98% - is close to saturation, according to the FinOps Foundation. The pace of that change is unusual even by enterprise technology standards and reflects how rapidly GPU-backed workloads, large language model APIs, and AI platform subscriptions have moved from experimental budgets into core operating expenditure.
For CIOs, the implication is practical rather than philosophical. AI inference and training costs do not behave like traditional compute: they spike unpredictably, pricing models vary significantly between providers, and chargeback attribution is harder when a single model serves multiple business units. FinOps teams that were built around reserved instance planning and storage tiering are now being asked to govern a category that did not meaningfully exist in their organizations 24 months ago.
AI spend is now in scope for 98% of FinOps practitioners - up from 31% just two years ago, according to the FinOps Foundation's State of FinOps 2026.
SaaS and software licensing widen the scope further
AI spending is not the only expansion underway. The FinOps Foundation's 2026 data shows 90% of FinOps teams now manage SaaS costs or have firm plans to do so, compared with 65% in 2025. Software licensing is in scope for 64% of teams - a 15-percentage-point increase year over year. Private cloud coverage also rose, from 39% to 57%.
This trajectory tracks with what FinOps practitioners and vendors have been calling 'Cloud+' or total technology spend - a framing that puts the discipline in direct competition with traditional software asset management and IT vendor management functions. For enterprise IT leaders, that boundary question matters: if FinOps now touches SaaS renewals, Microsoft EA negotiations, and on-premises virtualization licenses, it needs representation in procurement decisions well upstream of contract signature, not just a seat at the reconciliation table after the fact.
Kion, Flexera, and other FinOps platform vendors have been moving their product roadmaps in this direction, broadening ingestion from cloud provider billing APIs to SaaS spend data and software entitlement feeds. The market is responding to where the demand is going, not where it has been.
Executive alignment is rising - and it matters for influence
One finding from the FinOps Foundation report that deserves attention from IT leaders is the shift in organizational reporting lines. According to the accompanying Linux Foundation press release, 78% of FinOps practices now report into the CTO or CIO organization, an increase of 18 percentage points. The Foundation found that those teams showed measurably greater influence over cloud service selection compared with practices that sit elsewhere in the business.
That correlation - between executive sponsorship and operational influence - is not surprising, but the magnitude of the shift suggests the industry has moved past the phase where FinOps was a scrappy cost-savings initiative run by a handful of engineers with spreadsheets. Practices that report to finance or procurement without a CIO-level champion appear to have less pull when it counts: during contract negotiations, architectural decisions, and roadmap commitments with major cloud providers.
A 25% waste figure gives CFOs an audit target
PwC's 2026 research estimated enterprise-level waste at roughly 25% of combined cloud, data, and AI spend. That number has been picked up by MarketsandMarkets and others as a primary growth driver for the FinOps platform market, which MarketsandMarkets projects will reach $26.91 billion by 2030, up from $14.88 billion in 2025.
The CFO implication is direct. A 25% waste estimate applied to any large enterprise's technology budget is not a rounding error - it is a board-level conversation. CIOs heading into FY2027 budget cycles who cannot demonstrate AI and SaaS cost efficiency alongside traditional cloud optimization metrics are exposed to exactly the kind of line-by-line scrutiny that a skeptical CFO or audit committee is equipped to run. The political cover that 'we are working on it' provided two or three years ago is thinner now that the tools and frameworks to address waste are mature and widely adopted.
IDC projects global public cloud services to exceed $1 trillion by the end of 2026. At that scale, unmanaged spend is not a technical problem - it is a governance failure. FinOps, in its expanded form, is the organizational response enterprise IT has available.
What CIOs should do before the next budget review
The practical to-do list for IT leaders is not complicated, but it requires moving faster than most organizations currently are. First, audit whether the FinOps team's mandate formally covers AI infrastructure and SaaS - not just public cloud IaaS and PaaS. If it does not, that gap will surface in the next major spend review as an unexplained line item. Second, check the reporting structure. The data from the FinOps Foundation suggests that teams without CTO or CIO sponsorship have less leverage; if FinOps sits entirely in finance, a joint governance model at minimum is worth considering. Third, require that FinOps representation is part of any significant AI platform or SaaS contract negotiation from the outset - not brought in after commercial terms are set.
The discipline has grown up. CIOs who still frame FinOps conversations around cloud bill optimization are working from an outdated map.
