Most companies know almost to the unit how many laptops sit in the building. How many software licences they own, though, hardly anyone can recite from memory. Software asset management closes exactly that gap. The name sounds like a large corporation with a toolkit, but the heart of it is plain: know what you have, know what you use, and make sure the two line up.
What software asset management is
Software asset management, SAM for short, is the orderly handling of your software across its whole life. From the purchase through daily running to the day you retire it. In everyday speech people often just call it licence management, and in practice the two terms mean the same thing.
Why it matters usually becomes clear only when it is missing. A vendor announces a review, and nobody can say how many copies are really running. A subscription renews for people who left long ago. One department buys a program that another already has under contract. Each of these costs either money or nerves. Sound licence management makes them visible before they turn expensive.
The benefit runs on two tracks. On one side, compliance: you can show you have the right to use every piece of software you run. On the other, cost: you pay only for what you actually need. Together, those two are why the effort pays for itself.
The SAM cycle in four steps
SAM is not a one-off job but a loop that keeps coming round. You can boil it down to four steps. Get these four into your bones and you have grasped the essentials.
Discover. You find out what is actually installed and used. On servers, on laptops, in the cloud. Without this look at reality, everything that follows is guesswork.
Record. You capture your entitlements: what did you buy, in what quantity, on what terms? Purchase records, contracts and certificates belong in one place.
Reconcile. You put entitlements and usage side by side. This is where it shows whether you are under-licensed, spot on, or over-licensed. This is the heart of it.
Optimise. You act: pull back unused licences, buy the ones you are short of, adjust contracts. Then the loop starts again, because your estate keeps changing.
| Step | Guiding question | Output |
|---|---|---|
| Discover | What is really running? | A list of all installs and usage |
| Record | What do we own? | A complete licence inventory with proof |
| Reconcile | Do the two match? | A balance of surplus and shortfall |
| Optimise | What do we change? | Returns, top-up buys, adjusted contracts |
Building a licence inventory
The licence inventory is the foundation of everything. It is the list of what you own, with the proof to back it. Many firms never laid that list down properly, and it bites them the first time it matters.
Start small, but complete. For each piece of software you want a handful of core facts: the vendor and product, the version, how many licences you hold, the metric you are counted by, when the contract ends, and where the purchase record sits. These fields sound mundane, but it is precisely their absence that turns an audit into a nail-biter.
| Field | Example | Why it counts |
|---|---|---|
| Vendor / product | Office suite, standard | The basis for any reconciliation |
| Quantity | 50 licences | Your provable entitlement |
| Metric | per user | Determines how you are counted |
| Contract end | 31 March 2027 | Stops quiet auto-renewals |
| Proof | Invoice, certificate | Evidence when you are reviewed |
Tip: the metric decides
Two licences for the same program can be counted in completely different ways. Per user, per device, per processor core. Always note the metric, or later you will compare apples with pears and either scare or flatter yourself with the numbers.
Entitlements versus deployments
Now comes the moment the effort pays back. You lay the usage from step one next to the entitlements from step two. Three outcomes are possible, and each calls for a different response.
More licences than installs? Then money is sitting on the shelf. That surplus, often called shelfware, can be trimmed or dropped at the next contract. Fewer licences than installs? That is a shortfall, and it is dangerous. In an audit it becomes a back-charge. If the two line up, all is well, and now you have it in black and white.
Reconciliation does not run itself. Licence terms are often layered: second use on a personal machine, rights for test environments, downgrade to older versions. Anyone who knows these fine points not rarely finds rights they already hold and were about to buy again.
Careful: a shortfall does not sleep
A missing licence does not vanish on its own. It grows, because installs multiply and reviewers count backwards. Deal with every shortfall first, before you go filing down the shelfware. One is a risk, the other only a missed saving.
The usual gaps
When we look into a company's licence management, almost always the same three patterns show up. Knowing them spares you the painful discovery in your own house.
- Shelfware: paid-for licences nobody uses. Subscriptions for roles that no longer exist, or bundles bought big in one go.
- Over-deployment: more copies running than licensed. Usually meant harmlessly, but expensive in an audit all the same.
- Unknown installs: software nobody officially acquired. Grabbed quickly by a team on its own, past IT.
None of the three come from bad intent. They come from a missing overview. That is exactly why the first complete look at the estate is so valuable. It turns vague hunches into a list you can work with.
Spreadsheet or tool?
The question comes up early, and it often gets the wrong answer. Many believe they need an expensive system before they are allowed to start. The opposite is true. The process matters more than the tool.
A well-kept spreadsheet takes you surprisingly far. It is there at once, costs nothing and forces you to be clear. For a manageable estate it is often the right pick. It shows its limits when the number of installs grows, when you want usage captured automatically, or when several sites come together. That is when it is worth looking at dedicated tools.
These fall into rough categories, independent of any single vendor. There are discovery tools that scan networks and find installations. There are SAM platforms that bring entitlements and usage together and automate the reconciliation. And there are building blocks inside larger IT management systems that carry licences as one asset type among many.
| Situation | Spreadsheet | Tool |
|---|---|---|
| Few products, one site | a good fit | usually overkill |
| Usage should be captured automatically | reaches its limits | clearly ahead |
| Several sites, many users | error-prone | recommended |
| First step, tight budget | ideal to start | sensible later |
Roles and process
SAM is not pure technology. It lives on someone being responsible and rules taking hold. In a small firm one person can hold all the threads. In a larger one it needs clear ownership.
Someone has to keep the estate current, or it goes stale within weeks. Procurement needs to know that every new piece of software belongs in the inventory before it is handed out. And you need one simple rule for what otherwise goes wrong most: what happens when a member of staff leaves? Their account and their licences must go back into the pool, not carry on silently.
The process need not be heavy. A fixed date each quarter where someone reconciles usage against entitlements is plenty to begin. What counts is the regularity. An inventory you build once and never touch is worthless a year on.
The key points
- Software asset management means knowing what you own, what you use, and that the two match.
- The loop has four steps: discover, record, reconcile, optimise.
- The licence inventory is the foundation. Without proof, every reconciliation is guesswork.
- A shortfall is a risk, shelfware only a saving. Deal with the risk first.
- The process counts more than the tool. A kept spreadsheet beats an unused system.
Where to start
You do not have to get everything right at once. Begin with your five most expensive software contracts. That is where the most money and the biggest risk sit. For those five, capture what you own and what actually runs. Even this small reconciliation usually turns up the first saving or the first gap.
From there you work outward, product by product. After a few rounds you have an inventory that lives and a process that keeps it current. This is not a grand project but a habit. If you want a tailwind on the way, we are glad to look at your licence position with you and sort out where the first move pays off.
Frequently asked questions
What is software asset management in simple terms?
Software asset management (SAM) is the orderly handling of your software across its whole life: buying, deploying, monitoring and retiring it. The point is that you always know which licences you own, what is actually installed, and whether the two match. Many people simply call it licence management.
Is a spreadsheet enough, or do I need a SAM tool?
For small and mid-sized estates a well-kept spreadsheet is often plenty. It is cheap, available right away and forces you to be clear. A tool pays off once the number of installations grows, when you want usage captured automatically, or when several sites are involved. What matters is the process behind it, not the brand of the tool.
What is shelfware and how do I find it?
Shelfware is paid-for licences that nobody uses. You find it by reconciling your entitlements against real usage: accounts with no sign-in for months, installed programs with no activity, subscriptions for people who have left. Every unused licence is money you can claw back.
How does SAM help during a software audit?
An audit asks exactly what SAM already tracks: what you own, what you run, and whether you can prove it. If you keep a current licence inventory with purchase records, you answer calmly and with documents instead of guesswork. That shortens the review and lowers the risk of back-charges.
We trade in software licences and help with licence management, compliance and cost optimisation. Vendor-neutral, from Cyprus. Questions about your estate? Talk to us.
