For years, organizations have treated Software Asset Management (SAM) and FinOps as two separate disciplines. SAM manages software licenses, entitlements, renewals, compliance, and vendor relationships. FinOps manages cloud consumption, allocation, forecasting, commitments, and optimization. That separation may have worked when software lived primarily in the data center and cloud was simply another infrastructure platform. It does not work anymore.
Software has moved into SaaS. Licensing is embedded in cloud infrastructure. Enterprise agreements increasingly include marketplace purchases. Bring Your Own License (BYOL) decisions affect cloud economics. AI introduces consumption costs alongside traditional user licensing.
At the same time, vendors are combining subscriptions, cloud services, security, data, and AI into increasingly complex commercial relationships. Yet many organizations still manage these costs through separate teams, tools, budgets, and strategies. The result is a financial blind spot that can easily become a million-dollar problem.
Learn more about evaluating costs across the entire IT environment—not just individual categories; the effective approach for organizations looking to reduce technology waste.
The Data Shows a Disconnect Between SAM and FinOps
The gap between SAM and FinOps is particularly important because both disciplines are ultimately trying to accomplish something similar: Maximize the business value of technology spending. Yet they often approach that goal independently. In the ITAM research we reviewed, 77% of respondents reported that their organizations had a FinOps team, yet only 32% of SAM teams reported significant interaction with FinOps. Think about what that means.
Organizations have teams managing software economics. They have teams managing cloud economics. But in many cases, those teams are barely working together. That becomes increasingly problematic as the lines between software, SaaS, cloud infrastructure, and AI continue to disappear.
Software and SaaS Waste Remain Significant
Technology waste is not isolated to one category. The research found estimated wasted spend across desktop software, data center software, SaaS, and IaaS/PaaS. Depending on SAM maturity, respondents estimated waste ranging from approximately 18% to 32% across those categories.
SaaS deserves particular attention. 41% of respondents said wasted SaaS spending had increased during the previous year. This is exactly why organizations cannot manage technology costs in silos.
A cloud optimization program may successfully reduce Azure, AWS, or Google Cloud infrastructure costs while the organization continues accumulating millions of dollars in redundant SaaS subscriptions.
A SAM program may optimize Microsoft licensing while overlooking inefficient cloud architecture. Procurement may negotiate a strong SaaS discount without realizing that the same purchase could potentially support an existing cloud marketplace commitment. Each decision might make sense independently. Together, they may produce a completely different financial outcome.
Why License Optimization Is Also Cloud Optimization
The relationship between SAM and FinOps becomes especially important when enterprise software runs in the cloud. Consider Microsoft SQL Server and Windows Server. The cost of running a workload in Azure is not simply the cost of the virtual machine. Licensing rights, Azure Hybrid Benefit, existing entitlements, Software Assurance, architecture, reservations, savings plans, and workload placement can all influence the final economics.
The same concept applies across vendors and cloud platforms. If the FinOps team optimizes infrastructure without understanding software licensing, it may optimize only part of the cost. If the SAM team understands licensing but has no visibility into cloud architecture and consumption, it may miss opportunities to apply existing rights. This is why SAM and FinOps integration increasingly requires a shared optimization model.
The objective should not be to optimize software and cloud separately. It should be to determine the most efficient total cost of delivering the technology capability the business needs.
SaaS Has Become a FinOps Problem Too
SaaS spending deserves the same financial discipline organizations apply to cloud infrastructure. Many organizations now operate hundreds—or even thousands—of applications. Some are centrally purchased. Others are purchased by individual departments. Some arrive through acquisitions. Others are purchased with corporate cards or bundled into larger enterprise agreements. Some duplicate functionality already available elsewhere. And increasingly, SaaS solutions can be purchased through cloud marketplaces.
Traditional SAM questions still matter:
- Who owns the application?
- Who uses it?
- How many licenses do we have?
- When does it renew?
But FinOps introduces another layer of financial questions:
- What is the unit cost?
- How is consumption trending?
- Can demand be forecast?
- Can licenses be dynamically reclaimed?
- Does the contract structure match actual usage?
- Can the purchase contribute toward a cloud commitment?
- Could consolidation improve negotiating leverage?
Suddenly, SaaS optimization becomes much more than license reclamation. It becomes financial engineering.
Cloud Marketplaces Change the Economics of Software Procurement
Cloud marketplaces have created another reason SAM, procurement, and FinOps teams need to work together.
Organizations with significant commitments to Microsoft Azure, AWS, or Google Cloud may be able to purchase eligible third-party software through a provider’s marketplace and have qualifying purchases contribute toward portions of their existing cloud commitments, depending on the provider’s program and agreement terms. That changes the economics of procurement.
Imagine an organization planning to purchase a significant SaaS platform. Procurement negotiates directly with the software vendor and gets a strong discount. On the surface, that looks like a successful negotiation.
But what if purchasing the same solution through an eligible cloud marketplace could also help consume an existing cloud commitment? The lowest purchase price is not always the lowest enterprise cost. This is where contract strategy, SAM, FinOps, procurement, and cloud strategy need to intersect.
Cloud Commitment Waste Is Still Waste
Cloud providers encourage customers to make commitments in exchange for improved economics. Those commitments can provide significant value. But they also create another financial responsibility. Organizations need to make sure they actually consume what they commit to. Otherwise, they can end up negotiating excellent discounts on capacity they never needed.
SAM teams have dealt with this problem for decades. It is essentially the software shelfware problem translated into cloud economics. Buy 10,000 licenses and use 7,000. The unit price might have been excellent. The economics were not. Cloud commitments can create the same problem. Commit to significantly more consumption than the business ultimately requires, and the discount becomes irrelevant.
This is one of the most important lessons SAM can bring into FinOps: Never confuse a discount with savings. Savings only exist when an organization purchases something it actually needs at a better economic outcome.
Software License Reclamation Still Produces Real Savings
Not every IT cost optimization strategy needs to be complex. Sometimes the simplest strategies remain among the most effective. The ITAM research found that 91% of respondents reported savings by reusing licenses rather than purchasing new ones for non-cloud software.
Advanced SAM organizations also reported strong savings through better vendor negotiations and reductions in maintenance spending on unused software. This reinforces an important principle: cost optimization does not always require a major transformation.
Sometimes it means:
- Knowing what you already own before buying more
- Reclaiming unused licenses
- Changing a SKU
- Eliminating an overlapping SaaS product
- Applying existing licensing rights to cloud infrastructure
- Restructuring a contract
- Choosing not to renew something at all
Individually, these decisions may appear small. At enterprise scale, they can represent significant savings.
AI Will Make Technology Cost Management More Complex
The next challenge is AI. Traditional software economics were largely based on users, devices, processors, cores, subscriptions, or capacity. AI introduces another layer of cost. Organizations may soon have traditional software licensing, SaaS subscriptions, cloud infrastructure, AI licenses, and consumption-based AI charges associated with the same business process.
An employee could have a productivity license, an AI add-on, access to several AI agents, and workflows that generate additional consumption charges behind the scenes. That makes the separation between SAM and FinOps increasingly artificial.
The question is no longer simply “How many licenses do we have?” or “How much cloud are we consuming?”. The better question is: What does this technology capability actually cost us to deliver—and what business value are we receiving from it? That shift will become increasingly important as organizations move from experimenting with AI to deploying it across enterprise workflows.
How to Integrate SAM and FinOps
The first step is not necessarily buying another tool. It is connecting the disciplines already responsible for technology economics. Organizations should bring SAM, FinOps, cloud, procurement, finance, architecture, and application owners into the same cost conversations. That means creating shared visibility into software and cloud commitments, coordinating major renewals, and reviewing cloud marketplace opportunities before purchasing large SaaS agreements.
Organizations should also:
- Connect software licensing rights to cloud architecture decisions
- Include SaaS spending in FinOps reporting
- Bring cloud consumption data into SAM decisions
- Coordinate software, SaaS, and cloud contract negotiations
- Track realized savings instead of theoretical savings
- Evaluate commitments against actual and forecasted consumption
- Establish a common definition of technology value
Because saving money in one technology category while creating unnecessary spending somewhere else is not optimization.
It is cost shifting.
The Bottom Line: SAM and FinOps Need a Unified Cost Strategy
Organizations have spent years building SAM programs. They have spent the last several years building FinOps programs. Now those programs need to meet. Software, SaaS, cloud, AI, licensing, marketplaces, and enterprise agreements are becoming too interconnected to manage independently. Organizations that recognize this early will have a significant advantage.
They will negotiate better contracts, make smarter commitments, eliminate more waste, understand their true technology costs, and redirect trapped IT budget toward initiatives that create business value.
At The IT Strategists, we believe technology cost optimization should not be approached as isolated exercises in software, SaaS, licensing, or cloud. It should be one connected strategy for understanding where technology dollars are going, what value they are creating, and where that money can be put to better use.
Because the biggest savings opportunity may not be sitting inside your SAM program or your FinOps program. It may be sitting in the gap between them.
Turn Technology Spend into Business Value
If your SAM, SaaS, cloud, licensing, and FinOps strategies are still operating independently, there may be significant savings hidden between them. Talk to an expert at The IT Strategists to identify technology waste, connect your cost optimization strategies, and build a clearer picture of what your technology investments are actually delivering.
Frequently Asked Questions About SAM and FinOps
What is the difference between SAM and FinOps?
Software Asset Management (SAM) focuses primarily on software licenses, entitlements, compliance, renewals, usage, and vendor management. FinOps focuses on managing and optimizing the financial aspects of cloud consumption. As SaaS, cloud infrastructure, licensing, marketplaces, and AI become increasingly interconnected, the responsibilities of SAM and FinOps increasingly overlap.
Why should SAM and FinOps work together?
SAM and FinOps should work together because software licensing decisions can directly affect cloud costs, while cloud architecture and consumption can affect software licensing economics. Connecting the two disciplines gives organizations a more complete view of technology spending and can help uncover optimization opportunities that separate teams may miss.
How can SAM help reduce cloud costs?
SAM can identify existing software entitlements, licensing rights, unused licenses, contract terms, and programs such as BYOL that may affect the cost of running workloads in the cloud. This information can help FinOps teams evaluate the total cost of cloud workloads rather than infrastructure costs alone.
Is SaaS part of FinOps?
SaaS is increasingly becoming part of the broader FinOps conversation because SaaS spending involves consumption, unit economics, forecasting, utilization, contract commitments, and optimization. Combining traditional SAM practices with FinOps principles can provide greater visibility into SaaS costs and waste.
How do cloud marketplaces affect SAM and FinOps?
Eligible software purchases made through cloud marketplaces may, depending on the provider and agreement, contribute toward portions of an organization’s existing cloud commitments. SAM, procurement, and FinOps teams should therefore evaluate both the purchase price and the broader financial impact before making significant software purchasing decisions.
What is cloud commitment waste?
Cloud commitment waste occurs when an organization commits to more cloud consumption than it ultimately uses. Although a larger commitment may secure a better discount, unused committed capacity can reduce or eliminate the expected savings.
How will AI affect SAM and FinOps?
AI introduces additional licensing and consumption models that may overlap with SaaS, cloud infrastructure, enterprise software, and existing contracts. Organizations will increasingly need to understand the total cost of delivering an AI-enabled business capability rather than managing individual licenses or cloud charges in isolation.
What is the first step toward integrating SAM and FinOps?
Start by creating shared visibility and governance across SAM, FinOps, procurement, cloud, finance, architecture, and application teams. Before adding new tools, organizations should align data, major renewals, cloud commitments, licensing rights, SaaS usage, and definitions of realized savings.