What is Total Cost of Ownership (TCO)?

What Total Cost of Ownership Means

Two ERP proposals land on your desk. One is SAR 150,000, the other SAR 90,000. The choice looks obvious. Three years later the cheaper option may turn out to be the expensive one: servers you had to buy, an IT employee who spends half his week keeping them running, upgrades billed separately, and modifications you needed because the system never quite fitted how you work. The price on the proposal is where the cost starts, not where it ends.

Total cost of ownership (TCO) is everything an organisation pays to acquire, run and eventually retire a system or asset over its expected life. For ERP, that means purchase or subscription, implementation, operation, maintenance, support, upgrades and the cost of moving off it one day. The idea is simple. Applying it takes discipline, because many of those costs never appear on a single invoice.

TCO works for any long-lived purchase, from delivery trucks to factory machines. This article focuses on ERP because it is one of the decisions where hidden costs are most often underestimated. We cover the cost components, a five-year worked comparison of on-premise and cloud, how to estimate internal staff time, a step-by-step method, and the mistakes to avoid.

Why the Purchase Price Is Not Enough

Purchase price answers one question: how much do I pay today? TCO answers the one that matters: what will this decision cost me over the years I live with it? For ERP the gap between the two tends to be wide for four reasons.

• Long life. Companies typically run an ERP for five years or more, so modest annual costs add up to large sums.
• Costs are scattered. Some sit in the IT budget, some in salaries, some in electricity and internet bills. Nobody sees the full picture unless someone deliberately puts it together.
• Indirect costs are real. Your team's time during implementation and the productivity dip after go-live are costs even though nobody invoices you for them.
• Requirements change. In Saudi Arabia, ZATCA has been rolling out e-invoicing Phase 2 in waves since 1 January 2023. A system whose compliance updates are not covered by the subscription or maintenance contract will need a paid project every time the rules move.

The Components of ERP TCO

Acquisition and start-up

• Licences or subscription: a perpetual licence paid once, or a monthly or annual fee per user or per module.
• Infrastructure: servers, operating systems, database licences, network equipment, backup, perhaps a server room. Largely disappears with cloud ERP.
• Implementation: requirements, configuration, chart of accounts, users and permissions.
• Data migration: cleaning and loading items, customers, suppliers and opening balances.
• Customization and integration: custom reports, approval workflows, links to banks, government platforms or an online store.
• Initial training: by role.

Ongoing operation

• Maintenance and support: for on-premise, an annual contract usually priced as a percentage of licence value; for cloud, normally included in the subscription.
• IT staff time: server administration, patching, backups, security.
• Hosting and power: electricity, cooling, space, or data centre fees.
• Security and compliance: protection software, penetration tests, and the obligations of the Personal Data Protection Law, in force since September 2023.
• Connectivity: reliable internet, ideally with a backup line, especially for cloud systems.
• Ongoing training: for new hires and new modules.

Evolution and exit

• Version upgrades: on-premise upgrades can be projects in their own right.
• Hardware refresh: servers usually need replacing after several years.
• Growth: more users, branches or modules.
• Exit: what it takes to extract your data and move if you change systems later.

Hidden Costs Most Business Cases Miss

• Internal team time. If your senior accountant spends 40% of three months in workshops and testing, who does the day job? Either overtime or deferred work.
• The post-go-live dip. The first weeks are slower while people learn new screens and procedures.
• Workarounds. Any process the system does not cover goes back to spreadsheets, and double entry and errors come with it.
• Unplanned downtime. A server failure that stops invoicing for a day has a direct cost in sales and collections.
• Slow decisions. Reports that arrive late mean purchasing and pricing decisions made on stale data.

Worked Example: Five-Year TCO, On-Premise vs. Cloud

This example is entirely hypothetical. The figures illustrate the method and are not any vendor's prices. A Saudi trading and distribution company with 30 users compares a perpetual-licence on-premise system with a cloud subscription. Amounts are in SAR, excluding VAT.

Three lessons stand out:

• Licences are not the biggest line. On-premise IT time alone is three times the licence cost. It is often left out because "we pay that salary anyway".
• Year one misleads. A SAR 90,000 annual subscription can look expensive next to a maintenance contract. Only the five-year view shows the real comparison.
• The answer depends on assumptions. If the on-premise system needed only 10% of an IT person's time, its total would fall to about SAR 603,000 and it would win. A 5% annual subscription increase adds about SAR 47,000 to the cloud option. Run the numbers with your own inputs.

On VAT at 15%: a VAT-registered business can normally recover input tax on these purchases, subject to the usual conditions, so compare options before VAT. Still include it in cash planning, because you pay it before you recover it. For a fuller discussion of the two deployment models, read our article on cloud vs. on-premise ERP in Saudi Arabia.

Putting a Number on Internal Time

This is the line most often missing, so here is a hypothetical calculation for a four-month implementation:

