FinOps was built for the cloud and stops at the data centre door. ITAM knows the assets and licences underneath. Neither is complete alone — and hybrid cost control needs both working from the same data.
Cloud spending keeps climbing, and keeping it under control has become one of the hardest jobs in IT.
Plenty of organisations turn to FinOps for that. It brings visibility and discipline to cloud costs, and it helps teams understand where the money is going and why.
But FinOps was never meant to work in isolation.
Most enterprises now run hybrid infrastructure, where public cloud and on-premises systems coexist. In that model, cloud costs are shaped by on-premises decisions — licensing, hardware lifecycles, and where a workload is allowed to run.
This is where IT asset management becomes critical. Historically focused on the data centre and on-premises hardware, ITAM now supplies the infrastructure visibility FinOps needs to manage hybrid costs properly.
As hybrid becomes the default, FinOps increasingly draws on on-premises and data centre ITAM. Not as a parallel function, but as a necessary input to cost control.
The FinOps framework came out of a few recurring problems.
There was no centralised control over cloud infrastructure, so nobody could say which department or team should be paying for what. Costs jumped without warning, with workloads scaling faster than finance could track them. Leadership spent too much time reconciling spend against the things actually driving it.
FinOps brought financial maturity and accountability to a genuinely wild problem, and it created stakeholder ownership of resources. But it still runs into difficulty at the on-premises boundary.
That difficulty comes down to data.
Within the FinOps framework, ITAM is described as an allied persona — the function that supplies the asset data FinOps depends on. The problem many businesses have is that the ITAM persona does not have accurate data to hand over, because the tooling underneath it was never built for it.
That leaves a hole in FinOps. Without accurate asset data, there is no oversight of where workloads run or who should be charged for them. And without that, there is no real cost accountability.
ITAM steps in exactly where FinOps struggles, by creating visibility across the physical, virtual and licensed infrastructure underneath a hybrid environment.
It tells teams:
FinOps brings financial understanding. ITAM brings asset understanding. Separately, each gives you part of the picture. Together they give you the whole one, which is what most teams are missing.
This is already happening in practice. FinOps is pulling SAM into scope as cloud-first licensing models collide with on-premises reality — from SaaS and Shadow IT arriving outside procurement, to bring-your-own-licence decisions, to the true cost of running a data centre against running the same workload in cloud.
They look different. They follow the same pattern.
Unused cloud instances and unused laptops both waste money. Over-provisioned services and over-specified machines both inflate budgets unnecessarily. Untracked cloud services and untracked hardware both create security and governance risk.
The scale is not marginal. Wasted cloud spend runs at 29% — and it has risen for the first time in five years.
ITAM has been attacking this on the hardware side for years, by giving teams sight of everything they own so they can manage it. FinOps has more recently taken up the same fight for cloud.
The job now is making the two work together, so the waste gets removed in both places rather than one.
The two aim at the same outcome even though they approach it differently.
FinOps wants clarity and accountability on cloud costs. ITAM wants clarity on devices and software. Both need accurate information, clear ownership and better planning.
Once the teams share data, the guesswork goes. Forecasts get more accurate. Ownership gets clearer. Waste gets much harder to ignore.
FinOps scope is expanding to take in ITAM and SAM for precisely this reason — so teams see one picture of what the organisation runs rather than several sets of costs that never quite reconcile.
Most organisations do not manage cost in one system.
They have a FinOps platform, an ITAM tool, a CMDB, and often a set of spreadsheets filling the gaps between them.
That fragmentation is expensive in a way that rarely appears on any invoice. When cost data sits in one system and asset data in another, simple questions take days. Reports contradict each other. Forecasts drift. Teams repeat work because the systems do not speak the same language.
ITAM and FinOps are not competing approaches. FinOps tracks spend; ITAM tracks the assets and licences that create it.
With FinOps alone you see cloud usage but not the hardware behind it. With ITAM alone you see devices and licences but not the business need, the accountability or the ownership driving the workload.
Start by looking at how the two work in your organisation today. Do they share ownership, reporting and data? If not, begin joining the workflows so both sides make decisions from the same information.
The shortcut is to stop running them on different data models. CerteroX puts ITAM, SAM, SaaS Management, Cloud Management and AI Management on one platform with one schema, so the asset record and the cost record are the same record.
On the cloud side, CerteroX Cloud Management is a FinOps Certified Platform with native support for FOCUS, the FinOps Open Cost and Usage Specification, so your cost model stays portable rather than locked in a vendor schema. It runs 26 named, individually tunable optimisation checks — abandoned instances and load balancers, obsolete snapshot chains, instances stopped but not deallocated, rightsizing, reserved instance and savings plan opportunities — across 12 cloud and data platforms. Certero’s average cloud cost saving across environments under management is 38%.
On the on-premises side, the same platform carries the discovery, the licence position and the lifecycle data that FinOps needs as its input — including publisher-grade licence engines for Microsoft, Oracle, IBM, SAP, Adobe and Salesforce, which is where bring-your-own-licence decisions are actually settled.
One data model, one set of owners, one cost position. That is what makes hybrid cost management tractable.
Book a demo, or read more about cutting cloud waste.
Other posts covering the same ground.
Audit frequency went up, not down, as software moved to subscription. Meanwhile a fixed share of cloud spend is wasted every month. Both are real, and only one of them is a certainty.
Why fragmented hardware and software tracking derails a cloud migration, and what has to be true of your asset data before you start retiring things.
Eight shifts reshaping ITAM through 2025 — from the gap between MDM and true lifecycle management, to multi-cloud visibility, compliance automation, security convergence and workflow orchestration. What each one means, and what to do about it.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.