Software asset management (SAM) is the practice of tracking software licenses, usage, and costs to stay compliant and avoid overspending.
Software asset management (SAM) is the practice of tracking an organisation’s software - licenses, subscriptions, seats, and usage - so the business stays compliant with license terms and stops paying for software nobody uses. It is the software half of IT asset management, and day to day it rests on two disciplines: keeping software license management records current, and checking actual usage against what those records say you are entitled to - the heart of license compliance.
What SAM covers
Everything the organisation runs and pays for: perpetual licenses bought outright, subscription seats billed monthly or annually, operating systems, the software living on servers and end-user devices, and SaaS accounts that exist only in a browser. Alongside the software itself, SAM tracks the entitlements - the agreements, invoices, and license keys that prove what you may run, on how many machines or for how many users, until when.
The honest scope question for a smaller team: you probably do not need usage metering on every endpoint, but you do need to know every product you pay for, the seat count, the renewal date, and who owns the decision to keep it.
Why it matters
- Vendor audits. Major software vendors audit customers, and the remedy for running more than you bought is a true-up bill at list price - often backdated. Good records turn an audit from a scramble into a lookup.
- Waste. Seats assigned to people who left, overlapping tools doing the same job, and auto-renewals nobody reviewed are the standard leaks. Software spend is one of the few budgets where the savings are usually just sitting there, unclaimed.
- Security. Software no one recorded is software no one patches or offboards. Shadow IT - tools adopted outside any approval - is a SAM problem before it is a security one, because you cannot secure what you do not know you run.
SAM vs ITAM
ITAM is the umbrella practice for the whole IT estate; SAM is its software-specific subset. The split exists because software misbehaves differently from hardware: it is copied rather than moved, governed by contract terms rather than physical custody, and it renews and re-prices on the vendor’s schedule. But the two share a spine - most licenses are assigned to the same people and devices the hardware register already tracks, which is why keeping them in one system tends to work better than keeping two.
From records to governance
The record-keeping layer underneath is software license management’s job; SAM earns its keep in the governance built on top. Route new software requests through a named approver who checks whether an existing tool already covers the need - most overlap enters through well-meaning sign-ups, not bad decisions. Compare assigned seats against the people who actually use them at a regular cadence, and treat a persistent gap as a contract decision rather than a footnote. And stay audit-ready by default: entitlements, agreements, and assignment history kept retrievable mean a vendor’s audit letter triggers a lookup, not a project. AMPthilly supports this pattern by keeping software licenses and seats in the same register as the hardware they run on, assigned to owners, with the agreements attached and every change logged in the audit history.
Related terms
- Software License Management - the record-keeping core of SAM
- License Compliance - staying within the terms of what you bought
- True-Up - the reconciliation bill when usage exceeds entitlements
- Shadow IT - software in use that SAM does not know about yet
- Endpoint - the devices where installed software ultimately lives