The May 2025 Shift: What Changed

In May 2025, at the FinOps X conference, the FinOps Foundation released a redefined framework—the first major architectural revision since the discipline was formalized in 2019. The headline change was not a new tool or methodology. It was a single word: Scopes.

FinOps Scopes are defined segments of technology-related spending to which FinOps practitioners apply FinOps concepts. The framework now recognizes three initial Scopes: Public Cloud, SaaS, and Data Center.

"Scopes are the structural change that makes multi-domain FinOps possible. For the first time, the framework acknowledges that cloud is not the only technology spend category that requires rigor."

This is more significant than it appears. Here's why: the old FinOps framework treated cloud infrastructure as the primary focus. SaaS, data center, and AI spend were treated as secondary—nice-to-haves if your organization had the capacity. The 2025 framework inverted this: Scopes are co-equal. Public cloud, SaaS, and data center are now treated with the same rigor and governance.

Why? Because the data shows enterprises spend only 30-40% of their technology budget on public cloud. The rest is spread across SaaS (often 20-30%), data center infrastructure (20-25%), licensing (15-20%), and increasingly, AI consumption. Without a framework that covers all Scopes, FinOps teams are optimizing 40% of the budget while leaving 60% unmanaged.

What Are FinOps Scopes? Technical Definition

A FinOps Scope is a defined segment of technology-related spending. The framework defines Scopes by the type of infrastructure, not the vendor. Three core Scopes are formalized:

Scope 1: Public Cloud

Infrastructure-as-a-Service and Platform-as-a-Service consumption from hyperscalers: AWS, Microsoft Azure, Google Cloud, Alibaba Cloud, IBM Cloud. Includes compute, storage, networking, databases, and managed services.

Scope 2: SaaS

Software-as-a-Service consumption: Salesforce, Workday, ServiceNow, Microsoft 365, Slack, Figma, Datadog, etc. Any vendor-managed software where the enterprise purchases seats, licenses, or usage-based consumption.

Scope 3: Data Center

On-premises or colocation infrastructure: private cloud, virtual machines hosted in data centers, bare metal servers. Includes both capital expenditure (CapEx) and operational expenditure (OpEx).

The framework also flags a de facto fourth Scope emerging: AI Consumption. While not yet formally defined, 98% of FinOps teams now manage AI spend (tokens, LLM requests, GPU compute). The FinOps for AI certification launched in 2025 signals that AI is moving toward formal Scope status.

Why "Cloud+" Is More Than Just a Marketing Term

The term "Cloud+" emerged in 2024 to describe the reality of enterprise technology spend. It means: cloud infrastructure plus SaaS plus AI plus licensing, governed under one FinOps framework.

Why is this important?

1. Financial materiality. For Fortune 500 companies, SaaS spend is often equal to or greater than public cloud spend. Ignoring half your technology budget is not acceptable governance.

2. Operational alignment. The same teams managing cloud cost allocation, chargeback, and governance need to apply the same rigor to SaaS. The tools, processes, and accountability models need to be consistent.

3. Data leverage. Consolidated cost data across public cloud, SaaS, and data center gives procurement teams the leverage to negotiate vendor contracts. "Here is our detailed usage data for Salesforce, AWS, and our data center infrastructure. Based on this, we want X% discount." The data is the negotiation tool.

4. Organizational alignment. When finance, engineering, and procurement operate from the same cost data (not separate spreadsheets), negotiations are more effective and cost governance is more rigorous.

Cloud+ is not a new category of technology. It is the operational model that treats all technology spend categories with equal rigor.

The Three Core Scopes Explained in Depth

Public Cloud Scope: The Mature Foundation

Public cloud FinOps is now mature. The practices are well-defined: cost allocation via tagging, commitment management (Reserved Instances, Savings Plans), rightsizing recommendations, anomaly detection, forecasting, and chargeback.

The 2025 framework does not change public cloud FinOps—it codifies it as Scope 1 and makes it the baseline for all other Scopes. Any enterprise implementing multi-Scope FinOps should start with public cloud visibility and governance, then expand to other Scopes.

Key capabilities: tagging, cost allocation, commitment optimization, usage forecasting, anomaly alerting, chargeback, discount negotiation.

