Client Profile
The client is a UK-based integrated telecoms operator serving consumer, business, and public sector customers across fixed and mobile networks. The organisation employs approximately 11,500 staff and operates a large enterprise technology estate that supports network operations, customer services, billing, and back-office functions. Oracle has been the dominant enterprise software vendor in the client's environment for over a decade, with Oracle E-Business Suite managing finance and HR, Oracle Database Enterprise Edition supporting billing and operational systems, Oracle WebLogic providing the application server layer for customer-facing platforms, and Oracle Siebel CRM serving the enterprise B2B customer management function.
The organisation's Oracle support bill had grown steadily through a combination of historical licence accumulation and Oracle's standard annual 8% support uplift. At the time of the engagement, the firm was paying £4.8M per year across all Oracle support contracts. Oracle's account team had signalled an expectation of a further 8% increase at the next renewal cycle, which would have pushed the annual support obligation to £5.2M — a level the firm's technology leadership regarded as commercially unjustifiable given the operational performance of its Oracle estate.
The Challenge
The core challenge for large Oracle support estates is that Oracle's support pricing is designed to be passive. Once a support contract is in place, Oracle's account team has no commercial incentive to prompt customers to rationalise licences, terminate unused support, or explore alternatives. The standard renewal process offers organisations a choice between accepting Oracle's uplift or engaging in a negotiation that Oracle approaches from a position of maximum information asymmetry — Oracle knows the customer's deployment data through LMS tooling and through historical contract records; the customer rarely has an equivalent independent view of its own estate.
In this organisation's case, the estate review revealed three categories of support expenditure that were commercially questionable. First, Oracle Siebel CRM — a product Oracle had announced no new feature releases for — was carrying an annual support cost of £680,000. The organisation had been aware of Siebel's end-of-roadmap status but had not taken action because Oracle's team had framed continued support as necessary for regulatory compliance with data retention obligations. Second, Oracle WebLogic deployments supporting a customer portal that had been migrated to a SaaS platform were carrying £420,000 in annual support costs on an application environment that was technically still running but no longer serving customers. Third, Oracle E-Business Suite modules for manufacturing and supply chain — modules originally implemented for a business unit that had since been divested — were generating £540,000 in annual support costs on systems that had not been accessed since the divestiture.
Redress Compliance was engaged to independently review the Oracle estate, identify the contractual and technical options available, and produce a commercially viable support reduction plan that the organisation could implement without creating Oracle audit exposure or service continuity risk.
The Approach
The Redress engagement began with a structured inventory of all Oracle support contracts, cross-referenced against the organisation's active system records and IT asset management data. This produced a product-by-product assessment of support expenditure, system activity levels, patch application frequency, and strategic dependency.
For Oracle Siebel CRM, Redress challenged Oracle's position that continued Oracle support was required for regulatory compliance. The client's regulatory obligations related to data retention, not to Oracle support coverage; Siebel's data was accessible through standard database queries independent of Oracle support status. Redress identified that the client could transition Siebel to a third-party support provider and maintain full access to the existing Siebel patch history and configuration documentation. This transition reduced the Siebel support cost to £240,000 per year — a 65% reduction — through a third-party provider that maintained equivalent functional coverage.
For the decommissioned WebLogic deployments, Redress advised on the contractual mechanism for terminating support on perpetual WebLogic licences covering applications that were no longer serving active users. Oracle accepted the termination request after Redress provided technical evidence of decommissioning. This eliminated £420,000 in annual support cost entirely.
For the divested EBS manufacturing modules, Redress structured a support termination based on the licence transfer and divestiture documentation that had been agreed at the time of the business unit sale. Oracle's team accepted that support obligations for the divested entity's licences had transferred with the business and that the client organisation had no continuing support obligation for those CSIs. This eliminated £540,000 in annual support cost.
For the remaining active Oracle Database and EBS financial modules — where Oracle support continued to be commercially justified — Redress negotiated a multi-year support commitment with a price cap agreement, eliminating Oracle's standard 8% uplift for a three-year period in exchange for a committed support term. This produced an additional annual saving of £420,000 versus the projected uplift trajectory.
The Outcome
The combined effect of the Siebel third-party support transition, the WebLogic and EBS module terminations, and the Oracle price cap negotiation produced a total annual cost reduction of £3.1M. The £4.8M annual Oracle support spend was reduced to £1.7M — a 65% reduction on the specific product lines addressed through the programme. The remaining £1.7M covers strategic Oracle Database and EBS financial modules that the organisation expects to maintain for the foreseeable future, now under a committed price cap arrangement.
The third-party support transition for Oracle Siebel was completed over a four-month period. The transition included a structured knowledge transfer from Oracle's support records to the third-party provider's service platform, and a parallel-running period during which both Oracle and the third-party provider provided coverage before Oracle support was formally terminated. No production incidents occurred during the transition.
Key Takeaways
- Oracle's support pricing narrative is designed to prevent rationalisation. Oracle's account teams routinely overstate the compliance risk of terminating or transitioning support. An independent review of the contractual basis for Oracle's arguments typically finds the risk to be significantly overstated.
- Divested business unit licences are a common source of avoidable support cost. When businesses sell divisions, Oracle support contracts for the divested entity frequently remain on the parent organisation's account unless actively addressed. This is a straightforward but consistently overlooked saving.
- Third-party support is a mature, commercially viable option for stable Oracle products. For Oracle Siebel, legacy EBS modules, and Oracle Middleware on stable versions, third-party support provides equivalent functional coverage at 50% of Oracle's price, with no impact on compliance status for correctly scoped perpetual licences.
- Oracle will negotiate price caps if presented with a multi-year commitment. For organisations committed to remaining on Oracle support for strategic products, a multi-year price cap in exchange for a committed term is a commercially accessible mechanism that Oracle's account teams can approve — but rarely volunteer.
- Support rationalisation should precede Oracle renewal discussions. Organisations that enter Oracle renewal negotiations without having addressed their unused or low-activity support spend negotiate from a weaker commercial position than those who arrive having already taken action.
Oracle support renewal approaching? Paying for products you no longer rely on?
Redress Compliance reviews Oracle support estates and identifies commercially defensible reductions that Oracle's team won't suggest.