Cloud spending continues to rise, but waste remains a stubborn issue. Global spending on cloud infrastructure services reached $102.6bn in the third quarter of 2025, growing 25% year on year as enterprises moved from early artificial intelligence experiments towards large-scale deployment.
At the same time, priorities are changing. As cloud environments grow in scale and complexity, organisations are placing greater scrutiny on how infrastructure spending is managed and controlled. The market for FinOps tooling has grown in parallel, but more choices do not always translate to clarity.
The question for 2026 is not whether a company has a FinOps tool, but whether that tool is fit for purpose.
Beyond tracking the bill
Early FinOps practices were designed to track spend. While this remains true today, it’s no longer enough, as retrospective reporting does usually not prevent overspending.
As the business world evolves, tools should evolve with them, and instead of only showing what was spent, platforms should support forecasting, budgeting, and automated governance. These capabilities influence behaviour before the money leaves the account. They allow finance and engineering teams to work with the same data and the same targets, allowing accountability to be spread across the business.
To no surprise, cutting costs is important, but FinOps should also show whether cloud spend is paying off for the business. That means tracking the full journey of an application, from when it’s launched to when it’s retired, and weighing up cost against performance and sustainability.
Many organisations started doing this through unit economics, where costs are broken down per customer, transaction, or service. It gives a clearer picture of value, but only if the data coming from FinOps tools is accurate. Without that, it’s impossible to see whether an application is worth what it costs.
Fragmented tools create blind spots
Cloud-native tools are often the starting point as they are low-cost, accessible, and easy to adopt. But they also stop at the borders of a single provider. Most organisations now run multiple clouds, SaaS contracts and licensing agreements. A tool that only sees part of this picture will often miss these expanding costs.
Point solutions can create similar problems. A forecasting tool here, an anomaly detection service there. It appears manageable at first – but stitching everything together can be slow and difficult to make sense of, which means gaps can creep in and visibility can shrink.
What effective FinOps tooling should deliver
There are a few criteria that separate tools which simply report spend from those that actually help manage it.
Forecasting and budget planning should be accurate enough to support business decisions, not just technical ones. Governance should be automated so that policies apply consistently across teams without needing constant manual oversight. Additionally, allocation models should make it clear which department or application owns the cost, because shared accountability is only possible when responsibility is visible.
Integration matters as much as functionality. FinOps can no longer operate in isolation; they need to connect with IT asset management and licensing systems to provide a more comprehensive view of ownership and usage.
Usability plays a critical role. If engineering teams do not see value in the data, or if the interface is too complex to use daily, the tool is unlikely to deliver meaningful results.
Culture, cost, and collaboration
FinOps is not just a finance project, as it only works when responsibility is spread across functions.
In practise, this means working cross-functionally, and finance needs to see how architectural choices affect budgets. Engineers need access to real-time data that makes costs visible without slowing delivery, and leadership needs to frame this not as a cost-cutting exercise, but as a way to make better use of resources.
That cultural element is also where sustainability comes in. Many organisations already track or plan to track their cloud carbon footprint. That creates an additional layer of accountability: environmental as well as financial. FinOps can provide the framework to bring both together, but only if the tools support it.
Looking to 2026
The landscape is not getting simpler. AI workloads, edge deployments, containers and SaaS all make the picture more complex. Companies that continue to rely on basic cost trackers will remain reactive, spotting waste only after it happens.
The organisations that will succeed in 2026 are those that treat FinOps as more than an accounting function. They will use tools that integrate across the environment, provide accurate forecasting, and connect financial accountability with engineering and operations. They will back this with a culture that shares responsibility for spend.
FinOps is moving fast – adoption is rising, waste is still significant, and priorities are shifting towards efficiency and value. The question for leaders is whether their tooling keeps pace with this shift, or whether it risks leaving them behind.
