Total cost of ownership (TCO) is the sum of purchase price, licences, installation, maintenance, energy, training and end-of-life replacement costs. When IT budgets are planned on this basis, options with the lowest initial price are usually revealed as the most expensive choice. A sound budget also includes a renewal schedule and a contingency allowance for unplanned failures.
- Purchase price typically accounts for less than half of three-year total cost.
- The licence metric affects hardware choice and hardware choice affects licence cost; the two decisions must be made together.
- A budget without a renewal schedule produces surprise loads when multiple warranties expire in the same year.
- The hourly cost of downtime must be calculated before redundancy investment can be justified.
- A portion of the budget must be reserved for unplanned failures and urgent needs.
What total cost of ownership covers
A server's list price is a small fraction of what that server will cost the organisation over three years. Every item below must be included when making a comparison.
- Purchase price plus shipping, import and customs costs
- Operating system and application licences and their renewal fees
- Installation, configuration and data migration labour
- Annual maintenance agreement and support fees
- Energy and cooling consumption
- User training and documentation
- End-of-life replacement and data migration cost
Hardware and licence decisions cannot be made separately
Software licensed by core count turns the hardware selection directly into a budget line. A higher-core processor may save a few thousand on the hardware side while creating a much larger difference on the licence side.
This is why a server configuration should not be finalised without knowing the licence metric of the software that will run on it. Optimising each decision independently can produce the worst total outcome.
Renewal schedule: the only tool that prevents surprises
The warranty expiry date and manufacturer end-of-support date for every device in the inventory must be entered into a calendar. Without this, several critical devices can reach end-of-support in the same year and the budget faces a large unplanned load at once.
A renewal schedule allows investment to be spread across years and creates time to negotiate. Purchases made under time pressure always cost more.
Downtime cost must be calculated before discussing redundancy
Redundant power supplies, a second internet line or a failover cluster are cost items whose necessity is only understood when compared against the cost of downtime.
The calculation is straightforward: how many people cannot work when the system is down, what is their hourly labour cost, and how much revenue or production is lost per hour of downtime? Once this number is known, a redundancy investment changes from a preference into a calculable decision.
Capital expenditure or operating expenditure
On-premises hardware is typically classified as capex; cloud and subscription models as opex. This distinction is not only accounting; it directly affects budget approval processes and cash flow.
At stable, predictable load, on-premises infrastructure is generally more economical over the long term. At variable, seasonal or rapidly growing load, a subscription model provides flexibility. Both scenarios should be modelled over three years before deciding.
The contingency allowance
No plan anticipates every failure. A sound IT budget includes an allowance set aside for unplanned failures and urgent needs.
Without this allowance, every unexpected failure forces a planned investment to be deferred; the deferred investment typically becomes the cause of the next failure.
Questions on this topic.
There is no single correct ratio; it varies widely by sector, degree of digitalisation and business model. Rather than targeting a ratio, calculating the need from the inventory and risk list and then spreading it across years produces a more reliable result.
Typically three to five years for hardware, and the contract term for software. All options being compared must use the same period; comparisons across different periods are misleading.
It depends. Cloud is typically advantageous at variable, unpredictable load; on-premises is generally more economical at stable, high load. Data volume, egress costs and regulatory requirements must all be included in a three-year total before deciding.
Investments made without a current-state and risk inventory have a high probability of going to the wrong line item. The report remains with the organisation regardless of the procurement decision and can be used with any supplier.
