AI has pushed FinOps beyond cloud and into SaaS, licensing, and hybrid infrastructure. This is also changing where FinOps sits in the organization: CIO or CTO instead of finance. At the same time, FinOps has to shift from reactive cost clean-up to proactive governance: bringing cost awareness into the design phase already.
In Part 2, we saw why AI has pushed FinOps beyond cloud into SaaS, licensing, and hybrid infrastructure. That wider scope is also changing where FinOps sits and how it works. More FinOps teams now report into the CIO or CTO organization instead of finance, putting them closer to where decisions are actually made. At the same time, FinOps is shifting from reactive cost clean-up to proactive governance: bringing cost awareness into the design phase, before systems go live, rather than fixing overspend after the bill arrives.
One of the most noticeable changes in recent years is where FinOps sits within the organization. More and more teams are now part of the CIO or CTO organization, rather than reporting into finance. This may seem like a small organizational change, but it has a big impact on how FinOps operates.
But why does it matter whether FinOps reports to finance or to technology leadership? Because, when positioned within the latter, FinOps is much closer to where decisions are actually made. Instead of looking back and explaining past costs, it becomes involved earlier, helping to shape choices around:
This shift makes a real difference. Organizations that actively involve executives see FinOps having significantly more influence over technology. In those environments, FinOps is not just reporting numbers, it is helping guide direction.
The broader market is moving in the same direction. Technology spend, especially around AI, has become a topic discussed at board level. Leaders want to understand:
FinOps increasingly provides the insights needed for those conversations, helping organizations decide where to invest and how to measure returns. As a result, FinOps is turning from a function into a core part of how organizations plan, manage, and steer their technology strategy.
While cost reduction is still an important part of the job, it is no longer enough. The goal is not just to fix problems but to prevent them in the first place. In practice, this means bringing cost awareness earlier into the technology lifecycle. Rather than waiting until a system is live and generating bills, teams are starting to:
This approach is based on a simple idea: it is much easier to avoid unnecessary costs than to remove them later. If you make the right design decision at the start, you don't have to fix it afterwards.
Note that this also creates a new challenge. When costs are prevented before they ever appear, it can be difficult to show the value of that work. There is no "before and after" comparison. Only a smarter outcome that never generated an issue.
The nature of optimization itself is also shifting. The obvious savings from early cloud adoption, such as unused resources or heavily overprovisioned environments, have largely been addressed. What remains are smaller, more complex inefficiencies that are spread across teams and systems. Solving these requires closer collaboration between Finance, IT and Engineering, rather than isolated actions. Because of this, governance is becoming more important than individual optimization efforts. Organizations are investing more in:
The goal is to make sure that spending is always intentional, controlled, and aligned with business priorities.
Moving upstream, shifting left, forecasting instead of reacting - none of this works if the underlying data can't be trusted. And that's exactly the problem ITAM was built to solve. In Part 4, we get specific about the data problem behind FinOps, and why ITAM is the foundation that makes all of this possible.