SaaS Scope: The Rapidly Maturing Second Frontier

SaaS FinOps adoption is accelerating. The State of FinOps 2025 reported that 65% of organizations managed SaaS spend—by 2026, that number is 90%. Why the rapid adoption?

  • Financial impact: Typical enterprise SaaS optimization finds 25-35% waste (unused licenses, duplicate tools, underutilized seats).
  • Simplicity: SaaS cost models are simpler than cloud (seat-based, not variable compute). Standardization is easier.
  • Negotiation leverage: Detailed usage data gives procurement teams immediate leverage in SaaS renewals.

SaaS FinOps applies the same Crawl/Walk/Run model as public cloud: visibility, optimization, governance/chargeback. The implementation is often faster (3-4 months to Crawl, 6-9 months to Walk).

Key capabilities: license inventory, usage metering (via SSO logs, APIs), waste identification, seat optimization, renewal workflows, consolidation, procurement integration.

Data Center Scope: The Long-Tail Challenge

Data center FinOps is the most complex. On-premises infrastructure is often the most opaque: legacy contracts with fixed pricing, long renewal cycles, unclear allocations across business units.

FinOps practices for data center include:

  • Cost allocation: Attribute data center costs to owning business units (often based on power consumption, rack space, or custom allocation models).
  • Depreciation tracking: Equipment depreciation vs operating costs; lease vs buy analysis.
  • Utilization optimization: Server consolidation, decommissioning underutilized equipment, power management.
  • Migration planning: Use FinOps data to inform decisions about moving workloads to public cloud.

Data center FinOps is less developed than cloud or SaaS. Most enterprises are still in Crawl phase (cost visibility). Walk and Run phases will mature over 2026-2027.

FOCUS 1.2: The Data Standard That Makes Multi-Scope Possible

FinOps without standardized billing data is impossible at enterprise scale. This is where FOCUS comes in.

FOCUS (FinOps Open Cost and Usage Specification) is the open standard for cost and usage data. FOCUS 1.0, released in 2024, defined a unified schema for public cloud billing. FOCUS 1.2, released in 2025, extended this to SaaS and PaaS.

Why does FOCUS matter? Imagine integrating billing data from AWS, Azure, Salesforce, Workday, ServiceNow, and your data center billing system. Each uses different schemas, units, account hierarchies, and line-item definitions. Without standardization, integration is a custom engineering project for each enterprise—and reconciliation is error-prone.

FOCUS 1.2 solves this by defining a common schema:

  • Unified structure: All billing data—cloud, SaaS, PaaS—follows the same column structure
  • Invoice ID: Links each cost line to the original vendor invoice (enables reconciliation)
  • Billing account hierarchy: Parent/child relationships (organization, account, sub-account)
  • Usage standardization: Consistent units across different cost types (compute hours, requests, seats, etc.)
  • Amortization: Upfront costs (RIs, Savings Plans, SaaS annual licenses) are amortized over the commitment period
  • SaaS fields: Seat count, license keys, contract term, renewal dates

For enterprises, FOCUS 1.2 adoption is critical. It enables unified dashboarding, consolidated chargeback, and vendor-agnostic cost optimization.

AI and FinOps: The Emerging Fourth Scope

AI is becoming a material cost category for most enterprises. In the State of FinOps 2026, 98% of teams manage AI spend. The top challenge? Visibility.

Unlike public cloud or SaaS, AI spend is often invisible. A data science team spins up a Jupyter notebook using OpenAI API. A machine learning pipeline makes 1M calls to Anthropic Claude. A product team embeds an LLM into a feature. Without instrumentation, all of these costs are either completely hidden or buried in an aggregate cloud bill.

The FinOps for AI certification, launched in 2025, signals that AI is moving toward formal Scope status. Key practices:

  • Instrumentation: Tag every LLM call, model invocation, and GPU job with business unit, project, application, and model type
  • Cost allocation: Attribute AI costs to owning team; use metering to track token consumption per application
  • Anomaly detection: Alert on unusual spikes in API calls or token usage
  • Governance: Rate limits per application, approval workflows for new AI projects, cost caps
  • Optimization: Model selection (cheaper models vs expensive models), batch processing vs real-time, caching, prompt optimization

