Module 7 closes where the money actually lives: the renewal. A SaaS subscription is re bought in full at every renewal, and two things decide whether that re buy is fair, the shelfware you pay for but do not use, and the uplift that compounds on the whole base. This session turns the renewal into a discipline: how shelfware forms silently, right sizing to actual usage before any price is discussed because a discount on shelfware is still shelfware, managing the uplift with a cap and without one, swap rights and co terming, and the twelve month runway that is the only real source of renewal leverage. A renewal reached with no runway is not a negotiation, it is an invoice.
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 flat price offer on 1,000 seats when only 700 are active, a discount on shelfware; the 8% uplift bundled with a new module to hide both; and the renewal reached 30 days out with no usage data and no alternative, where the problem is the calendar, not the percentage. It closes with one renewal worked two ways, the drifting default against the disciplined runway.
The full narration of this session, section by section, for reading and reference.
Welcome back, session thirty five of forty, and the close of module seven. You've learned the SaaS metric, the SaaS contract, the Fusion negotiation, and NetSuite. Today we close the module where the money actually lives: the renewal. Here's the idea that reframes everything. A perpetual license you buy once and own. A SaaS subscription you re buy, in full, at every single renewal, because you own nothing, so every term is a fresh purchase decision, not a formality, whether anyone treats it that way or not. And two things decide whether that re buy is fair: shelfware, the subscriptions you're paying for but not using, and the uplift, module four's annuity in SaaS form, compounding on the whole base every year. Most organizations discover both only when the renewal quote lands, thirty days out, with no time to do anything but pay. This session turns the renewal into a discipline. Today: how SaaS shelfware forms, silently. Right sizing at the renewal, the one moment you can subtract. Managing the uplift, with a cap and without one. Swap rights and co terming. And building leverage, which starts twelve months before the renewal date, not the month before. Let's close the module.
Five takeaways. One, you'll see the shelfware: understand how unused SaaS subscriptions form silently, and why nobody notices until the renewal. Two, you'll right size at renewal: use the renewal as the one moment you can actually shed unused users, tiers, and modules, because mid term you can usually only add. Three, you'll manage the uplift: apply the cap where you have one and contest the uplift where you don't, with usage as your evidence. Four, you'll use swap rights: move spend from what you don't use to what you do, instead of losing it, and co term the estate into one negotiation. And five, you'll build leverage early: start the renewal a year out with usage data and a credible alternative, the only real sources of leverage in a SaaS renewal. One sentence to carry: right size to actual usage before you discuss price, because a discount on shelfware is still shelfware. The stakes, next.
Four numbers that frame the renewal. One hundred percent: the share of a SaaS subscription that's re bought at every renewal, because unlike a perpetual license nothing is owned, so every term is a fresh purchase decision, not a rubber stamp. Thirty percent: a common share of SaaS seats and modules that sit unused, the shelfware that forms silently and then rides the uplift, term after term, until someone acts. Twelve months: the runway a real renewal needs, because leverage comes from usage data and a credible alternative, and both take months to assemble before the notice date arrives. And three to eight percent: the annual uplift, module four's annuity in SaaS form, compounding on the whole base, shelfware included, every year you don't right size. Here's the through line of the module. Everything session seven taught, the metric, the contract, the negotiation, comes due at the renewal, and the renewal is where a subscription is either quietly re bought at its bloated size or deliberately right sized to what you use. This session turns those earlier lessons into a repeatable renewal discipline. How shelfware forms, first.
How SaaS shelfware forms, and it forms more quietly than perpetual shelfware, because there's nothing to install and nothing to see, it just accrues by default. Four ways. Users who left: people depart, change roles, or stop using a module, but their subscriptions roll on, because nobody deprovisions, because the seat costs the same whether used or not, so there's no prompt to remove it. Over tiered from day one: session thirty four's trap left uncorrected, full users doing self service work, paying the tier gap every single term because the assignment was never revisited. Modules never deployed: bundled or optimistically bought modules that never went live, session thirty one's bundle trap, riding the renewal uplift as pure shelfware. And growth that reversed: seats added for a project or a headcount plan that later shrank, never removed when the need passed, because SaaS makes adding easy and removing an afterthought. Here's the difference that makes SaaS shelfware worse. Perpetual shelfware you at least paid for once and keep, a sunk cost. SaaS shelfware you pay for again at every renewal, forever, with the uplift on top, until someone actually counts it and cuts it. And the first time it's visible is the renewal. Right sizing, next.
Right sizing at the renewal, because the renewal is the one moment the subscription is genuinely re opened. Four points. Why the renewal is the moment: SaaS contracts let you grow mid term but rarely shrink, so the renewal is the contractual opening to reduce quantities, drop modules, and re tier, which means right sizing doesn't happen whenever you notice the waste, it happens at the renewal or not at all. Count actual usage: pull the real numbers, active users per module, login recency, tier versus role, module adoption, and the platform measures all of it, so the evidence is available, precise, and undeniable. Cut, re tier, drop: remove the departed and dormant users, re tier the over tiered, drop the modules never deployed, and each one is a permanent reduction to the base that every future uplift compounds from, so the saving repeats every year. And do it before you discuss price: right size first, then negotiate the uplift on the smaller, honest base, because negotiating a discount on a bloated subscription just discounts the shelfware. That last point is the heart of the session, so let me state it plainly: a discount on shelfware is still shelfware. Right sizing is worth more than any uplift concession, because it shrinks the base that compounds, not merely this year's bill. Knowledge check one makes the trade off concrete.
Knowledge check one. At renewal, one thousand subscribed users show only seven hundred active in the last ninety days. Sales offers to hold the price flat if you renew all one thousand. Good deal? A, yes, a flat price with no uplift is a clear win. B, no: renew about seven hundred to actual use first, then negotiate, because flat pricing on one thousand is paying full price for three hundred unused seats, a discount on shelfware. C, yes, the three hundred extra seats are useful headroom for growth. Or D, no, demand a discount on all one thousand instead. Pause here. What is flat pricing on one thousand really holding flat, and how many seats do you actually use?
The answer is B. See the offer for what it is. Only seven hundred of the thousand seats are active, so three hundred are shelfware, and flat pricing on one thousand holds flat the cost of three hundred seats nobody uses, which isn't a win, it's paying full freight for emptiness and calling the absence of an increase a favor. The flat price is precisely the sweetener that keeps the three hundred in the base, because those three hundred seats carry into every future renewal and every future uplift, so the vendor happily forgoes one year's increase to preserve years of billing on unused capacity. B is the discipline: right size to the roughly seven hundred you actually use first, drop the three hundred, then negotiate price on the honest base, at which point flat, or better, on seven hundred is a genuinely good outcome. A mistakes the absence of an uplift for value while ignoring the thirty percent of the base that's pure waste. C rationalizes the shelfware as headroom, but that's exactly what the mid term price hold from session thirty three is for, you buy growth when it's real, at the held rate, not carry empty seats for years on the chance you might need them. D asks for a discount on one thousand, which just discounts the shelfware, session twenty four's lesson restated: a cheaper price on things you don't use is not a saving. The rule: usage sets the quantity, negotiation sets the price, and always in that order, because a price negotiated before right sizing is a price on your shelfware. The uplift, next.
Managing the uplift, module four's annuity in SaaS form, and how you handle it depends entirely on whether you set a cap at signature. Four points. If you have a cap: session thirty three's clause pays off right here, so you hold the vendor to it, and remember the cap is the ceiling, not the floor, so you negotiate below it where usage and market support, but the vendor never goes above it. If you have no cap: you contest the uplift with evidence, your right sized base, benchmark pricing, and a credible alternative, because an uncapped uplift is a proposal, not a fact, and it's negotiable when you bring leverage. Separate uplift from growth: vendors bundle the renewal uplift with new purchases so the total obscures the increase, so you unbundle them and negotiate the uplift on existing lines separately from the price on new lines. And cap it this time: if the last deal had no cap, the renewal is your chance to add one for next time, because every renewal is itself a signature, so every renewal can set the next term's cap. Here's why the uplift punishes shelfware twice: once as the wasted seat you're paying for, and again as the uplift applied on top of that wasted seat. Which makes right sizing the best uplift defense there is, you can't be over charged an uplift on a seat you already removed. Knowledge check two.
Knowledge check two. A renewal quote shows an eight percent uplift on the existing subscription, bundled together with a new module, as one total. How do you respond? A, accept the total, it's a single renewal number. B, unbundle it: negotiate the eight percent uplift on existing lines separately from the new module's price, so neither hides the other. C, reject the new module to avoid the uplift. Or D, accept, an eight percent uplift is standard and fixed. Pause here. What does bundling the uplift with the new module let the vendor hide?
The answer is B. The single total is a tactic, not a convenience. By presenting the eight percent uplift on your existing subscription and the price of the new module as one number, the vendor makes both harder to challenge: the uplift hides inside the excitement of the new capability, and the new module's price hides inside the routine of the renewal. B separates them, because they're two different negotiations. The uplift on existing lines is contestable with your usage data, your right sized base, and your cap if you have one, and it should be argued on those merits alone. The new module is a fresh purchase, priced on its own value and, ideally, on the price hold you negotiated in session thirty three, and it should be argued on those merits alone. Unbundled, each is negotiable; bundled, neither is, which is exactly why the vendor bundles. A accepts the tactic and pays whatever the blend conceals. C overreacts, rejecting a module you may genuinely want just to dodge an uplift you should instead contest, letting the tactic cost you the capability. D treats the uplift as fixed, which, absent a cap, it isn't, it's an opening position dressed as a standard, and evidence moves it. The rule: a renewal and a new purchase are two deals wearing one total, so split them apart and negotiate each on its own facts, always. Swap rights, next.
Swap rights and co terming, the most advanced renewal moves, turning unused spend into useful spend and aligning the estate so every renewal is one negotiation instead of many. Four points. What a swap right is: a contracted right to exchange unused subscriptions for others of equal value, moving spend from shelfware to what you actually need, instead of simply losing the unused. Why it beats a straight cut: sometimes the vendor resists dropping seats but will allow a swap, and a swap recovers the value of shelfware as capability you want, which is a better outcome than carrying the waste or writing it off entirely. Co terming the estate: align the renewal dates across your Oracle SaaS so they land together, because one combined renewal is one larger negotiation with far more leverage than many small, scattered ones spread across the year. And negotiate swap rights at signature: like the cap, swap rights are a signature term, cheap to obtain when the vendor wants the deal and valuable when your needs shift, as they always do across a multi year term. Put together, swap rights and co terming turn a scattered, drifting SaaS estate into a single, aligned negotiating position, and both are won at the signature and paid off at every renewal after it. Building leverage, next.
Where renewal leverage comes from, because a SaaS renewal feels like a position of weakness, your data and operations are already inside the vendor's cloud, so leverage has to be built deliberately, and early. Four sources. Usage data: the single strongest argument, because real adoption numbers, active users, module usage, tier fit, turn every right sizing and uplift discussion from opinion into evidence the vendor cannot dispute. A credible alternative: the exit terms from session thirty two made real, a genuine, costed migration option, even if you never take it, because leverage exists only when walking away is believable. Time: start twelve months out, because a renewal negotiated in the last month, against the notice deadline, has no leverage at all, since there's no time to build a case or stand up an alternative. And the cap and swap rights: the structural clauses from sessions thirty two and thirty three doing their job, because leverage built at the first signature is leverage you still have when the renewal arrives. Here's the principle to carry out of module seven: renewal leverage is not found at the renewal, it's built in the year before it, and written into the contract at the signature before that. Late is the same as none. The runway, next.
The renewal runway, twelve months out, five markers. Twelve months, start: pull the usage data and begin the right sizing analysis, because the renewal work starts a year before the date, not the month before, and it lives in the session twenty five calendar alongside every other renewal. Nine months, the case: build the right sized target and, if the leverage warrants it, cost a credible alternative, so the evidence is assembled deliberately, not improvised under pressure. Six months, open: open the conversation with the vendor on your terms and your timeline, not theirs, well ahead of any deadline pressure. Three months, negotiate: right size, contest or apply the uplift, unbundle new purchases, and set the next cap and swap rights, all with time to spare. And the notice date, decided: the auto renewal notice window from session thirty two, never missed, because the decision was made months earlier, not triggered by the deadline. Notice what the runway does. It converts the renewal from an event that happens to you into a process you run. The team that starts at twelve months negotiates; the team that starts at thirty days pays. Same subscription, same vendor, entirely different outcome, decided only by when the work began. Knowledge check three.
Knowledge check three. A renewal is thirty days away. The team has no usage analysis and no alternative priced. The vendor sends a nine percent uplift on the full subscription. What is the real problem? A, the nine percent uplift, negotiate it down now. B, the timing: with no usage data, no right sizing, and no alternative thirty days out, there's no leverage, so the problem is a renewal run in the last month, not the nine percent. C, nothing, nine percent is normal, just pay it. Or D, the contract, switch vendors immediately to escape. Pause here. Could the team right size or credibly threaten to leave in thirty days? If not, what does that tell you?
The answer is B. The nine percent is the symptom; the missing runway is the disease. Thirty days out, with no usage analysis, no right sized target, and no costed alternative, the team has nothing to negotiate with: it can't credibly propose a smaller base because it hasn't counted usage, and it can't credibly threaten to leave because no alternative exists and none can be stood up in a month. So whatever the vendor asks, the team pays, not because nine percent is fair but because it has no leverage to say otherwise. B names the real problem: this renewal was lost twelve months ago, when the runway should have started and didn't. A treats the nine percent as the issue and will negotiate from weakness, likely shaving a point or two off a number applied to an un right sized base, a small win on a big miss. C is surrender dressed as pragmatism, and it guarantees the same outcome next year and the year after. D is the panic move session thirty two warned against, you cannot switch vendors in thirty days, the threat isn't credible, and attempting it mid renewal is chaos, not leverage. The permanent lesson, and the reason this session closes with a calendar: SaaS renewal leverage is a function of time, so the work starts a year out, and a renewal reached with no runway isn't a negotiation, it's an invoice. Start early, every time. One renewal, worked, next.
One SaaS renewal, worked end to end, the same subscription taken two ways. Runway: the drifting default notices the renewal thirty days out; the disciplined renewal started twelve months out with usage data in hand. Shelfware: the default renews one thousand seats with seven hundred active; the disciplined renewal right sizes to seven hundred and drops three hundred from the base permanently. Tiers: the default keeps everyone on full users, unrevisited; the disciplined renewal moves the over tiered down to fit their actual work. Modules: the default carries two never deployed modules again; the disciplined renewal drops one and swaps the other for a module actually in use. Uplift: the default accepts eight percent on the full, bloated base; the disciplined renewal contests it on the right sized base and caps it for the next term. And the renewal itself, the bottom row: the default is a quiet increase on growing shelfware, and the disciplined renewal is a smaller, honest base, capped, co termed, and swap enabled. Look at the compounding difference. The default doesn't just overpay this year, it enlarges the base every future uplift works on, so the gap widens every term. The disciplined renewal shrinks that base, recovers the shelfware as capability, and bounds what comes next. Same subscription, two completely different futures. Recap, and module seven complete, next.
Session thirty five in three sentences, and with it module seven is complete. One, in SaaS the whole subscription is re bought at every renewal, so the renewal, not the first signature, is where most of the money is decided, and shelfware plus the uplift are what decide it. Two, right size to actual usage before you discuss price, because a discount on shelfware is still shelfware, then contest or cap the uplift, unbundle new purchases, and use swap rights to turn waste into capability. Three, leverage is built in the twelve months before the renewal, from usage data and a credible alternative, and written into the contract at the signature before that, so start early and every renewal becomes a negotiation, not an invoice. That completes module seven: the SaaS metric, the contract, the Fusion deal, NetSuite, and now the renewal discipline that keeps it all honest. Next session opens module eight, special topics and the capstone, starting with one of the most active audit fronts in the Oracle world: Java licensing. The employee metric that prices Java by your entire headcount, the subscription model, the audit campaigns catching estates off guard, and the migration paths to OpenJDK and other alternatives. Homework first.
Homework, about an hour, and it turns this session into a live renewal plan. One, measure the shelfware: for one SaaS subscription, pull active users per module against subscribed seats, and the gap is your shelfware, quantified for the first time. Two, draw the runway: for your next SaaS renewal, mark the date and count back twelve, nine, six, and three months into the session twenty five calendar, and ask honestly whether you're already behind. Three, test the uplift terms: find whether each subscription has a renewal cap, and where there's none, the next renewal is where you add one, per session thirty three. Four, look for swap rights: check whether any contract allows swapping unused subscriptions, and if not, that's a signature ask for the next renewal. And five, cost one alternative: for your largest SaaS spend, sketch what a credible alternative would cost and take, because even a rough figure is the start of real leverage. See you in session thirty six, where module eight opens with Java licensing.
Five reads, all free on redress compliance dot com. First, FinOps for SaaS licensing: managing subscription spend, shelfware, and renewals as a standing discipline, the operational home of this whole session. Second, Oracle NetSuite renewal negotiation: the renewal rhythm and how to bound it, worked in depth. Third, Oracle cloud contracts and credits for CIOs: where the cap, the swap rights, and the notice terms physically live in the paper. Fourth, Oracle Fusion ERP negotiation: the signature terms that make a good renewal possible in the first place. And fifth, the Oracle Fusion Cloud Applications guide: the portfolio you're right sizing at every renewal. That's session thirty five, and module seven is complete. The renewal is the deal; right size before you price, cap and contest the uplift, swap waste into capability, and build your leverage in the year before, not the month before. You can now run a SaaS renewal as a negotiation instead of receiving it as an invoice. Next session, module eight opens with Java licensing, one of the sharpest audit fronts Oracle runs. See you there.