Skip to content
ERP business case

ERP TCO calculator — 5-year cost of ownership

Model 5-year ERP total cost of ownership: subscription or licence, implementation, internal FTE, infrastructure, upgrades and support. Cloud vs on-prem.

Free · no signup · runs in your browserUpdated
Short answer

ERP TCO is the five-year sum of six cost lines: software (subscription, or licence plus annual maintenance), implementation, internal FTE time, infrastructure, upgrades and external support, each escalated annually. For 120 users on the seeded cloud assumptions that is $2,243,417 over five years — $3,739 per user per year, with software only a third of it.

An ERP TCO calculator has to price the whole system, not the invoice. Licence and implementation are visible and negotiated; internal FTE time, infrastructure, release testing and external support are the lines that quietly become the majority of the spend by year three.

This model runs five years, escalates every recurring line, and computes both delivery models from the same shared assumptions — so switching between cloud and on-premise changes only the lines that genuinely differ, and you can see the other model's total alongside the one you picked.

Every rate is yours to enter. The seeded values exist so the arithmetic is visible on first load; replace them with the figures on your quotes and your payroll before you show anyone the answer.

Your numbers

Delivery model
Subscription
users

All seat types combined. Cost per user per year falls as this rises, because support and internal FTE barely move.

$/user/yr

Use the rate on your own quote. The seeded value is a placeholder for the arithmetic, not a vendor price.

$

Cloud releases are not free to absorb. Budget the regression testing your team or partner runs each cycle.

Project and people
$

Everything spent to reach go-live. Charged in year 1 and not escalated.

FTE

Admin, report building, integration ownership, release testing. On-premise add DBA and server administration.

$

Salary plus employer taxes, benefits and overhead.

Run cost
$

Cloud: middleware, sandboxes, backups, monitoring. On-premise: add servers, storage, OS and database licences, DR and hosting — often several times the cloud figure.

$

Vendor support tier plus any partner retainer that starts when hypercare ends.

%

Applies to software, internal cost, infrastructure, support and upgrades. Model the cap in your contract, not the number you were quoted verbally.

Result

5-year TCO · cloud
$2,243,417

$3,739 per user per year · $642,500 in year 1, $424,074 by year 5

Cost per user per year$3,739
Average annual cost$448,683
Year 5 run rate$424,074
Software share of TCO33.3%
Internal FTE + support share43.1%
Same assumptions, on-premise$2,370,752
Cloud / SaaS — 5-year TCO$2,243,417
On-premise — 5-year TCO$2,370,752
Recurring lines escalate at 4% a year. Implementation sits in year 1 and is not escalated.
PeriodSoftwareImpl.InternalInfra + supportUpgradesTotal
Year 1$138,000$280,000$142,500$60,000$22,000$642,500
Year 2$143,520—$148,200$62,400$22,880$377,000
Year 3$149,261—$154,128$64,896$23,795$392,080
Year 4$155,231—$160,293$67,492$24,747$407,763
Year 5$161,440—$166,705$70,192$25,737$424,074
5-year total$747,453$280,000$771,826$324,979$119,159$2,243,417
Cost line5-year total% of TCOPer user/yr
Subscription$747,45333.3%$1,246
Implementation$280,00012.5%$467
Internal FTE (1.5)$771,82634.4%$1,286
Infrastructure$129,9925.8%$217
External support$194,9888.7%$325
Release testing$119,1595.3%$199
Total$2,243,417100.0%$3,739
Escalation factors at 4%: 1.0000 / 1.0400 / 1.0816 / 1.1249 / 1.1699
Software y1 = 120 × $1,150 = $138,000
Internal y1 = 1.5 FTE × $95,000 = $142,500
Run cost y1 = $138,000 + $142,500 + $24,000 + $36,000 + $22,000 = $362,500
Recurring 5y = $362,500 × 5.4163 = $1,963,417
TCO = $1,963,417 + $280,000 implementation = $2,243,417
Per user/yr = $2,243,417 ÷ (120 × 5) = $3,739
Cloud comes out $127,335 (6%) below on-premise on these assumptions, and spreads the spend evenly instead of concentrating it in year one. Software is only 33.3% of the total — internal FTE and support are what you are really committing to.

Everything is computed in your browser. Nothing you type is sent anywhere or stored.

