The rationalisation project that saved sixty thousand pounds from ten million.

Ten thousand software titles. Four months of dedicated effort. Sixty thousand pounds saved.

A construction company shared those numbers recently. They had run a proper rationalisation programme: external consultants, steering committees, workshops. Going in, they estimated their estate at around a thousand tools. The actual figure was ten times that. And after all of it, the savings came to sixty thousand pounds on an estate costing tens of millions a year.

The post-mortem did not point to bad data or the wrong people. It pointed to something structurally simpler. Nobody knew what any of the software actually did.

Owned by the catalogue, invisible in practice

The catalogue confirmed they owned it. The invoices confirmed they were paying for it. But the moment anyone asked the question that rationalisation depends on, "do we already own something that can do this?", the answer was always the same: we don't know.

So the decision was always the same. Tolerate it. Carry it forward. Renew it again.

This is not a failure of effort. It is the predictable result of a process trying to govern software spend without understanding what software does. SAM tools track licences and entitlement counts. They can tell you how many seats of a product you hold. They cannot tell you what that product does at a feature level, and they certainly cannot compare it against the rest of your estate. Without that intelligence, the catalogue is a list of what you own. Not a map of what you could consolidate.

Why the default is always renewal

Procurement teams are not irrational. When a renewal request lands and nobody can prove an alternative exists in the estate, approving it is the path of least resistance. The cost of a wrong rejection is immediate and visible. The cost of an unnecessary renewal is diffuse, buried in a budget line nobody owns.

So it stays. And the next cycle, it stays again. And the estate grows.

Enterprise architects face the same wall from a different angle. They can map the estate at a product level, but tracing feature-level overlap across thousands of titles is a manual process that would take months. Most rationalisation exercises rely on product category assumptions rather than actual capability comparisons. That is how you end up saving sixty thousand pounds from ten million.

Feature intelligence at the point of decision

The gap is not effort. It is intelligence, applied at the moment a decision is actually being made. Not in a report produced six months later. A renewal lands on a procurement desk, there is thirty days on the clock, and the question is whether the estate already covers the need. Without a system that can answer it, the renewal gets approved.

Here is what that question looks like when there is a decision layer in the workflow.

The evidence is sourced. The decision is auditable. And the team did not need a three-month rationalisation study to get there. This is what the decision layer does: it knows what your software does at a feature level, maps it against your full estate, and returns a sourced answer at the point of request.

What the £60,000 number actually reveals

The construction company that spent four months saving sixty thousand pounds was not unlucky. They were using the right intent with the wrong instrument. A periodic rationalisation exercise, no matter how well-resourced, will always hit the same wall: the decisions happen between the exercises, one renewal at a time, by people who do not have the intelligence to say no.

"Thanks to Samplify, we have doubled our throughput. What used to take a month now takes five to ten minutes." Ben Maudlin, SAM Lead, Cisco

At Cisco, 92 per cent of a $120 million software estate is evaluated through the platform, with $2 to $3 million a month in prevented spend. Not because the team grew, but because the intelligence improved. Every renewal request is checked. Every new purchase is compared against what already exists. Feature overlap is surfaced before the budget is committed, not discovered in a post-mortem two years later.

The estates that achieve meaningful savings do not do it with better spreadsheets or longer stakeholder lists. They do it because they can answer the question the catalogue never could: do we already own something that does this?

If your last rationalisation effort returned less than it cost to run, the case for a different approach is straightforward.