Request a quote
Emergency SectorsCareers About us Blog Get in touch
Table with printed charts, a laptop and a hand holding a pen

Total cost of ownership of IT: what to count, and what nearly everyone forgets

The total cost of ownership of a laptop, a server or a cloud service is almost never the price on the quote. That price is the only cost that arrives on one invoice; the rest is spread across budgets nobody puts side by side. This piece gives no figures. It gives the list of what to count, because that list is the same for every organisation.

7 min read Written by the ITproposal team
Short answer

Total cost of ownership is the sum of every cost over the whole period of use, from selection to wiping the last data. The purchase price is one line of it.

Before you count, fix the period, the unit and the service level you are comparing. Without that, you are comparing two different things.

The costs most often missing are your own time, downtime, the changeover, exceptions, renewal and exit. Note who supplied each figure and on what assumption.

What total cost of ownership is, and why the purchase price misleads

Total cost of ownership, or TCO, is the sum of all the costs a system, device or service causes over the whole period you use it: from the first round of quotes to the moment the last data has been verifiably wiped. The purchase price is one line of that, and usually the only one that appears on a single invoice.

That is what makes it misleading. The rest sits in other budgets: your own staff’s hours under payroll, power and space under facilities, the service desk with the support supplier, and downtime nowhere at all. Compare two options on purchase price alone and you are comparing the part that happens to be visible.

This piece gives no figures, deliberately. What each line costs depends on your environment, your contracts and your people; what goes into the list is the same for everyone. It is also a different question from the IT budget: the budget covers all IT in one year, TCO covers one decision over its whole life.

Set the boundaries first: period, unit and service level

Most TCO comparisons do not go wrong in the arithmetic but in what gets added up. So agree four things before you enter a single figure:

  • The period. The life you actually expect, not the depreciation period and not the contract term. Compare every option over the same period. A three-year rental next to a purchase you keep for five years tells you nothing.
  • The unit. Per seat, per user, per device or per system. Pick the unit the decision is made in, so that growth or a smaller headcount works through the same way in every option.
  • The service level. The same response times, the same backup and the same security in each option. A service with out-of-hours support next to a purchase with no support at all is not a comparison but a choice between two different things.
  • The edge of the scope. What you are deliberately leaving out, such as the building, line-of-business software or telephony, and leaving it out of every option.

Write those four at the top of the calculation. Anyone who looks at it later will see at once why the result is what it is.

The costs to count, from purchase to disposal

Walk through the life of the thing in five stages. Not every line applies to every decision, but every line you skip should be a conscious choice:

  • Acquisition. The price itself, and everything around it: the time spent comparing options, configuration and installation, delivery, rollout to desks, moving data across and clearing the packaging.
  • Operation. Licences and subscriptions, maintenance and support, hosting or floor space, power and cooling, the network capacity it needs, security software, backup and monitoring.
  • People. Support hours from your own IT staff or your supplier, service desk tickets, training, the time users need to get up to speed and the time of whoever is the internal contact.
  • Change. Upgrades, expansion, integrations with other systems, and adapting when your organisation changes: a new office, an extra team, a different way of working.
  • End of life. Wiping data with proof that it was done, disposal or take-back, any residual value if you sell, and for a service, the moment you leave: getting your data back in a usable format.

The costs that are nearly always missing

Six lines get overlooked in almost every comparison we are shown. They are hard to estimate, and that is exactly why they belong in it, even as a named line without a precise figure:

  • Your own time. The hours of your IT staff, of the colleagues who test and of the managers who choose. They appear on no invoice and with software they are often the largest line.
  • Downtime and slowness. A device near the end of its life that loses minutes every morning, or a system that is down for an afternoon. Express it in time if you cannot express it in money.
  • The changeover. The period when old and new run side by side and you pay for both, plus the time it takes to move across.
  • Exceptions. Every non-standard model or configuration costs extra support, because it needs its own procedure, its own spare parts and its own knowledge.
  • Renewal. What the contract says about price changes after the first term. A comparison that only counts the first term ends where it may get more expensive.
  • Exit. What it takes to leave: exporting data, migrating to a successor, a notice period that keeps running.

