What the FinOps Framework 2026 changes for practitioners
In brief
A close reading of the FinOps Framework 2026: the new Executive Strategy Alignment capability, rewritten Scopes guidance, technology categories and renames.
Steve Elliott · · 7 min read
On this page
- What changed in the FinOps Framework 2026?
- How are Scopes different from technology categories now?
- What does Executive Strategy Alignment ask a FinOps lead to do?
- Which technology categories does the framework now cover?
- Where does the 2026 framework overlap ITFM and TBM?
- What should a FinOps lead do differently this year?
- Sources
In our reading, the biggest change in the FinOps Framework 2026 is one the foundation calls documentation: public cloud, SaaS and data center, named as Scopes in 2025, now appear as technology categories, and a Scope is a slice of spend defined by a business question, such as a product, an initiative or a cost center. The second change is a new capability, Executive Strategy Alignment, which gives FinOps a defined role in multi-year investment planning, product prioritization and decision rights.
Around those two sit six renamed capabilities, five technology category pages and a new mission. If you learned the FinOps Framework between 2023 and 2025, in our view most of what you know still holds; what changes is where a FinOps lead spends time, and who they work with. This reading uses the FinOps Foundation's own announcement and framework pages, as of November 2026.
What changed in the FinOps Framework 2026?
The FinOps Foundation published the 2026 update on March 19, 2026. It followed a mission change announced a month earlier, from advancing the people who manage the value of cloud to advancing the people who manage the value of technology. The Governing Board discussed that change across three meetings between June 2025 and February 2026.
The capability changes are mostly renames that remove cloud-only language:
| 2025 name | 2026 name | What the foundation says changed |
|---|---|---|
| Workload Optimization | Usage Optimization | Applies across all Scopes; cloud-specific language replaced |
| Policy & Governance | Governance, Policy & Risk | Covers all technology categories and intersecting disciplines |
| FinOps Tools & Services | Automation, Tools & Services | Covers automation as well as tools and services, across categories |
| Benchmarking | KPIs & Benchmarking | KPIs tied to technology category and Scope, not cloud defaults |
| Architecting for Cloud | Architecting & Workload Placement | Multiple categories; placement decisions earlier in design |
| Cloud Sustainability | Sustainability | Carbon across on-premises, SaaS, colocation and end-user computing |
| (none) | Executive Strategy Alignment | New, in the Manage the FinOps Practice domain |
Two smaller points. Governance, Policy & Risk now lists 11 risk categories, from financial and contractual to reputational, and says FinOps should surface technology risks without owning risk management alone. And the framework overview, as of November 2026, no longer lists Onboarding Workloads, which earlier versions placed in the Manage the FinOps Practice domain (its old capability page still carries that breadcrumb). The 2026 announcement doesn't mention that change. By our count the overview still shows 22 capabilities, as in 2024.
The announcement describes no changes to the four domains, the three phases or the six principles; four principles and two domain names had been reworded in 2025. One principle still reads "Take advantage of the variable cost model of the cloud."
How are Scopes different from technology categories now?
In the 2025 framework, a Scope was a segment of technology-related spending, and the first Scopes named were Public Cloud, SaaS and Data Center. The Technical Advisory Council had approved Scopes in October 2024.
The 2026 definition reads differently. A Scope is now a defined segment of spending across technology categories, tied to business constructs such as products, cost centers or environments. The announcement puts it in two sentences: "The Technology Category is the 'what.' The Scope is the 'why.'" The foundation describes this as better documentation, not a change in what Scopes are for. In our view the practical effect is larger than that suggests, because a FinOps team split into a cloud team, a SaaS team and a data center team is, in 2026 terms, organized by technology category, not by Scope. That is not wrong, but it means Scopes have to be set up deliberately across those teams.
The Scopes page sets out how a Scope should start:
- A business question, usually from leadership. The page's example is "What are we spending on AI?"
- Questioning, such as the Five Whys, to find the outcome and decision behind it.
- A check on whether an existing Scope already serves that decision. The page warns that maintaining many Scopes adds overhead.
- Only then, a Scope definition.
Scopes can overlap, and the page gives an example of the tension: a cloud Scope targeting accurate forecasts next to an AI Scope that tolerates more variability. The team has to either exclude AI usage from the cloud Scope or keep it and account for the forecast variance. The AI category page adds that not all AI spending needs a new Scope.
Take an illustrative case. A CIO asks what the company spends on AI. Questioning shows the real decision is whether to move a customer-service pilot to production next quarter. The resulting Scope covers that product's model API charges (AI category), its vector database (Data Cloud Platforms category), its contact-center software (SaaS) and the GPU servers it uses on premises (data center). It answers one decision. When that decision is made, the Scopes page says the supporting activity can fade.
What does Executive Strategy Alignment ask a FinOps lead to do?
It asks FinOps to support decisions before money is committed, not only report on spend afterwards. The capability page names four areas:
- Executive Priority Alignment. Relate spend to strategic initiatives, with forecasting and unit economics, including AI measures such as cost per token and cost per inference.
- Multi-Year Investment Strategy. Feed FinOps data into budgeting, P&L ownership and reporting, working with IT finance practices where they exist, and govern overlapping multi-year commitments across cloud, SaaS, AI contracts, data center refreshes and licensed software.
- Facilitate Product Prioritization Strategy. Make cost, speed and quality trade-offs comparable across initiatives, with FinOps input at business design, project intake and architecture.
- Enable Strategic Decision Support. Define the operating model, reporting line, decision rights and guardrails, including whether cloud-era governance fits AI spend, prepare run-rate baselines and commitment exposure for M&A and restructuring, and keep measures stable through leadership transitions.
The audience is executives at VP, SVP or EVP level who sponsor the practice. The page calls this a FinOps Enabled Executive, a senior leader below the C-level, a role the foundation set out in a December 2025 post.
The maturity criteria show what moving up looks like. At Crawl there is a sponsor and at least one Scope, often public cloud, with informal boundaries, and FinOps is brought in late. At Walk, Scopes span categories and map to executive priorities, and definitions connect to finance and ITFM processes. At Run, Scopes are the standard lens for strategy, funding and accountability, and FinOps is a required input to strategic investments.
Most of the KPIs measure decisions rather than savings. Scope-level measures include the share of decisions with option comparisons covering cost, risk, timing and quality, and the follow-through rate on agreed actions.
The capability's personas section gives Finance and Procurement specific jobs. Finance brings ITFM reporting in line with FinOps views and defines shared-cost allocation rules. Procurement plans renewals and commitments from FinOps forecasts.
Which technology categories does the framework now cover?
The technology categories section has five pages: Public Cloud, SaaS, Data Center, Data Cloud Platforms and AI. The section says each page covers considerations for defining Scopes, how capabilities apply, which personas are involved, KPIs, and how that category's data can be unified with the FOCUS specification. The overview graphic also shows Private Cloud and Licenses, but as of November 2026 neither has its own page in that section.
The pages also say where FOCUS doesn't yet fit. The Data Center page adapts FOCUS columns to on-premises use, with Region pointing to the physical data center and billing periods considered against the amortization period. The AI page says FOCUS has no AI-specific columns yet, so token charges show up through SKU IDs and consumed quantity.
The expansion matches what practitioners report. State of FinOps 2026 drew 1,192 respondents representing more than $83 billion in annual cloud spend. Of those, 98% manage AI spend and 90% manage SaaS or plan to within a year; 64% manage licensing, 57% private cloud and 48% data center.
Where does the 2026 framework overlap ITFM and TBM?
In our reading, mostly through ITFM. IT financial management is one of five allied personas, alongside ITAM, ITSM, security and sustainability, and the Executive Strategy Alignment Walk stage expects definitions connected to finance and ITFM processes. State of FinOps 2026 reports that FinOps shares data with ITFM more often than with any other discipline. Neither the Executive Strategy Alignment page nor the Intersecting Disciplines page names TBM.
The Intersecting Disciplines capability says its point is not to get organizations to adopt those disciplines, but "rather to prepare FinOps teams to work with those already in place." For how ownership should split between the two, see TBM vs FinOps.
What should a FinOps lead do differently this year?
In our view, five things follow from the 2026 text:
- Organize by category, ask by Scope. A team organized by technology category is fine. Set Scopes deliberately across it, for the business questions leadership is actually asking.
- Audit your Scopes. Retire any that answer no live decision. The Scopes page says the aim is not to preserve Scopes for their own sake.
- Find your executive sponsor and the decision cadence. Executive Strategy Alignment KPIs measure whether major investments go through an agreed decision routine. If there is no routine, that is the first gap.
- Agree definitions with ITFM before building new reports. The Walk stage expects definitions connected to finance and ITFM processes. If FinOps and ITFM classify the same SaaS contract differently, the CFO gets two numbers for one invoice.
- Map your multi-year commitments in one place. The framework asks FinOps to avoid overlapping obligations across cloud, SaaS, AI and data center contracts, which is hard when each sits with a different owner.
The 2026 framework asks FinOps to connect spend to strategy, funding and outcomes, which in our view is work that needs one shared operating model across finance, technology and the business, not another report.
Sources
- FinOps Foundation, FinOps Framework 2026: Executive Strategy, Technology Categories, and Converging Disciplines, Vasilio Markanastasakis, March 19, 2026
- FinOps Foundation, FinOps Framework 2025, March 20, 2025
- FinOps Foundation, FinOps Framework 2024, March 21, 2024
- FinOps Foundation, Mission update, J.R. Storment, February 19, 2026
- FinOps Foundation, The FinOps Enabled Executive, J.R. Storment, December 8, 2025
- FinOps Foundation, FinOps Framework overview, accessed November 2026
- FinOps Foundation, Manage the FinOps Practice domain, accessed November 2026
- FinOps Foundation, Executive Strategy Alignment capability, accessed November 2026
- FinOps Foundation, FinOps Scopes, accessed November 2026
- FinOps Foundation, Technology Categories, including Data Center and AI, accessed November 2026
- FinOps Foundation, Intersecting Disciplines capability, accessed November 2026
- FinOps Foundation, Governance, Policy & Risk capability, accessed November 2026
- FinOps Foundation, Onboarding Workloads capability (legacy page), accessed November 2026
- FinOps Foundation, State of FinOps 2026, released February 19, 2026
Frequently asked questions
What is new in the FinOps Framework 2026?
A new capability, Executive Strategy Alignment, in the Manage the FinOps Practice domain. Scopes guidance is rewritten around business-driven segments of spend, while Public Cloud, SaaS, Data Center, Data Cloud Platforms and AI become technology categories with their own pages. Six capabilities are renamed to drop cloud-only language, and the mission now refers to the value of technology.
What is the difference between a Scope and a technology category?
A technology category is the type of technology, such as public cloud, SaaS or AI. A Scope is a segment of spending across categories, tied to a business construct such as a product, initiative or cost center. The FinOps Foundation frames the category as what the spend is on and the Scope as why the business cares. In the 2025 framework, cloud, SaaS and data center were themselves Scopes.
Does the FinOps Framework 2026 replace ITFM or TBM?
No. The framework lists ITFM as an allied persona, and its Intersecting Disciplines capability says the point is to prepare FinOps teams to work with disciplines already in place, not to get organizations to adopt them. Executive Strategy Alignment does give FinOps a role in multi-year planning and budgeting, which in our view overlaps work IT finance teams already do.
Who is Executive Strategy Alignment for?
Executive sponsors of the FinOps practice, typically at VP, SVP or EVP level, and the FinOps teams that support them. The FinOps Foundation calls this sponsor a FinOps Enabled Executive, a senior leader below the C-level. The capability covers tying spend to strategic priorities, multi-year investment planning, product prioritization, and decision rights and guardrails.
Steve Elliott
Published November 22, 2026
More on FinOps & Cloud
FOCUS, commitments, shared cost.
Keep reading
What State of FinOps 2026 shows, and what it can't
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.
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.