Software asset management (SAM)
The practice of tracking an organisation's software licences, subscriptions, costs, and compliance across their whole lifecycle.
Also known as: SAM
Software asset management (SAM) is the practice of tracking all of an organisation's software: what is owned or subscribed to, who owns it, what it costs, and whether usage stays within the terms of each licence.
Good SAM avoids paying for software nobody uses, prevents surprise renewals, and provides the evidence auditors and security frameworks ask for. A maintained software register is its foundation.
What it covers in practice
SAM is usually presented as an enterprise discipline with its own standard (the ISO/IEC 19770 family) and its own tooling. That is a fair description of an estate of several thousand licences and an unhelpful one for an estate of thirty. At the size most organisations actually run, SAM reduces to four questions asked repeatedly: what do we have, who owns each of them, what does each cost on a comparable basis, and when does each agreement next commit us to something.
The questions are ordinary. What makes them hard is that the answers live in three places that do not reconcile: a finance export listing card charges without contract terms, an IT inventory listing installs without prices, and a shared drive of order forms nobody opens until a renewal has already passed its notice deadline. A software register is the one record where those three are brought together, and SAM is the practice of keeping it current rather than rebuilding it from scratch every time an auditor or a budget round asks.
How StackTrackr handles it
The register is the artefact. Each tool carries its vendor, category, internal owner, business unit and the customer it is applied to, its licence type (subscription, perpetual, open source or usage-based), its seats, cost, currency and billing cycle, and its renewal date, notice period and whether it auto-renews. Order forms and invoices attach to the record itself, so the evidence sits with the entry rather than in a folder somebody has to go and find.
Status runs through trial, active, notice given, cancelled and expired, and a tool that leaves the estate is archived rather than deleted, so what you used to run stays readable after the tidy-up. Renewal reminders default to 90, 60, 30 and 7 days ahead and are set per tool. The reports read those same records: annualised spend broken down by vendor, owner, category, business unit and customer, what you are contractually committed to, and when the money actually leaves.
Related terms
- ShelfwareSoftware an organisation has paid for but does not use, whether unused seats or whole subscriptions nobody owns.
- Billing cycleHow often a subscription is charged, monthly, quarterly or annually, which sets both when the cash leaves and the multiplier needed to compare tools.
- Annualised costA tool's cost expressed as a yearly figure, so monthly and annual subscriptions can be compared and totalled on one basis.