Enterprise Software Licensing: Managing Cost Gravity and Compliance Risk

What Is Licensing Gravity?

Licensing gravity is the compounding mechanism through which enterprise software costs increase faster than usage, faster than business growth, and — left unchecked — faster than organisations can absorb. It operates through four reinforcing dynamics: shelfware accumulation, audit exposure growth, support cost inflation, and contractual lock-in deepening.

Each dynamic feeds the others. Shelfware creates the appearance of available capacity, discouraging proactive licence reviews. Audit exposure grows silently as technology landscapes evolve. Support costs increase annually under standard vendor agreements. And every renewal cycle that passes without renegotiation typically strengthens vendor leverage and weakens the customer's exit optionality.

The organisations that manage enterprise software costs most effectively are those that treat licensing as a continuous commercial discipline rather than a procurement event that occurs once every three to five years. The difference between these two approaches, across a typical large enterprise with £20 million or more in annual software spend, is commonly £4 million to £8 million per year in recoverable waste and risk reduction.

Force 1: Shelfware — The Silent Budget Drain

Shelfware is software that has been purchased, is under active support contract, and is not being used — or is being used at a fraction of the licensed capacity. Gartner research has consistently estimated that enterprises waste an average of 30 percent of their software spend on shelfware, with the figure rising above 40 percent in large organisations with decentralised procurement.

Shelfware accumulates in several common patterns. An enterprise-wide agreement (ELA) is signed to cover anticipated growth that does not materialise. A project is cancelled after the software is procured. A technology migration leaves old licences active. A large suite purchase provides capabilities that individual business units never adopt. Each instance contributes to a growing base of paid-for, unused entitlements that vendor support teams have no financial incentive to flag.

The Support Trap

Shelfware is expensive not only because the original licence spend was wasted, but because annual support charges continue to accumulate on unused entitlements. Oracle's standard annual support rate is 22 percent of net licence fees. SAP's standard rate is 22 percent. IBM's typical rate is 20 to 22 percent. A £1 million block of shelfware therefore generates £220,000 per year in ongoing support costs with zero return on that spend.

Vendors rarely proactively identify shelfware. Their commercial incentive runs in the opposite direction: unused entitlements that remain on support generate recurring revenue with minimal servicing cost. The responsibility for identifying and eliminating shelfware sits entirely with the customer, and doing so requires accurate usage data, contract review capability, and the willingness to challenge vendor account teams who will argue — often correctly — that reducing the licence base will affect future pricing leverage.

Force 2: Audit Exposure — The Hidden Balance Sheet Liability

Every enterprise with a significant software estate carries some degree of latent audit exposure. It may be an Oracle Database deployment that has accessed unlicensed features through automated tuning or diagnostic packs. It may be IBM software running on a virtualised environment where the ILMT tool has not been configured correctly, invalidating sub-capacity licensing. It may be an SAP indirect access scenario where a non-SAP system sends data into an SAP application without the users of that system holding individual licences. Whatever its form, this exposure sits on the balance sheet as an unrecognised liability.

The gravitational pull of audit exposure is that it compounds as the technology landscape evolves. Cloud migrations introduce new deployment patterns that may not align with on-premises licence terms. Virtualisation changes the processor footprint. New business processes create unexpected system integrations. Each change has the potential to create or enlarge compliance gaps — and vendors maintain specialised audit teams whose expertise is identifying exactly these scenarios.

The Asymmetry of Audit Outcomes

When a software audit results in a finding, the commercial asymmetry strongly favours the vendor. Oracle, SAP, IBM, and Microsoft all charge list price for licence shortfalls discovered during audits. Negotiated pricing — typically 40 to 70 percent below list for new licence purchases — is not available for audit remediation. The organisation must pay list price for the shortfall, plus annual support at 22 percent on the new licences, potentially backdated from the point the exposure originated.

A compliance gap that would have cost £400,000 to address proactively through a negotiated licence purchase can cost £1.2 million or more when discovered through an audit. The delta between these two outcomes — approximately £800,000 in this example — is pure cost of being unprepared. Multiplied across multiple vendors and multiple compliance gaps, this asymmetry represents the single largest source of recoverable cost in most enterprise software portfolios.

Force 3: Support Cost Inflation

Standard vendor support agreements almost universally include annual escalation provisions. Oracle's ASFU (Annual Software Update and Support) agreements permit price increases in line with CPI or by a fixed percentage, whichever is higher. SAP's Enterprise Support agreements have historically increased at rates above CPI, and SAP's 2023 price list introduced additional fee structures that effectively raised support costs beyond the headline rate.

