What Is Software Asset Management (SAM)? Why It Matters and How It Is Changing: The Complete 2027 Guide

Software asset management, or SAM, is the practice of managing software through its life so that you only pay for what you use, use only what you are entitled to, and can prove both. It sits between IT, procurement, finance, legal and security, and it is the discipline that most directly turns data about software into savings and reduced risk.

This guide explains what SAM is, why it is required, and how it is changing in 2027 as SaaS spreads through business units, AI tools bring consumption pricing, vendors change their licensing models and audits become a regular event. Numbers come from named sources, and where a source is commissioned research or a vendor we say so.

The short answer

Software asset management makes sure you use what you are entitled to and pay only for what you use, and that you can prove both. It is required because audits are routine, SaaS and AI spend is growing outside IT, and unused licenses and shortfalls both cost money. In 2027 it is changing through subscriptions, vendor pricing shifts, AI consumption models and a move from compliance defense to spend optimization.

What is software asset management?

SAM answers two questions repeatedly. First, do we have the right to use everything we are using? Second, are we using everything we are paying for? The first is about compliance and risk. The second is about cost. Good SAM answers both with evidence, for every major software publisher, on a regular schedule.

The standards community treats SAM as part of IT asset management. ISO/IEC 19770-1 describes an IT asset management system, and ISO/IEC 19770-3 defines a schema for software entitlements, covering usage rights, limits and metrics, so that license terms can be described in a common structure. Parts 2 and 5 cover software identification tags and the overview and vocabulary. Our companion guide, What Is IT Asset Management? The Complete 2027 Guide, places SAM in that wider context.

The software asset management cycleFive activities that repeat. The output of one feeds the next.InventoryWhat is installed, used orsubscribed toEntitlementsWhat the contracts andpurchases allowReconcileCompare use to rights andfind the gapOptimizeReclaim, rightsize andrenegotiateGovernPolicy, approvals and renewalcontrolSAMa continuous cycleSource: Desqcon Consulting.

The effective license position

The central output of SAM is the effective license position, often called ELP: a comparison of what you are entitled to use against what you actually deploy or consume, for each product. A shortfall is exposure that could become a true up, a purchase or an audit finding. A surplus is money spent on rights you are not using, which can be reclaimed, reused elsewhere or left unrenewed.

The effective license position: what you own against what you useIllustrative example with made up numbers. Shortfall means exposure. Surplus means money that can be reclaimed or notrenewed.0600120018002400EntitledDeployed or used1,0001,180Product A (shortfall of 180)500310Product B (surplus of 190)250250Product C (balanced)2,0001,450Product D (surplus of 550)Source: Illustrative only. Not data from any organization. Real positions depend on license metrics, contract terms and usage rights.

Computing a reliable position takes four data sets. Inventory and usage data say what is installed and used. Entitlement data from contracts and purchase records say what you may use. License rules, meaning the metric and terms for each product, say how to count. Organizational data such as users, devices, cost centers and contracts links all of it to owners. The hard part is rarely arithmetic. It is data quality and interpreting contract terms.

License metrics decide the result

Two organizations with the same installed software can have very different positions because of how the vendor counts. Always start from the metric.

Common license metrics and where they biteThe metric decides what you count. Count the wrong thing and the position is wrong.Per userNamed or concurrent users. Watchshared accounts, contractors andleavers.Per deviceCounts devices that access thesoftware. Watch virtual desktopsand spare machines.Per core or processorCommon for server and databaseproducts. Watch virtualization andcloud.Subscription seatPaid per assigned seat each term.Watch unused seats and autorenewals.ConsumptionPaid by usage or by token. Watchforecasts, caps and overage terms.Enterprise agreementA bundled commitment with true up.Watch scope, true up dates and exitterms.Source: Desqcon Consulting.

Why SAM is required

Audits are routine, and expensive when you are unprepared

In the Flexera 2026 State of ITAM Report, based on 512 technology professionals, 48% of organizations were audited in the last year and 44% spent more than $1 million on software audits over the previous three years. That share has stayed flat across the last three reports. Over three years, 64% reported a Microsoft audit, 38% an Oracle audit, up from 24% in the previous report, and 32% an Adobe audit, also up from 24%. ITAM teams reported spending 22% of their effort responding to audits and another 22% allocating audit costs and preparing, which is why prepared teams look so different from reactive ones.