Buy, rent or as a service: comparing fairly

Between buying, renting and a service, the costs move around. They do not disappear. With rental or a service, replacement after a fault, end of life and often support are in the fee; when you buy, you carry those yourself and in return have the residual value and the freedom to keep a device longer.

So check for each line whether it is included, and who carries the risk. A fault outside warranty, a stolen laptop, a leaver handing back a device: who pays for what, and is that in the contract? A lower monthly fee that does not cover damage is not a lower TCO but a risk that has moved.

For hardware we set out the three models in buy, rent or lease. Cloud works differently, because the cost moves with usage; that is covered in keeping cloud cost under control. When you weigh cloud against your own server, look above all at the lines that stay out of sight with the server: power, space, replacement and the time of whoever looks after it.

Who supplies which figure, and what you write down

A TCO calculation is a joint document. No single team holds all the figures, and a calculation filled in by one person mainly contains that person’s lines.

  • Finance: depreciation, financing and how a rental or lease contract is accounted for.
  • IT: support hours and the number of tickets per type of device or system, ideally from the ticketing system rather than from memory.
  • Procurement: terms, notice periods and what happens at renewal.
  • Facilities: space, power and cooling.
  • The supplier: its own lines, with the assumptions behind them, and what is not in its offer.

Note the assumption behind each figure, then see which assumption reverses the outcome. Usually there are two or three: the expected life, the number of users, growth. If the choice changes when you move that assumption one step, that is the conversation to have, not the total. Keep the calculation after the decision and lay it next to reality a year later.

Where our work stops

What we do. We supply hardware, to buy and to rent, and handle support and the lifecycle through to certified wiping and disposal. For a TCO comparison we provide our own lines with the assumptions behind them, and we say which lines are not in our offer and so belong elsewhere in your calculation.

What we do not do. We are not accountants or tax advisers: how you depreciate, how a rental or lease contract appears on the balance sheet and what the tax consequences are is a conversation with your accountant. Nor do we compare our quote with another supplier’s on your behalf, because we are a party to it. And the decision itself stays with you.

Frequently asked

Questions we get about this

The five that come up most often.

What is total cost of ownership?

Total cost of ownership is the sum of all the costs a device, system or service causes over the whole period you use it. Besides the purchase, it includes operation, support, your own staff’s time, changes and end of life. The point is to compare options on what they really cost, not on what is on the quote.

What is included in the TCO of IT?

Five groups: acquisition (including selection, configuration and rollout), operation (licences, maintenance, hosting, power, security and backup), people (support, service desk, training), change (upgrades and integrations) and end of life (data wiping, disposal, residual value and leaving a service). Your own time, downtime and the changeover period are forgotten most often.

How do you calculate TCO?

First fix the period, the unit, the service level and the scope, so every option measures the same thing. Then add up the lines for each stage of the life, noting for each figure who supplied it and on what assumption. Finally, see which assumption reverses the outcome; that is what the decision is really about.

What is the difference between TCO and ROI?

TCO counts what something costs over its whole life; ROI sets what it delivers against that. You need the TCO to make an honest ROI, because a return measured against the purchase price alone always looks better than it is. For a replacement decision TCO is often enough, as both options deliver the same.

Can you calculate our TCO for us?

We provide our own lines with the assumptions behind them and say which lines are not in our offer, so your calculation is complete. You build the full calculation with your own teams, because internal hours, space and financing sit there. Depreciation and tax treatment are for your accountant, and we do not compare our quote with others on your behalf.

Shall we put our lines next to yours?

Tell us which decision you are facing and over what period. We provide our lines with the assumptions behind them, and say which lines belong elsewhere in your calculation.

Practical IT knowledge in your inbox

New guides on management, security and the workplace, written by the people doing the work. No sales talk, and you can unsubscribe in one click.

We use your address for the newsletter only. See our privacy policy.

Request a quote Call