Practice viii · ULA
Oracle ULA Negotiation
Independent buyer side advisory across the full Unlimited Licence Agreement lifecycle, from pre ULA modelling to exit certification.
Independent buyer side advisory across the full Unlimited Licence Agreement lifecycle, from pre ULA modelling to exit certification.
Oracle ULA negotiation runs across a lifecycle, the entry business case, mid term management, and the certification that ends it. A ULA pays only when deployment growth outruns the fee, and the certification only protects you if the count is documented and defensible. A buyer side advisor models the case and certifies the exit without dispute.
An Unlimited Licence Agreement gives unlimited deployment of named Oracle products for a fixed term, usually three years, for a single up front fee. It is sold as simplicity and budget certainty, and it can be exactly that. But a ULA only pays when deployment of the covered products grows faster than the fee implies. Bought against a flat estate, it is a premium paid for flexibility that never gets used.
The products inside the ULA matter as much as the price. Oracle scopes the agreement to a defined product list, and anything outside it remains separately licensable and fully auditable during the term. A ULA that covers the database but not the options driving the real exposure leaves the customer paying for unlimited use of the cheap part while the expensive part stays on the meter.
Certification is where the value is realised or lost. At the end of the term the customer declares the quantity of each product deployed, and that declared number becomes a perpetual entitlement. Under declare and you strand licences you paid for. Over declare without evidence and Oracle challenges it. The declaration has to be built on documented, defensible deployment data assembled across every entity and environment, and that work takes months, not weeks.
We manage the full lifecycle. We model whether a ULA pays before it is signed, scope the product list to the real growth, manage deployment through the term to maximise the certified position, and prepare a certification that Oracle accepts without dispute. We have certified thousands of processors across multi entity estates with zero challenges, because the evidence was built to withstand the review.
A model of whether an unlimited agreement pays against forecast deployment, and which products belong inside the scope.
Definition of the covered product list so the agreement captures the products driving real growth, not just the cheap base.
Management of deployment through the term to maximise the position that can be certified at the end.
Assembly of documented, defensible deployment evidence across every entity and environment ahead of the declaration.
A decision framework on whether to certify and exit, renew, or restructure as a PULA, with the economics modelled.
Renewal, audit cure, and product addition terms written into the agreement to protect the next conversation.
We frame the ULA conversation on your terms, fix the scope of products under discussion, and lock the timeline so the negotiation runs to your calendar rather than Oracle's quarter end.
An independent model of forecast deployment against the proposed fee, with the product list tested for whether the agreement actually pays across the term.
The product list, fee, and certification terms argued line by line. We know from hundreds of buyer side engagements which positions Oracle treats as fixed and which are negotiable.
Through the term we manage deployment to maximise the certified position, then prepare a certification built to withstand Oracle's review without dispute.
ULA engagements span a lifecycle, so the structure follows the stage. A pre ULA business case or an exit certification fits a fixed fee. Full lifecycle management across a multi year term suits a retainer. Where the work centres on maximising a certification value, a gain share arrangement aligns the fee with the entitlement secured.
The right structure depends on the engagement. Read our engagement model overview to see when a fixed fee, a retainer, or a gain share arrangement fits, then request a consultation to scope your estate.
An Unlimited Licence Agreement grants unlimited deployment of a defined list of Oracle products for a fixed term, usually three years, in exchange for a single up front fee. At the end of the term the customer certifies the quantity deployed, which becomes a perpetual entitlement.
No. A ULA pays only when deployment of the covered products grows faster than the fee implies. Against a flat estate it is a premium paid for flexibility that is never used. The business case has to be modelled against realistic forecast growth before signing.
Certification is the declaration at the end of the term of how many units of each covered product are deployed. That number becomes a perpetual entitlement. It must be built on documented, defensible deployment data, because under declaring strands licences and over declaring without evidence invites challenge.
The list should capture the products driving real exposure and growth, not just the inexpensive base. A ULA that covers the database but excludes the options generating the cost leaves the expensive part on the meter and fully auditable during the term.
Products inside the ULA are not metered during the term, but anything outside the product list remains separately licensable and auditable. The certification at the end is itself a measurement event, so audit discipline applies throughout the lifecycle.
A Perpetual Unlimited Licence Agreement removes the fixed term, granting unlimited deployment of the named products indefinitely. It suits organisations with sustained high growth, but it ends the leverage a certification provides, so the decision to restructure into a PULA needs the economics modelled carefully.
At least twelve months before the term ends. Assembling defensible deployment evidence across every entity and environment takes months, and starting late forces a rushed declaration that either strands entitlement or fails to withstand Oracle's review.
The product most often placed inside a ULA, where the option scope decides whether it pays.
View the practice →Because the certification is a measurement event and products outside the ULA remain auditable.
View the practice →When a ULA and an OCI commitment are negotiated together as a single position.
View the practice →A buyer side model of whether the agreement pays, and a certification built to withstand review, is the difference between a ULA that banks value and one that strands it.