Skip to content
Biz Alternative
Sign in

Total Cost of Ownership Beyond the Sticker

Buying guides · 9 min read ·

The price you pay is the start of the cost. A practical way to estimate total cost of ownership for software: direct, indirect, one-off and leaving costs.

Illustration: An iceberg diagram with the visible tip labelled price and a larger hidden part labelled time, training, integration, support and exit, split layout

A product's price is the easiest number to compare and the least complete. It tells you what you pay to start, and little about what you pay to keep going, to make it work, to train people to use it and one day to replace it. Total cost of ownership, often shortened to TCO, is the idea that the real cost of a product is everything you spend and give up across its life, not just the amount on the invoice.

This article describes how to estimate TCO for software in a practical, honest way, and how to use it in a comparison without false precision.

What TCO is

Wikipedia describes total cost of ownership as a financial estimate intended to help buyers and owners determine the direct and indirect costs of a product or service. It stresses that these costs are often significantly greater than the cost of acquiring the product. Originally associated with hardware and large systems, the idea applies equally to software, including small subscriptions.

TCO is an estimate, not an accounting figure. Its purpose is to make hidden costs visible so that comparisons are fairer. A product with a low price and a high TCO can be a poor bargain. A product with a higher price and a lower TCO can be the better choice.

The main categories of cost

Acquisition

What you pay to get started.

  • Licence or subscription fees, at your expected number of users and level of usage.
  • Add-ons and extras you will need.
  • Setup or onboarding fees.
  • Hardware or hosting, if applicable.
  • Taxes. UK guidance for online sellers says customers must be given the price including all taxes, so check how a vendor shows it, and whether you can recover any tax you pay.

Setup and implementation

The effort of getting it working.

  • Configuration: setting up users, permissions, workflows and templates.
  • Data migration: moving data from your old system, cleaning it and checking it.
  • Integration: connecting with other tools, building and testing.
  • Customisation: anything beyond the standard setup.

Count the time of the people involved, at a realistic rate. Include the cost of any consultants.

Training and adoption

Getting people to use it well.

  • Training time: the hours people spend learning.
  • Documentation and support materials you create.
  • Reduced productivity while people adjust.
  • Champions or administrators who help others.

Adoption is often the largest hidden cost, and the most variable.

Running

The ongoing effort of keeping it going.

  • Administration: managing users, permissions, settings and billing.
  • Maintenance: updates, backups, monitoring, if you host it yourself.
  • Support: vendor support plans, or internal help.
  • Review time: for tools that produce outputs you must check, such as automated reports or AI-generated content.
  • Compliance: privacy assessments, audits and record-keeping.

Growth

How costs change as you scale.

  • More users: per-seat charges.
  • More usage: data, transactions, storage.
  • Higher tiers: features that you will need later.
  • Overage charges beyond limits.

Risk

The expected cost of things going wrong.

  • Downtime: what an outage costs you.
  • Data loss or security incidents.
  • Vendor changes: price rises, feature removal, closure.
  • Compliance failures.

You cannot price these precisely, but you can note them and weigh them.

Exit

What it costs to leave.

  • Exporting data and checking it.
  • Migrating to a replacement.
  • Contractual penalties or notice periods.
  • Retraining.

Wikipedia lists switching costs, including uncertainty, effort of evaluation, setup costs, lost past investment and emotional discomfort. They form part of the exit cost, and also affect the cost of staying with a product that no longer suits.

How to build an estimate

Step one: choose a horizon

Pick a period that matches how long you expect to use the product, such as three years. Longer horizons give more weight to ongoing costs and growth.

Step two: describe your situation

How many users now and later? How much usage? Which features and tiers? How technical is your team? What integrations do you need?

Step three: list costs by category

Make a table with the categories above as rows and the years as columns. For each cell, estimate a cost. Use ranges where unsure.

Step four: value your time

Time is usually the largest cost. Choose a rate for people's time that reflects reality, such as salary plus overheads, or an agreed internal rate. Use the same rate for all products.

Step five: compare scenarios

Calculate low, expected and high versions, varying growth and adoption. A product that wins in all scenarios is a strong choice. One that wins only in the optimistic case is risky.

