Oracle costs most where nobody owns it
The companies that hold their Oracle number flat are not better negotiators than the ones that do not. They have an operating model, and it runs whether or not a renewal is in front of them: one named owner, one calendar counted back from 31 May, five artifacts with expiry dates, and a monthly one page position that already exists when the letter arrives. The fix is structural, and it costs almost nothing.
Prepared by Redress Compliance · August 9, 2026 · Oracle advisory. Based on 30 to 40 Oracle estate reviews run with CIO and CFO teams 2024 to 2025.
Executive summary
Oracle's commercial model is built to find the gap between your functions, and an unowned account is all gap. Oracle sells as separate product lines, database, applications, middleware, Java and cloud, and negotiates them as one account sharing one support stream, one account team and one quota.
Five separate conversations give Oracle five chances to win and you five chances to lose. The fix is one named owner senior enough to say no, with a budget line, control of the calendar, and sight of every Oracle line in the ledger.
Where one person owned the relationship end to end, renewals opened on the buyer's calendar; where ownership split between procurement and infrastructure, they opened on Oracle's.
The most valuable artifact is the concession log, not the entitlement baseline.
Oracle account teams turn over roughly every 18 to 24 months, and the licensing specialist behind them changes at least as often, so institutional memory in the relationship is asymmetric and can be asymmetric in your favor.
Keep one file of every concession Oracle granted, dated, with the person, what you gave for it and the paper it landed in: price holds and escalator caps with the clause reference, definitional concessions that are almost never carried forward voluntarily.
And refusals whose reason a later product change can turn into an opening.
A concession you cannot cite is one you will pay for twice.
Nobody below the named owner confirms a deployment number in writing.
One helpful email from a database administrator has priced more audit claims than any measurement script: an engineer replies to a direct question about deployment, with no context and no review, and that email is now the baseline.
Almost every estate we reviewed had handed Oracle information it was under no obligation to give, usually through an architecture workshop or a support service request, and nobody had a rule against it.
The two decision rights that do more work than the whole org chart are that no deployment number goes to Oracle in writing below the owner, and no consumption commitment is signed without the consumption model attached to the paper.
Count the renewal backward from 31 May, never forward, because the binding constraint is your own approval chain.
Oracle's fiscal year ends 31 May and quarters close at the end of August, November, February and May, so a buyer who opens 60 days out is negotiating from Oracle's number with no time to build their own.
The rhythm is baseline at 270 to 180 days, strategy at 180 to 120, internal approval finished at 120 to 60, and price only in the final 60.
Approval running out of time is the most common reason a prepared buyer still signs a worse deal in the last week of May, so delegated authority, the legal position on the clauses you will not concede, and an executable alternative all have to be finished before the quarter you intend to sign in.
Who owns Oracle, and the decision rights that matter
| Decision | Decides | Failure mode when ownership drifts |
|---|---|---|
| Cluster, virtualization or DR design change | Head of infrastructure, with the Oracle owner consulted | The license count multiplies before anyone sees a bill |
| Any written statement of deployment to Oracle | The Oracle owner only, legal consulted | An engineer's email becomes the audit baseline |
| Accepting a change of licensing metric | CIO, with CFO and legal consulted | The counting basis changes and nobody prices the change |
| Signing a cloud consumption commitment | CIO and CFO jointly | The commitment is sized to Oracle's forecast, not yours |
| Terminating support on any support identifier | The Oracle owner, application owners and legal consulted | The remaining estate reprices and the saving disappears |
| Accepting an Oracle hosted health check workshop | The Oracle owner, security consulted | You fund Oracle's discovery using your own engineers |
Procurement is essential and is the wrong single owner. Oracle's commercial arguments are technical arguments: what a cluster is, what a processor is, what counts as installed and running.
A procurement lead who cannot challenge those definitions is negotiating a number they have no way to verify, so pair procurement with somebody who can read the deployment. The pairing is the control; the reporting line is a detail.
And decide the escalation response before it happens, because when a negotiation stalls Oracle escalates outward to the CFO or the chief executive: agree a single internal point of contact in writing, brief the CFO before the escalation rather than after, and give each executive two lines.
We have a process and a named owner, please work with them.
The Oracle year, counted backward from the fiscal close
- Q1, closes 31 August: refresh the entitlement baseline and the deployment ledger. The cheapest quarter in which to ask for non price terms.
- Q2, closes 30 November: open any renewal landing within nine months, and test alternatives while nobody is under pressure.
- Q3, closes 28 February: finish internal approval and legal review for anything you intend to sign in Q4.
- Q4, closes 31 May: sign, or walk. The strongest quarter for price and the weakest for careful drafting, which is exactly why the drafting has to be done already.
- The renewal ladder: baseline at 270 to 180 days out with entitlement, deployment and three years of invoices reconciled into one number; strategy at 180 to 120; internal approval finished at 120 to 60; price and terms only in the final 60, with nothing left to discover. Oracle's own quarter dates restate every June in its results announcement.
The Oracle CIO complete playbook
The five year plan to control Oracle spend, the operating model, the artifacts, and the negotiation calendar worked end to end.
Get the white paper →The five standing artifacts, and the freshness rule
Five artifacts have to exist before Oracle calls, each with a named owner and an expiry date, and the rule matters more than the document: an entitlement baseline that is fourteen months old is not a baseline, it is a memory.
The entitlement baseline sits with the software asset management lead and refreshes quarterly, preventing the inability to state your own position when a review opens.
The deployment ledger sits with infrastructure and refreshes on every architecture change, so a cluster decision surfaces at design rather than at audit. The contract and clause register sits with legal and refreshes on every signature.
The concession log sits with the Oracle owner and refreshes after every interaction. And the one page Oracle position sits with the owner and refreshes monthly, so there is something to hand the CFO when Oracle escalates.
Set a maximum age and treat a breach as an incident: our working rule is that the entitlement baseline and the deployment ledger must be reproducible within five working days at any point in the year, which is roughly the interval between a review letter landing and the first call where you either sound prepared or you do not.
The document that changes an Oracle outcome is rarely the negotiation deck. It is the one page position that already existed when the letter arrived.
Each artifact anchors to the same contractual spine, the ordering documents and master agreement terms, and where the artifacts disagree with the paper, the paper wins.
The domain method for each decision lives elsewhere: price and leverage in the pricing benchmarks playbook and the cost benchmarks, ULA strategy in the Fortune 500 certification, cloud in OCI cost optimization, engineered systems in the Exadata strategy.
And the whole cost stack in the cost reduction program.
- Percentile standing for your exact deal size and industry, from real closed transactions
- Scenario simulation before the call: test alternative terms and see the financial impact of each
- A negotiation playbook, talking points, and a two page executive brief on day one
What the board sees, and how the function is measured
Boards want three moments a year, not an Oracle briefing: the total Oracle envelope, contracted escalator and three year projection at budget setting; the decision, the alternative and the cost of declining before any commitment above the delegated threshold.
And same day notice with a realistic settled range on any audit or license review notification.
One thing should never appear: an unmitigated audit exposure figure with no settled range beside it, because board packs circulate and a large gross number becomes the anchor for everyone who reads it, including your own CFO.
The same applies to a vendor proposal with no counter model, and to any commitment described as unavoidable, because if it truly were you would not be presenting it.
Measure the function, not the spend, because spend moves for reasons that have nothing to do with how well you are run, acquisitions, growth, a single large project, while the operating metrics move only when the discipline moves.
Five metrics go on one page monthly to the same audience: renewals opened at 270 days or more, target above 80 percent and below half means the calendar belongs to Oracle; age of the entitlement baseline, target under 90 days and beyond 180 you cannot answer a review letter credibly.
Contracts carrying an uncapped support escalator, target zero because each compounds quietly for the life of the agreement; architecture changes that passed a licensing checkpoint, target 100 percent for anything touching clustering, virtualization, live migration or disaster recovery.
And days from an Oracle letter to a stated internal position, target five working days measured from the date on the letter.
The point is not the numbers. It is that somebody has to produce them, which is precisely what keeps the artifacts current.
What we saw across Oracle operating model reviews, 2024 to 2025
Across the 30 to 40 Oracle estate reviews Fredrik Filipsson ran with CIO and CFO teams in 2024 and 2025, the gap between the best and the worst outcomes was almost never negotiating skill. It was whether four things existed before Oracle called, and the common advice gets this exactly backward.
The common advice is to stand up an Oracle governance program: a steering committee, a charter, a workstream plan and a program manager. We disagree, because programs end and Oracle does not:
Estates that could reproduce a current entitlement baseline within five working days of being asked. That interval, not the compliance position, sets the tone of an audit response.
Estates that had handed Oracle information they were under no obligation to give, usually through an architecture workshop or a support service request, with no rule against it.
The program approach fails because it concentrates effort where the attention already is, the renewal in front of you, and leaves nothing running during the twenty months when nothing appears to be happening, which are exactly the months when the position is built or lost.
Every enterprise we have seen hold a durable Oracle position had something smaller and duller instead: one named owner, five documents with expiry dates, and a monthly page somebody is obliged to write. The companies that hold their Oracle number flat are not better negotiators.
They were better organized eleven months before anybody made them an offer.
The starting moves cost nothing: name the owner in writing this week, write the single point of contact rule, date stamp the five artifacts and treat anything over 180 days old as a finding.
Reconstruct the concession log from the last three years of ordering documents before the people who negotiated them leave, and add a licensing checkpoint to architecture change approval, one question, not a veto.
Method sits in the Oracle practice.
Your first five moves
- Name the owner this week, in writing, circulated to everyone who has ever emailed an Oracle representative: one person, senior enough to refuse a meeting, with a budget line and a route to the CFO.
- Write the single point of contact rule: nobody below the owner confirms deployment, headcount or roadmap to Oracle in writing, because the helpful email is where audit claims are priced.
- Date stamp the five artifacts and treat anything over 180 days old as a finding, not a document: baseline, deployment ledger, clause register, concession log, one page position.
- Start the concession log from memory, reconstructing the last three years from the ordering documents before the people who negotiated them leave.
- Put every renewal date on one calendar with the last termination date beside each and Oracle's quarters overlaid, then add a licensing checkpoint to architecture approval. The Oracle practice runs the cadence with you.
Frequently asked questions
Who should own the Oracle relationship inside a company?
One named person, senior enough to say no, with a budget line and a standing route to the CFO, not a committee, not a shared responsibility, and not procurement acting alone.
The title matters far less than the three things attached to it: authority to refuse a meeting and decide who talks to Oracle, control of the calendar so a renewal opens on your date, and sight of every Oracle line, support, cloud, licenses and services, in one number refreshed quarterly.
When does Oracle's fiscal year end and why does it matter?
Oracle's fiscal year ends 31 May, with quarters closing at the end of August, November, February and May. It matters because timing is the most underused lever a buyer holds, it costs nothing and concedes nothing, and the binding constraint is almost never Oracle, it is your own approval chain.
If your internal approval takes six weeks, the paper has to be finished in mid March, not started in May, or the deadline belongs to Oracle.
Why should procurement not own the Oracle relationship alone?
Because Oracle's commercial arguments are technical arguments, what a cluster is, what a processor is, what counts as installed and running, and a procurement lead who cannot challenge those definitions is negotiating a number they have no way to verify.
Procurement is essential, but pair it with somebody who can read the deployment. The pairing is the control; the reporting line is a detail.
What is the concession log and why is it the most valuable artifact?
It is one file recording every concession Oracle granted, dated, with the person, what you gave for it, and the paper it landed in: price holds and escalator caps with clause references, definitional concessions, and refusals with their reasons.
It is the most valuable artifact because Oracle account teams turn over every 18 to 24 months while your file outlives theirs, so institutional memory becomes asymmetric in your favor, and a concession you cannot cite is one you will pay for twice.
How far ahead should an Oracle renewal be opened?
Count backward from the fiscal year end, never forward. Baseline at 270 to 180 days out, strategy at 180 to 120, internal approval finished at 120 to 60, and price and terms only in the final 60 days.
A buyer who opens 60 days out is negotiating from Oracle's number because there is no longer time to build their own, and approval running out of time is the most common reason a prepared buyer still signs a worse deal in the last week of May.
Should we run an Oracle governance program to control cost?
No. Programs end and Oracle does not. A steering committee, charter and workstream plan concentrate effort on the renewal in front of you and leave nothing running during the twenty months when the position is actually built or lost.
Every enterprise we have seen hold a durable Oracle position had something smaller and duller instead: one named owner, five documents with expiry dates, and a monthly one page position somebody is obliged to write.
