← All postsHow-to

Software asset management software: entitlements against what is actually installed

Software asset management software discovers what is deployed, compares it to what you are entitled to, and exposes the gap before a vendor audit does. What it must do, and where the money is.

How-toS

Software asset management software exists to close one gap: the difference between what is installed and running across an organisation and what that organisation has actually bought the right to run. Both halves are harder than they sound. Discovery misses machines that are off, in a subsidiary, or in a cloud account nobody told you about; entitlements sit in purchase orders, reseller portals and contract amendments written in language that rewards careful reading.

What software asset management software must do

  • Discovery across endpoints, servers and cloud instances, including the ones outside the main domain.
  • Normalisation of what it finds, so eleven spellings of one product become one entry.
  • An entitlement record built from purchase evidence, not from a vendor's assertion of what you own.
  • Reconciliation of the two, with the shortfall and the surplus both visible.
  • Licence metric handling — per user, per device, per core, per concurrent session — because the metric decides the exposure.
  • Virtualisation and cloud rules, where a single workload can trigger licensing of an entire host.
  • Unused and underused licences, which is where the savings are rather than in renegotiation.
  • SaaS subscriptions discovered from expenditure, since nobody installs them.

Where the money actually is

Two places, and they pull in opposite directions. The first is overspend: seats bought for leavers, duplicate tools doing one job, premium editions assigned to people using basic features. That is recoverable at every renewal and is the easier win. The second is underspend, which is not a saving but a liability — if a vendor audit finds unlicensed deployment, the settlement is usually at list price with back-maintenance, far above what you would have paid by buying correctly. A programme that only reports savings is reporting half the picture.

Read the virtualisation clauses before anything else. The expensive audit findings almost never come from someone installing a copy they should not have; they come from a workload being moved onto a bigger host, which quietly multiplies what has to be licensed.

Building the baseline

  1. Pick the handful of vendors that represent most of the spend and start there, not with a full estate inventory.
  2. Gather purchase evidence for those vendors into one place, including amendments and reseller confirmations.
  3. Run discovery and reconcile against the entitlement record; expect the first pass to disagree with both sides.
  4. Record the licence metric per product, because that is what determines whether a change is safe.
  5. Reclaim unused assignments before renewal dates rather than after.
  6. Keep the record current at joiners, leavers and infrastructure changes — those three events create most of the drift.

Ettex Records holds the entitlement side honestly: products with licence metric, quantity, purchase evidence, renewal date and assigned owner, reconciled against whatever discovery output your tooling produces. It does not scan the estate, so pair it with your endpoint tooling — the structure is the same one a software license management programme needs on paper.

Frequently asked

What is the difference between SAM and licence management?

Licence management keeps the record of what you own. Software asset management is the wider discipline — discovery, reconciliation, optimisation and audit defence across the whole lifecycle.

How do vendor audits usually start?

Often with a routine-sounding request for a self-declaration. Treat that as the beginning of the audit, confirm the contractual basis for the request, and answer from your own reconciled data rather than from a script the vendor supplies.

Does SAM cover SaaS?

It has to now. SaaS has no installation to discover, so it surfaces through expenditure and identity provider data instead, and the typical waste is inactive paid accounts rather than licence breach.

MI
Written by Maria I.

Part of the Ettex team — writing about product, engineering and the future of work.

More posts
Get the best of the Ettex blogProduct news, guides and tips — straight to your inbox, no spam.