This is where module 7 becomes a deal. A Fusion negotiation feels like it is about the discount; it is about five levers, and the discount is the one that matters least. This session ranks them by lasting value: honest scope sizes everything else, the ramp matches what you pay to what you deploy, price holds keep growth off list pricing, the renewal cap bounds every future term, and the discount, the lever sales sells hardest, governs only the first. It works a real rollout, 600 to 1,400 to 2,000 users ramped across three years, the price hold that saves the expansion from list, and the offer to trade seven discount points for the cap, the trade the whole session teaches you to refuse.
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 2,000 user rollout that should be ramped 600 / 1,400 / 2,000 rather than billed in full from day one; the 55% discount that inflates to list on the 400 users added without a price hold; and the offer to trade seven discount points for dropping the renewal cap. It closes with one Fusion deal negotiated end to end, the discount treated as the least of five wins.
The full narration of this session, section by section, for reading and reference.
Welcome back, session thirty three of forty. Two sessions ago you learned the metric. Last session you learned the contract. Today the two become a deal, the Fusion applications negotiation, end to end. Here's the frame that organizes everything today. A SaaS negotiation feels like it's about one thing, the discount, because that's the number sales leads with, the number that feels like winning, the number everyone in the room watches. It is, in fact, about five things, and the discount is the one that matters least. The five levers are scope, how honestly you size the deal; the ramp, how you pay for users as they deploy rather than years ahead; price holds, the rate at which you'll add users later; the renewal cap, the ceiling on every future uplift; and the discount, the first term headline. Four of those five outlast the discount, and this session is about fighting for the four that last. Today: scoping the users honestly, module by module. The ramp schedule, matched to your rollout. Price holds, so growth never happens at list. The renewal cap, the clause session thirty two called the most valuable in the contract, and why. And the tactics Oracle uses to pull you back toward the discount and away from the structure. Let's negotiate the deal.
Five takeaways. One, you'll scope to reality: size the subscription to the real user population of each module, by its own metric, not to headcount and not to the org chart's ambition. Two, you'll structure the ramp: match the paid, billed quantity to the deployment timeline, so you pay for users as they go live, not from day one. Three, you'll lock the price holds: fix the rate for adding users mid term at your deal discount, so the company's own growth isn't punished with list pricing. Four, you'll set the renewal cap: the hard ceiling on the uplift, negotiated at signature because it's essentially unobtainable afterward, and the single most valuable clause in the deal. And five, you'll answer the tactics: the manufactured quarter end clock, the bundle sweetener, the free ramp year, and the offer to trade discount for the cap, each recognized and each held. One sentence to carry: the discount is the lever that lasts the least, so spend your leverage on the four that last the most. The stakes, next.
Four numbers that frame the deal. Five: the levers that decide it, scope, ramp, discount, price holds, and the renewal cap, and four of the five outlast the discount everyone fixates on, which is the entire strategic point of the session. One: the renewal cap, set once, at signature, converting every future renewal from a ransom into a negotiation, and essentially unobtainable after you've signed. Three years: the typical term you're negotiating, and the term the uplift compounds across, so the deal you sign is the deal you live in for years, not months. And zero: your leverage after signature. Right now, before you sign, Oracle wants this deal, your data is still yours, you can still choose a competitor, and every clause is negotiable. The moment you sign, your business runs on the service, switching becomes a migration, and the balance of power inverts. Which is why the discipline of this session is simple to state and hard to hold: negotiate everything now, because now is the only time you have the leverage to negotiate anything. The discount is a first term number. Scope, ramp, price holds, and the cap govern every term. We'll take them in that order, deliberately, because that's the order of their lasting value. Scoping, first.
Scoping the users honestly, and notice it comes before any price is discussed, because everything else is applied to this number. Four disciplines. Count per module, per metric: each Fusion module carries its own metric, so you count the real user population of each, Financials by named user, HCM by employee, per session thirty one, and you never let one module's metric price another's, which was that session's twentyfold error. The access list, not the org chart: size to who genuinely needs access, at what tier, from the actual access list, not the aspirational headcount sales defaults to, because every phantom user is a full subscription line, every term, forever. Read only and service accounts: per session thirty two's definition trap, know whether the metric definition sweeps in read only viewers and integration service accounts, and scope for them or carve them out explicitly before you name a single number. And separate the go live from the someday: users who go live in year one are today's subscription, users who might join in year two belong in the ramp and the price holds, not in the day one count. Here's why this is the foundation and not a formality. Every later lever, the discount, the ramp, the cap, is applied to the scope. Oversize the scope and you've handed Oracle a bigger number to discount, to ramp, to uplift, and no discount later recovers what an honest count would have saved at the start. Scope first, price second, always. The ramp, next.
The ramp schedule, matched to deployment, because large Fusion rollouts go live in waves, not all at once. Four points. What a ramp is: a schedule that increases the subscribed, and billed, quantity over the term, year one at a fraction of the users, ramping to full by year three, tracking the rollout. Why it matters: without a ramp, you pay for the full user count from day one while only a fraction are live, and on a multi year deployment that's years of paying for users who aren't yet using the system, real money spent on empty seats. The discount holds across the ramp, and this is the part buyers miss: the negotiated discount must apply to every ramp tranche, not just year one, because a discount that quietly lapses as the ramp climbs is a price rise wearing the costume of growth. And align to the implementation plan: the ramp should track the real project plan, phase by phase, region by region, because a ramp faster than the rollout is just an early bill, and a ramp slower than it is a compliance gap. The ramp is where honest scoping meets the calendar, and like the scope, it's a standard, expected ask on any large deal. Its absence isn't a rule, it's a default, and the default is expensive. Knowledge check one puts a real rollout on the table.
Knowledge check one. A company will deploy Fusion to two thousand users over three years: six hundred in year one, fourteen hundred by year two, two thousand by year three. Sales quotes two thousand users from day one. What do you negotiate? A, nothing, paying for two thousand from the start is simplest. B, a ramp: six hundred users year one, fourteen hundred year two, two thousand year three, at the same discount, so you pay for users as they go live, not years ahead. C, a smaller total, just buy six hundred and add the rest later at list. Or D, nothing, the quantity can't be phased in a SaaS deal. Pause here. How many users are live in year one, and how many is sales asking you to pay for?
The answer is B. Do the arithmetic sales' simplicity skips. In year one, six hundred users are live, but the day one quote bills for two thousand, so you're paying for fourteen hundred users who won't touch the system for a year or more, and in year two you still overpay for six hundred. Across a three year term that's a large sum spent on empty seats, and it's entirely avoidable. B is the ramp: the subscribed quantity climbs with the deployment, six hundred, then fourteen hundred, then two thousand, so the bill tracks reality, and, critically, the negotiated discount applies to every tranche, not just the first, so the users added in years two and three arrive at the deal price, not at list. A pays for years of unused seats in the name of simplicity, which is exactly the default sales prefers, because the overpayment is real revenue. C makes the opposite error and walks straight into last session's trap: buy six hundred now, add the rest later, but later means at Oracle's list price with your leverage gone, so the fourteen hundred future users cost far more than they would have as negotiated ramp tranches. D is simply false; ramps are standard structure on any large Fusion deal, and their absence is the expensive default, not a limitation. The principle: the paid quantity should match the deployed quantity across the whole term, and the discount should hold across the whole ramp, both fixed now, at signature, when you have the leverage to fix them. Price holds, next.
Price holds for growth, because you will add users beyond the plan, and the price hold decides whether that growth happens at your discount or at Oracle's list. Four points. What a price hold is: a contracted rate for adding users mid term, locked at the deal discount, so the thousand and first user costs what the first thousand did, not undiscounted list. Why growth is the trap: without a price hold, every user added after signature is priced at list, and Oracle knows you'll grow, so unpriced growth is quietly the most common way a good deal decays into an expensive one. Hold the discount, not just the rate: the hold must lock the discounted rate, not a list price that itself rises, because a price hold pegged to a moving list is no hold at all, peg it to a fixed figure or a fixed discount percentage. And cover the likely additions: new modules, new user tiers, new regions, because a price hold that covers only the exact seats you bought leaves every genuine expansion exposed to list pricing. Here's the relationship to hold onto: scope and ramp size today's deal, price holds protect tomorrow's, and together they're worth more than the headline discount, while costing Oracle nothing to grant at signature. That last point is why they're winnable, and why their absence is negligence rather than defeat. Knowledge check two shows what their absence costs. Knowledge check two.
Knowledge check two. A Fusion deal closes at a strong fifty five percent discount, but with no price hold for adding users. A year in, the company adds four hundred users. What happens? A, the four hundred are added at the same fifty five percent discount automatically. B, the four hundred are priced at Oracle's current list, because nothing held the discount, so the expansion lands far above the deal rate and inflates the renewal base. C, nothing, you can't add users mid term. Or D, the whole subscription re prices to list. Pause here. What, in the contract, holds the fifty five percent for users bought after signature?
The answer is B. The fifty five percent discount was a property of the original order lines, not a standing entitlement, and unless a price hold clause explicitly extends it to future purchases, it does not carry. So the four hundred new users are priced at Oracle's current list, and the gap between fifty five percent off and list is enormous, often more than doubling the per user cost, which means the company's own success, growing its Fusion footprint, is punished with the worst pricing in the deal. Worse, per module four's annuity lesson, those list priced users inflate the base the next renewal uplifts from, so the mistake compounds for the life of the subscription. B is what actually happens, and it's one of the most common and expensive oversights in SaaS negotiation, precisely because the headline discount feels like the win and the price hold feels like a detail. A is the comfortable assumption the absence of a clause quietly destroys; discounts do not extend themselves. C is false; you can always add users, that's exactly how Oracle wants you to grow, at list. D overstates it; existing lines usually hold their rate, it's the new users that get list priced, which is bad enough. The rule: a discount you can't extend to growth is a discount with an expiry date, and the price hold is what removes the expiry, negotiated at signature alongside the discount, never after. The renewal cap, next.
The renewal cap, the clause that matters most, the one session thirty two named the single most valuable in a SaaS contract. Four points on why, and how to set it. What it does: a hard ceiling on the renewal uplift, for example no more than three percent a year, written into the order, bounding the price of every future term before those terms arrive. Why it's decisive: without it, the renewal uplift runs free, and Oracle sets it from a position where you cannot easily leave, so the cap is what converts the renewal from a ransom into an actual negotiation. Set it at signature or never: at signature Oracle wants the deal, at renewal Oracle holds your data and your dependency, so the cap is obtainable now and essentially unobtainable later, which makes it a signature term by its nature, not by preference. And cap the whole base, ramp included: the cap must apply to the full subscription as it ramps and grows, not just the year one lines, or the uncapped additions become the renewal's escape hatch, the loophole that swallows the clause. Here's the way to rank the levers, and it decides the whole negotiation: rank them by how long they last. The discount governs the first term. The cap governs every term after it. That is why the cap outranks the discount in any deal you actually intend to keep, which is every deal. The levers, ranked, next.
The five levers, ranked by lasting value, the table that reorders the whole negotiation. Honest scope: it controls the quantity everything else is applied to, and it lasts the whole term, because a wrong scope taxes every other lever, forever. The renewal cap: it controls the uplift on every future term, and it lasts every term after the first, compounding, which is the longest reach of any lever in the deal. Price holds: they control the rate for all future growth, lasting the whole term, every user you add. The ramp: it controls paying for users as they deploy, lasting the deployment period, years one to three. And the discount: it controls the first term headline price, and it lasts the first term only, after which the cap governs. Look at what this ranking exposes. Sales sells the discount hardest because it's the lever that lasts the least, so conceding it costs Oracle a single term. The buyer negotiates scope, cap, and price holds hardest because those are the levers that last the longest, so winning them protects every term. Same deal, opposite priorities, and the buyer who understands the ranking negotiates a fundamentally different contract than the one who watches only the discount. Oracle's tactics are all designed to pull you back up this table toward the discount. Let's name them. The tactics, next.
Oracle's tactics, and how to answer each. Five of them. The quarter end clock: the discount is real but the deadline is manufactured, so per module two's lesson you negotiate on your timeline and let the structure, not the calendar, decide when you sign. The bundle sweetener: session thirty one's trap, free modules that compound at renewal, so you price the deal you want standalone and take the bundle only if it wins on the renewal math, not the day one math. The free ramp year: a free or discounted year one that expires into an uncapped year two, so you welcome the discount but only alongside the cap and price holds that govern what comes after it. The discount for the cap: Oracle may trade a deeper discount to keep the cap out of the contract, and you refuse, because a bigger first term number is a poor trade for an uncapped every term after it, which is exactly the offer in the next check. And later, not now: session thirty two's redirection, the cap and price holds sorted after signature, and there is no after, signature is the only moment your leverage exists, so you fix them now. Notice the pattern across all five: each tactic trades something that lasts, the cap, the structure, your timeline, for something that doesn't, a bigger discount or an earlier signature. Recognizing the pattern is most of the defense. Knowledge check three puts the sharpest version of it directly to you. Knowledge check three.
Knowledge check three. Late in the negotiation, Oracle offers to raise the discount from fifty five percent to sixty two percent if the company drops its request for a three percent renewal cap. The team is tempted. Your advice? A, take it, sixty two percent is a better discount and discount is what matters. B, refuse the trade: seven more points is a first term saving, but dropping the cap exposes every renewal to an uncapped uplift that compounds for the life of the deal, keep the cap. C, take it and negotiate the cap at the first renewal instead. Or D, split the difference, fifty eight percent and a six percent cap. Pause here. Which lasts longer, seven points off year one, or an uncapped uplift on every year after?
The answer is B, and this is the whole session compressed into one offer, an offer Oracle makes precisely because it knows which lever the buyer overvalues. Seven more discount points apply once, to the first term. An uncapped renewal applies forever, compounding: at a modest eight percent annual uplift an uncapped subscription roughly doubles in under a decade, and Oracle sets that uplift from renewal, when your data and operations are inside its cloud and leaving is a migration you won't want. Run the arithmetic across a realistic horizon and the extra seven points is dwarfed several times over by the difference between a capped and an uncapped uplift, which is exactly why Oracle offers the trade, it's giving up a small, one time number to keep a large, permanent one. B refuses it and keeps the structurally decisive clause. A is the trade Oracle wants and the buyer regrets, mistaking the visible first term number for the value. C is last session's redirection restated: there's no negotiating the cap at renewal, renewal is precisely when you have no leverage, which is the entire reason the cap is a signature term. D concedes the principle for no reason, accepting a weaker cap and a smaller discount when the discipline is simply to hold the cap and let the discount land where it lands. The permanent rule, and the close of the teaching: the discount is the lever that lasts the least, so never spend the levers that last the most, the scope, the cap, the price holds, to get more of it. One deal, negotiated, next.
One Fusion deal, negotiated end to end, the session in six rows. Scope: as proposed, two thousand users day one with mixed metrics rounded up; as negotiated, scoped per module to real users, Financials on the named user metric, not the employee metric. Ramp: as proposed, none, full quantity billed from year one; as negotiated, six hundred, then fourteen hundred, then two thousand across three years, with the discount held across every tranche. Discount: as proposed, fifty five percent, headlined as the win; as negotiated, it landed at fifty seven percent, but treated as the least of the wins, not the point of the deal. Price holds: as proposed, absent, all growth at list; as negotiated, the discount locked for every mid term addition and new module. Renewal cap: as proposed, absent, the uplift uncapped; as negotiated, a three percent annual cap on the full base, ramp included. And the deal itself, the bottom row: what sales proposed was a big discount on a bloated, exposed subscription, and what was negotiated was a right sized subscription protected on every term. Look at the difference in shape. The proposed deal led with the discount and left four levers lying on the table. The negotiated deal treated the discount as the smallest win and secured the four that outlast it. Same suite, same list price, a structurally different contract, and the difference shows up not in year one but in every year after. Recap, next.
Session thirty three in three sentences. One, the deal is five levers, not one: honest scope sizes it, the ramp matches payment to deployment, price holds protect growth, the renewal cap bounds every future term, and the discount, the lever sales sells hardest, lasts the least. Two, scope to the real user population per module, ramp the paid quantity to the rollout with the discount held across every tranche, and lock a price hold so growth never happens at list. Three, set the renewal cap at signature, because it's obtainable now and never later, and never trade it, or the scope, or the price holds, for a few more points of a first term discount. Next session stays in module seven but changes product: NetSuite licensing and negotiation. A different animal, Oracle's mid market ERP acquired whole, with its own three layer model, its own user tiers, its own deep discount then aggressive uplift rhythm that you plan for from day one. The Fusion discipline transfers, but the mechanics are NetSuite's own, and the renewal behavior is documented and predictable, which means it's plannable. Homework first.
Homework, about an hour, and it's the session applied to a deal you can actually touch. One, scope a real deal: for a live or upcoming Fusion purchase, count the real user population per module and metric, then compare it to the quantity on the proposal, and note the gap. Two, draw the ramp: map the deployment plan by year and region, write the ramp schedule it implies, and note the cost of paying full quantity from day one instead. Three, check the price hold: in any current SaaS order, find the clause that prices mid term additions, and if there's none, that's your growth exposure, priced at list, waiting to happen. Four, find the cap: in every SaaS subscription you hold, look for the renewal cap, and where there's none, note the uncapped uplift risk against the renewal date in your session twenty five calendar. And five, rank your last deal: take your most recent SaaS deal and rank how hard each of the five levers was fought, and most estates find, honestly, that they fought only the discount. That finding is the whole reason for this session. See you in session thirty four, for NetSuite.
Five reads, all free on redress compliance dot com. First, Oracle Fusion ERP negotiation: the Fusion deal, lever by lever, at reference depth, the written companion to this session. Second, the Oracle Cloud ERP pricing guide: how the modules and metrics price, the base your negotiation actually works on. Third, the Oracle Fusion Cloud Applications guide: the pillars and modules you're scoping and ramping, the catalog behind the deal. Fourth, Oracle cloud contracts and credits for CIOs: where the ramp, the price holds, and the cap physically live in the paper, the clause level view. And fifth, FinOps for SaaS licensing: governing the subscription and its growth after the deal is signed, because a well negotiated deal still has to be managed. That's session thirty three. Five levers, not one; scope and ramp size today, price holds and the cap protect tomorrow, and the discount, the loudest lever, lasts the least. You can now negotiate a Fusion deal for the structure that outlasts the headline. Next session, NetSuite, the other SaaS, on its own terms. See you there.