This is Part IV of our six-part EOFY series on preparing for Oracle's fiscal year end — May 31.
In Part III we worked through how to define your organizational goals and avoid common contractual pitfalls. Part IV moves from preparation to execution — how to read the signals Oracle is sending, use a practical negotiation cheat sheet, and understand what a successful negotiation actually looks like from the inside.
This is where strategy becomes action.
---
Oracle Contract Red Flags
Before negotiating anything, you need to know what to watch for. The table below summarizes the most common red flags that appear in Oracle proposals — and what each one actually means for your position:
| If You See This | Know This |
|---|---|
| OCI credits tied to your discount | Oracle is prioritizing cloud revenue. Don't overcommit just to reduce on-prem costs. |
| "Free" OCI credits | May auto-renew into paid usage — check expiration dates and terms carefully. |
| Support pricing removed for retired products | Oracle may be steering you toward OCI replacements. |
| New: 20% Extended Support fee in Year 6 | This fee increased from 10% in 2025 — plan upgrades or negotiate alternatives now. |
| "Modernization" or cloud bundles | Often higher-cost replacements. Scrutinize before accepting. |
| Usage-based OCI pricing with no cap | Can lead to significant surprise costs — negotiate fixed or reserved pricing. |
| Cloud terms in on-prem contracts | Separate cloud and on-prem clauses to avoid future conflicts. |
| Quiet amendments to audit rights | Small changes can significantly expand Oracle's audit scope. Read every amendment carefully. |
| One-line pricing with no breakdown | Always request itemized SKUs and full cost transparency. |
The bundling issue deserves particular attention. Oracle periodically retires products and introduces successors — sometimes with one or two enhancements — at a meaningfully higher price point. The goal is to move you to a new price tier. Anyone who has navigated VMware under Broadcom's ownership has seen this at scale.
"The bundling, depending on your leverage when you're negotiating the deal — if you have leverage, you should try to prevent some of those downsides. You're buying a product. Ask for itemized SKUs." — Dr. Michael Corey, Co-Founder, LicenseFortress
On subscription and cloud conversions specifically: the offer may look compelling. If Oracle is offering pricing that seems too good to be true relative to your on-premises costs, it's worth understanding the timeline. At what point does Oracle recapture that revenue? With perpetual licenses, you can keep running your software — without support, if needed — while you evaluate alternatives. With subscriptions, you cannot.
---
The Negotiation Cheat Sheet
The following covers the most common situations that arise in Oracle negotiations and what to do in each one:
Vague pricing details. Request a full breakdown: list price, entitled price, and final offered price. If costs seem inflated, push for SKU-based, itemized pricing. You are buying discrete products — treat it like one.
"Your version is end of life." Confirm with your own technical team before accepting any urgency narrative. Then ask for upgrade clarity, negotiate extended support, or evaluate third-party support for your current version. Moving to Oracle 21c or above is a technical decision, not a sales one.
Support costs increased. Request a complete breakdown of support tiers and what you're actually receiving. Push for a reduction, negotiate a lower-tier plan, or seriously evaluate third-party support.
Uncapped renewal costs. Negotiate a price cap or multi-year pricing guarantee. Uncapped support renewals — particularly at the new 8% annual ceiling — can exceed list price within a few years.
Automatic contract extensions. Request opt-in renewals. Automatic renewal clauses remove your leverage at the moment you need it most.
8%+ price hike. Request documentation of historical price increases and Oracle's stated future plans. Push to keep increases in line with an Employment Cost Index (ECI) benchmark of 4.5% or less.
Products you didn't intend to buy. Oracle sales compensation structures sometimes incentivize attaching products to deals. Investigate whether the bundle benefits you or the sales rep. Negotiate discounts without the additional purchases.
Usage-based pricing. Always request detailed cost projections. Set hard spending limits. Negotiate a flat-rate or reserved pricing model wherever possible.
"Understand how that usage is calculated — spell out the formula. We've seen customers come back to us and say they get the renewal on their application only to learn they're using twenty times what Oracle estimated. Spell out how it's calculated so that everybody knows exactly what it means." — Dr. Michael Corey, Co-Founder, LicenseFortress
---
How to Read Oracle's Position
Oracle's negotiating posture is not static. Before entering any discussion, understand where Oracle stands:
- Have they made their last two quarterly numbers? If they've missed analyst expectations, revenue is critical to them — which means they're hungry for deals.
- What has Oracle publicly committed to? Cloud growth is their primary strategic narrative. If you are part of a cloud deal, it means more to Oracle's sales team than a straight on-prem renewal.
- What's Oracle's fiscal quarter? May is Oracle's Q4 — the highest-pressure period for their sales organization. That pressure creates room to negotiate that doesn't exist in August.
"Always know how the vendor's doing and what's important to them. What have they told the press they're doing? In Oracle's case, they're growing the cloud. If you are part of a cloud deal, that means more to the vendor. If you're just revenue and they missed the last two quarters, then revenue is super critical." — Dr. Michael Corey, Co-Founder, LicenseFortress
A multi-year support agreement is often a straightforward ask during EOFY. "We're going down this path — what's our support cost for the next five years?" is a reasonable question, and the answer locks in predictability that's worth real money over time.
---
Case Study: Expert Contract Negotiations Transform an Outdated Oracle Agreement
One of our client engagements illustrates how these principles work in practice.
Background: A Fortune 100 company had been an Oracle customer for over two decades. Their application suite was licensed under a revenue-based structure — a model that made sense when it was signed, but had created significant problems over years of acquisitions and divestitures. Revenue grew and contracted; the license fees didn't adjust downward. The company went back to Oracle repeatedly to fix the contract. Oracle's consistent response: pay the bill. Eight years passed.
The challenges:
- The revenue-based structure created financial strain and lacked flexibility for modern operations
- Oracle resisted renegotiations — the team was told repeatedly to "pay the bill"
- The contract's rigid structure prevented IT spending from aligning with a planned cloud migration
- Annual support fee increases of up to 8% were compounding the pressure year over year
How LicenseFortress approached it:
We reviewed the company's 20-year-old contract in detail to identify unfavorable terms and compliance risks. Then we mapped all past purchases against entitlements to establish what the company was actually entitled to use — separate from what Oracle claimed.
Critically, we didn't approach Oracle as a renewal conversation. We approached it as a multi-team alignment. Oracle is cloud-focused, so we had the client bring in their Oracle cloud team alongside their renewal team. The Java team had been applying separate pressure — we brought them into the room too. Then, with Beeman & Muchmore providing legal expertise, we applied coordinated pressure at the right level.
The client's position was clear: we want a multi-year deal, we are evaluating OCI as a strategic cloud platform, and certain things have to change — or we look elsewhere.
The results:
| Metric | Outcome |
|---|---|
| Total First-Year Savings | $2.5M |
| ROI | 6,150% |
| Project Cost | $40K |
| Fee Reduction | 71% |
Beyond the financial outcome, the negotiation reset the company's relationship with Oracle. The revenue-based licensing metric was realigned to actual usage. The Java pressure was resolved. A defined OCI migration path — with clear milestones — was established, giving Oracle a cloud win they could point to, and giving the client a structured on-ramp rather than an open-ended commitment.
"The partner that brought us in was really mad at us because we were pushing back on Oracle hard. We looked at them and said: we work for the customer. There's no conflict. If we don't put pressure on Oracle, why would they change a contract that's completely to their advantage?" — Dr. Michael Corey, Co-Founder, LicenseFortress
The outcome worked for everyone. But it required someone in the room whose job was to represent the customer's interests — not to protect the relationship with Oracle.
---
Where This Series Goes Next
Parts III and IV cover goals and strategy. The final installments — Part V and Part VI — will address timing and final execution: when to push, when to wait, and how to lock in your position after a deal closes.
Watch the Part III & IV webinar on Vimeo to see the full session, including live Q&A.
Schedule a consultation to work through your negotiation strategy with our team before May 31.
