When we hear the term ‘FinOps’, the first thought is often cloud cost control. In practice, it must encompass managing total technology value across the IT landscape—private cloud, on-premises infrastructure, SaaS, licensing, and AI.

The FinOps framework has evolved to Business Value driven decision & Collaborative Accountability.

In March 2025, the FinOps Foundation described the Cloud+ era, where FinOps responsibility extends well beyond the cloud bill and includes ownership across domains such as IT financial management (ITFM), IT asset management (ITAM), software asset management (SAM), sustainability and security, driven by the principle that business value guides technology decisions.

SaaS is hiding in plain sight

Generally, it has been observed that most organizations are aware of only a fraction of the SaaS applications in use, rest auto-renew. Licenses sit unused. Overlapping tools serve the same function in different departments. No one has a full picture. Resulting SaaS to sit quietly outside the FinOps conversation and inflating the Organization Bill. While the same principles that brought order to cloud billing, shared visibility, cross-functional accountability, data-driven decisions, apply directly to SaaS as well.

AI infrastructure is the next cost shock and guardrails aren't ready

AI is already embedded in daily operations and is scaling rapidly. The challenge is no longer just volume, but the economics of the underlying infrastructure. Inference costs vary by model, prompt length, and the number of API calls an application makes. A product team can accumulate material spend before anyone notices and traditional cost management tools were never designed to catch it.

This is where AI cost guardrails matter. They enforce usage limits before models move into production, guide model selection based on cost to value fit rather than capability alone, and introduce token budgets, spend alerts, and policy-driven controls. These are not optional enhancements; they are the minimum viable governance for AI infrastructure. Without them, AI risks becoming the next unmanaged cloud.

Unit economics: Value driven expenditure

Total technology spend is a number. It doesn't tell you whether that expenditure is good or bad. Unit economics does; Cost per transaction, Cost per inference, Cost per active user, Cost per feature. These metrics connect technology spending to business outcomes.

The FinOps Foundation calls this "quantifying business value” one of the framework's four core domains. It means connecting usage and cost data to what the organization is trying to achieve. Without unit economics, optimization is guesswork. You can cut spending without knowing if you're cutting value.

This is the point most FinOps implementations miss. The goal isn't spending less. It's spending right. Unit economics is how you know the difference.

Showback before chargeback. Always.

It has been observed that organizations want to jump straight to chargeback, allocating costs back to the teams that generated them. The logic is correct: accountability requires ownership. But chargeback without visibility is punishment without understanding.

So, I think teams should be given a clear, honest view of what they're spending without the financial hit. Once teams understand their spending, chargeback becomes a natural extension of existing accountability. Without that foundation, it's just friction.

The savings no one is chasing: contracts and commitments

I have seen that most FinOps conversations focus on the engineering side, right-sizing resources, eliminating idle capacity, using spot pricing. That of course matters. But there's more to it that needs attention: Reserved capacity commitments, Enterprise discount agreements, SaaS contract renewals negotiated at the wrong volume or the wrong time, multi-year commitments locked in before usage patterns stabilized.

These are commercial and procurement decisions, and they can represent material cost reduction.

Governance: centralized policy, federated action

There are two ways FinOps governance fails.

• Pure centralization creates a bottleneck, a central team that owns every decision and can't keep up.
• Pure federation creates chaos, every team running its own practice with no shared standards.

So, there has to be the right mix of the above two, with setting the rules once centrally, so that every team works from the same playbook. And with individual teams owning their budgets, they see their costs in real time and make decisions within a governance framework.

Dashboards don't reduce costs. Decisions do.

Most FinOps tools today are excellent at showing what is happening. But when spending reports are merely reviewed in meetings and then archived, they add little value in helping teams decide what to do next.

The transformation requires decisions, not dashboards. It also requires tooling and visibility that covers the full hybrid estate, including private cloud and SaaS usage.

Finance, IT, and Engineering need to be in the same room

FinOps is not an IT function. It's not a finance function. It doesn't belong to engineering. It belongs to the conversation between all three. The FinOps Foundation lists six core personas: practitioners, engineering, finance, product, procurement, and leadership. All of them are in scope. FinOps does not require a single owner, but a structure that forces the right conversations and collaborations to happen, regularly among the mentioned teams.

What needs to change now

• Stop defining FinOps as cloud cost management. It is technology value management. The scope is broader, and the tools, teams, and practices need to match it.
• Build AI cost guardrails before the spend becomes unmanageable. Set budgets per model, per use case, per team. Measure cost per inference. Choose models based on right fit, not just capability.
• Move from dashboards to decisions. Invest in the governance and cross-functional structure that turns visibility into action. A FinOps practice without decision rights is just a reporting function.
• Treat contract optimization as a FinOps function, not a procurement afterthought. Reserved capacity, enterprise agreements, and SaaS renewals are FinOps work. The savings are real and they don't require engineering effort.

FinOps was always about balancing cost control with value. It’s time to act like it.

Organizations that arrive here sooner will operate with a clear advantage. Not because they'll spend less though they probably will. But because they'll understand what their technology is worth, across every layer of the stack, and they'll make better decisions because of it.

That, from my perspective, is what FinOps is about, not just cost control, but business value management as well.