Contents
Key takeawaysWhy programs missThe seven cost optionsWhy savings do not addDecisions you cannot undoThe last safe dateThe four wavesWorkstreams to keep apartCloud commitmentsWhat Oracle will sayContract terms to ask forWhat we have seenWhat to do nextFAQOracle cost programs miss their target on timing far more often than on choice. Rank savings by the date each option expires, model them in sequence because they do not add, and treat support notice dates as the real deadlines.
- Sequence by expiry. Rank savings by the date the option disappears, then by yield per week of effort, and treat size as the third criterion.
- Savings do not add. On a $10 million support line, retiring 10 percent shelfware and then moving half the rest at half the fee saves 32.5 percent, where the naive sum promised 35.
- The decision is due early. Count notice, legal review and internal approval back from the anniversary and the real decision date lands about four months before it.
- Three decisions are permanent. Support termination, a metric change written into an amendment and a ULA certification cannot be cheaply undone, and a product split reprices what stays with Oracle.
- Keep compliance and cuts apart. Fix compliance gaps first and wait at least a quarter before reducing support, then wait again before asking Oracle for commercial relief.
- Cloud savings pay at the boundary. Under a fixed Universal Credits commitment, unused credits are forfeited, so efficiency work turns into cash only when the commitment is resized or where you already run over it.
Why do Oracle cost programs miss their savings target?
Most Oracle cost programs that miss their number chose sensible savings and then ran them in the wrong month. The typical failure is a support termination notice date that passes while the business case is still being socialized.
The program is governed by dates you do not control: support anniversaries, notice periods written into ordering documents, cloud commitment end dates and ULA expiry. Each saving also behaves differently on three counts: what it returns against its own line, how long the cash takes to arrive, and whether you can undo it.
How should you rank the savings options?
Rank them by the date the option disappears, then by yield per week of effort, and only then by size.
- Expiry first. A support reduction whose notice date is close outranks a larger saving with no deadline, because a missed notice cannot be recovered until the next anniversary.
- Yield per week of effort second. A cloud cleanup your team can finish in a fortnight beats a metric renegotiation that needs six months of Oracle meetings, if both are worth similar amounts.
- Size last. Use it to break ties between options with similar dates and similar effort. Why we rank it last is set out in the section on what we have seen.
Getting the order wrong costs far more in one direction than the other. A missed notice date converts a decision you have already made into another 12 months of fees, because you have bought another full annual term. A metric change that starts a quarter late loses a quarter.
How to Negotiate an Oracle ULA: No Price List, Just Your Business Case
What does each Oracle cost option return, and how fast?
The fastest cash sits in the cloud line and the largest cash sits in support and licensing. The table sets out the seven options we work with, the yield against the line each one touches, when the saving reaches an invoice, and whether it can be reversed.
| Option | Yield against its line | Time to cash | Reversible? | Main risk |
|---|---|---|---|---|
| Cloud waste removal | Low to moderate on the cloud line | Next monthly invoice | Yes | Saves nothing under a fixed commitment |
| Escalator cap on support | Compounding, small in year one | Next anniversary, then every year | Not needed | Traded for a commitment you did not need |
| Shelfware retirement | Moderate on net license and support | Next support anniversary | No, or only at a high price | Retiring software that is still in use somewhere |
| Product split to third party support | Around half the fee on the products that go | The day after the current term ends | Rarely, and never cheaply | Patch access, and repricing of what stays with Oracle |
| Java migration off Oracle JDK | Large where the Java population is large | Next subscription renewal | Technically yes, commercially no | Runtime validation and unmanaged installs |
| Cloud commitment resizing | Moderate to large where the commitment is oversized | Only at the commitment boundary | Once per term | Undersizing, then overage at order rates |
| Metric or definition change | Can be the largest of all | On amendment | No | Accepting a metric that reprices you later |
Timing explains why a program that reports only total savings looks as though it is failing for its first two quarters. Cloud right sizing shows up in next month's invoice. A shelfware retirement lands at the next support anniversary, which may be eleven months away, so report run rate at a date instead of a headline percentage.
What can you do on the 22 percent support line?
Premier Support runs at 22 percent of net license fees a year, with an annual uplift on top. Five options sit on that line, and they are not equally recoverable.
- Escalator cap. The cheapest and most durable option. Ask for it early and have it written as a contract term that outlasts this renewal. The usual risk is being asked to buy a commitment you did not need in exchange.
- Coterming. Aligning support identifiers on one anniversary simplifies administration but removes optionality. Do it only where you would never change one line without the other.
- Challenging matching service levels. Oracle's support policy requires every license in a license set to sit at the same support level. When the account team cites it, test the claim against the policy that was in force on your original ordering date.
- Product split. Moving some product families to third party support saves around half the fee on what goes, and it reprices what stays.
- Full termination. The one way door, covered below.
Which layer of the stack to attack first is argued in our total cost optimization guide, and the clause by clause review sits in the support renewal checklist. Provider options and costs are covered on our third party support page.
Where do Oracle SaaS subscriptions fit?
Fusion Cloud Applications and other Oracle SaaS subscriptions follow the same timing logic on a shorter clock. In the SaaS renewals we see, the renewal proposal arrives about 90 days before the term ends and carries a 9 to 12 percent uplift. Buyers who wait for that proposal before looking at usage end up negotiating on Oracle's timetable.
A usage review run before the proposal arrives commonly finds 30 to 50 percent shelfware across subscribed users and modules in our work. The finding only turns into money if it reaches the negotiation before the renewal date, so start the review two quarters out. Our guide to identifying and reclaiming shelfware covers the method.
The Oracle CIO guide to controlling spend
The operating model, the ranked savings options and the five year schedule, worked end to end.
Get the white paper →Why do Oracle savings percentages not add up?
Each saving shrinks the base the next one applies to, so published yields cannot be summed. Business cases that add them together promise a number the program cannot deliver, and in our programs that gap surfaced around month 9.
A worked example on a $10 million support line
Take a $10 million annual support line. You plan to retire shelfware worth 10 percent of it, then move half of what remains to third party support at half the fee. Added naively, that is 10 percent plus 25 percent, or 35 percent.
| Step | Base the step applies to | Saving | Annual spend after the step |
|---|---|---|---|
| 1. Retire shelfware worth 10 percent | $10 million | $1 million | $9 million with Oracle |
| 2. Move half the remainder to third party support at half the fee | $4.5 million transferred | $2.25 million | $4.5 million with Oracle, $2.25 million with the provider |
| Sequenced total | $3.25 million, or 32.5 percent | $6.75 million | |
| Naive sum of published yields | $3.5 million, or 35 percent | $6.5 million (not achievable) |
The gap widens with every option you add. Say you then apply a hypothetical 20 percent metric saving to the $4.5 million still with Oracle. That returns $900,000 and takes the total to $4.15 million, or 41.5 percent, against a naive 55 percent.
What happens to the Oracle line after a product split?
It can be repriced upward. Under Oracle's technical support policies, when you terminate or reduce support on part of a license order, support for the remaining licenses is priced at the list price in effect at that time minus the applicable standard discount.
The policy caps that figure at the support fees you paid before for the whole order, plus any country annual adjustments. In the worst case the remaining products cost close to what the full order did. Model the whole remaining line after the split, and read the repricing language in your ordering document before you scope anything.
Which Oracle cost decisions cannot be reversed?
Three decisions are one way doors: support termination on a support identifier, a metric or definition change written into an amendment, and a ULA certification. Model the reversal cost of each before you serve any notice.
- Support termination. Reinstating terminated support is priced at current terms and is usually worse than never having left. Oracle's policy sets the reinstatement fee at 150 percent of the last annual support fee, prorated back to the date support lapsed.
- Metric or definition change. Once written into an amendment, a new metric reprices you permanently. It can deliver the largest saving of any option, and it can also cost the most later if the definition grows with your business.
- ULA certification. Certification fixes the license count from its date. Any growth beyond the certified quantities after that needs new licenses.
A product split to third party support is also effectively irreversible, for the repricing reasons above. Keep at least one product family you could still move later, so that option is not fully spent.
Say you pay $400,000 a year in support on one product, terminate it, and need it back 12 months later for an upgrade. The reinstatement fee, prorated over the lapsed year, comes to $600,000. That is $200,000 more than the year of support you saved, and the fee for the new support period is billed on top of it.
How far before a support anniversary is the decision really due?
Roughly four months. A last safe date is the final day on which you can still change a renewal without buying another full year, and every support option has one. It sits earlier than most teams assume, because your own approval time has to fit inside it.
Work backward from the anniversary. Subtract the contractual notice period, commonly 30 days but confirmed per support identifier, because it lives in the ordering document rather than a general policy. Then subtract two weeks of legal review for a termination notice, and four to six weeks of internal approval, longer if a board threshold is crossed.
| Step | Time allowed | Latest start |
|---|---|---|
| Support anniversary | 30 June | |
| Termination notice served | 30 days, confirmed in the ordering document | 31 May |
| Legal review of the notice | Two weeks | 17 May |
| Internal approval | Six weeks, at the upper end of the usual range | 5 April |
| Board paper, if a spending threshold applies | Your board cycle | The last board meeting before 5 April |
The bare arithmetic lands in early April, about 12 weeks out. We plan on four months because the steps rarely run back to back: the repricing figure from Oracle, third party quotes and the board calendar all need slack before approval can start.
A program that reaches the anniversary with the decision unmade has not delayed the saving by a month. It has delayed it by a year.
What should be done at each point before the anniversary?
- 12 months out. The date map is complete for this anniversary. If a ULA expires inside the window, the certify or renew comparison is already modeled.
- 6 months out. Deployment is reconciled against entitlement for the products in scope. If a split is on the table, third party quotes are requested and Oracle is asked in writing how the remaining line will be priced.
- 4 months out. The decision is made and the approval paper is submitted.
- 2 months out. Approval is signed and legal is reviewing the draft notice against the notice clause in the ordering document.
- 1 month out. Notice is served exactly as the ordering document requires, and proof of delivery is filed.
How should an Oracle cost program be sequenced?
Run it in four waves. Each wave has an entry condition that must be met before it starts, and each is tied to a date from your contracts. The entry conditions are what separate a program that delivers from one that generates a compliance claim in year two.
- Wave 1, map (months 0 to 3). Build the spend baseline, the entitlement and deployment picture, and a list of every renewal and notice date. Pull three years of invoices and separate net license, support, cloud and Java. The date map is the artifact most programs skip, and everything after it depends on it.
- Wave 2, internal fixes (months 2 to 6). Compliance remediation, cloud waste and cleanup of database options and packs in use. It cannot start until the deployment picture is reconciled and has an owner. Close any over deployment here, before any commercial step is visible to Oracle.
- Wave 3, structural (months 5 to 10). Shelfware retirement, product split, the Java migration and metric work. It waits until compliance is clean and at least one quarter has passed. Retiring shelfware before you know what is deployed removes licenses you are actually using.
- Wave 4, commercial (months 9 to 12). Renewal negotiation, the escalator cap and cloud commitment resizing. It starts only once the footprint you are negotiating over has already shrunk.
Reducing support revenue before compliance is clean invites a review into an environment that is not ready for one. Tie each entry on the date map to the contract terms explained in our Oracle licensing guide.
How do you check your own position before Wave 2?
Use Oracle's records and your own data, and reconcile the two before anyone from Oracle asks for them.
- Ordering documents and support renewal quotes. Each support identifier (CSI) has its own anniversary, notice terms and product list. The renewal quote shows the uplift Oracle has applied.
- My Oracle Support. Shows the support identifiers your organization holds and the products under each one.
- DBA_FEATURE_USAGE_STATISTICS. The database view that records which options and management packs have been used. Oracle's license auditors read the same view.
- OCI Cost Analysis, usage statements and the Subscriptions page. Together they show consumption against your commitment and the rate card you are billed on.
- Java inventory. Oracle's Java Management Service or your endpoint management tooling finds Oracle JDK installs before you size a per employee Java subscription or plan a migration.
Which cost workstreams should never run in the same quarter?
Two pairs must be kept apart. Where a compliance gap was remediated in the same window as a support reduction, the customer drew Oracle attention within the following year far more often than where the two were separated.
- Compliance remediation and support reduction. Running both together points a review at an environment that has just changed. Close the gap first, let at least one quarter pass, then reduce.
- Support reduction and a request for commercial relief. You would be asking the person whose forecast you just cut to give you something. Separate them by at least one quarter, and preferably by a renewal.
What changes if Oracle opens an audit mid program?
Three workstreams stop and two continue.
- Stop: any termination notice not yet served.
- Stop: any deployment change that alters the picture under examination.
- Stop: any commercial request that depends on the same account team.
- Continue: the baseline and date map work, which is now worth more than before.
- Continue: cloud efficiency work, which touches nothing under review.
How to handle the audit itself is covered in our audit negotiation guide.
Why does a ULA expiry override the program calendar?
Certification is irreversible and dated, so a ULA expiry takes priority over every other date in the plan. Model the certify or renew comparison at least twelve months before the window. The detail is in the ULA negotiation guide and our page on ULA certification.
When does cutting Oracle cloud consumption lower the bill?
Only at the commitment boundary, or immediately where you already consume above your commitment. Universal Credits are prepaid and drawn down as you consume, and any left unused at the end of the term are forfeited, so consumption cut below a fixed commitment saves $0.
At the boundary, a lower run rate is the evidence for a smaller next commitment. Oracle bills usage beyond the purchased credits at your contracted rates, and larger commitments earn larger volume discounts, so the sizing decision cuts both ways.
When should cloud efficiency work be scheduled?
Time it to the commitment date. Start right sizing, shutting idle instances and cleaning up storage two to three months before the commitment ends, so the lower run rate shows in the usage data you bring to the resizing discussion.
Check the commitment position before you fund any efficiency project. The mechanics are in our guides to OCI cost optimization and Universal Credits commitments.
What will Oracle's account team say, and how should you answer?
Once support revenue is at risk, expect a familiar set of responses. Each one has a factual answer you can prepare in advance.
| What the account team says | What to say back |
|---|---|
| "If you drop support on those products, the rest of the order gets repriced." | "Please send the calculation under the support policy: list price less our standard discount, capped at what we paid before. We have modeled it already." |
| "Matching service levels means you drop the whole license set or nothing." | "Confirm in writing which licenses form the license set, and which version of the policy applied on our original ordering date." |
| "We can hold your uplift if you commit to additional cloud spend." | "We want the cap as a standalone contract term. Any cloud commitment will be sized against our usage data at the commitment date." |
| "If you ever need support back, reinstatement will cost far more than you save." | "We have modeled the reinstatement fee for these products and the business has signed off on it." |
| "We should cover the renewal and the license review in one conversation." | "We keep those separate. Send the review scope in writing and the renewal stays on its own timetable." |
What contract terms should you ask Oracle for?
Ask for terms that keep protecting the savings after this renewal, because a one year discount is usually gone by the next one.
- Escalator cap across renewals. A stated maximum annual uplift on support for named support identifiers over several years. It works in your favor every year it runs.
- Repricing statement before partial termination. Written confirmation of what the remaining support line will cost if you terminate specific products, obtained before you serve notice.
- Notice terms per support identifier. The notice period and the address for notices, stated in the ordering document or confirmed by Oracle in writing.
- Fixed definitions in any metric amendment. The exact definition of the new metric, what counts toward it and how growth is measured. A loose definition reprices you later.
- Resizing rights on Universal Credits. The right to reset the commitment at renewal based on actual consumption, with overage pricing stated.
- ULA certification mechanics. What counts as a certified deployment, the reporting format and the deadline, agreed before the term starts.
What have we seen in Oracle cost programs in 2024 and 2025?
Across roughly 60 to 80 Oracle cost programs that Fredrik Filipsson and the Redress team ran between 2024 and 2025, the programs that missed their number rarely picked the wrong savings. They ran them in the wrong month.
- The most common single loss. A support termination notice date that passed while the business case was still circulating.
- Month 9. Where business cases that added yields together met reality, because each saving had already shrunk the base of the next.
Why we do not start with the biggest saving
The usual advice is to start with the biggest saving, on the reasonable theory that the biggest number deserves the most attention. We disagree.
The largest option, usually a metric change or a platform migration, has a long lead time and no deadline, so it can safely start in month three. The small option with a notice date 40 days away cannot wait at all. Put every dated option on the plan first, then start the large structural work alongside it.
How we run an Oracle cost program
We run it as a dated plan with a named internal owner for each saving, rather than as a workshop series. The date map is built in the first three weeks. Wave 1 is fixed price and short, and if the baseline shows nothing to recover, we say so and stop.
We do not run savings you cannot staff. Reporting is run rate at a date, and we ask clients to promise the CFO three things.
- The exit run rate you expect 12 months out.
- The in year cash for this fiscal year.
- The two savings that would change both figures if they slip.
That framing survives contact with reality, and a single headline percentage does not. A slipped headline figure costs the program its credibility just when it needs the hard decisions. The Java detail sits in the Java audit guide, and the operating model that keeps the work alive between renewals is in the Oracle CIO playbook.
How does the program change with the size of your Oracle spend?
A company with one or two support identifiers and a small OCI footprint can often compress the four waves into two: mapping and fixes in the first half year, structural and commercial work at the anniversary. The date map may fit on half a page.
A large customer with dozens of support identifiers, several anniversaries, a ULA and a Universal Credits commitment has the opposite problem. Some option is always close to its last safe date, so the program needs a standing owner and a monthly review of the date map.
What to do next
- Build the date map before the business case. Put every anniversary, notice date and commitment end date on one page, tied to the specific ordering documents.
- Mark the last safe date for each support option. Count notice, legal review and internal approval back from each anniversary, and put the result in the program plan as a hard deadline.
- Reconcile deployment against entitlement. Close any gap in Wave 2, before anything is visible to Oracle, and leave at least one quarter before any support reduction.
- Model the overlap. Sequence the savings in the model exactly as you intend to run them, and give finance the sequenced figure.
- Get the repricing figure in writing. Before scoping any product split, ask Oracle what the remaining support line will cost.
- Check the cloud commitment position before funding efficiency work. Book the commitment negotiation for Wave 4, against a footprint that has already been reduced.
- Bring in help where the calendar is tight. Our Oracle practice builds the date map and runs the plan with you.
Frequently asked questions
In what order should Oracle cost savings be run?
By the date each option expires, then by yield per week of effort, and only then by size. A notice date that passes cannot be recovered until the next anniversary, while a metric change or platform migration loses little by starting a quarter later. Schedule the dated options first and let the large ones run in parallel.
Why do Oracle savings percentages never add up?
Because each saving is calculated on a base that an earlier saving has already reduced. Retiring shelfware first leaves a smaller line for a later third party support split to work on, so the combined result is always below the sum of the published yields. Build the model step by step in the order you will execute, and report that figure to finance.
How early do you need to decide on an Oracle support renewal?
About four months, once the notice period, legal review and internal approval are counted back from the anniversary. Put that date in the program plan as a deadline and have the approval paper drafted before it arrives. If your organization needs board sign off above a spending threshold, move the date earlier to fit the board calendar.
Which Oracle cost decisions cannot be reversed?
Support termination, a metric or definition change written into an amendment, and a ULA certification. A product split to third party support behaves the same way in practice. Before any of them, write down what reversal would cost, get that approved alongside the saving, and keep one product family in reserve so a later option remains open.
Does cutting Oracle cloud consumption reduce the bill?
Not while you sit below a fixed Universal Credits commitment, because prepaid credits left at term end are forfeited either way. Efficiency work in the middle of a term is still worth doing: the lower run rate becomes the usage evidence you bring to sizing the next commitment, which is where the cash appears.
Can compliance remediation and support reduction run in the same quarter?
They should not. Close the compliance gap first, wait at least one quarter, then reduce support. Keep a dated record of the remediation and the deployment evidence behind it, so that if Oracle opens a review after the support reduction, you can show the gap was closed before the commercial change.
How much does Oracle charge to reinstate lapsed support?
Oracle's technical support policies set the reinstatement fee at 150 percent of the last annual support fee for the program, prorated from the date support lapsed to the date it is ordered again. Support for the new period is charged on top, which is why termination should be planned as permanent.