For most of the past decade, Software Asset Management (SAM) and FinOps have operated as parallel disciplines with minimal overlap. SAM sat within IT, focused on on-premises licence compliance and vendor audit defence. FinOps sat within finance or cloud operations, focused on cloud cost visibility and optimisation. The two teams often did not speak to each other, and the tools they used were entirely separate.
In 2026, that separation has become untenable. The enterprise technology estate is no longer neatly divided between on-premises software and cloud infrastructure. It is a hybrid, constantly shifting landscape where the same vendor — Microsoft, Oracle, IBM, SAP — has products spanning traditional perpetual licences, cloud subscriptions, SaaS agreements, and consumption-based services. Managing cost and compliance in this environment requires a unified discipline that neither traditional SAM nor traditional FinOps, on its own, is equipped to deliver.
How the Convergence Is Happening in Practice
The data reflects a structural shift that is already well underway. The Flexera 2025 State of ITAM Report found that collaboration between ITAM and FinOps teams has increased by six percentage points year-on-year globally, and by 14 percentage points in European organisations. These are not incremental changes. They reflect a fundamental rethinking of how IT cost governance needs to work.
The driver is simple: when the same vendor sells both on-premises and cloud products, and when the commercial terms governing those products are intertwined through enterprise agreements and volume discounts, you cannot optimise one without understanding the other. An organisation that optimises its Azure consumption without accounting for its on-premises Windows Server estate may inadvertently create a licence compliance gap. An organisation that negotiates its Microsoft 365 renewal without considering its Azure commitment risks leaving significant commercial leverage on the table.
The Five Areas Where SAM and FinOps Must Work Together
1. Hybrid licence model management
Most major enterprise software vendors now offer products on multiple commercial models simultaneously. IBM offers both traditional PVU-based licensing and cloud-native consumption pricing. Oracle offers both perpetual database licensing and Oracle Cloud Infrastructure consumption. Microsoft offers both perpetual Office licences and Microsoft 365 subscriptions. In each case, the commercial terms interact — and optimising the total position requires understanding both dimensions simultaneously.
2. Vendor commercial review cycles
Enterprise agreements are negotiated on commercial cycles — typically annual or multi-year — that rarely align between the SAM and FinOps domains. A SAM team negotiating an on-premises ELA may have no visibility into the cloud consumption commitments that the FinOps team is managing, and vice versa. Unified governance means unified commercial review cycles, with both teams contributing to a single, integrated position before any negotiation.
3. Usage data integration
The data required for software licence compliance and the data required for cloud cost optimisation comes from different systems. On-premises deployment data comes from endpoint management and discovery tools. Cloud consumption data comes from cloud provider billing APIs. SaaS usage data comes from vendor portals. Effective SAM-FinOps convergence requires a unified data layer that aggregates these sources and presents a single view of technology consumption against commercial entitlement.
4. AI tool cost governance
AI tools are creating a new category of complexity that sits squarely at the intersection of SAM and FinOps. AI products are typically consumption-based — priced per token, per API call, or per model inference — but they are deployed through enterprise software relationships and governed by contracts that have SAM-style entitlement structures. Neither traditional SAM nor traditional FinOps is fully equipped to manage this. A unified discipline is required.
5. Audit defence preparation
Software vendor audits do not distinguish between on-premises and cloud deployments. An Oracle LMS audit, for example, will examine the full Oracle estate — including any Oracle technology running on cloud infrastructure, whether in Oracle’s own cloud or in public cloud environments where specific licensing rules apply. Effective audit defence requires the same unified view that effective cost optimisation requires.
Building the Unified Function
Organisations at the leading edge of this convergence are creating unified Technology Business Management functions that sit above both SAM and FinOps and provide an integrated view of technology spend, compliance, and commercial exposure across the full estate.
The talent profile for this function is different from either traditional SAM or traditional FinOps. It requires people who understand licence metrics and contract interpretation, who can work with cloud billing data and optimisation levers, and who can engage as commercial peers with major vendor account teams. That profile is rare in the market, which is one of the primary reasons organisations are turning to specialist advisory firms to fill the gap.
For organisations building this function, the ITIL framework for IT asset management provides useful structural guidance on integrating asset management into broader IT governance — though it requires adaptation for the cloud and AI dimensions that traditional ITIL frameworks do not fully address.
The commercial case for investment is straightforward. McKinsey’s research on technology budget recalibration found that top-performing organisations consistently have technology leaders deeply integrated into enterprise strategy — and that the most effective technology cost management is achieved when commercial and operational technology governance are genuinely aligned. The convergence of SAM and FinOps is the operational expression of that alignment.
Conclusion
The organisations that build a unified SAM-FinOps capability in 2026 will have a structural commercial advantage over those that continue to manage on-premises and cloud spend in isolation. The technology estate is hybrid — and the governance model must be too. The investment required is real, but it is dwarfed by the savings available to those who make it.
