CFO looks at the IT cost report. SAM team reports: “we spent 5M PLN on software licenses this year, optimized 800K PLN.” Cloud team reports: “we spent 8M PLN on AWS/Azure, optimized 1.2M PLN.” CFO asks: “how much do we spend on software TOTAL? On-premise plus cloud? SaaS plus perpetual licenses? Where’s the complete picture?”
Silence. Because there is no complete picture. SAM (Software Asset Management) and FinOps (Cloud Financial Operations) operate in silos. Different teams, different tools, different metrics, different budgets. Yet it’s all software costs - just in different delivery models.
In 2026, the boundary between “licenses” and “cloud” practically disappears. Microsoft sells Office as M365 subscription. Oracle offers BYOL to OCI. Adobe, Salesforce, ServiceNow - all SaaS. Traditional SAM that only looks at perpetual licenses is blind to most software costs. And FinOps that only looks at cloud infrastructure misses the software licenses running in that cloud.
Why do traditional SAM and FinOps operating separately lose money?
“Organizations that implement a robust SAM program can expect to reduce their software spending by up to 30% in the first year.”
— Gartner, Market Guide for Software Asset Management Tools | Source
Duplicate licensing. Company has SQL Server on-premise licenses (perpetual). Simultaneously pays for Azure SQL Database (cloud). Nobody checked if BYOL (Bring Your Own License) could be used instead of paying twice. Because SAM team doesn’t look at Azure, and cloud team doesn’t know about on-prem licenses.
Uncontrolled SaaS sprawl. IT buys Jira, Marketing buys Asana, Sales buys Monday.com - all with corporate card. No central visibility. No optimization (do we need 3 tools for the same thing?). Neither SAM nor FinOps traditionally manages this.
Rightsizing decisions without license context. FinOps sees that VM on AWS is oversized and recommends downsize. But changing VM size can change software licensing on it (Oracle counts per core, downsize = fewer licenses = savings). Without SAM-FinOps connection, this optimization is missed.
True-up surprises. Azure Hybrid Benefit allows using existing Windows Server licenses in Azure, but this must be actively declared. Cloud team doesn’t know about these licenses. SAM team doesn’t know about these VMs. We overpay for licensing in cloud.
Renewal timing mismatch. Enterprise Agreement with Microsoft ends in June. AWS Reserved Instances purchased in January. Lack of coordination = suboptimal commitment decisions.
What is FinOps for Software and how does it differ from traditional SAM?
Traditional SAM focuses on: inventory (what we have), compliance (are we legal), optimization (can we reduce licenses). Mainly on-premise, perpetual licenses.
FinOps focuses on: visibility (what we spend), allocation (who pays for it), optimization (how to reduce waste). Mainly cloud infrastructure - compute, storage, network.
FinOps for Software is convergence: unified visibility of all software costs (licenses, subscriptions, SaaS), allocation to business units, optimization across delivery models (buy vs. rent vs. build vs. SaaS).
Shift from “license compliance” to “software economics.” Compliance is table stakes - you must be legal. But the goal is optimum economic outcome: minimizing Total Cost of Ownership of software while maximizing value.
Lifecycle perspective. From “buy/subscribe/SaaS” decision through deployment, usage, renewal/termination. Holistic view of entire lifecycle.
How to build a unified view of software costs?
Data sources integration. Need to connect data from:
- SAM tool (Flexera, Snow) - on-prem licenses, entitlements
- Cloud cost management (AWS Cost Explorer, Azure Cost Management) - cloud spend
- SaaS management platform (Zylo, Productiv) - SaaS subscriptions
- Procurement/ERP - invoices, contracts, POs
- CMDB/Asset database - infrastructure mapping
Common taxonomy. “Software costs” must be categorized consistently: vendor, product, cost center, project, environment (prod/dev/test), delivery model (perpetual/subscription/SaaS/cloud-native).
Allocation methodology. How to allocate shared licenses? How to split enterprise agreement across departments? How to assign cloud software to business units?
Total Cost of Ownership calculation. Licensing isn’t everything. Support/maintenance, implementation, training, infrastructure to run it, personnel to manage it. True TCO requires all-in accounting.
Unified dashboard. Single pane of glass: “We spent X PLN on software this quarter. Y% is perpetual licenses, Z% is cloud, W% is SaaS. Top 10 vendors. Trends. Alerts.”
What optimizations are possible only with unified view?
BYOL vs. license-included decision. You have Windows Server licenses with Software Assurance. In Azure you can use Azure Hybrid Benefit and pay only for compute. Without unified view - you pay for Windows in Azure PLUS have unused licenses on-prem.
Consolidation across delivery models. Company uses: on-prem Exchange, M365 mailboxes, Google Workspace in one department. Unified view shows: “we’re paying for 3 email systems, we can consolidate to one and save 40%.”
Contract negotiation leverage. “Microsoft, we spend with you annually: 2M PLN perpetual licenses, 3M PLN M365, 1.5M PLN Azure consumption. Total 6.5M PLN. We want enterprise discount.” Leverage from complete picture.
Reserved Instance / Savings Plan alignment with license renewals. RI/SP are commitments. Licenses are commitments. Aligning renewal dates allows negotiating together and avoiding overcommitment.
Shelfware identification across platforms. SAM finds unused perpetual licenses. FinOps finds idle cloud resources. SaaS management finds unused SaaS seats. Unified view: “we have shelfware worth 2M PLN annually across all platforms.”
Build vs. buy vs. SaaS analysis. For new capability: build in-house (infrastructure + dev costs), buy license (license + maintenance + infrastructure), SaaS (subscription). Only unified view allows apples-to-apples comparison.
How to organizationally connect SAM and FinOps?
Option 1: FinOps team expands to include SAM. FinOps team takes ownership of all software costs, including traditional licenses. Pro: single ownership. Con: FinOps may lack license expertise.
Option 2: SAM team expands to include cloud. SAM team expands scope to cloud licensing (BYOL, SaaS spend). Pro: leverage license expertise. Con: SAM may not understand cloud economics.
Option 3: Unified Software Economics team. New team combining competencies. Members from SAM background + cloud background. Pro: fresh start, no legacy silos. Con: organizational change, headcount.
Option 4: Virtual team / governance model. Keep SAM and FinOps separate, but create cross-functional governance with regular syncs, shared KPIs, unified reporting. Pro: less disruption. Con: slower decision making, potential conflicts.
Recommendation: Option 3 or 4 depending on maturity. Mature organizations - unified team. Less mature - start with governance, evolve to unified.
RACI clarity. Who is Responsible, Accountable, Consulted, Informed for: software procurement, license optimization, cloud cost optimization, SaaS management, vendor negotiations?
What tools support unified software cost management?
ITAM/SAM platforms expanding to cloud:
- Flexera One - traditional SAM + SaaS management + cloud cost (through Cloudability acquisition)
- Snow Software - SAM + SaaS + cloud visibility
- ServiceNow ITAM - integration with cloud management
Cloud cost tools expanding to licenses:
- Apptio Cloudability - cloud FinOps + license optimization features
- VMware CloudHealth - multi-cloud + some license tracking
SaaS Management Platforms:
- Zylo - SaaS discovery, optimization, renewal management
- Productiv - SaaS analytics, engagement, optimization
- Torii - SaaS management, workflows
Integration platforms:
- Custom dashboards (PowerBI, Tableau, Looker) pulling from multiple sources
- iPaaS (Workato, Tray.io) connecting data flows
Choice depends on: starting point (SAM-first vs. FinOps-first), vendor ecosystem (Microsoft-heavy vs. multi-cloud), budget, existing tool investments.
How to measure success of unified software cost management?
Cost metrics:
- Total software spend (all models combined)
- Software spend as % of IT budget
- Software spend per employee
- Cost avoidance (savings from optimizations)
- Cost savings (actual reductions)
Efficiency metrics:
- License utilization rate (used vs. owned)
- SaaS engagement rate (active users vs. paid seats)
- Cloud software waste (unused cloud licenses/subscriptions)
- Shelfware value ($ of unused entitlements)
Compliance metrics:
- Compliance gap (under-licensed positions)
- Audit risk score
- Time to remediate compliance issues
Process metrics:
- Time to onboard new software (procurement to deployment)
- Time to offboard unused software
- Contract renewal lead time (% renewed on time with optimization)
Business value metrics:
- Cost per transaction/user/unit of business value
- Software ROI (value delivered vs. cost)
How to choose between perpetual, subscription, SaaS for new software?
Financial analysis factors:
- Perpetual: High upfront, lower ongoing (maintenance ~20%/year). Favorable if: long-term use (5+ years), stable requirements, capital available.
- Subscription: No upfront, predictable ongoing. Favorable if: uncertain duration, need flexibility to scale up/down, OpEx preferred.
- SaaS: No upfront, no infrastructure, vendor manages everything. Favorable if: standard functionality enough, fast deployment needed, no in-house expertise to run.
Hidden cost considerations:
- Perpetual: infrastructure to run it, personnel to maintain, upgrade projects
- Subscription: potential lock-in, price increases at renewal
- SaaS: data portability, integration costs, customization limitations
Strategic considerations:
- Control: on-prem > hosted subscription > SaaS
- Speed to value: SaaS > hosted subscription > on-prem
- Customization: on-prem > hosted subscription > SaaS
- Security/compliance: depends (on-prem control vs. SaaS provider investment)
TCO modeling. Build spreadsheet model: 5-year TCO for each option including all costs. Sensitivity analysis: what if usage changes? What if we need to exit early?
How to manage vendor relationships in unified model?
Consolidated vendor view. How much do we spend with Microsoft total? On-prem licenses + M365 + Azure + Dynamics + GitHub. Unified leverage.
Strategic vendor tiering. Tier 1 (strategic, 80% spend): Microsoft, Salesforce, AWS. Deep relationships, executive sponsorship, annual business reviews. Tier 2 (important): Adobe, ServiceNow. Regular reviews, negotiated agreements. Tier 3 (tactical): Long tail of small vendors. Standard terms, minimal management.
Negotiation playbook per vendor. Microsoft: leverage EA + Azure commits together. AWS: RI/SP + marketplace software deals. Oracle: license optimization + cloud migration leverage.
Contract calendar. All renewals in unified calendar. 6-month lead time for strategics, 3-month for others. No surprise renewals.
Benchmark data. What are others paying for same software? Gartner, IDC, vendor community benchmarks. Negotiate from informed position.
Exit strategy always. For every major vendor: what if we need to switch? Migration path, data portability, contractual exit terms. Reduces lock-in and improves negotiation position.
What does the maturity model for unified software economics look like?
Level 1 - Silos: SAM and FinOps separate. No shared data. No coordination. Suboptimal decisions. Most organizations today.
Level 2 - Awareness: Recognition that integration is needed. Ad-hoc sharing of data. Occasional joint meetings. No unified tools.
Level 3 - Coordination: Regular sync between SAM and FinOps. Shared reporting for leadership. Joint optimization projects. Still separate tools and teams.
Level 4 - Integration: Unified data platform. Cross-trained team members. Joint KPIs. Single governance. Systematic optimization across all software costs.
Level 5 - Optimization: Proactive, data-driven decisions. Predictive analytics. Automated optimization. Software economics embedded in all technology decisions.
Assessment: Where are you today? Where do you want to be in 12 months? What needs to happen to get there?
Table: Unified Software Cost Management Framework
| Dimension | SAM (Traditional) | FinOps (Traditional) | Unified Approach |
|---|---|---|---|
| Scope | On-prem licenses, desktop software | Cloud infrastructure | All software: licenses, subscriptions, SaaS, cloud |
| Primary metric | Compliance, license position | Cloud spend, unit economics | Total software TCO, value delivered |
| Optimization focus | Reduce shelfware, downgrade editions | Rightsize, reserved capacity | Holistic: delivery model optimization, consolidation |
| Time horizon | Annual (true-up, renewal) | Real-time (consumption) | Continuous with strategic planning windows |
| Tooling | ITAM platforms (Flexera, Snow) | Cloud cost tools (Cloudability, CloudHealth) | Integrated platforms or unified dashboards |
| Team | SAM/ITAM specialists | Cloud FinOps engineers | Unified software economics team |
| Vendor relationship | Per-vendor negotiations | Cloud provider negotiations | Consolidated vendor management |
| Decision support | License compliance, audit prep | Cloud architecture decisions | Build/buy/SaaS, technology selection |
| Finance integration | Capex planning | Opex optimization | Total software budget ownership |
| Procurement involvement | License procurement | Cloud commitment purchases | Unified software procurement |
Silos between SAM and FinOps are a relic of an era when “licenses” and “cloud” were separate worlds. In 2026 it’s one world - software in different delivery models. Organizations that build unified view win: better decisions, greater savings, stronger negotiation position.
Key takeaways:
- Unified view of software costs is necessary - silos cost millions in missed optimizations
- SAM + FinOps + SaaS management = complete picture
- BYOL, Hybrid Benefit and similar mechanisms require connecting license data with cloud data
- Organizational integration is as important as technical - governance, KPIs, ownership
- TCO modeling for perpetual vs. subscription vs. SaaS decisions requires all-in cost perspective
- Vendor consolidation and unified negotiations provide leverage that silos don’t have
The trend is clear: Software Asset Management is evolving into Software Economics Management. Companies that make this shift earlier will have cost and decision-making advantages.
ARDURA Consulting offers comprehensive Software Asset Management services covering traditional licenses, cloud licensing, and SaaS optimization. Our approach connects SAM with FinOps for a complete picture of software costs. Contact us to discuss a unified approach to managing software costs in your organization.