What is inside the playbook?
Inside is the full buyer side sequence for settling an Oracle audit on your terms, written for the CIO, the IT asset manager and the general counsel who receive the finding together. It opens with the mechanics of the inflated preliminary number, walks through the line by line review that strips out overcounted cores, accidental options and cluster wide virtualization claims, and ends with the negotiation moves that convert a defended position into a signed settlement.
- Why the preliminary finding arrives inflated at list price, and how to read it as an opening position
- The line by line review method that typically cuts a claim 60 to 80 percent
- How findings feed ULA renewals, OCI commitments and Java subscriptions, and how to keep those off the table
- A settlement checklist and a negotiation worksheet you can use on a live finding
- How to write future audit protection into the settlement so the same exposure does not return
Treat the first number as the start of a negotiation, not the end of one. Around 20 to 30 percent of Oracle's on premises license revenue is estimated to come from audits, so the inflated finding is a commercial instrument, and it is meant to be negotiated.
For the standing position behind the settlement, read the Oracle Negotiation Guide, and for the database mechanics that underpin most findings, the Oracle Database Licensing Guide. When the number is large or the deadline is close, an independent buyer side review takes you the rest of the way.