Home  ›  Blog  ›  Software Cost Optimization
Pillar · Cost · Optimization

Software Cost Optimization — durable savings, not one-time concessions.

Most software cost programmes capture a discount and call it savings. The discount disappears at renewal; the underlying spend pattern does not. Durable software cost optimization restructures what is bought before negotiating the price — removing shelfware, right-sizing tiers, consolidating vendors, and renegotiating commercial vehicles. This pillar walks through the optimization disciplines that compound year on year and the operating model that holds them in place.

Updated: April 2026 Reading time: 19 min Audience: CIO, CFO, Procurement
Financial analysis and cost optimization
The starting point

Discounts evaporate. Optimization compounds.

The most common software cost programme follows a predictable arc. Procurement squeezes a discount at renewal, captures the saving in a deck, and the underlying spend pattern continues unchanged. Two renewal cycles later the discount baseline has reset upward, the vendor has captured the consumption growth, and the original saving is invisible in the run-rate. The pattern is so common that the procurement teams who execute it have stopped noticing how little it captures.

Durable optimization works in the other direction. The unit price is not the lever — the scope is. Removing shelfware before renewal captures the saving forward; right-sizing tier mix before renewal locks the lower run-rate; consolidating vendors before negotiation removes the alternative-supplier pricing escape valve. The discipline is operational, not commercial. In our experience across 340+ engagements, the customers who run this discipline capture 18-32% durable savings on optimised vendor categories, with the largest gains concentrated in cloud commits, SaaS sprawl, and shelfware-heavy legacy estates.

Cost programme that captures discounts but not durable savings?

The optimization work happens before the negotiation, not during it.

Contact Us →
The optimization disciplines

Five disciplines that actually compound.

Across the cost engagements we run, the durable savings concentrate in five disciplines. Each can be operated independently, but the savings compound when they run as a sequence.

1. Shelfware reduction

Shelfware is the entitlement an enterprise pays for but does not deploy or consume. It accumulates through M&A, organisational change, project cancellations, and discount-driven over-purchase. The typical shelfware ratio in a mid-size enterprise sits between 12% and 28% of total software spend; the top quartile sits below 8%. Shelfware reduction is the cleanest source of durable savings — every removed entitlement is a permanent saving net of any switching cost. The discipline requires deployment and consumption telemetry, not just procurement records.

2. Right-sizing

Right-sizing reduces the spend per entitlement without reducing the entitlement count. Common patterns: Microsoft E5 users who only consume E3 features (5,000 user shift typically captures $1.2M annual); ServiceNow Pro+ users who only consume Pro (often 30-50% of the licensed Pro+ base); Adobe All Apps users who only consume Single App (typically 40%+ of the All Apps base). The work is mechanical but requires usage telemetry the vendor does not volunteer.

3. Contract restructuring

Contract restructuring captures durable savings by changing the commercial vehicle. Migrating from on-premise perpetual to subscription, from CSP to NCE, from monthly cloud commits to annual or three-year, from named-user to consumption — each migration carries a price implication that the vendor does not surface unsolicited. The largest single Oracle restructuring saving we have captured for a client was $14.2M over five years, driven by a ULA-to-NUP-and-Processor restructure at certification.

4. Vendor consolidation

Vendor consolidation reduces the long tail of software spend by replacing redundant capabilities with fewer vendors. The most common patterns: collaboration tools (3-5 instances of overlapping Zoom/Teams/Webex/Slack functionality), security tools (8-15 vendor stack across endpoint, network, identity, SIEM), monitoring tools (overlap between Datadog, New Relic, AppDynamics, Dynatrace), low-code platforms. Consolidation savings sit at 20-40% of the consolidated category spend when executed end-to-end.

5. Cloud commit optimization

Cloud commits (AWS EDP, Azure MACC, GCP CUD) are the fastest-growing category of software spend and the most frequently mis-sized. Commits are typically sized against optimistic three-year growth assumptions, captured in deck-level commitments, and locked in at signing. Optimization at renewal restructures the commit against actual consumption pattern plus realistic growth, captures committed-use discounts on the right products, and renegotiates the marketplace surcharge for third-party software billed through the cloud. Typical durable saving: 14-26% of the committed spend.

