List versus net, what discounts actually land by deal size, and the calendar that moves them. Three knowledge checks along the way, and 1 clip from a senior cloud advisor.
This is a taught session, not a talking head. The instructor works through analyst grade slides, and three times the video stops on a question with four options on screen. Pause, commit to an answer, and the next slide explains which option is right and why each of the others is wrong. Once in the session the frame splits and a senior cloud advisor gives the view from inside real Oracle negotiations, and the instructor picks the clip apart when the slides return.
The full narration of this session, section by section, for reading and reference. Guest analyst clips are marked.
Welcome back, session five of thirty, and the module one finale. We've done the master, the orders, and the policies, the whole written stack, and I promised you money, so today: money. How Oracle actually prices cloud, list versus net, the levers that move the number, what good looks like by deal size, real ranges you can hold a quote against, and the calendar, because in this vendor relationship, when you ask is worth almost as much as what you ask. If you did session three's homework, you computed a net unit rate for your biggest cloud order and wrote it on the front page in pen. Keep it in reach. By the end of this session you'll know whether that number is something to defend or something to fix. Let's talk about the machine first.
Five takeaways. One, the machine: how a cloud price is actually built, public rate cards, internal discount tiers, and an approval ladder, because once you see the machine, the word impossible loses most of its power. Two, the levers: the four things that genuinely move a cloud price, ranked by power, and the ranking will surprise people who think volume is king. Three, the benchmarks: realistic net outcomes by deal shape, for credits and for SaaS, so that your quote meets a number instead of a feeling. I'll give you a table you can put on the wall. Four, the programs: migration funding, Support Rewards stacking, marketplace routes, the money that sits beside the discount and never appears on a quote unless you ask. And five, the calendar: Oracle's fiscal rhythm, May thirty first above all other dates, and the posture that turns their deadline into your leverage.
The pricing machine, three parts. Part one, the public rate card. OCI publishes unit prices for every service, SaaS publishes per user list prices, and this public layer creates a comforting illusion of transparency. Understand: the transparency ends exactly where the money starts. List is the anchor Oracle sets for the negotiation, not the price anyone serious pays. Part two, the discount tiers. Universal Credits discounts scale with committed volume and term, SaaS discounts scale with subscription value and how strategic the deal is internally. The tier thresholds are internal, but they're real, and they're worth probing for, because sometimes a slightly larger commitment crosses a threshold and buys a disproportionately better rate, and your rep will rarely volunteer where the cliff is. Ask what the rate would be at the next tier. It's a free question. Part three, the approval ladder. The rep owns small discounts. The deal desk owns real ones. Executives own exceptions. Which means every impossible you'll ever hear is relative to a rung on that ladder, the ask that dies with a rep on a Tuesday clears the deal desk in the last week of a quarter. And one translation for the on premises veterans: list minus discount is still the game, but the compounding changed. On premises, your discount compounded through support forever. In cloud, the renewal is where your rate lives or dies, so you protect the rate across time, not just at signature. Session three taught you that; today we price it.
The four levers, ranked by power, and the ranking matters. Lever one, the strongest by a distance: a credible alternative. A costed AWS or Azure path for the workload, a rival SaaS bid, even a rigorous stay put case. Notice the word costed, not preferred, not planned, costed. You don't have to want it. You have to be able to show it, because the deal desk prices against your options, and a buyer with no alternative is a buyer paying list minus courtesy. Lever two, volume and term: bigger commits and longer terms buy deeper tiers, genuinely. But this lever is powerful and dangerous in equal measure, because every volume pitch is also a forfeit pitch, and session three's arithmetic doesn't stop being true because the discount got prettier. Commit to what you measure. Lever three, timing: the identical ask lands differently in week two of a quarter and in the last week of May. Timing costs you nothing, which makes it the best value lever on this list, and we'll spend two full slides on it. And lever four, strategic weight: reference status, a public logo, a lighthouse migration story. Real currency, Oracle genuinely pays for it, but price it consciously and trade it explicitly. A logo given away as a courtesy is a discount you paid for and never received.
First check. Your OCI rep tells you thirty five percent is the maximum possible credit discount. The deal is two point four million a year for three years, so seven million total. The disciplined read: A, accept, reps know their own price list. B, that maximum is a rung, not a ceiling, a deal this size clears the rep's authority, so the ask goes to the deal desk in writing, timed to the quarter, with an alternative priced. C, walk away, anything under fifty percent is an insult. Or D, split the difference and propose forty two and a half. Pause here. Whose maximum is it?
The answer is B. Maximum possible, in a rep's mouth, almost always means maximum I can approve without asking anyone, and a seven million dollar relationship sits several rungs above that. So you run the move you learned from the advisor's clip in session two: the ask goes in writing, attached to the draft order, and if it's truly impossible, the deal desk can refuse it in writing, because impossible from a rep is an opinion and impossible from the desk is information. You time the escalation to the quarter, and, before any of it, you price the alternative, because that's the document the desk actually prices against. Now the wrong answers, quickly. A confuses the rep's authority with Oracle's flexibility, an expensive confusion at this deal size. C, walking on a fixed percentage, mistakes theater for benchmarks, the next slide gives you real ranges and fifty percent flat isn't how they work. And D, splitting the difference against yourself before Oracle has moved once, is negotiating your own position down for free. Never counter your own quote. Make the machine respond first.
Now the table you came for: what good actually looks like, by deal shape. OCI credits under half a million a year: weak outcomes sit between list and fifteen off, strong outcomes land twenty to thirty off with a ramp and carryover attached. Credits between one and five million a year: weak is twenty to thirty off on a flat commit, strong is thirty five to fifty off, ramped, with the discount tier priced at the full run rate, session three's refinement. Enterprise scale credits: weak is forty off with a naked renewal, strong is fifty plus with rate locks, carryover, and Support Rewards worked into the same arithmetic. SaaS, first purchase: weak is thirty to forty off with no protections, strong is fifty to sixty five off with a renewal cap and fixed expansion pricing. And SaaS renewals with leverage: weak is paying the uplift as quoted, strong is flat to modest uplift with the estate right sized and the cap extended another term. Two health warnings on this table. These are ranges, not promises, workload mix, region, and competitive tension all move them. And the pattern that never moves: in every row, the strong column is defined by protections attached to the rate, not by the headline percentage. A deep discount with a naked renewal is a weak outcome wearing makeup. Which is exactly what the next check tests.
Before the check, one more look inside the machine. Here's our advisor on what the deal desk actually is, and why understanding it changes how you ask.
Guest analyst Buyers imagine the deal desk as a wall. It is closer to a spreadsheet with a committee attached. When your ask arrives, someone models the deal: the margin, the competitive situation the rep reported, the quarter, and the account's history. Three things follow from that. First, the desk prices your alternatives, not your arguments. A paragraph explaining that money is tight does nothing to the model; a one page summary of the AWS quote for the same workload changes the competitive field in the spreadsheet, and the output moves. Second, the desk sees the whole account. If you are negotiating credits in one thread while your colleagues discuss a Fusion expansion in another, the desk knows, and they will happily give margin in your thread and take it back in the other. That is why I keep telling buyers: one negotiation, one date, one owner. And third, the desk has a quarter target like everyone else at Oracle. The identical model that says no in week three says yes in week thirteen, because an approved discount that closes now beats a protected margin that closes never. So make your ask desk shaped: written, specific, evidenced, and dated inside their closing window. You are not persuading a person. You are feeding a model the inputs that move it.
Feed the model, don't argue with the wall. Written, specific, evidenced, dated. And catch the second point, because it's the one buyers miss: the desk sees your whole account across every thread. If you don't consolidate your negotiations, Oracle consolidates them for you, on their terms. Session one's fragmentation failure, seen from the inside.
Check two, the table in action. Two Fusion offers on your desk. Offer A: sixty two percent off list, renewal at then current rates. Offer B: fifty five percent off, a four percent renewal cap, and expansion pricing fixed at the same net rate. Over six years, which wins? A, offer A, seven extra points is seven extra points. B, offer B, in almost every realistic scenario, because the cap and expansion pricing govern years four to six, where offer A is unpriced. C, they're equivalent, renewals always land near the original discount anyway. Or D, offer A, but only if you plan to leave at year three. Pause. Which years does each offer actually price?
The answer is B, and this is the most valuable arithmetic in the session, so let's actually run it. Offer A prices years one through three and says nothing about four through six, at the exact moment your switching costs peak and your leverage bottoms. Offer B prices all six years. Now apply any realistic repricing to A's naked renewal, and historically, unprotected SaaS renewals reprice hard, and A's seven point head start is gone before the middle of year four. Add an acquisition, and A's expansions land at list while B's land at the fixed net rate, and it's not even close. C is the myth this whole module was built to kill, so hear it plainly: absent protection, renewals reprice toward list, not toward your discount. Your original percentage is not a precedent, it's a memory. And D is at least internally consistent, but let's be honest about what it is: a plan to leave at year three is a negotiating posture, not an ERP strategy, and Oracle can smell the difference. The rule you take from this check: deals are judged across their whole life, and the strong outcome column is always, always the protected one.
Now the money beside the discount, three programs that change your effective price without touching the rate card. Program one, migration funding. For workloads Oracle wants, and they want most workloads that currently run on AWS, Oracle funds proofs of concept, migration services, partner work, sometimes substantial amounts. It's sized to the deal and granted to buyers who ask while the deal is still open. Ask. Program two, Support Rewards, stacked properly. Session one gave you the twenty five cents per consumed dollar. Here's the stacking insight: rewards accrue on top of your negotiated discount. A credit dollar at forty percent off that also earns twenty five cents against your support bill is a materially cheaper dollar than either number suggests alone. Model them together, always, and bring the combined number to the business case, because Oracle's own comparison won't. Program three, the marketplace route. Buying Oracle services through the AWS, Azure, or Google marketplace burns down your hyperscaler spend commitment, and that commitment has its own discount attached. Which produces the delightful arithmetic where the cheapest Oracle dollar is occasionally the one that also retires an AWS obligation. Module three does that math properly. One warning across all three programs: this is quarter end grease. It appears when a deal needs closing and evaporates the day after you sign. Sequence your asks so the program money is on the table while your signature still matters.
The calendar, the lever that costs nothing. The facts first: Oracle's fiscal year ends May thirty first. Quarters end in August, November, February, and May. Discount authority, deal desk flexibility, and program money all loosen as each close approaches, and most of all in the fourth quarter, March through May, when the year's number is made or missed. Now the buyer's counter, and I want the exact phrasing: be able to sign in their closing window, without needing to. Ready but willing to slip. Approvals done on your side, terms agreed, alternative still live, and no operational reason you must close. That posture is worth more points than any argument you will ever construct, because it lets their deadline do your negotiating. Third, the false deadline: expiring quotes, end of quarter pricing, sign by Friday. Pressure dressed as calendar. Session three's clip watched a Friday deadline die and the deal sign eleven days later on the buyer's four sentences. Prices that vanish on Friday reappear the following Friday. And fourth, start the clock early: a renewal engaged six to nine months out has quarters to play with, and can choose which Oracle close to land on. A renewal engaged three weeks out has no calendar at all. Your session two date discipline isn't just hygiene, it's pricing strategy. Fifth and last: one negotiation. The desk sees your whole account, the clip told you so. Consolidate credits, SaaS, funding, rewards, and any audit noise onto one date, and negotiate once, with the whole relationship's weight behind it.
Last check of module one. It's April. Your Fusion renewal is dated September thirtieth. Oracle offers an early renewal now, with an extra five percent off, if you sign by May thirty first. The disciplined response: A, sign, five percent free is five percent free. B, refuse on principle, early renewals are always traps. C, treat it as the opening of your renewal negotiation five months early, with Oracle under Q4 pressure: price the full ask, caps, right sizing, expansion terms, against their deadline, and sign early only if the whole package clears your benchmarks. Or D, counter by demanding ten percent with no other changes. Pause here. Who needs May thirty first more, you or them?
The answer is C, and notice what the offer itself just told you. Two facts arrived with it: Oracle wants this revenue inside their fiscal year, and your September date means you don't need to move at all. That combination, their urgency, your runway, is the best negotiating position this relationship ever hands you, and the question is only whether you spend it well. Answer A spends it terribly: five points for surrendering your calendar, with no cap, means you've repriced from a lower base and armed next year's uplift. B walks past genuine Q4 money out of superstition, early renewals aren't traps, unprotected ones are. D haggles the number while ignoring where the value lives, in terms. C does it right: the full ask from this session's playbook, caps, right sizing, expansion pricing, program money, priced calmly against their deadline while yours stays comfortable. If the package clears your benchmark table, sign in May and take their urgency as your discount. If it doesn't, September is still yours, and so is the November quarter end behind it. Their deadline, your agenda. That's the whole calendar lever in one sentence.
The module one money discipline, five lines, on the wall. One, anchor on net: every quote converts to a net unit rate before anyone in your organization reacts to it, because percentages are theater and rates meet benchmarks. Two, price the alternative first, before the ask, not after the counter, because the alternative is the input the deal desk's model actually responds to. Three, ask past the rep: real asks go to the deal desk in writing, and you let the desk refuse in writing if it will, because half the impossibles come back signed. Four, protect the years the quote ignores: caps, holds, expansion pricing. The deal's real life is longer than its first term, and the strong outcome column is always the protected one. And five, spend the calendar: consolidate to one date, engage early, and stand at their quarter end ready but not needing, so that May thirty first, for once, works for the buyer. That's module one complete: the master, the orders, the policies, and the money. You can read the whole stack and you know what to pay. Everything from here builds on it.
Session five, three sentences. One: cloud pricing is a public list and a private net, moved by four levers, a credible alternative above all, then volume and term, timing, and strategic weight, and the strongest lever costs nothing but preparation. Two: benchmarks beat feelings, know the realistic net range for your deal shape, judge every offer across its whole life, and take the protected fifty five over the naked sixty two every single time. Three: Oracle negotiates on a clock that ends May thirty first, so consolidate your asks, engage early, and be ready to sign at their deadline without needing to, because that posture outbids any argument. Next session opens module two and we go deep into OCI: the consumption models themselves, Pay As You Go versus Universal Credits versus the funded variants, OCPUs versus ECPUs and why the unit changed, and the anatomy of a real OCI bill, which services actually eat the money. The contract knowledge is banked. Now we learn the meter. See you there.
Homework, about an hour, and it turns today's table into your table. One, grade your net rates: take the rate you computed in session three and place each of your deals into today's benchmark table. Write down which column you're in. If it's the weak column, congratulations, you've just found next quarter's project. Two, map the fiscal calendar: Oracle's quarter ends and May thirty first go into the team calendar, next to your own renewal dates from session two. Look at where they collide, those collisions are your windows. Three, draft the alternative, one page: for your biggest Oracle cloud line, what's the credible alternative, roughly what would it cost, roughly what would the move take. Not a migration plan. A price. It's the single highest leverage document you can own. Four, list the program money: any migration funding, Support Rewards accrual, or marketplace commitments in play right now. If the list is empty and you're running OCI workloads, money is sitting on the table, and now you know its names. And five, write the one date: if you consolidated every Oracle thread, credits, SaaS, support, the works, onto a single negotiation date, what date would it be? Just write it down. Module six turns that date into a strategy, and you'll want to have been thinking about it.
Five reads before next session, all free on redress compliance dot com. First, Oracle cloud negotiations, the negotiation playbook that today's levers plug straight into. Second, the OCI licensing and cost guide, the rate card mechanics underneath every credit benchmark in today's table, and required background for next session's meter work. Third, the Support Rewards guide, the stacking arithmetic done properly, discount plus rewards as one number. Fourth, negotiating Oracle ERP cloud pricing, the SaaS side of the benchmark table from the buyer's chair. And fifth, the Oracle cloud ERP pricing guide, Fusion list price territory, the anchor your net rate gets measured against. That's session five, and that's module one, complete: you can read the entire Oracle cloud contract stack, and now you know what the numbers in it should be. Next session, module two, the meter itself. See you there.