State of FinOps 2026: read scope and AI trends carefully
Published and reviewed: 1 October 2026
Scope my cloud cost reviewThe State of FinOps 2026 report was listed as available on 20 February 2026.

On this page
What the report is, and when it appeared
The FinOps Foundation's updates page lists « State of FinOps 2026 Report Now Available » on 20 February 2026. The report, published at data.finops.org, is the sixth annual survey of the FinOps community, run by the Foundation since 2020. It is a survey of the practitioners who answered, not a census of companies, and the charts on the page show question bases that range from 523 to 695 respondents depending on the question.
Figures that are in the source
- AI spend: 98% of respondents manage it (63% in 2025, 31% in 2024). FinOps for AI is the top forward-looking priority.
- Other categories: 90% manage SaaS or plan to (65% in 2025), 64% licensing, 57% private cloud, 48% data center, and 28% are including labor costs.
- Reporting line: 78% of practices report to the CTO or CIO, and 8% to the CFO.
- Operating model: 81% use centralized enablement (60%) or hub-and-spoke (21%). Organizations managing $100M+ in cloud spend average 8 to 10 practitioners and 3 to 10 contractors, according to the report.
- Priorities: workload optimization and waste reduction remain the top current priority, but the report says scope expansion, governance, organizational alignment and forecasting together outweigh optimization alone.
The report quotes a practitioner who says the « big rocks » of waste are already addressed and what remains is a high volume of smaller opportunities that take more effort to capture. Keep that sentence in mind when a proposal promises quick wins from a mature environment.
Reading the numbers without over-reading them
A percentage of respondents is a statement about who answered, not about your company. Before a figure enters a board deck, record its edition, the question wording and the base. Two sections of the same page give different comparison figures for influence over technology selection by seniority (for example 53% against 12% in the summary and 53% against 24% in the detailed section for cloud service selection), which is a reason to cite the page you actually read, and to avoid quoting the gap as a fixed fact.
The report itself notes that larger companies tend to have separate FinOps and ITAM teams while smaller ones combine them. A small company can therefore start with one person and a narrow scope without being behind the survey.
Questions the report helps you ask internally
- If AI spend is material, can finance separate training, inference and overhead, and does each have an owner?
- Which technology categories beyond cloud does finance expect FinOps to cover in the next twelve months, and is reliable data available for each?
- Does anyone at VP level or above sponsor the practice? The report ties executive engagement to more influence over technology selection.
- Is the team built to scale through champions and automation, or through headcount?
The AI cost optimization guide details what an audit of tokens and GPUs should deliver, and the FinOps KPIs guide explains how to measure value with your own data rather than a survey average.
Turning survey priorities into a bounded brief
Do not rank providers on the report's priorities. Choose one priority that matches a real decision, for example governing AI spend before a budget round, and ask each candidate for a deliverable, a review period and the customer effort required. Ask how the output can be maintained once the engagement ends. Survey material supports your questions, and your own data supports the purchase.
Primary sources
The Foundation's updates page, which dates the release, and the report itself:
Continue your review
Request a quote for my project
Describe your project in a few lines and receive a quote from a specialist.
Request my quote