A Canadian SaaS provider saved three million dollars on the Oracle licensing through Oracle licensing assessment, Oracle Database licensing optimization, and the Oracle support optimization.
How to Negotiate Your Oracle SaaS Renewal: The Five Moves at the Table
Scope before price: strip the 18 to 32 percent of inactive bundle modules first. Kill the escalator with a 0 to 3 percent cap that survives the term, trade term for protections, refuse the easiest-path module bundling, and close on Oracle's May 31 clock.
A Canadian SaaS provider with roughly three thousand employees runs its platform on Oracle Database Enterprise Edition, with Real Application Clusters underneath the high availability tier and the Diagnostics Pack in use across the estate.
That last item is where the money was. Options are licensed on the same processor count as the database itself, and the Diagnostics Pack is reachable from tooling database administrators use as a matter of routine.
The assessment took three million dollars out of the position across a three year term.
Around three thousand employees across North America, operating a software platform that its own customers depend on. Oracle sits underneath the product, not beside it.
That distinction changes the licensing question. For most companies Oracle supports the business. For a SaaS provider it is part of what the business sells, so the licence position scales with customer growth rather than with headcount.
It also means capacity is provisioned for peak customer demand rather than for internal use, and peak provisioning is what gets licensed.
Oracle's opening renewal position priced the estate at its provisioned capacity, with options carried across the full processor count and support renewed on everything.
None of that is unreasonable as an opening. It is simply the maximum defensible reading of an estate nobody had measured recently, and it was accepted as the starting point because there was no alternative number.
We rebuilt the position from three angles, and each one moved it.
Processor counting first. The correct basis is physical cores multiplied by the core factor for the processor family, and estates that grew organically frequently have this wrong in ways that compound across a cluster.
Options second. Which of Real Application Clusters, the Diagnostics Pack and anything else were genuinely in use, on which instances, against what was licensed. This is where most of the three million came from.
Support third. Maintenance renewed across the whole estate, including capacity that had been decommissioned but never taken off the support line.
These are the moves that produced the saving.
The transferable point for any SaaS provider on Oracle is that your licence position scales with your customers, so it needs measuring on the same cadence as your capacity planning rather than at renewal.
The eleven moves, processor counting on the correct core basis, auditing enabled options, support alignment, and the buyer side position at every step of an Oracle renewal.
Used across more than five hundred enterprise clients. Independent. Buyer side. Built for CIOs running the next Oracle Database renewal cycle.
Oracle framed the Oracle Database as the immediate Oracle uplift at the renewal cycle. Redress reframed the approach around the customer's actual Oracle Database utilization. Three million dollars saved against the publisher's opening Oracle Database renewal quote.
Confidential consultation. No follow up sales call unless you ask for one.
Oracle Database licensing signals, Oracle support signals, Oracle ULA signals, and the broader Oracle licensing leverage signals across the practice.