The renewal uplift cap is the single most consequential clause in any Oracle support contract. The standard Oracle contract permits up to twenty two percent annual uplift on support, calculated against the previous year support value. Compounded over five years, a twenty two percent annual uplift more than doubles the support cost. A renewal cap negotiated at the original deal stage at three percent, four percent, or five percent annual uplift produces compound savings that exceed the original deal value in most multi year scenarios. This article covers the mechanics of negotiating that cap and the contract language that holds.
The structure of the cap.
A renewal cap is a written contract amendment that limits the annual uplift on support to a specified percentage. The cap should be expressed on net price not on list price. The cap should specify the period to which it applies. The cap should specify whether it applies only to the first renewal or to all subsequent renewals. The cap should be enforceable through the standard Oracle contractual remedies.
The four parameters to negotiate are the rate, the duration, the scope, and the enforceability. The rate is the headline number. The duration determines how many renewal cycles benefit. The scope determines which products and which support types fall under the cap. The enforceability determines what the buyer can do if Oracle proposes a renewal above the cap.
When to negotiate the cap.
The leverage to negotiate a cap is asymmetric. The leverage is highest at the original new licence deal when the buyer is making a substantial commitment. The leverage is moderate at the ULA renewal stage. The leverage is low at the support renewal stage. The optimal pattern is to negotiate the cap at the original deal or at the ULA renewal, not to wait for the support renewal cycle.
Buyers that have already signed without a cap can still introduce the cap at the next material commitment. A cloud commitment, a new licence purchase, an audit settlement, or a ULA renewal all create the leverage moment. See the ULA exit strategy for the ULA renewal lever.
Cap rates observed in the market.
The cap rates observed in the engagement data range from zero percent to seven percent. The lower bound of zero percent is a hard price hold for the duration of the cap. Hard price holds are accepted by Oracle in a small minority of cases, typically large strategic deals with multi year commitments. The upper bound of seven percent is observed in deals where the buyer commitment is smaller and the buyer alternative is less credible.
The most common rate in mid sized deals is between three and five percent annual uplift. Five percent is achievable in most negotiations where the buyer position is documented and the deal value justifies the deal desk attention. Three percent requires stronger leverage. Zero percent requires a strategic deal context.
Cap durations observed in the market.
The cap duration observed in the engagement data ranges from three years to perpetual. Three year caps are the most common at moderate cap rates. Five year caps require larger deal values and stronger leverage. Perpetual caps are observed in a small number of strategic deals and typically come with offsetting commitments in scope or term.
The buyer should not accept a cap shorter than the planned product use horizon. A three year cap on a product the buyer expects to run for ten years leaves seven years of uplift exposure. The cap should match the expected horizon or the buyer should accept the residual exposure as a known item.
Cap scope and product families.
The cap scope determines which products and support types fall under the cap. The standard cap covers all products in the contract. Variations exist. Caps that cover only Technology products and not Applications products. Caps that cover only Enterprise Edition products and not Standard Edition products. Caps that cover only the original products and not products added during the cap period. The buyer should negotiate the broadest possible scope at the original deal stage.
The exact language that works.
The language pattern that holds in audit and in renewal disputes is precise. The cap clause should reference the support cost in the prior year as the baseline, not the list price. The cap should be expressed as a percentage uplift. The cap should specify that the cap applies notwithstanding any general price increase by Oracle. The cap should specify that the cap applies in the absence of any contrary written agreement.
For broader contract language see the Oracle end user licence agreement note and the indemnification clauses analysis. The contract review service is at Contract Review.
What to expect from Oracle.
Oracle deal desk response patterns on cap requests are consistent. The first response is typically a counter proposal at a higher rate or a shorter duration. The second response moves toward the buyer position if the buyer position is documented and the commitment in the original deal justifies the cap. The third response converges. The negotiation typically resolves within two to three rounds when the buyer position is clear from the start.
For the wider tactical context see the Negotiation Tactics cluster. For the research see the Oracle Negotiation Playbook. For the deal structure see Co-Term Renewal. The service is at Renewal Negotiation.