What audits cost and how common they areSoftware audit experience reported in the 2026 survey48%of organizations were audited inthe last year44%spent more than $1 million onaudits over three years, a figureunchanged across the last threereports22%of ITAM team effort goes on auditresponse, and another 22% onaudit allocationSource: Flexera 2026 State of ITAM Report (512 respondents).
Which vendors audit most: share of organizations audited over three yearsOracle and Adobe audit activity rose between survey editions0%25%50%75%100%Previous report2026 report64%Microsoft24%38%Oracle24%32%AdobeSource: Flexera 2026 State of ITAM Report press release (512 respondents). A prior figure for Microsoft was not given in the release.

We would add one caution. Third party summaries of the Flexera report sometimes quote different Oracle and Microsoft percentages. We use the figures from the Flexera press release.

Waste is hidden in plain sight

The Zylo 2026 SaaS Management Index, based on more than 40 million licenses and $75 billion in spend, finds that an average of 36% of licenses are unused against recommended utilization levels, and that median SaaS spend is $9,455 per employee. Business units control 81% of SaaS spend, and IT directly manages 15%. That means most of the spend is committed by people who are not looking at license position.

Who controls SaaS spendShare of SaaS spend by the group that controls the purchase81%bought outside IT81%Business units control the purchase15%IT directly manages4%Other (remainder)Source: Zylo 2026 SaaS Management Index. Remainder calculated as 100% minus the reported shares.
SaaS and AI spend, in numbersFindings from a large SaaS spend benchmark36%of licenses are unusedon average, measuredagainst recommendedutilization$9,455median SaaS spend peremployee78%of IT leaders reportedunexpected charges fromconsumption or AIpricing in the past 12months108%rise in AI native appspend overall, and 393%in organizations above10,000 employeesSource: Zylo 2026 SaaS Management Index (January 29, 2026): more than 40 million licenses and $75 billion in spend under management. Charge andproject findings are from a survey of 218 IT leaders.

A simple calculation shows why the 36% matters. If 1,000 users each have a subscription at $30 per user per month, the annual cost is $360,000. If 36% are unused, the yearly cost of unused seats is about $129,600. This is illustrative arithmetic using the Zylo average, not a benchmark for your own estate, which is exactly why you need your own data.

Other reasons

  • Security and compliance. Unapproved or unpatched software is a risk. An accurate inventory is the base for vulnerability work and for data protection reviews.
  • Contract leverage. Knowing your real consumption lets you negotiate on facts. In the Flexera survey, negotiating SaaS contract terms rose 14 percentage points year over year as a SAM activity.
  • Mergers, divestments and restructures. Licenses often do not transfer cleanly. A current position avoids surprises.
  • AI governance. AI tools arrive with new pricing models and new data risks. Only 31% of organizations report accurate visibility into AI software.

How SAM is changing

1. Subscriptions and SaaS replaced installs

Classic SAM counted installed copies. Subscription and SaaS software is counted by assignment, activation and usage, and it appears through procurement, expense cards and single sign on, not through discovery agents. Flexera reports visibility of SaaS up from 50% to 66%, and visibility of cloud and bring your own license entitlements up from 27% to 43%. Both are improving, and both are still far from complete.

2. Vendor pricing and packaging shifts create sudden cost events

VMware after its acquisition by Broadcom is the clearest example. A January 2026 survey of 302 IT decision makers, commissioned by CloudBolt and reported by Network World, found 59% had seen price increases above 25%, 14% had seen prices double, 88% worried about further increases and 86% were reducing VMware use. Among those moving, 72% planned public cloud IaaS, 43% Hyper-V or Azure Stack, and 44% had already moved a quarter or more of their environment. Only 2% had moved 75% or more, which tells you migration takes time. Advisory firms that sell negotiation services report much larger increases for some customers, including a move to bundled subscriptions with minimum core counts, but those figures come from their own engagements and are not independently verified.

