Oracle comes calling

Roger: A mid sized company with eight thousand employees was paying thirty three thousand dollars a year for Java. Under the new per employee model, the same Java costs them over half a million. Same software. Same servers. Seventeen times the bill.

Bill: And the letter that starts that conversation is not an invoice. It is a friendly note asking about your Java usage.

Bella: Today, the vendor with the most refined audit machine in enterprise software. Oracle. This is Off List. Read the paper before you sign it.

Bella: Welcome back to Off List. Bella here, with Roger, Bill, and Laura. Today's vendor needs no introduction and gets one anyway: Oracle. No vendor in enterprise software runs a more disciplined commercial machine, and I say that with genuine professional respect, because understanding the machine is the whole defense. We are covering four things: the Java licensing change that is producing the biggest surprise bills in the industry, the audit playbook and its timing, the ULA, the all you can eat agreement, and when to certify out of one, and the cloud and support levers that connect everything. Bill, you have run Oracle estates for decades. Frame the vendor honestly.

Bill: Honestly: Oracle is not tricky, Oracle is consistent. That is what people misunderstand. The playbook has been stable for twenty years, it is documented, it is predictable, and it works anyway, because it exploits things that are true about buyers, not things that are hidden about Oracle. They know your deployment better than you do, they time pressure to your renewal, and they sell relief from problems their own licensing created. If you know your estate and your dates, Oracle is one of the most manageable vendors there is. If you do not, they will manage you.

Laura: The consistency is real. Every Oracle story on today's show follows the same arc: a metric changes or a letter arrives, the exposure is bigger than you thought, and the resolution on offer happens to be the product they wanted to sell you anyway. Once you see the arc, you cannot unsee it, and you stop taking any single step of it personally.

Bella: Start with Java, because this is the one producing the phone calls that begin with, is this real. Roger, the mechanics.

Roger: The mechanics, and the date that matters is January twenty twenty three, when Oracle changed how Java is sold. Before that, you licensed Java the traditional way, by processor or by named user, and you paid for what ran Java. The new model, the employee universal subscription, prices Java per employee. And the definition of employee is the whole story: every full time employee, every part timer, every temporary worker, and, read this part twice, the employees of your agents, contractors, outsourcers, and consultants who support your internal operations. Not Java users. Everyone. If one application server in the basement runs commercial Java, the metric is your entire workforce plus your contractors.

Bella: And the rates.

Roger: List runs from fifteen dollars per employee per month for organizations under a thousand employees, sliding down through volume bands to five twenty five at the very largest counts. Which sounds almost reasonable until you do the arithmetic on the metric change. The example that has become the industry's reference case: a company with eight thousand employees, previously paying around thirty three thousand a year under processor licensing, now facing roughly five hundred seventy six thousand a year under the employee model. Seventeen times the cost, same deployment. Across the market, the increases for large organizations are commonly running four hundred to eight hundred percent.

Bill: And this is why the audit letters surged, because the metric change converted every company with any commercial Java anywhere into a potential seventeen x upsell. The friendly note asking about your Java usage is not curiosity. It is the first step of a well built funnel, and the funnel ends at an employee count negotiation.

Bella: So what does the defense look like? Laura, practically.

Laura: Three layers, in order of value. Layer one, and it is the one nobody wants to hear: get off commercial Java where you can. OpenJDK and the other open distributions are free, they are compatible for a huge share of workloads, and every workload you migrate shrinks the exposure to zero for that workload. The Java conversation is one of the few in this industry where the walkaway is genuinely technical and genuinely available, and companies that ran the migration have simply exited the problem. Layer two, if you need commercial Java somewhere, contain it: inventory exactly where, isolate it, and license the containment story, because the negotiation over what counts is winnable when your inventory is airtight. Layer three, if you are stuck licensing the employee metric, negotiate the rate, because the list bands are an opening position. The benchmarks on negotiated deals for mid sized organizations, the one to ten thousand employee range, land meaningfully under list, in the nine and a half to thirteen dollar range against the fifteen dollar list. And negotiate the employee definition itself, especially the contractor language, because that definition is where the count doubles.

Roger: The single most expensive sentence in a Java negotiation is, we probably have it running somewhere. Walk in with the inventory or do not walk in.

Bella: The audit. Bill, you called it the most refined machine in the industry. Take it apart.

Bill: The machine has stages, and knowing which stage you are in is half the defense. Stage one is the soft touch, an email from someone with a title like license management services or a partner acting for them, asking to discuss your deployment, offering a friendly review. It is worded as a service. It is discovery. Stage two, if the soft touch finds something or you ignore it, is the formal review, contractual audit rights invoked, scripts to run, data to produce. And stage three is the settlement conversation, where the exposure number appears, usually large, usually negotiable, and the resolution offered is never just a check. It is a purchase. Cloud credits, a ULA, a subscription conversion. The audit is the top of a sales funnel, and the exposure is the price anchor for the products at the bottom.

Roger: And the timing is the tell we keep repeating on this show, because it is the same across vendors and Oracle perfected it: the audit interest arrives somewhere around nine months to a year before a major renewal or a support decision. That is not coincidence, it is coordination. The exposure conversation is meant to be running in parallel with your renewal, so the settlement and the renewal merge into one negotiation where they hold the leverage on both sides of the table.

Bella: Defense.

