SaaS, OCI, and multicloud: where the money flows now, and why the renewal replaced the audit. 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 in. This is Oracle Cloud Management, session one of thirty. If you took our Oracle Licensing Mastery course, think of this as the sequel, same buyer's side of the table, different battlefield. That course taught you to count processors and defend audits. This one is about what happens when the meter replaces the license, when Oracle stops selling you software and starts selling you subscriptions, credits, and consumption. And here's the thing I want you to hold from the first minute: the cloud didn't make Oracle simpler. It moved the complexity. It moved it out of the datacenter and into the contract, out of the audit and into the renewal. Thirty sessions, thirty minutes each, three knowledge checks per session, homework you can actually use. Let's draw the map.
Five things you'll walk away with today. One, the map itself: Oracle runs three distinct cloud businesses, and you need to know which one you're standing in at any moment, because the rules change at the border. Two, the contract stack: there's a master agreement called the CSA, and orders, service descriptions, and policies hanging off it, and when they disagree, there's a precedence order that decides who wins. Three, the money: subscriptions, Universal Credits, Support Rewards, the actual plumbing that moves dollars from your budget to Redwood Shores. Four, the shift: why the renewal date quietly replaced the audit letter as the moment of maximum danger, and maximum opportunity. And five, the burns: the five places I watch enterprises lose real money in these deals, so that when one of them starts happening to you, you recognize it early enough to stop it.
Four numbers to frame the whole course. Twenty five cents. That's what one dollar of OCI consumption earns you against your on premises support bill under Oracle Support Rewards, thirty three cents if you hold a ULA. Sit with that: the support annuity, the thing that never went down, is now a lever Oracle itself handed you. One hundred percent. That's how much of an unconsumed Universal Credits commitment you forfeit at period end. The commit is a prepayment with an expiry date, not a wallet. Three. That's how many rival hyperscalers now run Oracle Database as a native first party service, AWS, Azure, and Google Cloud, and you can pay for it through their commitments. Real competition exists for the first time in this relationship. And year three. That's when a SaaS deal is actually decided, because that's when the renewal reprices everything you signed in the honeymoon, unless you bought protection when Oracle still wanted your signature. Every one of these numbers gets its own session later, with a negotiation attached.
Now the map. One vendor, three cloud businesses, three rulebooks. Business one, SaaS: Fusion ERP, EPM, supply chain, HCM, the CX applications, and NetSuite. Applications by subscription, priced per user or per employee per month, against documents called service descriptions that define exactly who counts. The fight there is definitions at signing and pricing protection at renewal. Business two, OCI, Oracle Cloud Infrastructure: compute, storage, database, and AI services, metered by the hour. You either pay as you go at list, or you commit to Universal Credits for a discount. The fight there is commitment sizing, ramp, and rate. Business three, and this one's new: multicloud. Oracle Database running natively inside AWS, Azure, and Google Cloud, plus bring your own license onto their compute. The fight there is whose paper governs and whose commitment your spend burns. Three businesses, but, and this matters, one master agreement over all of it: the Cloud Services Agreement. Session two takes that document apart clause by clause.
Here's the translation table between the world you may know and the world we're entering. What you own: on premises you bought perpetual licenses, an asset that survived the relationship. In cloud you hold a subscription right that evaporates the day you stop paying. The master contract: the OMA governed licenses; the Cloud Services Agreement governs services, and it comes with orders, service descriptions, and policies stacked on top. How they check you: on premises, Oracle needed an audit clause and scripts to find out what you deployed. In cloud, they don't need to ask. They meter you. Your usage arrives at the renewal table before you do. Where the leverage lives: on premises it was audit defense and the next big purchase. In cloud it's the renewal date, the size of your commitment, and whether you have a credible alternative priced. And the compounding cost: on premises it was twenty two percent support uplifted forever. In cloud it's renewal repricing, overage rates, and forfeited credits. Nothing got simpler. The exposure moved from what you deployed to what you signed.
First knowledge check. Your company runs Fusion ERP, an OCI Universal Credits commitment, and Oracle Database at Azure. Which master agreement governs the Fusion subscription? A, the Oracle Master Agreement, because Fusion replaced E-Business Suite which sat under it. B, the Cloud Services Agreement, with the Fusion ordering document and its service descriptions on top. C, Microsoft's Azure terms, because part of the estate runs at Azure. Or D, no master at all, each cloud order stands alone. Pause here. Think about which piece of paper you actually signed for each of the three.
The answer is B, the Cloud Services Agreement. Every Oracle cloud service hangs off the CSA: the SaaS subscription, the OCI credits, and Oracle's side of the multicloud services, all of it. The OMA still exists in your world, but it governs your remaining on premises licenses, and it does not follow a product into the cloud. Fusion replacing E-Business Suite doesn't drag the old master along, and that distinction matters, because the protections you negotiated into your OMA over the years, they don't apply to your subscriptions unless you negotiate them again. The Azure answer is half clever: yes, Database at Azure involves Microsoft paper for the Azure side, but the Oracle service itself runs on Oracle terms. And orders are never standalone. They inherit the master and override it only where a special term explicitly says so, which is precisely why special terms are where negotiation value lives. Session two builds on exactly this.
Now follow the money, because there are really only four pipes. Pipe one, SaaS subscriptions: per user or per employee per month, billed annually in advance, with minimum quantities baked into the order and an uplift proposal arriving at every renewal like clockwork. Pipe two, Universal Credits: you prepay an annual commitment, you draw it down by consuming services at your discounted rates, and here's the sting, whatever you don't consume by period end is gone, while whatever you consume beyond the commit bills as overage. Pipe three, the hyperscaler channels: Database at AWS, at Azure, at Google, and marketplace private offers, which is Oracle revenue that can simultaneously burn down your AWS or Azure or Google spend commitment. Genuinely useful, genuinely confusing, module three's whole topic. And pipe four, the loop that connects old money to new: Support Rewards. Your OCI consumption earns credits against your on premises support bill. Twenty five cents per dollar, thirty three for ULA customers, all the way to zero if you consume enough. Four pipes. Every Oracle cloud negotiation you'll ever run is about the pressure in one of them.
Before the next check, I want you to hear from someone who sits across from Oracle for a living. We'll do this through the course: short clips from a senior advisor who negotiates these deals for buyers. Here he is on the three ways he watches Oracle cloud deals go wrong.
Guest analyst In the deals I review, the same three failures keep coming back. The first is the commit sized to a slide. The migration plan says sixty percent of workloads by year two, so someone signs a credit commitment sized to sixty percent. The migration lands at thirty, and every unconsumed dollar is forfeited, year after year. Size the commit to what you measure, never to what you hope. The second is the renewal nobody owned. The first SaaS term gets a beautiful discount, everyone celebrates, and no one negotiates a renewal cap, because year three feels far away. Year three arrives, the system is embedded in the business, and the uplift lands against a customer who cannot credibly leave. That protection was available for the asking on signing day, and only on signing day. And the third is fragmentation. The support renewal sits in procurement, the OCI evaluation in infrastructure, the Fusion expansion with the CIO's office. Oracle runs those three conversations as one account plan with one revenue target. When the buyer runs them separately, every thread pays retail. Run them as one negotiation, on one calendar, with one owner.
Three failures: the commit sized to ambition, the naked renewal, and the fragmented negotiation. Write those down, because the entire course is, in a sense, the antidote to each. Modules two and five give you the first two in depth, and the capstone in session thirty is literally a masterclass in running the threads as one.
Knowledge check two, and it's the one that stings. You commit to one point two million dollars a year of Universal Credits. Twelve months later, you've consumed seven hundred thousand. What happens to the remaining five hundred thousand? A, it rolls into next year's pool automatically. B, Oracle refunds the difference at year end. C, it's forfeited, use it or lose it, unless you negotiated carryover into the order. Or D, it converts into Support Rewards credits. Pause. Remember what the commitment actually bought you: a discount, not a wallet.
The answer is C, forfeited. The standard Universal Credits terms carry no rollover and no refund: the commitment is a prepayment with an expiry date. Carryover, ramp schedules that start small and grow with the actual migration, true up mechanics, those exist only when they were written into the order before signature, which is why session seven is entirely about commitment structure. And notice the trap in answer D: Support Rewards accrues from what you consume, never from what you forfeit. So under consumption loses twice, once as the forfeited dollars themselves, and again as the support bill reduction those dollars would have earned if they'd been consumed. When we size commits in module two, the rule is measured consumption plus a margin you can defend, and not one dollar more.
Now the good news, and it's real: the cloud handed you leverage the on premises world never did. Instrument one, the calendar. Every subscription and every commitment has a date, and dates are power if you respect them. A renewal engaged six to nine months out, with alternatives priced and a walk away position, is a negotiation. A renewal engaged three weeks out is data entry. Instrument two, competition. For the first time in the history of this vendor relationship, Oracle's crown jewel runs natively inside three rival clouds, and credible substitutes exist at almost every layer. You don't have to want the alternative. You have to cost it, because a costed alternative moves every Oracle number even when you never take it. Instrument three, the Support Rewards loop: if you carry a support bill, OCI consumption pays it down, and that arithmetic belongs in every business case and every renewal conversation, worked deliberately, not discovered after signing. And instrument four, data. Oracle sees your consumption, but so can you, and your own utilization analysis is the standing counter to every expansion pitch and every uplift. Four instruments. The estates that use them pay a fraction of the estates that don't.
And now the other side of the ledger: the five burns, the places I actually watch money leave enterprises in these deals. Burn one, the forfeit, you just did the math on it. Burn two, the naked renewal, the guest clip's second failure: no cap, no hold, repricing at then current rates exactly when your switching costs peak. Burn three, the metric definition. Hosted employee, hosted named user, records, transactions: the service description defines who counts, and I've seen the definition move a bill by more than the discount did. If you remember one sentence from module four later, it'll be: read the service description before the price. Burn four, the quiet auto renewal: orders that renew themselves unless written notice lands inside a window that nobody put in a calendar. The notice window is a contract term; treat it like one. And burn five, the seam. Workloads that cross between worlds, BYOL moving onto a hyperscaler, a ULA certifying while cloud deployments are running, support dropped in anticipation of a migration that slips a year. Every seam has a rule, and audits and renewals both love seams. We'll walk each one in its session.
Last check of the day, and it's the arithmetic I most want you to carry out of session one. Your Oracle support bill is two million dollars a year. The business case for moving six million dollars of annual workload spend to OCI is on your desk. Under standard Support Rewards, what belongs in that business case? A, nothing, Support Rewards only applies to SaaS. B, about one and a half million a year of accrued rewards, cutting the support bill to roughly five hundred thousand. C, a twenty five percent discount on the OCI rate card. Or D, two million in rewards, the bill zeros out regardless of consumption level. Pause here. Twenty five cents per consumed dollar, applied against tech support.
The answer is B. Six million of consumption, times twenty five cents per dollar, is one and a half million of rewards, applied against the two million support bill, leaving roughly five hundred thousand. That's not a discount on cloud, answer C has it backwards, it's a reduction of the old bill funded by the new spend, and it's precisely why Oracle built the program: it makes OCI look cheaper than any rate card comparison suggests, using money you were going to pay anyway. It doesn't apply to SaaS, and it doesn't zero anything by magic, the bill only hits zero when consumption times the rate covers it, two point six six million consumed in this example if you hold a ULA at thirty three cents. Here's the discipline: if your company pays Oracle support and someone is writing a cloud business case that doesn't mention Support Rewards, that case is wrong, in your favor or against you, and you should be the person in the room who knows it. Session nine works this arithmetic into an actual renewal negotiation.
So here's where we go from here. Module one, the rest of it, sessions two through five: the contract stack. The CSA clause by clause, cloud ordering documents and how to read one like an analyst, the policy layer Oracle can change without asking you, and cloud pricing mechanics with real discount benchmarks. Module two, sessions six through ten, OCI commercials: consumption models, sizing and negotiating the commitment, BYOL, the full Support Rewards playbook, and cost governance so the meter doesn't surprise you. Module three, eleven through fifteen: Oracle on the other clouds, including JD Edwards on AWS and the Database at services, ending in a worked TCO comparison across all four platforms. Modules four and five, sixteen through twenty five: the SaaS estate, ERP and HCM deals, and the full subscription lifecycle from first signature to exit rights. And module six, twenty six through thirty: governance, corporate events, the Oracle relationship run deliberately, and a capstone where we take a company with an expiring ULA, a growing OCI bill, a Fusion renewal, and an audit letter, and sequence all of it into one negotiation. Modules one and two are the prerequisites. After that, take what your estate needs first.
Session one, three sentences. One: Oracle runs three cloud businesses, SaaS, OCI, and multicloud, under one master, the Cloud Services Agreement, and each is metered and negotiated differently, so always know which one you're standing in. Two: the commercial machinery is subscriptions, Universal Credits, and Support Rewards, and every piece of it rewards preparation and punishes optimism, forfeit by forfeit, uplift by uplift. Three: the renewal is the new audit, the leverage lives in your calendar, your consumption data, and a costed alternative, and all three of those are things you control, starting this week. Next session, we open the Cloud Services Agreement itself, the master every Oracle cloud dollar flows through, and go clause by clause: what it says, what it deliberately doesn't say, and the short list of things in it that are genuinely negotiable. Bring your own CSA if you can get it; it's more interesting when it's your name on it.
Homework, about an hour, and it builds the foundation for everything after. One, inventory the orders: every Oracle cloud order currently in force, SaaS subscriptions, Universal Credits, marketplace purchases. Procurement has them, or the Oracle console does. Two, stamp the dates: for each order, the term end, the renewal notice window, and whether it auto renews, into the team calendar, today, because burn four only happens to people without calendars. Three, pull the consumption: for any credit commitment, committed versus consumed by month for the trailing year. The gap is your forfeit exposure, and you want to know it before Oracle's rep does. Four, find the support bill, the actual annual number, you'll put it next to the Support Rewards arithmetic in module two. And five, write down the metrics: for each SaaS service, the metric it bills on, from the service description itself, not from anyone's memory. An hour of homework, and you'll already know your estate better than most of the people who signed for it.
Five reads before next session, all free on redress compliance dot com. First, the OCI licensing and cost guide, the full commercial model behind module two. Second, the Oracle Support Rewards guide, today's twenty five cent arithmetic with the eligibility rules and the renewal tactics. Third, Oracle cloud contracts and credits for CIOs, the contract stack we dismantle next session, seen from the executive seat. Fourth, Multicloud Universal Credits, the newest construct, one credit pool spendable across OCI and the Database at services, and you want to know it exists before module three. And fifth, Oracle database licensing in cloud environments, the counting rules for Oracle software on other people's clouds. That's session one. You have the map, you have the four pipes, and you have homework that makes next session personal. Session two, the Cloud Services Agreement, clause by clause. See you there.