IBM's support pricing has been subject to product-by-product changes, with several middleware and analytics products experiencing support cost increases of 20 to 40 percent over five-year periods. Microsoft enterprise agreements typically include pre-agreed annual escalations of three to five percent, which compound significantly over multi-year terms.

Support cost inflation is structural — it is built into the vendor's revenue model and is rarely negotiable at standard renewal without third-party advisory support or the credible threat of a switch to alternative products or third-party support providers. Organisations that renew without challenge effectively accept the vendor's pricing formula indefinitely.

Third-Party Support as a Counter-Gravity Option

Third-party software support providers — Rimini Street, Spinnaker Support, and others — offer support for Oracle and SAP products at 50 to 55 percent of vendor support rates. The trade-off is that third-party support does not include vendor product updates or new feature releases, and Oracle and SAP have pursued legal action against certain third-party providers. Nevertheless, for stable, mature product deployments where functional change is not a priority, third-party support is a proven mechanism for eliminating a significant portion of annual support cost gravity.

Force 4: Contractual Lock-In Deepening

Each renewal cycle that passes without a strategic review typically deepens vendor lock-in. Enterprise licence agreements and cloud subscription agreements are structured to increase the cost of switching over time: integration points multiply, internal processes become dependent on vendor-specific features, and the institutional knowledge of alternative products declines. Vendors are acutely aware of this dynamic and price their renewal offerings accordingly.

Lock-in gravity is particularly acute in cloud subscription agreements, where contract structures often reward multi-year commitments with discounts that create financial disincentives to switching. AWS Enterprise Discount Program commitments, for example, provide meaningful discounts at $2 million or more per year in annual spend, but the commit structure means that switching cloud providers mid-term triggers financial penalties equivalent to the discount foregone on the remaining term.

Four Counter-Gravity Strategies

Breaking the compounding dynamics of licensing gravity requires deliberate, consistent action across four disciplines.

Strategy 1: Continuous Licence Position Monitoring

The foundation of cost control is visibility. Organisations that run continuous licence position assessments — rather than point-in-time reviews triggered by impending renewals — catch compliance drift before it becomes audit exposure, identify shelfware before it accumulates years of support cost, and approach renewals with accurate data rather than vendor-supplied projections. Software asset management (SAM) tools, combined with specialist advisory for complex products like Oracle, IBM, and SAP, provide the baseline visibility required.

Strategy 2: Commercial Preparation Six Months Before Renewal

Effective vendor negotiation begins six months before the renewal date, not six weeks. At six months, the organisation has time to benchmark pricing against market rates, model alternative licence structures, engage competitive alternatives, and present a coherent commercial position that demonstrates willingness to change rather than pressure to renew. At six weeks, the negotiation window is typically insufficient to create meaningful competitive tension, and vendors know it.

Strategy 3: Proactive Audit Defence Preparation

Treating audit defence as a reactive capability — mobilising only when Oracle or IBM sends a letter — means the organisation always negotiates from a position of discovered exposure. Proactive audit defence preparation identifies compliance gaps before the vendor does, allowing the organisation to choose between remediation (closing the gap before audit), negotiation (approaching the vendor with a proposed settlement before formal audit proceedings), or architecture change (restructuring the deployment to eliminate the exposure). All three options are preferable to responding to a vendor-initiated audit finding at list price.

Strategy 4: Portfolio Rationalisation at Every Renewal

Each renewal is an opportunity to question whether the current product selection remains the right one. Cloud-native alternatives, open-source replacements, and competitive products have matured substantially over the past five years. Products that previously required incumbent vendor deployment — enterprise databases, integration middleware, business intelligence tools — now have credible alternatives that can be deployed at significantly lower total cost. Presenting genuine alternatives as part of renewal preparation transforms the negotiation from a price discussion to a platform decision, which fundamentally shifts commercial leverage.

Building Structural Resistance to Cost Gravity

No single initiative eliminates licensing gravity — it is a structural feature of the vendor-customer relationship in enterprise software. But organisations that consistently apply the four counter-gravity strategies described above typically achieve measurable results: shelfware reduction of 20 to 35 percent of the affected product base, audit exposure reduction that removes seven-figure balance sheet liabilities, support cost reductions of 15 to 50 percent through third-party support or negotiated rate adjustments, and renewal savings of 20 to 40 percent compared to auto-renewal pricing.

The cumulative impact of these results, applied consistently across an enterprise software estate of £20 million or more in annual spend, commonly delivers returns of three to eight times the cost of the advisory programme. The organisations that treat software licensing as a strategic commercial discipline rather than an administrative procurement function are the ones that escape the gravity trap — and the ones that go into every renewal negotiation with leverage rather than urgency.