The buildup

With the introduction of Scopes in late 2024, the FinOps Foundation signalled their intent to take FinOps beyond the cloud. The 2025 Framework saw Scopes officially added, and the word “cloud” replaced with “technology” in many places. Early 2026 saw an update to the FinOps Foundation Mission from:

“Advancing the People who manage the Value of Cloud”

to

“Advancing the People who manage the Value of Technology”

And the official definition of FinOps is now:

“FinOps is an operational framework and cultural practice which maximizes the business value of technology, enables timely data-driven decision making, and creates financial accountability through collaboration between engineering, finance, and business teams.”

Additionally, the definition of a “FinOps Scope” has been updated:

“A FinOps Scope is a defined segment of spending across technology categories, aligned to business constructs, such as products, cost centres, or environment that guide the application of FinOps to maximise technology value.”

1 New 2026 FinOps Framework https://www.finops.org/framework/

Changes to Framework Capabilities

The 2026 Framework brings new and updated Framework capabilities. There are still 22 capabilities, but some have been updated, and there is one new entrant, too:

Name Changes

Most of these changes reflect the continued move away from a “cloud-only” lens. Dropping the word “cloud” is the clearest signal that FinOps is now positioning itself as a cross-technology discipline, spanning SaaS, licensing, data centres, and AI consumption models.

The addition of “risk” to “Policy & Governance” suggests a deliberate shift towards closer alignment with adjacent functions such as ITAM, security, and enterprise risk. This change elevates FinOps from cost optimisation alone to a more balanced view that includes compliance, contractual exposure, and operational risk.

Merging “Architecting for Cloud” and “Onboarding Workloads” appears. In practice, these activities are tightly coupled, and the updated naming better reflects real-world decision-making, where workload placement is evaluated across multiple environments rather than assuming cloud as the default destination.

Removing “FinOps” from “Tools & Services” may indicate that this capability is no longer confined to specialist FinOps tooling. Instead, it recognises a broader ecosystem that includes ITAM platforms, procurement systems, observability tools, and SaaS management solutions, reinforcing the idea that FinOps is becoming an integrated discipline rather than a standalone function.

Taken together, these naming changes are less about semantics and more about signalling intent. They reinforce the direction of travel towards a more holistic, enterprise-aligned FinOps model that integrates more naturally with existing governance, architecture, and financial management practices.

A Brand-New Capability

Although the total number remains 22, we have a new FinOps Framework Capability:

Executive Strategy Alignment

The definition from the Foundation says:

“Executive Strategy Alignment connects technology-related spend, usage and adoption to the organisation’s business strategy and priorities, helping leaders compare options, make trade-offs, and govern investment for value.

This guidance is intended for executive leaders, typically one level below C-level (VP, SVP, or EVP), who shape and sponsor the FinOps practice to support strategic outcomes.

It is also for FinOps teams partnering with executive leaders to support executive strategy alignment of technology-related spend through clear decision support, shared accountability, and business-relevant measures.”

This capability is focused on driving the principle “Business value drives technology decisions” and is about linking technology spend to business strategy – something that should be a key goal of all FinOps (and ITAM) teams.

See more here - Executive Strategy Alignment FinOps Framework Capability

Technology Categories

New for 2026, Technology Categories provide “guidance on how FinOps Capabilities, Personas, and measures of success apply within that category”. The current categories are:

• FinOps for Public Cloud
• FinOps for SaaS
• FinOps for Data Centre
• FinOps for Data Cloud Platforms
• FinOps for AI

*Data Cloud Platforms includes products such as Snowflake, Databricks, and Google BigQuery.

These are to help organisations define where their spend sits via technology type – and organisations may well informally create sub-categories as required.

See more here - FinOps Technology Categories

When is more too much?

Expanding the scope of FinOps raises 2 immediate questions:

• How much can FinOps realistically cover before it loses focus as a discipline
• How much more can FinOps practitioners cover before burning out and/or dropping several balls?

If FinOps practitioners become responsible for cloud, SaaS, software licensing, AI, and data centre, that is effectively the entire technology spend landscape. That is a big ask for any single function – especially as technology use continues to grow.

There is also a capability gap. FinOps practitioners are very strong on public cloud economics but, in most cases, have limited exposure to:

• Licensing metrics
• SaaS contract models
• Commercial negotiation
• Business case development

Those skills sit elsewhere today, such as ITAM or procurement. The 2026 framework assumes all these areas and skills can be pulled together within an organisation, but most organisations are not structurally set up to deliver this. 

FinOps teams are not growing, and days are not getting any longer – how are they expected to:

• learn the new rules/metrics etc.
• build the required processes 
• keep up with the ongoing management and reporting requirements 

across all these new areas? There needs to be increased investment in hiring and upskilling of FinOps practitioners and/or a thoughtful, considered approach to better integrating existing internal teams. 

Really, organisational redesign is needed. If you have separate ITAM & FinOps teams, perhaps a new “Technology Value Management” team with clearly defined shared goals and a single path into leadership is the way forward?

In practice, we rarely see FinOps teams with meaningful insight into license-based SaaS contracts and usage…just as we rarely see ITAM teams with meaningful insight into cloud-based SaaS data platforms. Most organisations still separate licensing, procurement, and cloud economics but the updated FinOps Framework assumes they don’t…or is perhaps challenging them to change that in 2026 and beyond.

At Synyega, we've long advocated for a converged approach to technology value management - one that brings FinOps, ITAM, Procurement, and GreenOps together around shared goals rather than parallel silos. The real opportunity is organisational. If the 2026 FinOps Framework prompts leadership to rethink how these functions are structured and resourced, it could mark the beginning of something genuinely useful. If it doesn't, expect the same practitioners to simply have a longer list of things they can't quite keep up with.

None of this should be read as criticism of the direction of travel for practitioners. The shift to business value, executive alignment, and cross-technology applicability reflects where organisations need to go.

The challenge now is not whether this vision is correct, but how it is realised in practice. Bridging that gap between ambition and execution within customer organisations is where the real work begins. As for how this new Framework aligns with TBM, that’s a separate article…