The formula

TCO = Σ over years 1–5 of (Software + Internal FTE + Infrastructure + Support + Upgrades) × (1 + escalation)^(year − 1), plus Implementation in year 1
Software (cloud)
Users × subscription per user per year, escalated annually.
Software (on-prem)
Perpetual licence in year 1, plus annual maintenance calculated as a percentage of that licence in every year.
Implementation
One-off cost to reach go-live, charged in year 1 and not escalated.
Internal FTE
Full-time equivalents your business spends on the system × loaded annual cost per FTE. The line most models omit.
Infrastructure
Cloud: middleware, sandboxes, backups, monitoring. On-prem: servers, storage, OS and database licences, DR and hosting.
Upgrades
Cloud: annual release testing and regression. On-prem: a major upgrade project every N years, charged in the years it lands.
Escalation
Annual increase applied to every recurring line. Subscription uplifts, maintenance rises and salary inflation all compound.

Two modelling choices worth knowing. On-prem maintenance is charged from year one, not year two — vendors differ, so shift the licence figure if your contract bundles the first year. And a major upgrade lands in every year divisible by the interval you set, so an interval of 3 produces one upgrade inside a five-year window and an interval of 2 produces two.

Worked example

Users
120
Subscription per user per year
$1,150 (your quoted rate)
Implementation (one-off)
$280,000
Internal FTE
1.5 at $95,000 loaded
Infrastructure / support / release testing
$24,000 · $36,000 · $22,000 a year
Annual escalation
4%
Result
$2,243,417 over 5 years · $3,739 per user per year

The five escalation factors at 4% sum to 5.4163. Recurring cost in year one is $138,000 subscription + $142,500 internal + $24,000 infrastructure + $36,000 support + $22,000 release testing = $362,500. Multiply by 5.4163 for the five-year recurring total of $1,963,417, then add the $280,000 implementation to reach $2,243,417. Year one alone is $642,500; by year five the run rate is $424,074. Software is 33% of TCO — internal FTE and support together are more.

What an ERP TCO calculator must include

Cost lineCloudOn-premiseCommonly understated by
SoftwareSubscription per user, escalating annuallyPerpetual licence plus 18–22% annual maintenanceThe escalation. A flat subscription across five years is a fiction.
ImplementationOne-off to go-liveOne-off to go-live, usually higherInternal time, which sits in the FTE line here.
Internal FTEAdmin, report building, integration ownerThe above plus DBA and server administrationHalf to two FTE is normal at mid-market scale and rarely appears in any vendor comparison.
InfrastructureMiddleware, sandboxes, backups, monitoringServers, storage, OS and DB licences, DR, hostingOn-prem, by a lot. Database licensing alone can rival the ERP licence.
UpgradesRelease testing two or more times a yearA major upgrade project every 2–4 yearsCloud teams assume releases are free. Regression testing is not free.
SupportVendor support tier plus partner retainerSame, plus hardware and OS support contractsThe partner retainer, which usually starts the day hypercare ends.

Cloud vs on-premise: where the difference actually sits

The two models rarely differ much on total. They differ on shape. Cloud front-loads less capital and spreads cost evenly; on-premise concentrates spend into licence, hardware and periodic upgrade projects. Which is better depends on your cost of capital, your appetite for running infrastructure, and whether a regulator or a contract requires the data to stay in your building.

DimensionCloudOn-premise
Cost shapeFlat and escalating, mostly operating expenseCapital spike at year 1, then lumpy upgrade years
Version controlYou upgrade when the vendor doesYou choose, and pay for the choice
Infrastructure riskVendor's problem, priced inYours, including refresh cycles and DR testing
Exit costData extraction and a new implementationSame, but you keep running the old system while you decide
Where it winsPredictable spend, no data-centre, faster to stand upData residency mandates, heavy customisation, existing infrastructure already sunk

Cost per user per year is the comparison number

Total TCO cannot be compared between two organisations of different sizes. Cost per user per year can, at least directionally. Divide five-year TCO by users × 5, and use it to sanity-check a vendor comparison, to price a subsidiary rollout, or to test whether a per-seat charge to business units is fair.

Watch what happens when you add users. Subscription scales linearly, internal FTE and support barely move, so cost per user per year falls as you grow. That is the honest argument for consolidating a second entity onto the same instance instead of buying it a system of its own.