VMware customers are changing courseResults of a survey of 302 IT decision makers at North American enterprises with 1,000 or more employees, January 2026Saw prices rise by more than 25%59%Are reducing VMware use86%Worry about future increases88%Plan to move some workloads to publiccloud IaaS72%Plan to use Hyper-V or Azure Stack43%Have moved 25% or more of theirenvironment44%Source: CloudBolt survey of 302 IT decision makers, fielded January 2026, reported by Network World on February 18, 2026. Commissioned research.14% reported that prices doubled.

Other vendors are changing models too. Oracle moved Java SE subscription pricing to an employee based metric in 2023, which changes the count from servers or processors to headcount. One ITAM software vendor reports that Microsoft removed volume discounts on online services in enterprise agreements from November 2025 and pushes smaller customers toward the cloud solution provider channel. Check any such change against the vendor’s own announcement and your agreement before acting.

3. Audit behavior is shifting

The Flexera data shows more organizations reporting Oracle and Adobe audits than in the previous report. An analysis from The ITAM Review published in April 2026 expects more audit activity over the next 12 to 24 months from vendors under financial pressure, naming Oracle Java, SAP indirect use and Broadcom as areas to watch. That analysis is opinion and a forecast, not a measurement, but the direction fits the survey. Prepare for audits as a routine event.

4. AI software brings consumption pricing and a new visibility gap

AI features are sold as seats, as usage or as a mix. Zylo found AI native app spend up 108% overall, and 78% of IT leaders reported unexpected charges from consumption or AI pricing. The Flexera survey found 59% saw wasted AI spend rise and only 29% measure the value of their AI software. SAM teams need new fields: usage limits, overage terms, data handling terms, approved use cases and the business owner who can say whether the tool earns its cost. In many organizations the SAM team that tracks AI now reports into cybersecurity, as 58% of teams tracking AI do in the Flexera survey.

5. The priority moved from proving compliance to optimizing spend

Optimizing software spend is the top SAM priority in the Flexera survey, more than 19 percentage points ahead of the next item. Software optimization is also the largest single use of ITAM team time at 32%. Reuse matters: 43% say license reuse produces significant savings. That is a healthy shift. Compliance remains the floor, and savings are what fund the function.

6. SAM is merging with FinOps and procurement

Cloud and SaaS spend are managed by the same people who run FinOps, procurement and vendor management. The best SAM teams in 2027 will share data and a calendar with those teams: renewal dates, usage, commitments, and savings targets. A combined view avoids the common failure where one team reclaims licenses while another renews at the old quantity.

How to prepare for an audit

The best audit defense is a current position, built before anyone asks. The steps below describe the first days after a notice. They are general guidance and not legal advice, so involve legal counsel and procurement from the start. Our free Software Audit Readiness Checklist turns this into a working document, and our guide to why SAM stalls covers the problems that undermine preparation.

The first ten days of a software auditA calm order of work protects your position1Receive androuteSend the notice toa named owner,legal andprocurement. Do notreply informally.2Read thecontractCheck audit rights,notice period,scope, costshifting andconfidentiality.3Set scope andtimelineAgree scope, dataand dates inwriting. Appointone point ofcontact.4Build yourpositionPull entitlementsand deployment dataand compute yourown position first.5Respond andnegotiateShare what isrequired, resolvegaps commerciallyand close the auditin writing.Source: Desqcon Consulting practice summary. This is general guidance, not legal advice. Involve legal counsel for any audit.

Who does what in SAM

RoleMain responsibility
SAM leadOwns the process, the position for each publisher and the savings report
Procurement and vendor managementOwns contracts, renewals and the negotiation calendar
IT operations and endpoint teamsProvide inventory, usage data and deployment control
Business ownersApprove need, confirm usage and release unused licenses
SecurityReview software risk and AI tools, and use the inventory for vulnerability work
Finance and FinOpsLink spend to budgets and track savings
LegalInterpret contract terms, rights and audit clauses

Where is your SAM today?

SAM maturityJudge each major publisher separately. Most organizations vary widely.ReactiveReports are builtwhen a vendor asks.AwareInventory andcontracts arecollected for thelargest publishers.ManagedPosition isreconciled regularlyand renewals areplanned.OptimizedReclaim, reuse andnegotiation savemoney every quarter.IntegratedSAM data drivesprocurement,security, finance andAI policy.Source: Desqcon Consulting maturity view.

