An Oracle renewal that produces the bottom decile outcome of less than ten percent savings is almost always the same renewal that started six weeks before the renewal date. An Oracle renewal that produces the top decile outcome of more than sixty percent savings is almost always the same renewal that started twelve months before. The single biggest factor in renewal outcomes is the time the buyer side has had to prepare, document, and execute the negotiation. This article maps the twelve months in operational detail.
The timeline is conservative. Some renewals can be executed in nine or ten months. Some require fifteen. The principle is constant. The renewal is not a renewal. It is a negotiation event with leverage symmetric to a new license event when executed with discipline.
Month 12: Discovery and inventory.
Twelve months out the buyer side begins the deployment audit. Every Oracle product covered by the renewal, every install, every server, every named user, every employee covered by the licence metric. The audit produces the inventory that becomes the input to every subsequent decision. The audit also surfaces compliance exposure that will need to be quantified and managed before any conversation with Oracle.
The audit work should be conducted by software asset management with explicit involvement from the application owners. Inventory data alone is insufficient. The mapping of installations to applications and to business value is required for the strategy phase. See Contract Review for the contract side of the discovery work.
Month 10: Cost benchmark.
Two months into discovery the cost benchmark begins. The current Oracle support spend is decomposed by product, by metric, and by support type. The benchmark compares the buyer support cost to the published Oracle support rate. The gap is documented. The benchmark also compares the buyer support cost to comparable benchmarks from advisory data sets. The output of the benchmark is the documented buyer position on what the renewal price should be.
Month 8: Alternative analysis.
Four months in the alternative analysis begins. The alternatives include third party support, the migration to a non Oracle product, the termination of unused entitlements, and the renegotiation of the support model. For Database, see the Oracle Database product page for the alternative options.
Month 6: First conversation.
At six months out the first conversation with Oracle takes place. The buyer position is presented in summary. The buyer expectations are set. The Oracle account team is engaged. The negotiation is officially open. The buyer position is documented. The Oracle response is recorded.
Month 4: Counter offer.
At four months out the written counter offer is delivered to Oracle deal desk through the line account executive. The counter offer addresses every commercially significant line item with the buyer position and the analytical justification. See Renewal Negotiation for the structured counter offer methodology.
Month 2: Escalation and deal desk.
At two months out the negotiation enters the deal desk phase. The line account team has reached its discount approval ceiling. The escalation is initiated. The buyer side has the documented alternative and the credible walk away ready. Oracle responds with revised terms that reflect the deal desk approval level. The pricing converges to the documented floor.
Month 1: Close and signature.
The final month is the close. The contract terms are finalised. The renewal uplift cap is documented. The legal review is completed. The signature package is prepared. The signature occurs on or near the renewal date. The renewal is complete. The post signature documentation is filed for the next cycle.
For the broader pillar coverage see the Renewal Negotiation cluster. For the deal structure see Co-Term Renewal. For the full research see the Oracle Negotiation Playbook and the year end renewal leverage note.