Step six: look beyond the number

Compare TCO with the value each product delivers: time saved, errors avoided, revenue gained. A product with a higher TCO may deliver much more value. Also consider things that cannot be priced, such as flexibility, reliability and fit with how your people work.

Common mistakes

Ignoring time. Counting only invoices understates cost, especially for free or open-source products.

Using the optimistic case only. Adoption is slower and setup is longer than the brochure suggests.

Forgetting growth. A cheap per-seat product can become expensive when the team doubles.

Ignoring exit. Costs of leaving are real, particularly where data is locked in.

False precision. A TCO of a precise figure suggests more certainty than you have. Round and use ranges.

Comparing different horizons. Use the same period for all.

Excluding benefits. A cost comparison alone is not a decision.

Use TCO in a comparison honestly

If you publish a comparison with TCO, be transparent.

  • State your assumptions: number of users, usage, period, rate for time.
  • Show the categories, not just the total.
  • Date it, since prices and features change.
  • Link to vendors' pricing pages rather than copying figures that will go out of date.
  • Offer a way for readers to use their own numbers, such as a simple calculator or a table to fill in.
  • Disclose relationships to any vendor.

A TCO estimate built on your own assumptions is informative. One presented as universal fact is misleading.

A worked example

A six-person consultancy compares two document tools over three years.

Tool A has a lower monthly price per user. Tool B costs more per user but includes features the team currently pays for separately.

For Tool A, they estimate: subscriptions for six users, growing to ten in year three; two add-ons they need; ten hours of setup; twelve hours of training; two hours of administration a month; extra spending on a separate signature service. For Tool B, they estimate higher subscriptions, no add-ons, fifteen hours of setup, twelve hours of training, one hour of administration a month and no separate signature service.

They value time at a standard internal rate and compute three scenarios. Tool A is cheaper in year one. By year three, with ten users and the extra services, Tool B is cheaper in the expected and high-growth scenarios, and close in the low one. They also compare exit: both can export in open formats. They note that B's vendor has a longer track record.

They choose B, record the assumptions and set a review at the end of year one to compare actual costs with the estimate.

A checklist

  • Horizon chosen
  • Situation described with ranges
  • Costs listed by category: acquisition, setup, training, running, growth, risk, exit
  • Time valued consistently
  • Low, expected and high scenarios
  • Value and unpriced factors considered
  • Assumptions stated and dated
  • Review scheduled

The pricing page here shows how this site's own paid options work, the categories and search pages help you find products to compare and the blog has more guides on buying.

A simple spreadsheet to start with

You do not need specialist software. Open a spreadsheet and make one sheet per product. Put the cost categories in the first column and the years across the top. Add a row for assumptions at the bottom, listing the number of users, the hourly rate you used for time and any growth you expected. Make a summary sheet that shows the totals for each product under low, expected and high scenarios. Share it with the people who will use the tool and ask them to challenge the numbers. A fifteen-minute review often finds a missing cost, such as a training session or a required add-on, that changes the picture.

Revisit after a year

An estimate is a prediction, and predictions improve when you check them. After a year of use, compare your actual costs with the estimate: subscriptions, hours spent on administration, extra services bought, problems encountered. Note where you were wrong and why. Use the findings in your next purchase, and in the decision about whether to keep the product. Teams that do this a few times become noticeably better at buying, because their estimates stop being guesses and become experience.

Frequently asked questions

Is TCO only for large purchases? No, but the effort should match the stakes. A simple version works for small tools.

How do I estimate training time? Ask a few users to try the product and time them, then scale.

Should I include the value of my own time for free tools? Yes. Otherwise free tools will always look cheaper than they are.

Questions and answers

What is total cost of ownership?
An estimate of all the direct and indirect costs of acquiring, running and eventually replacing a product over a chosen period.
Which costs do people most often forget?
Time spent setting up and administering, training, integration work, the cost of mistakes and the cost of moving away later.
What period should I use?
Three years is common for software, but choose a period that matches how long you expect to use the product.
Is the lowest total cost always best?
No. Cost is one criterion. Weigh it with quality, fit, risk and the value the product delivers.

Sources

Related guides

Ask us