ITAM and FinOps: Why it’s time these two worlds collide
31st March 2026
Sean Robinson
Blog,
IT asset management (ITAM) teams focus on software governance, licensing, and compliance. FinOps teams focus on cloud usage, cost visibility, and financial accountability. But both aim to answer the same question: are we getting value from our technology spend?
Yet they often approach that question separately. As cloud, SaaS, and hybrid infrastructure continue to grow, that separation makes less sense.
Two disciplines with a shared goal
At their core, ITAM and FinOps both exist to bring control and transparency to technology costs.
ITAM traditionally manages software licences, vendor contracts, and compliance risk. It helps organisations understand what they own, what they are entitled to use, and where licensing exposure may exist.
FinOps focuses on the financial management of cloud services. It gives organisations better visibility into consumption-based spending and helps teams optimise how resources are used.
Although they evolved from different areas of IT, the objectives are closely aligned. Both rely on accurate data, clear ownership, and continuous optimisation. Both help organizations make smarter financial decisions about technology.
If you’re exploring how FinOps fits within software asset management, our article An Introduction to FinOps: Understanding FinOps in SAM explains the foundations of the practice.
The risk of managing them separately
When ITAM and FinOps operate in isolation, organisations rarely see the full financial picture.
A typical cloud workload can involve infrastructure costs, licenced software, and subscriptions purchased through a cloud marketplace. FinOps may track the infrastructure spend, while ITAM monitors the licence entitlement. But neither team necessarily sees how those costs interact.
This disconnect can lead to inefficient decisions. Cloud environments may be technically optimised but still carry unnecessary licencing costs. SaaS applications may be purchased without visibility of existing software investments. Different teams may adopt tools that duplicate capabilities already available elsewhere in the organisation.
The result is fragmented optimization. Costs are reduced in one area while overspending continues in another.
IT and SAM news delivered straight to you
Why convergence is becoming inevitable
As organizations adopt more cloud and SaaS services, the boundaries between infrastructure, software, and subscription costs continue to blur.
This shift is already driving closer collaboration between FinOps and ITAM teams. Both depend on similar data sources, including asset inventories, SaaS usage data, vendor agreements, and cloud billing information. When these insights are combined, organizations gain far better visibility into technology spend.
It also supports stronger financial planning. When licensing commitments, cloud usage patterns, and SaaS subscriptions are analyzed together, organizations can make more informed decisions about renewals, migrations, and optimization initiatives.
Want to explore further? We look at this growing relationship further in our blog The Future of FinOps and SAM.
Building collaboration between ITAM and FinOps
Bringing these practices together does not require a major organizational overhaul. In most cases, progress starts with better collaboration and shared visibility.
ITAM and FinOps teams should be working from the same core datasets, including asset inventories, license entitlements, SaaS subscriptions, and cloud billing data. When these sources are connected, organizations gain a clearer view of how technology spending flows across the estate.
Just as importantly, optimization efforts should be aligned. Cloud cost initiatives often affect software licensing, and licensing decisions can influence how workloads are designed. Without collaboration, those decisions risk working against each other.
Many organizations also benefit from shared governance structures that bring together finance, engineering, ITAM, and FinOps stakeholders. Technology spending now spans multiple teams, and effective financial management requires input from all of them.
If you’re building the case for stronger FinOps practices internally, our blog on developing business cases for FinOps provides a helpful starting point
Let’s continue the conversation
ITAM and FinOps are moving closer together as organizations look for better control of technology spend. If you’re exploring how these disciplines can work together in practice, our FinOps resources provide deeper insight into the frameworks and challenges involved.
Browse the full FinOps series here 👉
Contact us to find out more