Use our software asset management tool assessment when you are choosing or replacing a platform, and see our reviews of SAM tools, enterprise license management models and AI in SAM tools for the tooling view.

A practical SAM plan for 2027

A practical SAM plan for 2027Start where the money and the risk are1Pick the toppublishersRank vendors byspend, audit riskand complexity.Start with three tofive.2Build thebaselineCollectentitlements,contracts anddeployment data andcompute a position.3Close the gapsFix shortfallscommercially andreclaim surplusbefore renewaldates.4Control thefront doorRoute new softwareand AI requeststhrough approvalwith a contractcheck.5Repeat on arhythmReconcilequarterly, reviewrenewals six monthsout and reportsavings.Source: Desqcon Consulting.

Pick the top publishers

Do not try to cover every vendor. Rank publishers by annual spend, audit exposure and license complexity, and start with three to five. Most of the value and most of the risk sit there.

Build the baseline

Collect contracts, purchase records, entitlements and deployment data. Compute an effective license position with the correct metric for each product. Record assumptions and open questions. A baseline with documented uncertainty is far more useful than none.

Close the gaps

Treat shortfalls through the right commercial path, in coordination with procurement and legal. Reclaim surplus and plan non renewal or reduction ahead of renewal dates. Reuse before you buy.

Control the front door

Route requests for new software, SaaS and AI tools through an approval step that checks existing entitlements, contract terms, security and data handling. That step is where you prevent the next round of waste.

Repeat on a rhythm

Reconcile quarterly, review each major renewal six months ahead and report savings and risk reduced. A rhythm turns SAM from a project into a process.

Measures that show SAM is working

MeasureWhat it shows
Licenses reclaimed and subscriptions removedSavings from active management
Share of spend with an up to date license positionCoverage of the process
Renewals reviewed at least six months aheadWhether renewals are planned or reactive
Shortfalls identified and resolvedCompliance risk reduced
Shadow software and AI tools discovered and brought under controlEffect of the front door process
Cost per user or per unit for key productsUnit economics and negotiation leverage
Audit outcomes and time to respondAudit readiness

Common mistakes to avoid

  • Counting installs when the metric is something else. A correct count needs the contract definition.
  • Treating SAM as a compliance project. Savings and spend control are what keep it funded.
  • Ignoring SaaS and AI because discovery agents do not see them. Use finance, single sign on and contract data.
  • Waiting for the notice. The right time to build a position is before a vendor asks.
  • Renewing at the old quantity. Check usage and release surplus before every renewal.
  • Splitting ownership. One team reclaiming while another renews undoes the work.

Frequently asked questions

What is the difference between SAM and ITAM?

ITAM covers all IT assets: hardware, software, cloud and more. SAM is the software part, focused on licenses, entitlements, usage and compliance. SAM is usually a specialist stream within ITAM.

What is an effective license position?

It is the comparison of what you are entitled to use and what you actually deploy or consume, product by product. A shortfall is risk and a surplus is wasted spend.

How often should we run a license reconciliation?

Quarterly for major publishers is a good default, plus before every major renewal and after any large change such as a merger or migration.

Do we need a SAM tool?

A tool helps once volume and complexity grow, because license data must be reconciled across many sources. Start by deciding the process, data and ownership. Then choose a tool that fits them.

How does SAM handle SaaS and AI tools?

Through finance, expense, contract and single sign on data rather than discovery agents. Record owner, seats, usage, renewal date, data handling terms and, for AI tools, usage limits and approved use cases.

What should we do if a vendor sends an audit notice?

Send it to a named owner, legal and procurement. Read the audit clause, agree scope and timelines in writing and compute your own position before sharing data. Involve legal counsel.

Know your license position before a vendor asks

Start with our free Software Audit Readiness Checklist, then use the Software License Position Workbook to build a baseline for your top publishers.

Free audit readiness checklistLicense position workbookSAM tool assessment

Sources and notes

Leave Comment

Your email address will not be published. Required fields are marked *

Are you human? Please solve:Captcha