Full narration of the briefing. Click a section heading to jump the player to that moment.
Roughly four in five customers certify. This session is for the other one, because renewal is sometimes genuinely right and it deserves to be done well rather than defended apologetically. Renewal is right when you will deploy materially more Oracle in the next three years than you already have, with named projects behind that claim. It is also right when a major acquisition is landing, or when a platform programme is about to multiply your database estate.
I am Tom, Daniel is with me, and this is how to negotiate a renewal so that it is a purchase rather than a rollover.
Start with how Oracle prices it, because that shapes everything else. A renewal fee is built from your current certified position plus the growth they expect you to have. In other words, the number you would certify at is the floor of the conversation. That produces a result which surprises people: the more successfully you deployed during the term, the higher the renewal quote, because the value you extracted becomes the baseline they price from.
That is not a reason to deploy less. It is a reason to know your certification number before Oracle proposes a fee, so you can see exactly what you are being charged for.
Which brings us to the anchor, and it is the most common failure in a renewal. The fee gets presented as a percentage change against your old fee. Ten percent up, or flat if you sign early. That framing is comfortable and it is the wrong comparison entirely.
The right comparison is what those licences would cost you to buy outright, at your best achievable discount, set against what the renewal costs. If a renewal costs more than simply purchasing the growth you actually expect, then renewal is a worse deal wearing a familiar label. Build that comparison yourself, before you respond to any number.
So what is actually on the table. Five things, and price is only one. The product scope, which is your chance to remove products you never deployed and add the ones you now need. The entity and territory definitions, which should be updated for every acquisition and disposal since the last signature.
The certification methodology, which is the single most valuable clause in the document and the subject of session eight. The term length, because three years is a default rather than a rule. And the support base treatment, which is often the largest number in the agreement and gets discussed last, if at all.
Now three traps. First, silent scope shrink: the renewal paperwork quietly drops a product or narrows a territory, and nobody compares the schedules line by line. Always diff the new agreement against the old one. Second, support base creep: your support bill is calculated from an underlying licence value that a renewal can reset upward, so ask explicitly what happens to it and get the answer in writing.
And third, automatic renewal language, which converts a decision into a default. If your agreement renews unless you act, put the notice date in the calendar with a six month warning, because missing it costs you the entire negotiation.
Here is the tactic that matters most, and it is straightforward. Prepare your certification in full even if you intend to renew. Run both tracks in parallel through the final year. That gives you an actual number for what you would own if you walked away, and that number is your alternative to agreeing.
A renewal negotiation where you can say precisely what certifying gives you is an entirely different conversation from one where certification is a vague and slightly frightening unknown. The preparation costs a few weeks of effort, and it is the only thing that makes renewal a choice rather than the safer option.
The move from this briefing: before you accept any renewal quote, write two numbers on one page. What certifying today would give you, in products and quantities. And what buying your genuinely expected growth would cost at your best discount. If the renewal fee beats the sum of those, renew with confidence.
If it does not, you now have the argument, in your own numbers. Next session: life after certification, and the costs and options that arrive on the day the ULA ends. See you there.
Redress Compliance works on contingency: our fee is 25 percent of what we save you. Nothing saved, nothing paid. Independent, buyer side only, never vendor funded. Want Redress to contact you? Reach out and we respond the same day.
Talk to a Oracle negotiator