Certify or renew is a cost decision, not a fear decision. Model the five year total cost of each path against your real deployment and your true growth forecast. In most estates that are stable or shrinking, certification keeps more value, because support stays flat and the certified count becomes free perpetual entitlement.
Every Oracle Unlimited License Agreement ends with the same question. As the term closes, the customer either certifies the quantities deployed during the agreement into a perpetual entitlement, or renews the ULA for another term at a new fee. The decision is worth millions in most enterprises, it usually has to be signed by a C level executive, and it is frequently made on instinct or on the strength of a single renewal quote. This paper replaces the instinct with a model.
We are an independent advisory. We are not a reseller, we hold no Oracle quota, and we sit on the buyer side of the table. What follows is the framework we run with clients, written so that an IT asset manager, a procurement lead, or a general counsel can build the same comparison and defend it to a board.
Why this is a cost decision and not a fear decision
Renewal is often sold on anxiety. The concern that a certified count will be challenged, that support will be repriced, that an audit will follow, or that future growth will leave the business short of licenses, all push organisations toward renewing when the numbers do not support it. Each of these fears has a factual answer, and once the answers are on the table the decision becomes arithmetic.
The model has two outputs. The first is the five year total cost of certifying now and running on perpetual entitlements plus support. The second is the five year total cost of renewing for another term and certifying later. The gap between them, adjusted for the value of any new deployment each path allows, is the decision. Everything else is input gathering.
The two paths, defined precisely
Certification converts the quantity of each named product deployed during the term into a perpetual license entitlement. There is no fee to certify. You declare the deployed counts in a certification letter, the entitlement becomes permanent, and you continue to pay technical support at the level set in the ULA. You lose the right to deploy without limit, so any growth beyond the certified count requires new licenses bought deliberately.
Renewal extends the unlimited right for another term, usually three to five years, for a new fee. You keep the ability to deploy without counting, you defer the certification decision, and you pay the renewal fee plus support across the term. A renewal makes sense when the value of the deployment you will add during the next term, valued at what those licenses would otherwise cost, exceeds the renewal fee by a comfortable margin.
A perpetual ULA, or PULA, has no certification exit at all. If your agreement is a PULA, the certify or renew model does not apply in the same way, and the levers are different. Read the PULA guide before you model anything.
The inputs the model needs
A defensible comparison rests on six inputs. Five are knowable from your own records and your contract. The sixth, the renewal fee, is a number Oracle will quote, and it is an opening position rather than a fixed price. Gather the five you control before you ever see the quote, so the quote is measured against your model rather than the other way round.
| Input | Where it comes from | Why it matters |
|---|---|---|
| Annual support fee | Your current Oracle support renewal notice | This continues on both paths and is the largest recurring number |
| Certified deployment value | A measured count of what is deployed, valued at list less your historic discount | The perpetual value you keep at no fee by certifying |
| Forecast growth | Your real three to five year deployment plan, not a defensive guess | Decides whether unlimited deployment still has value to you |
| New license cost | List price of the products you would add, less an achievable discount | What growth would cost outside a ULA |
| Renewal fee | Oracle quote, treated as an opening position | The price of keeping the unlimited right |
| Risk and effort | Audit exposure, evidence readiness, internal cost to certify well | The soft costs that tilt a close decision |
The support repricing myth, settled
The single most expensive misconception in this decision is the belief that certifying a higher number raises your support bill. It does not. Support fees on a ULA are set at the ULA level and continue at that level after certification, regardless of whether you certify a thousand processors or ten thousand. A higher certified count is free value, not a higher cost. The fear runs exactly backwards.
This matters because the support myth is the lever most often used to push a customer toward renewal. If a team believes that a large certified count will be punished with a larger support invoice, it will under count out of caution, or renew to avoid the question entirely. Both moves leave money on the table. Certify the largest number you can defend, and your support stays exactly where it is.
Certification has no fee, and support does not rise with the certified count. The number you certify is the number of permanent licenses you keep for free. Within the bounds of what you can evidence, more is always better.
A worked five year comparison
The figures below are indicative and illustrate the method. They describe a mid sized enterprise with a stable Oracle estate, a support bill near three million per year, and a modest growth plan. Substitute your own numbers and the structure holds.
| Line | Certify now | Renew one term |
|---|---|---|
| Certification or renewal fee | 0 | 7,500,000 |
| Support, five years at 3.0m | 15,000,000 | 15,000,000 |
| New licenses for growth | 1,800,000 | 0 |
| Internal cost to certify well | 250,000 | 250,000 |
| Five year total | 17,050,000 | 22,750,000 |
| Perpetual value retained | High | Deferred |
In this illustrative case, certifying now and buying the modest growth as new licenses costs roughly 5.7 million less across five years than renewing, while locking in the perpetual entitlement immediately. The renewal only wins if the growth the business will actually add, valued at avoided license cost, exceeds the renewal fee. Here it does not come close. The figures are indicative and your own ratios will differ, but the shape of the answer is common in stable estates.
Indicative figures for a stable mid sized estate. The renewal premium is the cost of an option to deploy without limit. Only buy that option if you will use it.
When does renewal genuinely win?
Renewal is the right answer in a real set of cases, and a buyer side advisor should say so plainly. The model favours renewal when the next term carries heavy, certain deployment growth that would be expensive to license outside a ULA. It favours renewal when you are about to add a new Oracle product that is not yet widely deployed and that you want to spread without counting. It can favour renewal around a known acquisition, where the incoming estate could be folded under the agreement on favourable terms. And it favours renewal when your evidence is not yet strong enough to certify a defensible number, and a short, well negotiated extension buys the time to build the file.
The discipline is to require the growth to be real. A renewal justified by deployment that never materialises is the most common way enterprises overpay. Hold the forecast to the same standard you would hold a capital request, and let the model, not the calendar, decide.
| Signal points to certify | Signal points to renew |
|---|---|
| Estate is stable or shrinking | Heavy, certain growth in the next term |
| Deployment is already broad and well evidenced | A new Oracle product is about to be rolled out widely |
| Cloud and virtualization positions are clean | An acquisition will add Oracle estate soon |
| You want to cap Oracle spend and exit unlimited | Evidence is not yet strong enough to certify well |
| Renewal quote is far above your model | Renewal quote, once negotiated, beats new license cost |
The renewal quote is an opening position
When the renewal quote arrives, treat it as the start of a negotiation, not a price tag. Opening renewal positions commonly move by 20 to 40 percent over the course of a properly run negotiation, and the strongest lever you hold is a credible willingness to certify and walk away from the unlimited right. A customer who has already modelled certification, measured the deployment, and prepared the evidence file negotiates from strength. A customer who has done none of that is quoting against fear, and the quote knows it.
This is why the model is built before the quote is requested. The figures you control set the ceiling you are willing to pay for the unlimited option. If the negotiated renewal lands below that ceiling and the growth is real, renew. If it does not, certify. The quote does not set your number. Your model does.
The Meridian certify or renew method
We run the decision as a repeatable sequence. Each step produces an artifact a board will accept, and the order matters, because measuring the deployment before requesting the quote is what creates the leverage.
- Read the contract. Confirm the agreement type, the certification rights, the cloud and territory clauses, and the customer definition. The decision is contract specific and starts here.
- Measure the deployment. Build a defensible count of every named product, across production, test, disaster recovery, cloud, and virtualization, with the evidence to support it.
- Value the certified position. Price the measured deployment at list less your historic discount to find the perpetual value certification would lock in for free.
- Forecast growth honestly. Hold the three to five year deployment plan to a capital grade standard and value the new licenses it would require outside a ULA.
- Model both paths. Build the five year total cost of certify now versus renew, exactly as in Table 2, on your own figures.
- Request and negotiate the quote. Only now invite the renewal quote, and measure it against the model with certification as your walk away.
- Decide and document. Choose the path the figures support and record the reasoning, the evidence, and the numbers for the board and for any audit that follows.
How to present the decision to the board
Boards do not want the mechanics. They want the number, the risk, and the recommendation. Lead with the five year total cost of each path and the gap between them. State the perpetual value certification retains. Name the one or two assumptions the decision is sensitive to, usually the growth forecast and the negotiated renewal fee, and show how the answer changes if those move. Close with a single recommendation and the evidence that backs it. A decision framed this way is approved quickly, because it reads as arithmetic rather than as a bet.
Certification rights, cloud counting, the customer and territory definitions, and any cap on the unlimited right are all set by your specific agreement, and they change the inputs to the model. In ULA work the answer almost always depends on the exact language. Treat every figure here as indicative and confirm the mechanics against your own contract before you act.
The one page workbook
Use this as the cover sheet for your own model. Fill the left side from your records and your contract, request the renewal quote last, and let the totals decide.
- Agreement type confirmed and certification rights read.
- Current annual support fee recorded from the renewal notice.
- Measured deployment count built with evidence, across all environments.
- Certified value calculated at list less historic discount.
- Growth forecast held to a capital grade standard and valued as new licenses.
- Five year totals modelled for both paths.
- Renewal quote requested last and measured against the model.
- Decision documented with reasoning and evidence for the board and the audit file.
The next step
The model is only as good as the deployment number underneath it, and that number is where most of the value and most of the risk sit. If you would like the measurement and the comparison run with you, on your contract and your figures, that is the work we do. For the wider decision in context, read the certify or renew guide and the Oracle ULA certification guide.