# QAD Subscription vs Perpetual License TCO Calculator

> Source: https://netray.co/tools/qad-cloud-subscription-vs-perpetual-tco-calculator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Model the multi-year total cost of owning QAD on a perpetual license plus maintenance versus a cloud subscription, and find the break-even year.

## Category

other-erp

## Erp

QAD Adaptive ERP

## Industry

Discrete Manufacturing

## Audience

- CIO
- Controller
- ERP manager

## Tool

**Kind:** calculator

**Currency:** $

**Inputs:**

#### Named users

**Key:** users

**Type:** number

**Default:** 100

**Min:** 1

**Step:** 5

**Unit:** users

**Help:** Users you would license in either model.

#### Perpetual license price per user

**Key:** license_per_user

**Type:** number

**Default:** 4500

**Min:** 0

**Step:** 100

**Unit:** $

**Help:** One-time price from your quote or last purchase.

#### Annual maintenance rate

**Key:** maint_pct

**Type:** number

**Default:** 20

**Min:** 0

**Max:** 40

**Step:** 1

**Unit:** % of license

**Help:** Yearly support and maintenance as a percent of license value.

#### On-premise infrastructure per year

**Key:** infra_per_year

**Type:** number

**Default:** 30000

**Min:** 0

**Step:** 1000

**Unit:** $

**Help:** Servers, storage, backup, database licences and hosting you pay for yourself.

#### In-house admin and DBA effort

**Key:** admin_fte

**Type:** number

**Default:** 0.5

**Min:** 0

**Step:** 0.1

**Unit:** FTE

**Help:** Fraction of a person spent keeping the platform running.

#### Loaded cost per admin FTE

**Key:** admin_cost

**Type:** number

**Default:** 60000

**Min:** 0

**Step:** 1000

**Unit:** $ per year

#### Subscription price per user per month

**Key:** sub_per_user_month

**Type:** number

**Default:** 180

**Min:** 0

**Step:** 5

**Unit:** $

**Help:** From the subscription quote. Illustrative default only.

#### Other subscription-side costs per year

**Key:** sub_other

**Type:** number

**Default:** 15000

**Min:** 0

**Step:** 1000

**Unit:** $

**Help:** Integration hosting, extra environments, sandbox add-ons.

#### Time horizon

**Key:** years

**Type:** slider

**Default:** 5

**Min:** 1

**Max:** 10

**Step:** 1

**Unit:** years

**Outputs:**

#### Perpetual license purchase

**Key:** perp_license

**Expr:** users * license_per_user

**Format:** currency

#### Perpetual yearly run cost

**Key:** perp_annual

**Expr:** perp_license * maint_pct / 100 + infra_per_year + admin_fte * admin_cost

**Format:** currency

**Description:** Maintenance plus infrastructure plus admin effort.

#### Perpetual total over horizon

**Key:** perp_total

**Expr:** perp_license + perp_annual * years

**Format:** currency

**Primary:** true

#### Subscription yearly cost

**Key:** sub_annual

**Expr:** users * sub_per_user_month * 12 + sub_other

**Format:** currency

#### Subscription total over horizon

**Key:** sub_total

**Expr:** sub_annual * years

**Format:** currency

**Primary:** true

#### Perpetual minus subscription

**Key:** diff

**Expr:** perp_total - sub_total

**Format:** currency

**Description:** Positive means subscription is cheaper over the horizon.

#### Break-even year

**Key:** breakeven

**Expr:** if(gt(sub_annual - perp_annual, 0), perp_license / (sub_annual - perp_annual), 0)

**Format:** years

**Description:** Years until perpetual becomes cheaper. 0 means subscription is cheaper every year, so there is no break-even.

**Chart:**

#### Cumulative cost by horizon

**Type:** line

**X:** years

**From:** 1

**To:** 10

**Steps:** 10

**Series:**

- perp_total
- sub_total

**Disclaimer:** Illustrative model only. Use figures from your own QAD quote and contract. Excludes implementation, upgrade projects, taxes and discounts.

## Content

**Intro:** Moving QAD to a subscription changes the shape of spend, not just the amount. This calculator lays a perpetual license with maintenance next to a subscription so a controller or CIO can see where the lines cross.

**Sections:**

#### How to use it

**Body:** Enter the user count and the two price points from your quotes. For the perpetual side, include what you really pay to run it: infrastructure, database licences and the share of an administrator who patches and monitors the system. For the subscription side, add costs the vendor does not bundle, such as extra non-production environments or integration hosting. Move the time horizon slider to see how the answer changes at three, five and ten years. The chart plots both cumulative totals against years so the crossover is visible.

**Bullets:**

- Use the same user count on both sides
- Take maintenance percent from your last renewal invoice
- Include admin time even if it is nobody's full-time job
- Test a discount case and a list-price case

#### The maths behind it

**Body:** Perpetual total equals the up-front license plus yearly run cost multiplied by years. Yearly run cost is maintenance rate times license value, plus infrastructure, plus admin FTE times loaded cost. Subscription total equals users times monthly price times twelve, plus other yearly costs, times years. Break-even is the license purchase divided by the yearly gap between subscription and perpetual run cost. If the subscription is cheaper every year, the break-even shows zero because the lines never cross.

#### Reading the result

**Body:** A short break-even, say under three years, favours subscription for a business that expects to change ERP or shrink. A long break-even favours owning if you plan to run the same release for a decade. Cost is only half the story: subscription typically bundles upgrades and hosting, while a perpetual estate keeps control of upgrade timing and data location, which matters for regulated or air-gapped sites. Treat the difference as one input beside risk, capability and exit terms.

#### Common mistakes

**Body:** The most frequent error is comparing a subscription quote with license price alone and ignoring infrastructure and admin cost. The second is forgetting that maintenance usually rises with license additions. The third is ignoring one-time migration to the cloud edition, which belongs in a separate project budget. Also check whether the subscription price escalates yearly; if it does, raise the monthly price to the average over the horizon.

**Cta:** If you are weighing a move and want the numbers tied to your real user, transaction and customization footprint, Netray can review the inputs with you. No obligation.

**Faq:**

#### Does this use real QAD prices?

**Answer:** No. Defaults are placeholders so the tool works on first load. QAD pricing varies by contract, volume and region, so replace every figure with those from your own quote or renewal invoice before relying on the result.

#### Why include infrastructure and admin time?

**Answer:** Because a perpetual license runs on hardware and people you pay for separately. Leaving them out understates the cost of owning and makes the subscription look dearer than it is, which is the most common bias in these comparisons.

#### What if the subscription price rises each year?

**Answer:** Estimate the average monthly price across the horizon and enter that figure. For a rough check, run the calculator twice with the starting and ending prices and compare the totals to see the sensitivity.

#### Can I use it for other ERPs?

**Answer:** Yes. The model is generic: a one-time license with percentage maintenance versus a per-user subscription. Replace the inputs with figures from any vendor, though terms such as bundled hosting differ between vendors.

## Search terms

QAD subscription vs perpetual, QAD ERP TCO calculator, QAD licence cost, QAD cloud cost vs on premise, ERP subscription vs perpetual license calculator, QAD maintenance cost percentage, QAD Adaptive ERP pricing model, ERP break even calculator

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json