Perpetual vs subscription software: three-year cost

Quick answer: Compare three-year cash cost only after matching the rights you actually need. For a perpetual license, add the upfront licenses, required maintenance, chosen major-version upgrades, add-ons, tax, and eventual export or migration work. For a subscription, add each billed seat-month, renewal changes, add-ons, tax, and the same exit work. Then check what can still be used or opened after payments stop. A lower total for unequal rights is not a useful purchasing answer.

Important constraint: “Perpetual” can mean a continuing right to use a named version, not future features, every device, cloud services or support forever. Conversely, a subscription may bundle services or device rights a one-time license lacks. Microsoft’s Office comparison and Foxit’s license terms illustrate why the current contract matters more than the pricing label.

A small team often starts with two offers that look comparable on a price card: one payment for software it can keep using and a smaller charge every month. The arithmetic is simple; making the workflows equivalent is the harder part. Use the same number of people, required devices, features, territory, currency, tax basis and three-year horizon in both columns. Name the product editions and contract dates next to the figures. If one plan handles a necessary task that the other cannot, resolve that gap before totaling the prices.

Define the work and rights before adding dollars

Write down the tasks the software must support over the next three years. A PDF editor, for example, might need form editing, redaction and third-party signature requests; a document suite might need desktop apps, shared storage and use on multiple devices. A price comparison cannot turn missing functionality into a discount. Treat a required cloud service as a separate add-on for the perpetual route if it must be purchased elsewhere, or remove it from the subscription side only if it is genuinely unnecessary.

The answers can vary within one vendor’s catalog. Microsoft’s Office 2024 FAQ identifies Home & Business 2024 as a one-time purchase for one PC or Mac; a later major release requires a new purchase. Microsoft says Office 2024 receives security updates during its support period but no new feature upgrades, while Microsoft 365 is a subscription with updates and services. These statements describe those products, not every perpetual or subscription license. Do not merge a consumer Office 2024 edition with volume-licensed Office LTSC or an unspecified Microsoft 365 business plan when comparing rights.

Foxit’s PDF Editor agreement supplies a different example: a single-use perpetual license and annual maintenance have distinct terms, and lapsed maintenance may affect access to future major versions and support. An owner should read the clause for the exact edition and version under consideration. The question is not whether “perpetual software has maintenance”; it is whether this purchase needs maintenance to keep receiving a specific benefit the team values.

Build a three-year cash worksheet

Use nominal cash totals unless your business has a finance policy requiring present-value discounting. Keep the horizon explicit: 36 months from the planned purchase date. For each offer, record the currency, market, billing term, quote date, applicable tax and how many licenses or seats are needed. A per-device perpetual offer and a per-user subscription should be multiplied by their actual assignments, not automatically by the same headcount.

Write the renewal period separately from the introductory term. A “$14/month” figure billed for 12 months can have different commitment and cancellation implications from a cancellable month-to-month rate, even if the display uses the same monthly unit. Record scheduled increases if the contract specifies them. If future renewal prices are unknown, create a range or sensitivity row rather than quietly assuming they remain flat for all 36 months.

Maintenance is not the same as an upgrade. If maintenance includes the next major version, counting both its fee and a separate upgrade purchase would double-charge the perpetual column. If it only covers support, a desired later version may need its own row. Ask for the exact entitlement and date it ends. Likewise, do not add a subscription’s included service twice as an external add-on.

Worked example: two seats with invented prices

Suppose two users need the same core function for three years. For the exercise, a perpetual license costs $250 per seat now; both users choose an $80-per-seat major upgrade in year three; and export or migration work at the end costs $120. The subscription costs $14 per seat per month for all 36 months, with the same $120 exit work. Assume no tax, price increase, maintenance, extra service or change in seat count. These are worksheet inputs, not a quote for Microsoft, Foxit or any other product.

The subscription total exceeds the perpetual total by $348 under these exact assumptions. That difference is useful for checking the model, not for announcing that perpetual software generally saves money. If the subscription includes a service the perpetual buyer must obtain separately, add its real price and test whether it closes the gap. If the subscription provides necessary multi-device access while a perpetual license needs another installation purchase, normalize that right before comparing totals.

Now change one assumption at a time. If the buyer never needs the year-three upgrade, the perpetual arithmetic becomes $500 + $120 = $620. But the two routes may no longer have matching feature sets, because the subscription might receive improvements over those years. If a third person joins for only the final year, the subscription example adds 1 × $14 × 12 = $168, while the perpetual route needs a new license on the date that person joins. Its cost and later transfer rights must come from the actual offer; inventing a resale value would disguise a gap in the quote.

A basic break-even shortcut divides upfront price by monthly charge. For a single $250 license against $14 per month, $250 ÷ $14 ≈ 17.9 months. That crossing point assumes identical rights, one user, no maintenance, upgrades, renewal jump, service fee, tax or exit difference. In most serious software choices, at least one of those conditions changes. Use the shortcut only as a prompt to fill the full worksheet, not as the final decision.

Test the exit before valuing continued access

The end of the three-year term can matter as much as the entry price. Ask whether the perpetual app will still open existing files on the team’s supported computers, and whether security or compatibility support continues. Ask which subscription functions remain after cancellation, how long data can be retrieved, and whether an export preserves attachments, formatting, permissions and metadata the next workflow needs. A promise that “export is available” does not tell you how much staff time the move will require; Microsoft’s data-export documentation describes methods for some services, not a zero-effort transition.

Price exit work in both columns. Even a perpetual app can become unsuitable if the business changes file formats, operating systems or collaborators. A subscription can be easy to leave in one workflow and laborious in another. Use a small representative file set to estimate export, conversion, validation and staff review. If access to historical records is a legal or operational requirement, get the organization’s appropriate advice and name the retention owner rather than assuming continued product access solves it.

Choose that sample deliberately: include the largest ordinary file, one with comments or tracked changes, one with embedded assets, and one shared with another person. Try opening the export in the intended destination and note what survives. If a field or permission has to be rebuilt manually, multiply the time by the number of comparable files you expect to migrate. Record the estimate as a range when the full collection is unknown. This turns an abstract “switching cost” into work a team can plan, while keeping the estimate separate from a vendor’s license price.

There is also a timing question. A perpetual purchase concentrates cash upfront; a subscription spreads payments. A buyer with a cash constraint may prefer the latter even if the nominal three-year total is higher. Conversely, an offline workflow that rarely needs new features may value continued use of a named version. These are business preferences to record beside the arithmetic, not universal product properties.

Make the choice from a same-rights quote

Request a current quote or checkout for the exact editions, territory, seat or device assignment, billing commitment and tax treatment. Attach the relevant license and cancellation terms to the worksheet. Put unknown rather than zero beside an unpriced upgrade, service or export task. If an unknown could reverse the $348 hypothetical gap, resolve it before signing a multi-year commitment.

Then state the decision in one sentence that names both the rights and the horizon: “For two named users, our required features and devices are covered, and this option has the lower verified three-year total after maintenance, expected upgrades and exit work.” Another team may reasonably choose the other route because it needs bundled services or easier provisioning. The software hub covers further product decisions; the worksheet remains useful whenever a one-time purchase and a subscription appear to offer the same task.