A PULA binds for the life of the agreement, so the questions you ask before signing are the only ones you will get. Settle the product list, the customer definition, the territory, and the support basis, and confirm you have priced the certification alternative, before you commit to a right that never closes.
Because a PULA has no certification exit, it has no second chance. A fixed term ULA forgives a weak negotiation, because the term ends and you get to certify or renegotiate. A PULA does not. Whatever you accept at signature is what you hold, potentially for the life of the organisation, so the diligence before signing carries the entire weight. This is a checklist for that moment. It assumes you have read the structure and concluded a PULA may fit, and it gives you the eight questions that separate a sound perpetual agreement from a permanent mistake. Work through each against your own contract draft, because every answer turns on the specific language in front of you.
Check the product list, the customer definition, the territory, and the support basis, because each one binds for the life of the agreement. Then confirm you have priced a certification alternative, since a PULA only earns its permanence when the estate will grow enough to use the unlimited right. If any of these is unresolved, the agreement is not ready to sign.
1. Is the product list exactly right? Every product carries perpetual support. Remove anything you will not strategically use.
2. Does the customer definition match the group? Confirm it reaches every entity that will deploy, and excludes those that should not.
3. Is the territory wide enough for your real footprint? A region you operate in but the clause omits is a permanent gap.
4. How is the support basis calculated and escalated? This is the dominant lifetime cost. Fix the basis and any escalation now.
5. Have you priced the certification alternative? Model the owned count you could certify instead, so you know what you are giving up.
6. Will the estate actually grow into the unlimited right? A flat estate rarely justifies a perpetual agreement.
7. What happens on a future merger or divestiture? Confirm how the customer definition behaves when the group changes.
8. Is there any negotiated path out? A PULA has no contractual exit, so understand what an exit would require before you rely on never needing one.
The first four questions cover terms that, in a fixed term ULA, would be revisited at the next term boundary. In a PULA there is no boundary. The product list, the customer definition, the territory, and the support basis are set once and govern the agreement for as long as you hold it. The customer definition deserves the closest reading, because it is the clause most likely to drift out of alignment as the group changes, and its failure mode under a perpetual agreement is permanent rather than temporary. The detail is in the PULA customer definition risk.
Questions five and six are the strategic core. A PULA is the right choice only when the estate will use the unlimited right enough to justify giving up the conversion a ULA would offer. The way to know is to price the alternative: model the count you could certify and own, and compare its lifetime cost against the perpetual support stream. If the owned entitlement is the better value, a PULA is the wrong structure however convenient it looks. Pricing that alternative also gives you the leverage to improve the PULA terms if you do sign, which is the subject of negotiating into a PULA from strength.
Questions seven and eight protect you against the future you cannot see. A PULA has no certification exit, so leaving it is a negotiated change with Oracle rather than a contractual right. Understanding, before signing, how the customer definition behaves through corporate change and what an exit would actually require means you commit with open eyes. You may never need the answer, but a permanent agreement is exactly the kind of commitment where the unlikely scenario is the one worth pricing. The full structural context sits in the Oracle PULA guide.
If a PULA is in front of you, do not sign until all eight questions have firm answers grounded in your own contract draft and your real estate. Confirm the product list, the customer definition, the territory, and the support basis, price the certification alternative, and understand the exit you are giving up. Read the structure in the Oracle PULA guide, prepare your position with negotiating into a PULA from strength, and frame the decision with our PULA and capped ULA guide. Because the answers depend entirely on your contract language, the safest step is a careful review before you commit to a right that does not close.
Check the product list, the customer definition, the territory, and the support basis, because each binds for the life of the agreement. Then confirm you have priced a certification alternative, since a PULA only makes sense when the estate will grow enough to use the unlimited right.
Not easily. A PULA has no certification exit, so there is no built in moment to convert it to a fixed entitlement and walk away. Exiting usually means a negotiated change with Oracle rather than a contractual right, which is why the questions to settle are the ones asked before signature.
We review the PULA draft against your estate, price the certification alternative, and tell you whether the perpetual right is worth what it asks you to give up.