The renewal problem.
Oracle support renewals are the largest recurring cost in the relationship between Oracle and its customers. The contract terms permit Oracle to increase support by up to twenty two percent per year for support that is decoupled from the original product purchase, and Oracle frequently takes the full uplift. Over a five year period, an annual twenty two percent uplift compounds to roughly two and a half times the original support cost. That is the headline problem.
The deeper problem is that Oracle structures the renewal conversation to make negotiation difficult. Renewals are processed as administrative events through the customer success organisation. Discounts are framed as exceptions that require deal desk approval. Counter offers from the buyer are routinely returned with the explanation that the contract terms do not permit the requested change. Most buyers accept the proposed renewal without serious negotiation because the cost of pushing back appears to be higher than the cost of compliance. That perception is wrong.
What we do.
Our renewal negotiation engagement starts ninety days before the renewal date when possible, and earlier for complex estates. The first phase is discovery. We inventory the current Oracle estate, the historical pricing, the support tier, the previous discount level, and the deployment footprint. We model the renewal under several scenarios including continue as is, partial termination, repricing through a co terminated structure, and full restructuring.
The second phase is counter offer build. We construct the buyer side proposal with three reference points. The market floor for similar deals in similar industries. The cost based floor that Oracle internally treats as the limit of negotiability. The walk away point at which the buyer is better off either terminating support, migrating to third party support, or moving the workload to a different platform. Each of these reference points is documented and shared with the procurement leadership.
The third phase is the negotiation itself. We do not sit in front of Oracle as the named buyer. We sit alongside the procurement and finance leaders on the buyer side and prepare the moves in real time. Oracle responses are decoded as they come in. Counter responses are drafted with reference to the documented floor and the deal timing. Concession patterns are tracked against the agreed savings target.
Engagement deliverables
- Current state assessment with full Oracle estate inventory and renewal modelling.
- Counter offer document with three reference points and supporting market data.
- Negotiation playbook tailored to your account profile and Oracle relationship pattern.
- Live negotiation support across multiple rounds until contract signature.
- Thirty day post signature question and answer support to handle any residual issues.
How we price.
Renewal negotiation is offered exclusively on the success fee model. Zero retainer. We get paid only when you save against an agreed baseline. The baseline is set at engagement start using the most recent Oracle proposal or, if a proposal has not yet been issued, the modelled renewal at current contract terms with the maximum uplift applied. The fee is a percentage of documented savings against that baseline.
The success fee model is appropriate for renewal work because the engagement outcome is measurable, the baseline is contractually defined, and the timeline is bounded by the renewal date. Procurement leaders prefer this model because it places the advisor fully on the buyer side of the outcome.
When to engage.
The ideal engagement window is six months before the renewal date. This window allows time for full discovery, complete counter offer development, and multiple negotiation rounds with Oracle. Engagements starting four to six months before renewal are common and still produce strong outcomes. Engagements starting under sixty days before renewal are possible but constrain the available tactics.
Some scenarios benefit from very early engagement, eighteen months or more before renewal. These include co termination strategy for clients with multiple staggered Oracle agreements, repricing strategy for clients moving workloads off Oracle, and any case where the buyer is considering migration to third party support providers.
Common renewal scenarios.
The renewal portfolio across our engagements falls into a small number of recurring patterns. The standard renewal involves a single Oracle agreement renewing on its anniversary date with the support uplift applied. The co terminated renewal aligns multiple Oracle agreements to a single anniversary, which simplifies administration but also creates a single high stakes negotiation. The partial termination renewal removes a subset of licenses from the support contract, which requires careful analysis because Oracle support termination is not always available without a corresponding price increase on the remaining licenses.
The restructured renewal converts the relationship to a new commercial structure such as a new ULA, a multi year support agreement, or a cloud commitment. The third party support transition migrates support away from Oracle to a provider such as Rimini Street or Spinnaker, which Oracle will typically respond to with aggressive retention tactics. Each scenario requires a different playbook.
Related resources.
- Co-Term Renewal deal type page covers how aligned renewal dates change the leverage equation.
- Perpetual Licenses deal type page explains the underlying license structure that drives the renewal.
- Oracle Database product page for Database specific renewal patterns.
- The Negotiation Playbook 58 page white paper with counter offer templates.
- Renewal Negotiation blog cluster with detailed tactical articles.