Total cost of ownership (TCO)

Total cost of ownership (TCO) is the full cost of a piece of software across its life, not just the subscription or licence fee. It includes support and maintenance, implementation, training, data migration, any integration work, and the admin time to manage it.

TCO gives a fairer basis for comparing tools and for deciding what to keep at renewal, because the cheapest headline price is not always the cheapest tool to run. The gap is widest where the quoted price is smallest: a tool priced low enough to be bought without much scrutiny is often the one whose setup, integration and internal upkeep were never costed at all.

The other half of the definition is time. Two tools with identical invoices can differ by weeks of internal effort a year, and that effort is a real cost that never appears on a purchase order. It is also the part nobody has a number for, which is why a TCO comparison is usually more useful as a ranking than as a single figure: it is reliable enough to tell you which tool is dearer, and rarely precise enough to tell you by exactly how much.

Two tools are quoted for the same job. Tool A is £12,000 a year with a £9,000 one-off implementation fee and £2,500 of training in the first year. Tool B is £18,000 a year with implementation and training included. On the headline prices A is £6,000 a year cheaper, so over three years it looks like an £18,000 saving.

Add the rest and it is not. Three years of A is £36,000 plus £9,000 plus £2,500, so £47,500, against £54,000 for B. A is still cheaper, but by £6,500 rather than £18,000. Take the same two tools over two years and A is £24,000 plus £11,500, so £35,500, against £36,000 for B: a difference of £500 on a decision that looked like a £12,000 one. The break-even sits a little under two years, which means the right answer depends entirely on how long you expect to keep the tool, and that is a question the quotes never ask.

This is the practical use of TCO. It rarely reverses a decision outright, and it is not meant to. What it does is tell you how much of the apparent saving is real, which is the difference between a choice made on evidence and a choice made on the first number in the proposal.

Each record carries one contracted cost and a billing cycle, so the register holds the recurring half of TCO accurately and converts it to an annual figure. A support or maintenance agreement earns a record of its own against the same vendor, because it is a real contract with its own renewal date and notice period: given one, it gets a cancellation deadline and reminders like any other, which matters because it is usually the line that renews silently while the licence it supports is treated as settled.

A one-off cost behaves differently, and it is worth knowing how before you record one. A record on the one-off billing cycle contributes nothing to any annualised figure, because a fee paid once is not a yearly commitment. The Expenditure report shows it instead as a separate one-time total for that currency, not attributed to any vendor, owner or category, so the breakdown answers what a supplier costs you in a year rather than what you have spent on them in total. Records also count individually toward your plan allowance, so splitting one tool across three lines uses three of them.

StackTrackr does not reduce any of this to a single TCO number, and it would be a worse register if it invented one, because the largest term is usually internal time that nothing here can measure. Keep that part of the estimate in the record's notes, beside the quote and the statement of work in the document vault, so the figure and the reasoning behind it stay with the tool they describe.