Using TCO in the business case

  • Present TCO and the year-five run rate. The first tells the board what it costs; the second tells them what they are committing to forever.
  • Model your escalation rate at the contractual cap, not at what you hope. If the contract has no cap, that is the finding.
  • Size the go-live number properly first with the ERP implementation cost estimator, then bring it here as the implementation input.
  • Set the whole cost against benefits in the ERP ROI calculator — TCO alone answers 'how much', never 'is it worth it'.
  • Split the seat mix before trusting the software line; full, limited and self-service users price very differently.

One line you can influence quickly is internal FTE. A large share of it is people assembling reports that the system will not produce on its own. answers those questions from your own account in plain language, shows the SuiteQL behind every figure, and runs read-only by default — so the hours come back without a report backlog or a new integration to own.

Frequently asked questions

What is included in ERP total cost of ownership?

Six lines over the appraisal period: software (subscription, or licence plus annual maintenance), implementation, internal FTE time spent running and reporting on the system, infrastructure, upgrades or release testing, and external support. Escalate every recurring line. Omitting internal FTE is the most common error, and it is often 30–40% of the total.

Is cloud ERP cheaper than on-premise?

Over five years the totals are usually closer than either vendor claims. Cloud avoids servers, database licences and DBA time but pays a subscription that escalates. On-premise concentrates cost into licence, hardware and periodic upgrade projects. The real difference is cost shape and who carries infrastructure risk, not the total.

How do you calculate ERP cost per user per year?

Divide total cost of ownership by users multiplied by the number of years. At $2,243,417 over five years for 120 users, that is $2,243,417 ÷ 600 = $3,739 per user per year. Use it to compare options and to price internal chargebacks — it falls as you add users, because support and internal FTE barely move.

How many years should an ERP TCO model cover?

Five is the standard window and roughly matches how long a mid-market ERP goes before a significant re-platform or major upgrade. Three understates on-premise because it can miss an upgrade cycle entirely. Seven flatters nothing and makes the escalation assumption do too much of the work.

What escalation rate should I use for ERP subscription costs?

Use the cap in your contract. If your agreement caps annual uplifts at 5%, model 5% rather than the 3% you were quoted verbally. If there is no cap, that absence is a finding worth raising before signature, and you should model a higher rate to show the board what an uncapped renewal can do over five years.

Why is internal FTE cost part of ERP TCO?

Because it is real money and it never stops. Someone administers users and permissions, builds and maintains reports, owns each integration, and tests every release. At mid-market scale that is commonly half an FTE to two FTE. At $95,000 loaded, 1.5 FTE is $142,500 a year — larger than most infrastructure lines and frequently larger than support.

Related calculators

ERP business case
ERP implementation cost estimator

Estimate ERP implementation cost from licence, services, data migration, integrations, training and contingency, scaled by users, sites and complexity.

ERP business case
ERP ROI calculator

Build an ERP ROI case from your own numbers: hours saved, inventory and receivables released, rework avoided. Get ROI %, payback months and 3-year NPV.

ERP business case
ERP user licence cost calculator

ERP user license cost calculator: enter your own seat rates and term to get annual cost, cost per user and a 3-year projection with uplift.

ERP business case
Reporting time savings calculator

Reporting time savings calculator — price the hours your team spends building reports, the annual cost, hours recovered and the FTE equivalent.

Read the background

ERP strategy
What does an ERP implementation cost?

What drives ERP implementation cost: scope multipliers, services-to-licence ratios, the internal time nobody budgets, and what to ask an integrator.

ERP strategy
How to build an ERP ROI business case a CFO will approve

Build an ERP ROI business case a CFO will approve: benefit categories with named owners, payback and NPV mechanics, and honest sensitivity analysis.

ERP strategy
ERP reporting tools compared: native, queries, BI and AI

ERP reporting tools compared: native reports, saved searches, a BI stack and conversational AI — with the real weaknesses of each, including ours.

All 50 ERP & finance tools

Stop calculating it by hand. Just ask your ERP.

This calculator needs you to find the inputs first. ERPray pulls them from your own ERP account and computes the answer live — with the exact query shown so you can check it.

Get early access — freeBrowse all 50 tools