What State of FinOps 2026 shows, and what it can't
In brief
State of FinOps 2026 shows FinOps spreading to AI, SaaS and data centers. What its 1,192 responses support, where the method is thin, and what to tell a CIO.
Steve Elliott · · 7 min read
On this page
State of FinOps 2026 shows that FinOps teams now cover far more than public cloud: 98% report managing AI spend and 90% manage SaaS or plan to, and 78% of practices sit under the CTO or CIO. What it can't show is how well any of that is done, because it is a self-selected survey of the FinOps community, answered question by question by roughly 520 to 700 people, with some figures that mix today's scope and next year's plans.
That makes it a good map of where practitioners think their job is going, and a weak benchmark for your own practice. Reading the report closely, we also found one result reported two different ways and a headline change the report doesn't define.
What are the headline findings?
The FinOps Foundation published the sixth annual survey on February 19, 2026. The scope figures come from one multi-select question asking which areas of technology spend the FinOps team manages today and in the next 12 months.
| Area of spend | 2026 | 2025 | Change |
|---|---|---|---|
| AI | 98% | 63% | +35 points |
| SaaS | 90% | 65% | +25 points |
| Licensing | 64% | 49% | +15 points |
| Private cloud | 57% | 39% | +18 points |
| Data center | 48% | 36% | +12 points |
Other findings worth knowing:
- AI is the future priority. FinOps for AI is the top forward-looking priority, and AI cost management is the skill teams most want to add. Many organizations report being asked to self-fund AI investments through optimization savings.
- Optimization is still the current priority, with less left to find. Workload optimization and waste reduction remain the top current priority, but the report says practitioners see diminishing returns as the large items of waste are already gone.
- Reporting lines. 78% of practices report into the CTO or CIO organization. Reporting to the CFO fell to 8%.
- Team shape. 60% use centralized enablement and 21% hub-and-spoke. The report describes small central teams working through federated champions. Organizations spending $100 million or more on cloud average 8 to 10 practitioners plus 3 to 10 contractors.
- Labor. 28% manage or plan to manage labor costs within FinOps.
- FOCUS. Among respondents spending $100 million or more, about 68% use or experiment with FOCUS-formatted data, and another 18% plan to, according to the Linux Foundation release.
The Foundation changed its mission on the same day, from people who manage the value of cloud to "advancing the people who manage the value of technology." The mission post cites the survey's scope figures in support of the change.
Who answered, and how much spend do they represent?
The report counts 1,192 respondents representing more than $83 billion in annual cloud spend. In 2025 it was 861 respondents and about $69 billion.
- Size. 47% come from organizations with 10,000 or more employees, 33% from 1,000 to 9,999 and 20% from smaller ones.
- Region. 35% Europe, Middle East and Africa; 34% North America; 16% Asia Pacific; 15% South and Central America.
- Per question. Each charted question shows its own sample size, from N=523 to N=698. The reporting-line question has N=523, the scope question N=632.
The report describes itself as a snapshot from the global FinOps community. It gives no fieldwork dates, sampling method, weighting or breakdown of respondents by role. The 2025 report said the survey was run from within the Foundation's community of large cloud spenders. As of November 2026, the 2027 survey is open on the same site.
What changed from 2025 to 2026?
Scope moved first, maturity may follow. Every category in the scope table grew by double digits in one year. AI went from 31% in 2024 to 98% in 2026. In our view that pace says more about mandate than capability: a team can be asked to cover AI or SaaS spend long before it has the data and the cost allocation to do it well. The report's own list of AI challenges points that way: visibility into AI costs across varied pricing models, allocating AI costs to business units, and showing AI value.
Priorities widened beyond savings. In 2025, the report put workload optimization first by a clear margin, with full allocation and forecasting next, and governance and policy at scale as the top priority for the coming year. In 2026, optimization is still first, but the report says that scope expansion, governance and policy, organizational alignment (the report's category name) and forecasting, taken together, outweigh it. A practitioner quoted in the report puts the AI problem bluntly: "Is your AI providing value? No one can answer that question yet."
The practice moved closer to technology leadership. 78% now report to the CTO or CIO, and the Foundation's executive director, J.R. Storment, said in the release that "FinOps has definitively expanded to a broad array of technology value management." He tied that to c-level decisions on multi-year technology investment as AI costs rise.
What can't the survey tell you?
These limits come from reading the report itself. None of them makes the survey wrong. They change how hard you can lean on it.
- One finding is reported two ways. On the influence of executive engagement, the team section and the press release say teams engaged at VP level or above influence cloud service selection 53% of the time, against 24% for Director-level engagement. The executive summary gives 53% against 12%, with similar mismatches for provider selection and for cloud versus data center placement. We would use the team section's figures, which match the release, until the Foundation clarifies.
- A headline change is undefined. The report says the CTO/CIO share is up 18% on 2023 data without saying whether that is percentage points or a relative change, and it gives no prior figure for the CFO share.
- It is self-selected. Respondents come from the FinOps community and chose to answer. We would expect people who run an active practice to be more likely to take part than companies with none, so the figures describe FinOps practitioners, not all companies with cloud spend.
- "Manage" is not defined, and some figures include plans. The scope question covers today and the next 12 months, and the SaaS figure explicitly includes teams with plans. The report text doesn't say how much of the 98% for AI is current work and how much is intended. In our view, managing AI spend could mean anything from reading a monthly invoice to allocating token costs by product.
- Each question has its own sample. Each charted question shows its own sample size, from N=523 to N=698, so each of those figures rests on between 44% and 59% of the 1,192 respondents (our arithmetic). The 8% reporting to the CFO is 8% of 523, or about 42 respondents. The executive-engagement influence figures show no sample size at all.
- Correlation, not cause. Even the consistent influence figures show only that teams with senior engagement report more influence. They don't show that senior sponsorship causes influence. A team that already has influence may simply attract senior attention.
- Spend is measured as cloud only. The $83 billion-plus is annual cloud spend, while the headline story is about AI, SaaS, licensing and data centers. The report doesn't say how much non-cloud spend these teams cover.
- The 2025 and 2026 samples aren't like for like. The 2025 report described size in different bands (organizations over 20,000 employees, cloud spend tiers). It also measured spend as public cloud, where 2026 says cloud, so the move from $69 billion to $83 billion-plus may not compare the same thing.
What should a FinOps lead take to their CIO?
This section is our view. The survey is useful in a CIO conversation as evidence of direction, not as a benchmark score.
- Ask for a scope decision, not a headcount comparison. Peers report covering AI, SaaS and licensing. The question for your CIO is which of those your team owns, with what data and by when. Agree it in writing so the mandate and the resources arrive together.
- Bring an AI cost view, even a rough one. If peers are being asked to self-fund AI from savings, your CIO is likely facing the same question. Show what AI spend you can see today, what you can't, and what it would take to allocate it to products. We covered the labor side in AI initiative costs: tokens vs labor.
- Reset the savings story. If your own data shows the same diminishing returns the report describes, say so before the CIO's targets assume last year's savings rate. Shift the measure toward forecast accuracy and unit economics.
- Agree who you work with. The report says FinOps collaborates most often with IT financial management. If your organization has a TBM or ITFM team, agree one cost number with them before the CIO sees two. Our TBM vs FinOps post sets out where we would draw the line.
- Quote the survey with its caveats. Say "98% of State of FinOps respondents report managing AI spend now or in the next 12 months," not "98% of companies manage AI spend." A CIO who later finds the gap will discount the rest of the case.
The survey shows FinOps moving from the cloud bill into technology investment decisions. In our view that only works when the team's scope, the spend it covers and the decisions it informs sit in one operating model rather than in separate reports.
Sources
- FinOps Foundation, State of FinOps 2026 Report, released February 19, 2026
- FinOps Foundation, State of FinOps 2025, 2025
- FinOps Foundation, Data Library (2027 survey announcement), accessed November 21, 2026
- Linux Foundation, State of FinOps Survey: AI Value and Skills Top Priorities as FinOps Matures Across Technology Value, February 19, 2026
- FinOps Foundation, Mission update, J.R. Storment, February 19, 2026
Frequently asked questions
How many people answered State of FinOps 2026?
The report counts 1,192 respondents representing more than $83 billion in annual cloud spend, up from 861 respondents and about $69 billion of public cloud spend in 2025. Individual questions were answered by fewer people, with sample sizes from 523 to 698. The reporting-line question, for example, rests on 523 responses, so read each figure against its own sample.
Do 98% of companies really manage AI spend?
No. The figure is 98% of survey respondents, who are FinOps practitioners from the Foundation's community, not a sample of all companies. The question asks which areas the FinOps team manages today and in the next 12 months, so the figure may include teams with plans. The report doesn't define what managing AI spend involves.
Who do FinOps teams report to, according to the survey?
In the 2026 report, 78% of FinOps practices report into the CTO or CIO organization, and 8% report to the CFO. The report says the CTO/CIO share is up 18% against 2023 data, without saying whether that means percentage points or relative growth. The reporting-line question had 523 responses.
What changed in State of FinOps 2026 compared with 2025?
Scope grew most. AI rose from 63% to 98%, SaaS from 65% to 90%, licensing from 49% to 64% and data center from 36% to 48%. Optimization stayed the top current priority, though practitioners report diminishing returns. FinOps for AI became the top future priority, and the Foundation changed its mission from cloud to technology.
Steve Elliott
Published November 22, 2026
More on FinOps & Cloud
FOCUS, commitments, shared cost.
Keep reading
What the FinOps Framework 2026 changes for practitioners
A close reading of the FinOps Framework 2026: the new Executive Strategy Alignment capability, rewritten Scopes guidance, technology categories and renames.
Should FinOps report to the CTO, CIO or CFO?
Most FinOps teams report to the CTO or CIO; 8% report to the CFO. When each line fits, what it costs, and how to make a dotted line to finance work.
What AI agents should and shouldn't do in FinOps
Agents suit FinOps work that is read-only or easy to undo. Commitments, policy and chargeback disputes need a person. Where the line sits, with guardrails.
Who owns SaaS spend: FinOps, software asset management or procurement?
SaaS is moving into FinOps, but ITAM and procurement already hold contracts and entitlements. Who should own what, where FOCUS stands, and a working split.