Most organizations discover the problem in a similar way: a finance leader extracts a cloud cost report, flags a spike in software licensing fees, and sends it to the IT Asset Management team. The ITAM team opens their CMDB or SAM tool and finds… nothing that matches. Different categories, different vendors listed, different time periods. Two teams, two systems, two versions of reality. And somewhere in the gap, there’s a six-figure problem that neither team had the authority or visibility to detect alone.
This is the core dysfunction that the convergence of ITAM and FinOps is designed to solve.
IT Asset Management has traditionally lived in IT operations. Its mandate is lifecycle-focused: track hardware from procurement to disposal, manage software licenses to stay compliant with vendor audits, maintain a reliable record of what the organization owns and where it's deployed. The SAM analyst's nightmare is an Oracle audit with an incomplete entitlement record. Their tooling - ServiceNow, Flexera, Xensam - is built around discovery agents, license positions, and contract dates.
FinOps grew out of cloud adoption and typically lives closer to finance or a hybrid cloud team. Its mandate is cost visibility and accountability: make cloud spend legible, allocate it to the right teams, right-size resources, and eliminate waste. The FinOps practitioner's nightmare is an engineering team that spun up a fleet of oversized EC2 instances and tagged them incorrectly. Their tooling - CloudHealth, Apptio Cloudability, native cost explorers - is built around billing data, tags, and showback reports.
These disciplines developed in parallel, not in conversation. Different vocabularies, different KPIs, different reporting cadences, different audiences.
SaaS, hybrid infrastructure, and shadow IT have made the old boundary untenable. Your software spend no longer lives in one place. It's split across vendor contracts in the CMDB, consumption billed through AWS Marketplace, and departmental purchases that bypassed procurement entirely. ITAM sees the entitlements. FinOps sees the billing lines. Neither sees the full picture.
The result: duplicate spend, compliance gaps, and optimization decisions made on half the data.
Two scenarios show up constantly.
A company running SQL Server in Azure has an existing on-premises Enterprise agreement with Software Assurance. ITAM knows about the agreement. FinOps sees Azure SQL spend growing. Without the two talking, the organization keeps paying list rates instead of applying Azure Hybrid Benefit: a difference of 40% or more on eligible workloads, year over year!
The reverse is equally common: a workload migrated to cloud-native tooling, but the on-premises license was never retired. ITAM shows it as active. FinOps shows the cloud service running. Both costs tick along in parallel because no one was looking at both at once.
Beyond those direct savings, unified visibility across on-prem licenses, cloud consumption, and SaaS contracts lets you negotiate better, reallocate faster, and stop paying for things twice.
Start with a shared data model: agree on how to classify assets, tag cloud resources so they map to known applications, and normalize vendor names so "Microsoft Corp," "Microsoft Azure," and "MSFT" resolve to the same entity. That unglamorous work is the foundation everything else sits on.
From there: a joint governance forum - ITAM, FinOps, procurement, and finance in the same monthly review - replaces four separate quarterly reports. Dashboards surface entitlement position and cloud consumption side by side. KPIs expand: from license compliance ratios and cost-per-unit, to metrics like effective license utilization across all deployment types and untracked SaaS spend as a share of total software cost.
|
Three obstacles that derail most programs before they start – and how to overcome them Organizational politics: ITAM and FinOps teams often report to different leaders, own different budgets, and have built their credibility in different directions. Data sharing means giving up some control. Name this tension early and get executive alignment before touching any tooling. Tool fragmentation: Most mature IT orgs have a CMDB, a SAM tool, a cloud cost platform, a procurement system, and a SaaS management layer - none designed to talk to each other. Don't buy another tool. Start by building a shared data layer, even if that's a BI dashboard pulling from both systems. Dirty data: The CMDB has gaps. Cloud tagging is inconsistent. License entitlement records live partly in a spreadsheet. Pick one vendor, one product category, one set of workloads, and build the shared view there first. Prove the value on something small, then expand. |
Pull your top ten software vendors by total spend. Then work through these three questions:
If the answer to any of these is "no" or "I'm not sure," you already know where the gap is. That's your starting point! Not a strategy document, not a tool evaluation. Fix the data problem for one vendor, then use it to make the case for the broader program.