"Fully loaded" means salary plus allowances, GOSI contributions and other benefits. None of this appears in a vendor proposal, yet here it rivals the external implementation fee. If the project slips by two months, it rises by half. That is why a vendor with a clear method and a firm timeline can save real money even at a slightly higher price.

How to Calculate TCO for Your Business

1. Fix the period. Five years is common and sensible for ERP. Use the same period for every option.
2. Ask for itemised proposals. Licences or subscription separate from implementation, training, support and customization, with a clear list of what is included and what is extra.
3. Ask about increases. Does the subscription or maintenance fee rise each year, and by how much? Are future ZATCA compliance updates covered?
4. Estimate internal costs. Hours per team member multiplied by fully loaded hourly cost.
5. Be honest about infrastructure. Servers, refresh, power, backup, security and IT time.
6. Add contingency. 10% to 15% on implementation and customization is reasonable, because requirements sharpen during the project.
7. Test sensitivity. Change key assumptions such as users and annual increases and see whether the winner changes.
8. Set it against the return. TCO is half the equation. Our guide to ERP ROI covers the other half.

Questions to Ask Every Vendor

1. What exactly does the subscription or maintenance fee include: support, updates, backups, hosting?
2. What is the annual price increase, and is it capped in the contract?
3. Are ZATCA compliance updates included at no extra charge?
4. How many training hours are included, and what does extra training cost?
5. How are custom reports and changes priced after go-live?
6. What does it cost to add a user, a branch or a module?
7. How do I export all my data if I leave, and in what format?

Ways to Reduce TCO Without Cutting Corners

• Start with the core. Accounting, invoicing, inventory, sales and purchasing first; add modules once things are stable.
• Match the pricing model to your size. Per-user pricing usually suits small firms; a flat fee per module with unlimited users can be cheaper above roughly 50 users.
• Customize less. Every bespoke change adds implementation cost and can complicate upgrades. Ask first whether the process can change instead of the software.
• Invest in training. Well-trained users make fewer errors, build fewer workarounds and raise fewer support tickets.
• Clean data before migration. Moving messy data just moves the problem and multiplies the clean-up cost.
• Avoid known implementation traps. Vague scope, no decision owner, rushed go-live. Our ERP implementation guide explains how to avoid them.

TCO Beyond Software

The same logic works for any long-lived asset. Take a hypothetical delivery truck: Truck A costs SAR 280,000 and Truck B SAR 320,000. B saves SAR 9,000 a year in fuel and SAR 4,000 in maintenance, and is expected to resell for SAR 20,000 more after five years. Over five years B comes out about SAR 45,000 cheaper despite costing SAR 40,000 more up front. The precondition is real operating data, meaning actual maintenance cost, consumption and breakdowns per asset, recorded somewhere you can retrieve it.

Review TCO After Go-Live

Companies that get value from TCO revisit their estimate after a year of operation. Compare actual spend with each line of the original model, list costs you did not anticipate, check whether every licence is actually used, identify processes still running outside the system, and estimate how many hours a week staff spend supporting colleagues. Half a day once a year is enough, and the output should be concrete: drop unused licences, schedule extra training, bring a spreadsheet process into the system.

Common TCO Mistakes

• Comparing only year-one cash between a perpetual licence and an annual subscription.
• Leaving out existing staff salaries on the grounds that they are paid anyway, even though their time is pulled from other work.
• Forgetting server replacement and version upgrades for on-premise systems.
• Assuming customization will be minor without first mapping how the business actually works.
• Ignoring exit cost and how hard it may be to get your data out if you switch later.
• Using the vendor's own TCO calculator without checking which costs it leaves out.

Each of these errors tends to favour the option with the lowest headline price. A model that avoids them will not always pick the more expensive proposal, but it will tell you honestly what you are signing up for.

Tranquil and Cost Transparency

Tranquil is a cloud ERP, so there are no servers to buy or infrastructure to run. It is offered on two pricing models: per user for smaller firms, or a flat fee per module with unlimited users for organisations above 50 users. The team provides customization and certified training with 30 days of post-training support, and quotes within 24 hours. See the pricing page or contact the team for an itemised proposal you can drop straight into your TCO model.

Frequently Asked Questions

What is the difference between TCO and purchase price?

Purchase price is what you pay to acquire the system. TCO adds every cost of implementing, running, supporting, upgrading and eventually exiting it over its life.

What period should I use for ERP TCO?

Five years is the usual choice. It covers a hardware refresh cycle and several upgrades and allows a fair comparison between perpetual licences and subscriptions.

Is cloud ERP always cheaper?

No. It depends on company size, IT staff cost, user count and subscription increases. It does usually cut infrastructure and internal IT costs substantially.

Should TCO include VAT?

For comparing options, use pre-VAT figures if you can recover input tax. For cash planning, add the 15% VAT because you pay it before you recover it.

How do I estimate my team's implementation time?

Estimate hours per person over the project, multiply by fully loaded hourly cost including allowances and GOSI, and add any overtime or temporary staff needed to cover their usual work.