A support renewal is not an invoice event; it is an annual negotiation most companies decline to attend. This session runs it properly: the five phase season that opens at T minus six months, the ask menu with each item's yes condition, the leverage inventory from priced alternatives to the fiscal calendar, the five rung escalation ladder above the renewal desk's scripted no, and the multi year trade that buys caps and locks without selling optionality the reduction program still needs. The worked season recovers $204K a year across four streams, and module 4 closes complete.
The presenter in this session is an AI generated avatar. The curriculum and guidance are real, produced by Redress Compliance analysts from our consulting engagements and market network.
A taught session with three knowledge checks: the invoice arriving thirty days out diagnosed as leverage already expired, the uplift waiver file that actually gets signed, and the desk's Oracle never discounts support script read as accurate testimony about its own authority. It closes with one four stream renewal season scored: $204K a year recovered, a three year zero percent cap on the largest stream, every win in writing.
The full narration of this session, section by section, for reading and reference.
Welcome back, session twenty of forty, the halfway mark of the course, and the last session of module four. Everything this module built converges on one recurring event: the renewal. Session sixteen taught you what the invoice really is, an annuity on autopilot. Seventeen taught you the policies underneath it. Eighteen gave you the reduction paths, nineteen priced the alternative. Today, all of it becomes a negotiation, run on a calendar, with a letter, up a ladder, to a signature. And here's the reframe that powers the whole session: a support renewal is not an invoice event, it's an annual negotiation that most companies simply decline to attend. The renewal desk counts on that absence. The uplift compounds on it. Today you learn to attend: the six month timeline, the full menu of winnable asks, the leverage inventory that makes them land, the escalation ladder past the desk's scripted no, and the multi year strategy that locks wins in. By the end, module four is a complete toolkit and the season is yours to run. Let's open it.
Five takeaways. One, you'll run the timeline: the renewal season opens at T minus six months, and you'll know exactly what happens in each phase, because the invoice date is the deadline for leverage, not the beginning of it. Two, you'll order from the menu: the complete list of winnable renewal asks, uplift caps, price locks, credits, terms cleanup, co termination, each with the conditions under which Oracle actually says yes. Three, you'll inventory the leverage: the priced alternatives, the pending business, the fiscal calendar, the portfolio view, and the one credible walk away that makes everything else believable. Four, you'll climb the ladder: the renewal desk, the account manager, the escalation tier, and the quarter end force multiplier, because knowing where each decision lives saves months of asking the wrong person. And five, you'll close the module: the machine, the policies, the paths, the alternative, and the negotiation, one integrated discipline, applied one date at a time, forever. Halfway through the course, and this is the session that pays the earliest and most often. The stakes, next.
Four numbers. T minus six, months before the renewal date, when the season opens. Why so early? Because the two things leverage is made of, open notice windows and executable alternatives, both die as the date approaches, and they die quietly. Three to eight percent, the default uplift that applies when nobody challenges it, compounding, per session sixteen's table, into a doubled bill across a decade. The uplift waiver or cap is the single most reliably winnable ask on the menu, and most estates have never once asked. Four, the sessions of preparation behind today: the audit that knows the estate, the policies that map the walls, the paths that price the exits, the alternative that disciplines the table. Today compresses them into a letter. And one, the renewal desk's answer to every first ask: no. Always no. It's a script, not a decision, and the entire back half of this session is the ladder above it. The framing sentence for everything today: every support stream renews annually whether anyone negotiates or not, so the only question is whether the one date a year finds you prepared or finds you absent. The timeline, next.
The renewal season, five phases. T minus six, refresh the baseline: session sixteen's audit rerun for this stream, what's deployed, needed, shelf, and ghost, today, not last year. Facts before strategy, always, because every ask downstream stands on this page. T minus four, price the alternatives: third party quotes requested and received, termination and restructure models built, session eighteen's paths applied to this stream's candidates. This is where the walk away gets built, and a walk away built after the notice window closes is a story, not a walk away. T minus three, check the windows: the notice periods verified against the current policies, dates diarized, because termination optionality survives only if notice can still be given, and the policies, not your assumptions, set the window. T minus two, deliver the ask: one written letter, all asks, the alternatives referenced calmly as priced facts, the term offer included if the strategy says multi year. The negotiation opens on your paper, at your time. And T zero, close on the date: the signed renewal with every win written in, or the executed alternative. Either way, a decision, not a default. One more encouragement: the second season is half the work of the first. The baseline rolls forward, the quotes refresh with a phone call, and the desk remembers who you are. The menu, next.
The ask menu, five items, each with its yes condition, because a menu without conditions is a wish list. The uplift waiver or cap: stops the compounding, the most reliably winnable item, granted when alternatives are priced and the ask is written, the desk's manager needs a file to point at, give them one. The multi year price lock: budget certainty for you, revenue certainty for them, granted when a longer commitment is on the table, it's a trade, and we'll handle its cost in the multi year section. Credits and fee relief: one time but real money, granted when pending purchases or cloud commitments need goodwill, support relief rides on deals Oracle wants closed, session eight's leverage moments, again. Terms cleanup: session eight's clauses retrofitted onto old streams, notice periods, definitions, caps, granted when bundled with a commitment worth having, never as a standalone favor. And co termination: aligning scattered renewal dates into one season, granted readily because it costs Oracle nothing and the account team likes it too, just remember seventeen's warning, align the dates, never merge the sets. Notice the shared precondition running down the yes column: a credible alternative in the room. The menu with leverage is a term sheet. Without it, a wish list. First test of the calendar. Knowledge check one.
Knowledge check one. The renewal invoice arrives, thirty days before the date, with an eight percent uplift. Is this the moment to open the negotiation? A, yes, the invoice is the natural trigger. B, no: the season opens at T minus six, because notice windows and alternatives need runway the invoice date no longer has. C, no, renewals cannot be negotiated at all. Or D, yes, but only by refusing to pay. Pause here. What options are still alive thirty days out?
The answer is B, and the reasoning is worth internalizing as a reflex. Run the clock backward from that invoice. Thirty days out: the termination notice window, typically longer than thirty days, has closed or is closing, so the walk away is dead or dying. No third party engagement can be diligenced, contracted, and onboarded in a month, so the alternative is a brochure, not an option. The baseline hasn't been refreshed, so even your facts are stale. What remains at thirty days is a request for mercy, and mercy is not a line item the renewal desk carries. That's why A, the natural feeling answer, is the expensive one, and notice the design: the invoice arrives precisely when every form of leverage has expired. That timing is not an accident; it's the autopilot working. B is the discipline: T minus six opens the season with everything alive, and the renewal calendar you built in session sixteen's homework, every date, every notice period, every owner, is exactly what makes T minus six visible before it passes. C is the desk's favorite customer belief, refuted by every uplift cap and retention counter this module has shown you. D confuses leverage with breach: unpaid invoices produce disputes and collection letters, not discounts, and hand the high ground away for free. Write the reflex down: the invoice is the deadline, the calendar is the invitation. Now, what makes asks land.
The leverage inventory, five sources, assembled before the letter goes out. One, the priced alternatives: the third party quotes and termination models from sessions eighteen and nineteen, current, documented, specific to this stream. Leverage, defined precisely, is an alternative the other side believes you can execute; the file is what makes them believe it. Two, the pending business: every purchase, expansion, and cloud commitment in the pipeline. Support relief travels on deals Oracle wants, so the renewal ask and the pending order should know about each other, coordinated by whoever owns the portfolio. Three, the fiscal calendar: session nine's quarter ends govern support like everything else. A renewal negotiable near May thirty first meets a counterpart with expanded flexibility and a number to make; time the escalation for it. Four, the portfolio view: twelve renewals negotiated separately by twelve cost centers have no leverage anywhere; the same twelve, coordinated into one season by one owner, have plenty, which is why the vendor management question from session sixteen keeps recurring. And five, the credible walk away: at least one stream, somewhere in the portfolio, where the alternative genuinely would be executed, and occasionally is. One real termination, executed calmly, teaches the desk more about your company than a decade of assertive letters. Credibility is bought in actions and spent everywhere. The uplift, tested. Knowledge check two.
Knowledge check two. The eight percent uplift on a five hundred thousand dollar stream: what actually gets it waived or capped? A, a firm letter explaining that eight percent is too high. B, nothing, the uplift is contractual and immovable. C, a written ask at T minus four, alternatives priced and referenced, ideally attached to pending business or a multi year commitment. Or D, paying it this year and complaining next year. Pause here. What does the desk's manager need to see to say yes?
The answer is C, and the mechanism deserves to be understood, not just memorized. The uplift is the policies' default, not a law of physics, and it moves for exactly one profile of buyer: the one whose file, when it lands on the approver's desk, shows priced alternatives and timing that leaves them executable. C assembles that file: the ask is written, so it can travel up the ladder intact; it arrives at T minus four, so the notice window is still open and the walk away breathes; it references the third party quote and the termination model as facts, not threats; and where the pipeline allows, it rides a pending purchase or offers a multi year term, giving the account team an internal reason to spend capital on your cap. That package gets uplift waivers and multi year zero caps signed every quarter of every year, and the wins go into the paperwork per session eight, in writing, multi year where possible. The wrong answers: A is eloquence without consequence, the desk processes too high daily and has a paragraph ready. B mistakes the desk's script for your contract; unless a cap clause exists, the uplift is practice, and practice bends to leverage. D forgets the compounding: this year's eight percent becomes next year's base, so a deferred challenge pays the increase twice. And notice what C never includes: anger, ultimatums, drama. The strongest renewal letters read like arithmetic. Because they are. The choreography, next.
Running the negotiation, five rules of choreography, several of them old friends. Rule one, one letter, all asks: the season's requests travel as a single written package at T minus two, session ten's rule at renewal scale. Bundled asks get negotiated as a package; serial asks get individually declined and forgotten. Rule two, reference, never threaten: the alternatives appear as priced facts, we hold third party quotes at approximately half the current fee, delivered in the tone of a weather report. Facts travel up the ladder and into approval files; threats generate defensiveness and stall at the desk. Rule three, let the desk say no: the first no is the script executing, not the negotiation concluding. Receive it politely, thank them, and treat it as the signal to climb, which it is. Rule four, trade term for terms: the asset you hold that Oracle genuinely wants is commitment length. Spend it deliberately and visibly, years in exchange for caps, locks, and terms cleanup, and never hand over term length for atmosphere, session ten's donation rule, still in force. And rule five, bank everything: every concession goes into the renewal paperwork before signature, in writing, multi year where the trade supports it. The retention desk's verbal warmth has the shelf life of the fiscal quarter that produced it, and module four has repeated this rule in every session because estates keep learning it the expensive way. The ladder itself, next.
The escalation ladder, five rungs, because support pricing authority is distributed by design and most negotiations die from asking the wrong altitude. Rung one, the renewal desk: processes paperwork, quotes the uplift, and says no to everything, because its job is throughput, not deals. Authority: effectively none. Spend exactly one exchange here, then climb, staying friendly, the desk controls your paperwork's speed if nothing else. Rung two, the account manager: owns the relationship number, wants the pipeline protected, can sponsor your asks internally. This is the real first conversation, and your leverage inventory is written for their consumption, they need a story to carry upward. Rung three, the escalation tier: regional management and renewal specialists, engaged by the account team when real revenue is at risk. This is where caps, waivers, and credits actually get signed. You rarely meet them; your file does, which is why it's written like arithmetic. Rung four, not a person but a force: the quarter end. Every rung's flexibility expands as session nine's dates approach, so the climb is timed to arrive at rung three inside a closing quarter. And rung five, the executive lever: your executives to theirs, reserved for portfolio scale moments, powerful precisely because it's rare. Spend it annually and it devalues to noise. The ladder reframes the desk's no completely: it's not the answer, it's the door. Multi year strategy, then the final check.
The multi year strategy, the deliberate trade, four points. What term length buys: caps, locks, and credits get granted against commitment, and a three year renewal with a zero percent cap, in writing, routinely beats three consecutive annual fights, in both outcome and effort. The desk's ladder moves for multi year offers because revenue certainty is what their side is paid to manufacture. What it costs, stated honestly: optionality. A locked stream cannot move to third party, cannot terminate, cannot restructure until the term ends. So the rule is: lock only what the fit profile says is staying, the actively developed core that session nineteen kept on Oracle support anyway. Locking a stream the reduction program might touch is selling your own options cheap. Co terming done right: aligning renewal dates concentrates twelve scattered skirmishes into one annual season with real leverage, and Oracle grants it readily. But hear session seventeen's warning again, because the paperwork will blur it: align the dates, never merge the sets. Consolidated billing is convenience; consolidated license sets are hostages. Read the consolidation offer carefully and take only the calendar. And the mixed portfolio, the pattern that works: multi year locks on the committed core, annual flexibility everywhere the program might reach. Certainty where you want it, options where you need them. Final check: the desk's favorite sentence.
Knowledge check three. The renewal desk responds to your carefully assembled letter: Oracle does not discount support, ever, for anyone. What is actually true? A, the desk is right, and the negotiation is over. B, the desk is describing its own authority accurately, and the ladder above it grants caps, waivers, and credits every quarter, to prepared buyers. C, the desk is lying and should be reported. Or D, discounts exist but only for the largest companies. Pause here. Whose authority did the answer describe?
The answer is B, and there's a small epiphany inside it: read the desk's sentence as testimony about the speaker, and it becomes perfectly true. The renewal desk does not discount support, ever, for anyone. That is the design. Its script speaks in company wide absolutes because absolutes end conversations, and ending conversations is the desk's function. But module four has now walked you through everything above that desk: retention counters at thirty five percent when a termination was credible, session eighteen. Uplift caps at zero signed against multi year terms, this session. Credits riding pending purchases, the menu. All granted on the ladder's upper rungs, every quarter, to buyers who arrived with the file. So the desk's no gets processed exactly as the choreography prescribes: politely, once, and then the account manager conversation begins, leverage inventory attached, quarter end approaching. A mistakes a script for a fact and funds the difference in perpetuity. C misdiagnoses institutional design as personal dishonesty; the agent is doing their job, and hostility toward rung one buys nothing on rungs two and three. D is folklore with a grain: scale helps, but every mechanism in this module, the audit, the paths, the alternative, the season, runs on preparation rather than mass, and mid size estates cap their uplifts every quarter too. The desk, in trying to end your negotiation, just summarized the module: authority lives above the script, and preparation is the climb. Let's score the season.
One renewal season, four streams, coordinated by one owner, scored. The ERP support stream, four hundred thousand: the ask was a zero percent uplift cap for three years plus terms cleanup, offered against a three year commitment on a platform the fit profile said was staying anyway. Granted at rung three, inside the quarter. Locked certainty on the committed core, costing optionality the program was never going to use. The legacy estate, two hundred twenty thousand: no ask at all, the third party switch simply executed, per session nineteen, saving a hundred ten thousand a year. Sometimes the negotiation is a letter; sometimes it's just the alternative, executed. The middleware stream, one hundred eighty thousand: a termination notice, sent expecting the retention counter, which arrived on schedule at thirty percent off. Compared against the alternative, taken, banked in writing for the term. Session eighteen's fifth path, run exactly by the book. And the analytics stream, one hundred fifty thousand: a credit request attached to the pending expansion order, forty thousand granted, riding the purchase Oracle wanted closed. The season's total: two hundred four thousand dollars a year recovered, plus a three year cap on the largest stream, every win in writing, no wanted coverage lost anywhere. One owner, one calendar, one letter per stream, one climb. That's module four, executed. That's the session.
Session twenty in three sentences, and with it, module four. One, the renewal season opens at T minus six with the baseline refreshed and the alternatives priced, because the invoice date is when leverage expires, not when it's gathered, and the calendar is what makes the season visible in time. Two, the asks travel as one written package, the desk's scripted no marks the first rung of a ladder where caps, waivers, and credits genuinely get signed every quarter, and commitment length is the currency that buys them, spent only on streams that are staying. Three, module four is complete: the annuity machine, the two policies and their set boundaries, the five reduction paths, the priced alternative, and the negotiated season, one integrated discipline that pays every single year. Next session opens module five, and it's the one everyone has been waiting for, or dreading: audits and compliance defense. Every Oracle customer gets audited eventually, and the outcome is decided long before the letter arrives, by preparation, which, conveniently, is what the last twenty sessions have been building. The letter, the process, the defense, the negotiation, the settlement. Five sessions. Bring the records. See you in session twenty one.
Homework, about an hour, and it stages your first real season. One, build one season plan: your largest renewal stream, the T minus six timeline laid against its actual date, phases and owners assigned. If the date is closer than six months, start anyway, compressed seasons still beat absences. Two, draft the ask letter: the menu applied to that stream, alternatives referenced as facts, the term offer considered. One page, arithmetic tone. Even unsent, drafting it reveals which leverage you have and which you need to build. Three, map the ladder: actual names, your renewal desk contact, your account manager, and whoever the escalation tier would be for your account. Most estates have never written these three names on one page, and the page changes how the next no lands. Four, design the portfolio: which streams get multi year locks, which stay annual for the program's sake. The mixed portfolio, drafted deliberately instead of accreted accidentally. And five, archive the module: the baseline audit, the set map, the path assignments, the fit profile, and now the season plan, into one support playbook file with an owner. Module five will borrow its discipline shortly, and audits love nothing more than an estate with its files in order. That's the hour, and that's module four. See you in session twenty one.
Five reads, all free on redress compliance dot com. First, the Oracle renewal negotiation checklist, today's season in checklist form, laminate it if you're the type. Second, Oracle renewal negotiation strategy, the leverage inventory and the escalation ladder worked as full strategy. Third, the Oracle contract renewal strategy guide, the portfolio wide season, twelve streams, one owner, one calendar. Fourth, the Oracle support renewal contract checklist, the clauses every renewal signature should carry out the door. And fifth, dealing with Oracle sales tactics, the motion on the other side of your season, worth rereading now that you know what the desk's script is for. That's session twenty, and that's module four: an annuity examined, two policies mapped, five paths walked, one alternative priced, and a season that turns the quietest large number in the budget into an annual negotiation you attend and win. Halfway through the course. Module five is audits, and for the first time in twenty sessions, the phone rings from their side. See you there.