The Three Models Defined
Overpaying for Enterprise Software? We handle software and cloud contract negotiation on a 25% gainshare basis — you keep 75% of every dollar saved. No retainer. No risk.
Get a free Enterprise Software savings estimate →Before evaluating which model is right for your organisation, it is worth being precise about what each model actually is — because vendors use the terminology loosely, often in ways that obscure the financial reality.
Enterprise Licence Agreement (ELA)
An ELA is a multi-year, all-you-can-use licence for a defined set of products across a defined scope of deployment. The buyer pays a fixed annual fee in exchange for unlimited deployment rights within agreed parameters. Oracle ELAs (often called ULAs — Unlimited Licence Agreements), ServiceNow ELAs, and IBM ELAs are the most common examples. At the end of the term, the buyer "certifies" — declares actual deployment and converts to named perpetual licences. Alternatively, they renew the ELA for another term.
Subscription
A subscription model charges the buyer per user, per seat, per core, per worker, or per unit of consumption, typically billed annually or monthly. The buyer's rights terminate when the subscription ends — there is no underlying perpetual entitlement. Microsoft 365, Salesforce, Workday, SAP RISE, and most modern SaaS products operate on subscription models. Subscription costs are typically classified as operating expense (OpEx) rather than capital expense (CapEx).
Perpetual Licence
A perpetual licence grants the buyer an indefinite right to use a specific version of a product, in exchange for a one-time capital payment. The licence itself does not expire. However, ongoing support and maintenance is charged separately — typically 18–22% of the original licence value per year. Oracle Database, SAP on-premise, IBM Db2, and older versions of many enterprise products are sold this way. Perpetual licences are CapEx-heavy upfront but can be cheaper over a 5–10 year horizon if maintenance costs are controlled.
The model isn't neutral. Every vendor's preference for a particular licensing model is driven by its own revenue dynamics. Oracle's pivot away from perpetual licences toward cloud subscriptions (OCI, Fusion Cloud) was about recurring revenue predictability, not buyer economics. SAP's RISE push is similarly about converting one-time licence revenue into multi-year subscription ARR. Your model choice should be driven by your economics — not theirs.
Head-to-Head: ELA vs Subscription vs Perpetual
The table below compares the three models across the dimensions that matter most to enterprise procurement and finance teams.
| Dimension | ELA | Subscription | Perpetual |
|---|---|---|---|
| Accounting treatment | OpEx (typically) | OpEx | CapEx + OpEx maintenance |
| Cost certainty | High (fixed term fee) | Low (usage/seat-based) | Medium (maintenance escalates) |
| Deployment flexibility | High (unlimited within scope) | Medium (add seats as needed) | Low (fixed licence count) |
| Exit / switching cost | Medium (perpetual licences on cert) | High (no residual entitlement) | Low (perpetual rights retained) |
| Audit exposure | Low (during ELA term) | Medium (usage-based audits) | High (perpetual = permanent audit risk) |
| Negotiation leverage | High (scope, term, cert mechanics) | Medium (unit price, term) | Medium (licence count, support rate) |
| 3-year TCO vs deployment growth | Favourable (fixed regardless of growth) | Unfavourable (cost grows with seats) | Depends on maintenance rate |
| Typical vendor preference | Neutral to positive | Strongly preferred | Declining preference |
Not sure which licensing model is right for your Oracle, SAP, or ServiceNow estate? Our multi-vendor negotiation team performs licensing model analysis as part of every engagement. 25% gainshare — you pay only on verified savings.
Get a Licensing Model AssessmentVendor-by-Vendor: Which Model They Push and Why
Understanding the vendor's motivation is as important as understanding the model mechanics. Here's what each major vendor is pushing in 2026 and why:
Oracle: Perpetual to cloud subscription
Oracle's traditional model was perpetual licences plus 22% annual support. It generated reliable maintenance revenue but didn't grow with inflation or customer expansion. Oracle is now aggressively pushing OCI and Fusion Cloud (subscription) and using licence reviews (LMS script deployment) to create audit pressure that pushes customers toward cloud migration deals. Buyers who understand the perpetual model — particularly ULA certification mechanics — can achieve significant savings by right-sizing rather than converting. Our Oracle negotiation service specialises in ULA exits, perpetual right-sizing, and cloud migration deal structuring.
Microsoft: Annual subscription EAs
Microsoft's Enterprise Agreement is a subscription model — M365, Azure, and Dynamics 365 all operate on annual subscription terms under the EA or MCA-E framework. Microsoft is pushing E5 SKUs (high commission) and Copilot add-ons aggressively in 2026. The EA structure itself favours Microsoft: annual true-ups mean licence counts only go up during the term, and NCE (New Commerce Experience) has reduced buyers' ability to downsize. The right counter-strategy is meticulous usage analysis before each true-up and aggressive E3/E5 right-sizing at renewal.
SAP: RISE (cloud subscription)
SAP is converting its on-premise perpetual licence base to RISE with SAP (a bundled cloud subscription). RISE pricing bundles S/4HANA Cloud, BTP credits, and managed infrastructure into a single per-FUE (Full Use Equivalent) annual fee. The bundling makes benchmarking difficult. Buyers who accept RISE without interrogating the FUE count, BTP allocation, and infrastructure cost assumptions routinely overpay by 25–35% versus a well-negotiated deal. Perpetual SAP licences remain legally valid under vendor support until at least 2027 for ECC — buyers should not convert until the economics are demonstrably favourable.
ServiceNow: ELA strongly preferred
ServiceNow's ELA model suits enterprises with significant Now platform expansion plans. An ELA caps the annual fee regardless of fulfiller count growth or new module adoption during the term. However, ServiceNow's ELA certification mechanics at the end of term require careful management — how you count fulfillers and scoped users at certification determines your post-ELA base. Negotiate the certification rules upfront, not at the end of the term. Our ServiceNow negotiation service addresses ELA certification traps specifically.
Salesforce: Multi-year subscription lock-in
Salesforce's preference is a multi-year subscription with annual price escalation clauses. Its auto-renewal provisions are aggressive — the default notice period for non-renewal is 90 days, which passes unnoticed in many organisations. Salesforce subscription pricing benefits enormously from bundling: Sales Cloud, Service Cloud, Data Cloud, MuleSoft, and Tableau packaged together generates significant discount and co-terming complications that work in Salesforce's favour. Negotiate term, auto-renewal terms, and price escalation caps at contract signature — not at renewal.
When an ELA Is the Right Choice
An ELA makes financial sense under three conditions: you are in a rapid-growth phase where licence counts will increase significantly during the term; you are at risk of audit exposure that an ELA would eliminate during the term; or you are deploying the product broadly and the fixed-fee model creates a lower per-unit cost than the alternative.
High-growth deployment requiring flexible licence scaling
If you're planning to grow from 500 to 2,000 ServiceNow fulfillers over 3 years, an ELA caps your cost while subscription pricing triples it.
Oracle estate with audit exposure and deployment uncertainty
A 3-year Oracle ULA eliminates audit risk during the term and allows you to deploy freely, then certify to a clean perpetual position at the end.
IBM products with complex PVU/sub-capacity compliance requirements
IBM ELAs simplify compliance dramatically and often produce better unit economics than managing PVU sub-capacity across a complex server estate.
Stable platform with predictable 3-year roadmap commitment
If you can commit to the platform for 3 years and have significant negotiating leverage, an ELA produces the deepest per-unit discount of any model.
When Subscription Wins
Subscription models make sense when your usage is variable and unpredictable, when you want OpEx treatment for financial flexibility, or when the product category is evolving rapidly and you don't want to be locked into a particular version or deployment approach.
For SaaS products like Salesforce, Workday, and modern Dynamics 365, subscription is the only model available — the question is not whether to subscribe, but how to negotiate the subscription terms. For infrastructure software like Oracle Database on OCI or SAP RISE, subscription versus perpetual is still a genuine choice, and the financial analysis is worth running carefully before committing.
Subscription models look cheaper in year one because they convert capital expenditure to operating expenditure. Over 5–7 years, the total cost of ownership of a subscription model for stable, fully-deployed software typically exceeds the perpetual equivalent by 40–80%. The subscription model transfers this risk to you — you stop paying only when you stop using the software, which for core ERP, database, and ITSM platforms is effectively never.
When Perpetual Licensing Still Makes Sense
Perpetual licensing is not obsolete. For software that is stable, fully deployed, and core to operations — Oracle Database running on-premise, SAP ECC on supported infrastructure, IBM mainframe tools — perpetual licences with negotiated maintenance represent the lowest total cost of ownership over a 7-year horizon, provided the maintenance rate is managed.
The key to making perpetual economics work is controlling the annual maintenance cost. Oracle's 22% maintenance fee and SAP's enterprise support cost are both negotiable. Buyers with perpetual licence estates should benchmark their maintenance rate against third-party alternatives (Rimini Street, LzLabs for IBM mainframe) and use the threat of switching to drive vendor concessions on support pricing. Our SaaS contract negotiation and multi-vendor advisory practices both address support cost reduction as a core service.
Considering a model transition — perpetual to RISE, on-premise to OCI, or Oracle EA to cloud? Before you convert, get an independent analysis of whether the economics work in your favour. Our gainshare model means we only get paid when we save you money — and preventing a bad model transition is as valuable as negotiating a better price.
Get a Model Transition AnalysisHybrid Models and Transition Strategies
Real enterprise software estates rarely operate on a single pure model. A typical Fortune 500 company might have Oracle Database on perpetual licences, Oracle Fusion Cloud on subscription, Microsoft on EA subscription, SAP on a mix of perpetual (ECC) and RISE (new S/4 workloads), and ServiceNow on an ELA. Managing the interaction between these models — and the transition strategies between them — is often where the most significant savings opportunities sit.
Hybrid model management creates specific negotiating opportunities. When a vendor wants to convert your perpetual licence base to subscription, you have structural leverage: you own the perpetual rights indefinitely, the vendor needs your business to demonstrate ARR growth, and you can use the conversion discussion to extract significant economic concessions — better subscription unit pricing, extended support on the perpetual estate, or cloud migration credits. Do not convert perpetual licences to subscription without extracting value for the rights you are surrendering.
How to Negotiate Each Model
The negotiation priorities differ significantly by model. Here is the focus for each:
Negotiating an ELA
The critical ELA terms are: scope of products included, deployment scope (entity-level, geography, affiliate coverage), certification mechanics at term end, price for renewal versus certification conversion, and what happens to deployment rights if you decide not to renew. Many ELA buyers discover at certification that the vendor interprets the scope more narrowly than the buyer assumed — resolving this ambiguity in the contract text during negotiation avoids expensive disputes 3 years later.
Negotiating a subscription
For subscriptions, the key levers are: unit price (per seat, per user, per worker), annual price escalation cap (aim for 0% or CPI-linked rather than vendor-defined), auto-renewal notice period extension (90 days is standard; push for 180 days minimum), downward adjustment rights (can you reduce seat counts at renewal, or only increase?), and bundling discounts versus standalone pricing. The auto-renewal clause is often the single highest-value term to negotiate in a SaaS subscription — it determines whether you have a genuine renewal negotiation or are forced to accept vendor pricing.
Negotiating perpetual licences
For perpetual licences, negotiate the licence count (right-size to actual deployment with a measured buffer), the metric (processor versus NUP for Oracle — this can swing cost by 40–60%), the support rate (22% is not mandatory — third-party support threat drives real reductions), and the support escalation cap. Perpetual licence negotiations also benefit from competitive pressure — IBM, for instance, responds significantly to Red Hat Linux alternatives on workloads currently served by IBM proprietary products.