Key takeaways
- A perpetual license is a one-time purchase of the right to run a specific software version forever, typically paired with an annual maintenance fee for support and updates.
- Maintenance fees usually run 18 to 22 percent of the original license price per year, meaning a customer pays back the license cost in maintenance within four to five years.
- SAP is one of the clearest examples of a company built almost entirely on perpetual licensing for its first three decades, with a central ERP core and separately licensed modules on top.
- Vendors get large upfront cash and high-margin maintenance revenue, but they carry a structural problem: growth depends on closing new deals, not on customers using the product more.
- Customers get ownership and control at a high entry cost, and they often underestimate the hardware, hosting, and internal IT cost required to run the software they bought.
Where the perpetual software license model came from
The perpetual software license model is the oldest of the four license models covered in this series, and it grew directly out of how physical products were sold. A customer bought a copy of the software, much like buying a machine, and owned the right to run it. IBM formalized this approach for mainframe and midrange software in the 1960s and 1970s, bundling a license fee with an annual support and maintenance charge that has stayed remarkably consistent, at roughly 18 to 25 percent of license cost per year, for more than fifty years.
SAP is the company most associated with taking this model and scaling it into one of the largest software businesses on the planet. Founded in 1972, SAP built its R/2 and later R/3 ERP systems around a central financial and operational core, with additional modules for HR, sales, manufacturing, and dozens of other functions licensed on top as separate line items. A customer bought the core system, then added modules as their needs grew, each with its own license fee and its own maintenance line. This modular, perpetual structure defined enterprise software procurement for almost four decades, and it is still how a large share of on-premise ERP, database, and engineering software is sold today.
Metrics: how a perpetual software license model is measured
The perpetual model is measured very differently from a subscription business. There is no monthly recurring revenue to track. Instead, the core metrics are the following.
License revenue is booked largely upfront, at the point of sale, based on the scope purchased: number of named or concurrent users, number of server cores, or a site license covering an entire location. In a B2B context, a mid-sized manufacturer buying an ERP core plus a production planning module might pay a one-time license fee in the range of a few hundred thousand euros, scaled by user count and module selection.
Maintenance revenue is the recurring layer, typically 18 to 22 percent of the original license fee per year, covering technical support, patches, and version upgrades. Because there is almost no marginal cost to delivering maintenance once the support organization exists, this line carries some of the highest gross margins in the software industry, often above 85 percent.
Attach rate measures what share of license customers also buy each additional module, which is how a perpetual vendor grows revenue per account without a new full-price sale. Net license growth, the year-over-year change in new license bookings, is the metric that matters most to a perpetual vendor’s growth story, because unlike a subscription business, there is no compounding installed base revenue to fall back on if new sales slow down.
Pro tip: If you still sell under a perpetual license model, track your license-to-maintenance ratio over time. A shrinking ratio of new license bookings to existing maintenance revenue is an early warning sign that growth is slowing, well before it shows up in total revenue.
The vendor side: what a perpetual software license model gets right and wrong
For the company selling it, the perpetual model has one clear advantage: it generates a large amount of cash at the point of sale, which is attractive for funding operations or demonstrating strong bookings in a single period. Maintenance revenue is also highly profitable and reasonably sticky, since switching enterprise software is expensive and disruptive for the customer.
The structural weakness is growth. Because most of the revenue is recognized upfront, a perpetual vendor has to keep closing new license deals every quarter just to maintain its growth rate. There is limited natural expansion revenue from existing customers, aside from module attach and occasional user growth. This also creates a subtle incentive problem: once a customer has paid for a version and is on maintenance, the vendor’s near-term revenue is largely secured whether or not that customer is thriving with the product. This can quietly reduce the pressure to keep improving the product as aggressively as a subscription vendor, whose revenue depends on renewal and expansion every single year.
The customer side: what a perpetual software license model gets right and wrong
For the buyer, ownership is the main draw. The software keeps working even if the vendor disappears or the customer stops paying maintenance, which matters in regulated industries or for systems that must run for a decade or more without forced upgrades. A perpetual license is also a capital expenditure rather than an operating expense in many accounting frameworks, which some finance teams prefer for budgeting and depreciation purposes. Once the license is paid off, the ongoing maintenance fee is usually lower than an equivalent SaaS subscription would cost over the same period, assuming the customer does not need frequent feature updates.
The downside is the entry cost. A perpetual license requires a large upfront capital outlay, which is a harder budget approval than a smaller recurring subscription fee, especially for a mid-market buyer. Customers also frequently underestimate what they are signing up for beyond the license and maintenance fee. Running the software still requires servers or data center capacity, an internal IT team to patch, back up, and secure the system, and a separate budget line for major version upgrades, which are usually treated as their own projects rather than included in the annual maintenance fee. When companies compare perpetual and SaaS total cost of ownership, they often compare the license and maintenance fee against the subscription fee, and forget to add back their own infrastructure and staffing cost on the perpetual side.
Quick facts
- Perpetual license maintenance fees typically run 18 to 22 percent of the license price annually, so a customer pays back the license cost in maintenance within four to five years.
- SAP built its ERP business on a central perpetual license core with separately priced modules, a structure that shaped enterprise software procurement for decades.
- Perpetual license revenue is recognized largely upfront, which makes a vendor’s growth almost entirely dependent on closing new deals each period.
- Maintenance revenue on a perpetual license commonly carries gross margins above 85 percent, because delivering patches and support has little marginal cost per customer.
- Customers on a perpetual license still carry the full cost of hosting, IT staffing, and periodic major upgrades, costs that are easy to leave out of a total cost of ownership comparison.
Frequently asked questions
- What is a perpetual software license model?
A perpetual software license model is a one-time purchase that grants a customer the right to use a specific version of software indefinitely. It is usually paired with an annual maintenance fee, typically 18 to 22 percent of the license price, that covers technical support and access to updates. - Why did SAP succeed with the perpetual license model?
SAP structured its ERP system around a central core with additional modules licensed on top, which let customers start with a defined scope and expand over time. This modular, perpetual approach became the standard procurement pattern for enterprise software for nearly four decades. - Is a perpetual license cheaper than SaaS over time?
It can be, once the license is paid off and if the customer’s needs stay stable. However, the comparison only holds if the customer also accounts for the cost of hosting, IT staff, and periodic major upgrades, which a SaaS vendor typically absorbs as part of the subscription. - Why is growth harder for a company selling perpetual licenses?
Because most revenue is recognized at the point of sale, a perpetual vendor has limited built-in expansion revenue from existing customers. Growth depends heavily on closing new license deals every period, unlike a subscription business, where the installed base itself compounds revenue through renewals and upsell. - Who still uses the perpetual software license model today?
Perpetual licensing remains common in industries with long hardware refresh cycles, such as manufacturing engineering software, and in regulated or security-sensitive environments where customers need full control over exactly which software version runs in production.
The perpetual software license model still has a place, just a smaller one
The perpetual model is not a relic. It is the right choice for customers who need long-term control over a fixed system and are willing to pay for that control upfront. It also remains one of the most profitable ways to monetize software on a per-transaction basis, thanks to high-margin maintenance revenue.
What has changed is which products it fits. As the earlier article on B2B software license models laid out, the choice between models is really a choice about how a company wants its revenue, and its relationship with the customer, to behave over time. Perpetual licensing behaves like a series of one-time transactions. The next article in this series looks at the model built to behave the opposite way: SaaS, where the relationship, and the revenue, is meant to compound every year.
If you are still selling under a perpetual model and want to know whether a shift toward subscription or usage-based pricing makes sense for your product, let’s have a conversation.