Download the License Optimization Toolkit.

The full 2026 playbook covering shelfware reduction, right-sizing, and the optimization disciplines that compound year on year.

Get the toolkit →
Sequence matters

Optimization before negotiation, every time.

The single most common cost-programme failure is reversing the order. A procurement team that walks into renewal with the current entitlement scope is asking the vendor for a discount on what they have already over-bought. The vendor offers a 12% discount, the customer accepts, and the renewal closes 30% above where it should have. Customers who reverse the sequence — optimize the scope before opening the renewal — present the vendor with a smaller, cleaner deal and capture the unit-price discount on top of the structural saving.

The 12-month optimization runway

A material renewal needs a 12-month optimization runway. Month -12 to -9: compliance baseline and effective licensing position. Month -9 to -6: shelfware identification, tier-mix analysis, scope adjustment. Month -6 to -3: restructured proposal, vendor benchmark, negotiation strategy. Month -3 to 0: execution. Renewals that compress this runway into 90 days consistently underperform because the optimization work is the leverage; without it, only the price moves.

The ongoing operating model

Optimization as a function, not a project.

One-time optimization programmes capture significant savings and then decay. The savings disappear because the conditions that produced the bloat — uncontrolled deployment, tier inflation, vendor sprawl — reassert themselves once the programme team disbands. Customers who treat optimization as an ongoing function — typically a 2-4 FTE practice inside the SAM or FinOps function — sustain the savings indefinitely. The function pays for itself many times over against its own run-rate and produces a defensible cost story for the CFO every quarter.

Standing up a software cost programme?

We design and operate optimization functions buyer-side. No vendor commissions, no platform sales.

Contact Us →

Internal next steps

If you are reading this in advance of a cost programme, three actions consistently set the right starting point. First, baseline the current state with an effective licensing position across the top-10 vendors. Second, prioritise the optimization disciplines against the highest-yield categories (cloud commits, SaaS sprawl, legacy shelfware). Third, sequence optimization before negotiation on every renewal above $1M. The License Optimization Toolkit walks through each discipline in detail.

FAQ

Common cost optimization questions.

What is software cost optimization?
Software cost optimization is the structured reduction of total software spend through shelfware removal, right-sizing, contract restructuring, vendor consolidation and pricing renegotiation — without compromising business capability. It targets durable savings, not one-time concessions.
How much can an enterprise save through optimization?
In our experience across 340+ engagements, mid-size enterprises capture 18-32% durable savings on optimised vendor categories, with the largest savings concentrated in cloud commits, SaaS sprawl, and shelfware-heavy legacy estates.
What is the difference between optimization and negotiation?
Negotiation captures price reductions at renewal; optimization restructures what is bought. Negotiation alone leaves shelfware, over-deployment and tier mismatches intact. Optimization restructures the scope before negotiation, then captures the new scope at a lower unit price.
Where does software cost optimization start?
It starts with an effective licensing position — entitlement against deployment against consumption — for each vendor in scope. Without this baseline, optimization decisions are guesses.
Is cost optimization the same as FinOps?
No. FinOps focuses on cloud cost optimization within a vendor (typically AWS, Azure, GCP). Software cost optimization spans the full software portfolio across vendors and licensing models — perpetual, subscription, consumption.
Should optimization be a project or a function?
Both — but the durable savings come from the function. One-time projects capture significant savings that decay as the conditions that produced the bloat reassert themselves. An ongoing 2-4 FTE optimization function inside SAM or FinOps sustains the savings indefinitely.

Mandate to cut software cost?
Get the durable savings, not the one-time concession.

We design and operate cost-optimization functions buyer-side. No vendor partnerships, no platform commissions.

The Compliance Brief

Weekly compliance intelligence for IT leaders.