AI FinOps is nascent but maturing fast. Enterprises should plan for AI cost visibility and governance in 2026 Q2/Q3.

SaaS FinOps: What Practitioners Need to Know Now

SaaS FinOps is the most immediately actionable Scope for most enterprises. Here's what you need to know:

The SaaS Waste Opportunity

Typical enterprise SaaS audits find:

  • 30-40% of licensed seats are unused or inactive
  • 20-25% of tools are duplicates (same function licensed across business units)
  • 15-20% of licenses are on higher tiers than usage justifies
  • 10-15% of subscriptions are zombie licenses (renewed but never used)

Practical SaaS FinOps implementation takes 4-6 months and typically recovers 20-30% of annual SaaS spend in waste alone.

The SaaS FinOps Workflow

Crawl (Month 1-2): Inventory all SaaS contracts, map to actual users via SSO logs, identify waste.

Walk (Month 2-4): Right-size licenses, consolidate duplicates, implement chargeback, begin renewal review process.

Run (Month 4+): Quarterly renewal reviews, ongoing adoption tracking, procurement leverage during negotiations.

Implementation Implications: Extending Your FinOps Practice

If you have existing cloud FinOps, expanding to multi-Scope requires:

  • Tooling expansion: Your cloud FinOps tool likely handles only cloud. You need SaaS management tools (Zylo, Vendr, Apptio), AI cost tools (Lakera, Vellum), and data center costing models.
  • Data standardization: Adopt FOCUS 1.2 or migrate to a tool that supports it. Do not build custom ETL pipelines.
  • Team expansion: Add SaaS manager, AI cost engineer, data center analyst to your FinOps CoE.
  • Governance evolution: Expand chargeback, forecasting, and approval workflows to cover all Scopes.
  • Timeline: 6-12 months to add SaaS and AI Scopes to existing cloud FinOps. Data center is 12-18 months.

What This Means for Procurement and Negotiation

Multi-Scope FinOps data is the single most valuable input to vendor negotiations.

Example: Redress Compliance helped a Fortune 500 financial services firm set up multi-Scope FinOps. The result:

  • AWS negotiation: Detailed usage data revealed 30% unused capacity. Negotiated 20% discount on full-year commitment.
  • Salesforce renewal: Usage data showed 200 inactive seats. Negotiated 15% reduction in seat count and added 5% volume discount.
  • Workday renewal: Detailed cost per transaction analysis revealed cost overruns in two business units. Renegotiated to usage-based pricing, saving 18%.

Total impact: $4.2M in savings across cloud, SaaS, and data center over 24 months. The FinOps data was the leverage.

Ready to expand to multi-Scope FinOps?

Our FinOps Cloud+ advisory services help organizations implement Scopes across public cloud, SaaS, AI, and data center.
Explore FinOps Cloud+ Advisory Services →

Six Recommendations for Implementing Scopes

1. Start with SaaS, not data center. SaaS FinOps matures faster (4-6 months to value), and the ROI is immediate (20-30% waste reduction).

2. Adopt FOCUS 1.2 early. Do not build custom cost schemas. FOCUS 1.2 is the standard; most tools now support it. Make it a requirement in your tooling decision.

3. Unify data, not tools. You may use different tools for cloud, SaaS, and AI—that is fine. But all data should flow into a unified cost hub that follows FOCUS 1.2, enabling consolidated reporting and chargeback.

4. Implement FinOps before procurement negotiations. Build cost visibility for 3-4 months before going to vendors. Detailed data is the leverage; using it without preparation weakens your position.

5. Invest in the team. Multi-Scope FinOps requires a cross-functional CoE: finance, engineering, SaaS manager, procurement, and AI cost engineer. Budget 6-8 FTE for full implementation.

6. Crawl, Walk, Run is sequential, not parallel. Get visibility before optimization. Get optimization before automation. Rushing leads to poor decisions based on incomplete data.

Stay ahead of FinOps trends

Get weekly FinOps updates, Scope implementation guides, and procurement negotiation strategies delivered to your inbox.