Bill: Same religion as always, with Oracle specific verses. Keep your own count, continuously, not when the letter arrives. Deployment records, entitlement records, reconciled quarterly, so their number is never the only number in the room. Route every audit contact through one owner immediately, no well meaning engineer answering scripts and questions informally, because informal answers become findings. Check what the contract actually obligates, formal audit clauses have notice periods and scope limits, and the soft review is usually voluntary, which means the timing and the terms of your cooperation are negotiable. And never, ever settle inside their deadline pressure. The exposure number at first presentation and the number that settles are routinely far apart, and the gap is a function of your calm, your count, and your calendar.

Laura: The one sentence version for anyone who gets the letter this quarter: it is a negotiation that has chosen to look like a legal event, and the moment you respond to it as a negotiation, with an owner, a count, and a clock of your own, it becomes one.

Bella: The ULA. The unlimited license agreement, Oracle's famous all you can eat deal. Roger, explain the instrument and the decision at the end of it, because the decision is where the money is.

Roger: The instrument: you pay a fixed fee for a term, usually three years, and during the term you deploy specific Oracle products without counting. Unlimited, for the listed products, for the term. And at the end, the fork. You either certify, count everything you deployed, declare it, and that count converts into a perpetual license pool you own from then on, no further license fee. Or you renew, another term, another fee, and the counting question is deferred again. Oracle's economics obviously prefer the renewal, forever, and the whole end of term experience is engineered toward it.

Bella: When is each answer right?

Roger: Certify when your growth has flattened. That is the clean rule. If you deployed aggressively during the term and the estate has plateaued, certification locks the whole plateau in as perpetual licenses, you stop paying the recurring ULA fee, and you regain freedom, third party support, cloud choices, everything opens up. Renew only if you genuinely project major deployment growth in the products covered, and even then, price the renewal against what certification plus incremental licenses would cost, because the renewal is rarely the cheaper path once growth slows.

Bill: And the trap at the fork is time. The standard end of term experience compresses the decision into about ninety days, and inside ninety days you cannot run a proper certification count, you cannot pull deployment evidence across a big estate, and you cannot test your alternatives. That compression is the sales strategy. So the preparation window is twelve to eighteen months before expiry, not ninety days. Deployment evidence collected from day one of the term, as routine hygiene. Major rollouts timed to land before the certification window, because everything deployed before you certify is in the pool, and everything after is a new negotiation. A company that arrives at the fork with eighteen months of evidence and a finished count has all the leverage. A company that arrives with ninety days has a renewal.

Laura: Deploy like you will certify, from day one, even if you end up renewing. The evidence costs almost nothing to collect in real time and almost everything to reconstruct at the deadline.

Bella: Last mechanism, and it connects everything: support, and the cloud. Bill.

Bill: Support is the quiet engine of the whole Oracle relationship. You pay annual support on your licenses, it is a substantial percentage of the license value, and it rises. The current pattern is support costs climbing around eight percent year on year, and that escalation has become Oracle's favorite renewal pressure, because the pitch for a new ULA or a cloud deal now leads with, we can cap your support increase if you do this deal. The relief from their own escalation is the product.

Roger: And here is the thing the market has learned, and it is the single most useful sentence in this segment: the support cap is negotiable on its own. The zero percent support cap that gets dangled as a reason to sign a ULA can be negotiated directly, as its own concession, without buying licenses you do not need. It is harder, it takes leverage and timing, but it is a known, achievable outcome. So when the cap appears as the sweetener on a bigger deal, price the cap alone first. If the only way they will cap your support is inside a purchase, now you know exactly what the purchase is really costing you.

Bella: And the cloud credits.

Roger: Same shape. Oracle wants OCI commitments, their cloud, and cloud credits get folded into ULAs and settlements and renewals as sweeteners. The pattern in real deals: credits bundled inside a bigger agreement routinely go unused, the same stranded pool problem we found in the SAP platform credits, and a commitment made to dress up a settlement is consumption you have to invent later. If OCI genuinely fits your workloads, negotiate an open, standalone commitment sized to a real forecast, it will be cheaper and cleaner than credits stapled to a license deal. If it does not fit, do not let credits into the agreement at all, because every credit is a future obligation wearing a gift bow.

Laura: The through line of this whole episode: every Oracle product conversation is really a portfolio conversation, support, licenses, cloud, audit exposure, all connected, and they negotiate it as one portfolio. The buyer who negotiates each piece separately, on Oracle's schedule, loses each piece separately. The buyer who connects them, on their own schedule, is playing the same game Oracle is, and that is the only fair fight available.

Bella: Round to close. One sentence. The single most valuable Oracle move. Roger.

Roger: Inventory your Java, today, before the friendly letter arrives, because the walkaway to open distributions is real, and the most expensive sentence in the building is, we probably have it running somewhere.

Bill: Collect ULA deployment evidence from day one and arrive at the fork with eighteen months of preparation, because a company with ninety days does not make a decision, it signs a renewal.

Laura: Route every audit contact through one owner and keep your own count, because their number should never be the only number in the room.

Bella: And mine. Price the support cap alone before you price the deal it is sweetening, because relief from their own escalation is the oldest product Oracle sells. Next week, Broadcom and VMware, what happens when the acquirer rewrites every contract at once, and what it teaches about the next acquisition. This is Off List. Read the paper before you sign it.