Compliance tells you whether you are safe. Optimisation tells you whether you are wasting money. They are different questions, and only one of them is answered by buying more licences.
Organisations have long understood the headline benefits of software asset management: controlling costs, improving compliance, reducing security exposure, and running a tidier operation. All of that is real. But it stops short of the more interesting question.
Compliance asks whether you are safe. Optimisation asks whether you are wasting money. Those are different questions, and answering the first one well does nothing to answer the second.
Software licence optimisation goes beyond compliance to manage software actively across its whole life: what you buy, what you deploy, what gets used, and what you should stop paying for. Where compliance work ends when the position balances, optimisation keeps going until the position is not just defensible but as small as it can legitimately be.
The distinction matters because there is a trivially easy way to be compliant, and it is to buy too many licences. It works. Your publisher will be delighted. It is also the single most expensive way to run a software portfolio, and it is what a compliance-only programme quietly incentivises.
Licence optimisation arrived on most organisations’ agendas by an unglamorous route.
After the 2008 downturn, the major software manufacturers found that the years of easy growth were behind them and looked for other ways to keep revenue moving. Rather than build better products, several of them turned to the customers they already had. The modern software audit is what came out of that. Licensing agreements were complex enough — and in places deliberately ambiguous enough — that publishers could reasonably assume a good proportion of their customers were non-compliant somewhere. They were right often enough for it to become a durable revenue line.
The cost of an audit is not only the true-up. It is the weeks of internal effort, the diverted engineers, and the negotiation conducted from a position you did not choose.
The response was the Effective Licence Position: reconcile entitlement against deployment, and know where you stand before someone asks.
The ELP is the right idea. The problem was always how it got produced. Historically it was a project — a long, painful one — which meant most organisations only did it when an audit was imminent. In between, the position drifted. And because it was produced as a one-off, it was out of date the moment it was finished. A point-in-time answer to a question your environment keeps re-asking.
That is a tooling problem, not a conceptual one, and it is solved. CerteroX SAM maintains a continuous compliance position rather than a point-in-time reconciliation: purchased, used, available, required, variance and exposure, recalculated as inventory and entitlement change. The ELP stops being a project and becomes a number you can look at on a Tuesday.
Compliance needs two inputs: what you own, and what you have deployed. Optimisation needs a third and a fourth — what is actually being used, and what your product use rights entitle you to do about it.
Usage is where most of the recoverable money is. CerteroX SAM meters application usage at file level through AppsMonitor, with first-used and last-used tracking and a percentage-used figure over a rolling 90-day window. That is what turns “400 installs” into “160 installs nobody has opened since March”, which is a completely different conversation with a completely different budget outcome.
Product use rights are where the expertise still earns its keep. Downgrade rights, second-use entitlement, cover-down logic, core factors, cluster and virtualisation rules — these are the mechanisms by which the same deployment can require materially fewer licences, and they are specific to each publisher and each agreement. CerteroX SAM handles downgrade rights and second-use entitlement directly, and provides an Exclude From Licensing workflow for the legitimate exceptions — MSDN, development, training, second-use devices — that would otherwise inflate the position you are defending.
Six publishers get dedicated engines rather than generic treatment: Microsoft, Oracle, IBM, SAP, Adobe and Salesforce. That is deliberate, because those are the six where the difference between a naive count and a correct one is largest.
This piece was written when “software” meant something installed on a machine you owned. That is no longer the whole picture, and a licence optimisation programme that stops at the desktop leaves most of the modern waste untouched.
The same discipline applies to subscriptions, and the same failure mode shows up: seats bought defensively, never reclaimed, renewed automatically. 46% of SaaS licences go unused — the average organisation uses 54% of what it pays for.
CerteroX SaaS Management applies the optimisation loop to that population: unused licence detection at thirty or more days of zero usage, App Rationalization that finds overlapping applications ranked by recoverable saving, renewal tracking with days-to-renewal alongside utilisation rate, and actions to reclaim, reassign, downgrade or archive a seat rather than just report on it. Forty-seven vendor connectors pull authoritative user and licence lists directly from the vendor, so the usage picture does not depend on self-reporting.
The principle has not changed since 2016. Only the surface area has.
The requirement is not complicated to state. You need discovery and inventory you trust, usage data over a meaningful window, entitlement held somewhere other than a spreadsheet and someone’s memory, and a licence engine that understands the publisher’s actual rules rather than counting installs.
If you have the first two and not the second two, you have a compliance capability. It is worth having. It is not the same as knowing what your software should cost.
To see a continuous ELP and the metered usage underneath it, title by title, book a demo.
Other posts covering the same ground.
Locking an application down at user level does not make you compliant with a per-device licence. In a Citrix or RDS environment, one user with access can cost you a licence for every device in the organisation.
A third-party summary of a vendor can be wrong, and it stays wrong for as long as people read it. The case for checking a vendor's facts at source — and the current, sourced record for Certero.
An audit is won or lost on the quality of your inventory long before the letter arrives. Six ways data goes wrong, and what it takes to have the answer already in hand.
Everything argued above is checkable. Name the publisher, the billing account or the platform you would argue with, and the session is built around it — the reasoning attached, not a summary slide.
No gated download at the end of it.