Why do support terms matter at settlement?
Support terms matter at settlement because the recurring cost they create often outweighs the one time finding the settlement resolves, and a deal that fixes the finding while quietly adding new licenses at standard support has simply replaced a one off problem with a compounding one. Support runs at roughly 22 percent of the net license fee each year and escalates annually, so every new license added in a settlement carries a tail of recurring cost that grows for as long as you hold it. The headline of a settlement is the finding number, but the durable cost is in the support.
Buyers focused on beating down the finding sometimes accept the support terms as fixed, when they are as negotiable as anything else in the deal. The escalation, the support base on new licenses, and the way the new entitlement is grouped into support sets all shape the recurring cost, and all can be addressed in the settlement paper. Treating the support terms as part of the negotiation, rather than as policy handed down, is what separates a settlement that closes the issue from one that opens a new annual bill. This topic links up to the Oracle negotiation guide, and it sits beside splitting the finding from the deal.
What support terms can be negotiated at settlement?
The support terms that can be negotiated at settlement are the support base on any new licenses, a cap or freeze on the annual escalation, the way the new entitlement is grouped into support sets under the matching service levels rule, and any Support Rewards offset that reduces support through OCI consumption. Each one moves the recurring cost, and each is on the table at the moment a settlement is being papered, when Oracle wants the deal closed and the buyer holds genuine leverage.
The escalation is often the most valuable to address, because it compounds. A cap or a freeze on the annual increase changes the cost curve for the whole life of the entitlement, not just the first year. The support set structure matters because the matching service levels rule will govern any future attempt to terminate support on part of the entitlement, so how the new licenses are grouped now decides what flexibility you keep later. Support Rewards, which offsets support spend through OCI consumption, can be folded in where a cloud plan is genuine. The specifics are contract dependent and are written into the settlement paper rather than left to standard policy. For the standing recurring picture, read Support Rewards and the OCI offset.
| Term | Why it matters | Buyer aim |
|---|---|---|
| Support base on new licenses | Sets the recurring fee | Minimise the base that attracts support |
| Escalation cap or freeze | Compounds over the life | Cap or freeze the annual increase |
| Support set grouping | Governs future termination | Group to keep future flexibility |
| Support Rewards offset | Reduces support via OCI | Fold in where a cloud plan is real |
Why is the point of settlement the moment of leverage?
The point of settlement is the moment of leverage because Oracle wants the audit closed and the deal signed, and that desire is the buyer's strongest card for shaping the support terms before the entitlement is locked into standard policy. Once a settlement is signed without addressing the support terms, the recurring cost is set and the next opportunity to change it is a future renewal, where the leverage is weaker and the escalation has already compounded. The settlement is the rare moment when the finding, the new licenses, and the support terms are all on one table at once.
Using that moment well means bringing the recurring cost into the negotiation explicitly, with a model that shows the support tail of the whole deal across a realistic horizon. The finding number alone understates the cost; the model that adds the compounding support reveals it, and that revelation is itself leverage, because it reframes the deal from a one time number to a multi year commitment that deserves multi year terms. Where the settlement also releases historic exposure, the release language and the support terms are negotiated together, so the deal closes the past and sets fair terms for the future in one paper.
A settlement sets the finding once and the support cost for years. The point of settlement is when the support terms are most negotiable, so model the recurring cost and negotiate it then.
Our negotiation guide models the recurring support cost of a settlement, negotiates the escalation and the support set structure, and puts the agreed terms in the settlement paper. Fixed Fee or Gainshare, with no risk to you.
What is the buyer move on support terms?
The buyer move is to model the recurring support cost of the whole settlement across a realistic horizon, negotiate the escalation, the support base, and the support set structure at the point of settlement when leverage is highest, and put every agreed term in the settlement paper rather than relying on standard policy. Bring the support tail into the room as a number, not an afterthought. Cap or freeze the escalation where you can, because it compounds. Group new entitlement into support sets that preserve your future right to terminate. Fold in any Support Rewards offset where a cloud plan is genuine. Write it all down in the paper. To round out the settlement, work across to settlement paper release language that protects and up to the Oracle negotiation guide.
FAQ
Why negotiate support terms? Because new licenses at standard support add recurring cost at roughly 22 percent each year with escalation, often outweighing the one time finding.
What can be negotiated? The support base, an escalation cap or freeze, the support set grouping under matching service levels, and any Support Rewards offset.
What is the buyer move? Model the recurring cost, negotiate the terms at settlement when leverage is highest, and write them into the settlement paper.