Vendor-neutral guide · 8 min read

Using total cost of ownership and return on investment to steer IT decisions

Shape of the topic

A cost bar chart, a comparison table and a renewal timeline representing an investment case.A cost bar chart, a comparison table and a renewal timeline representing an investment case.
The numbers behind the decision: licence, labour, downtime and renewal, plotted against what the estate returns.

In short

Careful, considered decisions are far more likely to succeed than large risks taken on instinct, and IT purchases are no exception. Total cost of ownership sets out every direct and indirect cost of a purchase over its lifetime, while return on investment measures whether a completed project actually delivered value. Used together, these two calculations turn a major IT decision from a guess into a figure that can be tested, monitored and defended, whatever the size of the business making it.

Key takeaways

  • Total cost of ownership captures every direct and indirect cost of a purchase over its lifetime, not just the purchase price.
  • Return on investment measures whether a completed project delivered value, typically assessed around two years after implementation.
  • Large, organisation-wide software projects carry the most risk and benefit most from rigorous TCO and ROI calculations.
  • TCO variables should be monitored constantly, not calculated once and forgotten, so cost increases and strategic drift are caught early.
  • Artificial intelligence can help analyse the data behind these calculations, but the underlying figures still need human judgement and ethical care over what data is used.

Why financial acumen matters for IT purchases

Big company failures, from Google+ to Windows phones, are reminders that large sums of money spent without careful assessment can go badly wrong. Sometimes taking a risk pays off, but most of the time careful and considered decisions are far more likely to succeed. Whether a business is large or small, financial acumen sits at the root of operational success, and there is little room in any budget for genuine surprises.

Every purchase and project should be assessed, with its costs set out clearly, to determine whether it is realistic and achievable, and later whether it actually delivered results. With so much data now available from the technology already inside a workplace, using it to pin down costs, investment and planning is easier than it has ever been.

What total cost of ownership actually captures

If a business plans a major purchase, such as a new IT system, it makes sense to work out exactly what makes up that cost. Total cost of ownership, or TCO, is a mechanism for doing this. It will not be accurate to the last pound, but it gives a realistic figure to work with, to see whether a project is viable, needs to be scaled back, or could be expanded.

The key point is that TCO is not the single price of the item being considered; it is all the related expenses combined over the longer term. In the same way that buying a car means adding predicted direct costs, such as repairs, servicing and fuel, and indirect costs such as insurance, registration and parking, an IT system's TCO estimate should encompass all direct and indirect costs associated with it across its lifetime.

  • Initial purchase costs: software licences, maintenance, subscriptions and any subsequent expansion
  • Operational costs: power, broadband and administration expenses
  • Implementation costs: installation, configuration, integration and migrating data from an old system
  • Training costs: essential regardless of the time and money involved, or the solution will sit unused
  • Maintenance costs: technical support and updates, alongside cybersecurity, compliance and data protection

How return on investment differs from TCO

Alongside TCO, a return on investment calculation shows how successful, or otherwise, a project has been. Unlike TCO, ROI does not take a set time period into account by design; it provides a window into an established project's costs so a business can assess whether the activity was worth the money, and be better informed for future decisions.

Numerous ROI calculators exist online, where business figures can be entered to produce a result as a percentage, making it easy to see whether the impact of an investment was negative or positive. With ROI, the focus is on the benefit delivered, and two years after implementation is generally considered an acceptable point at which to assess whether a project has delivered on its promise.

Where these calculations matter most

TCO and ROI calculations come into their own on big projects, most often when an organisation buys new technology to use across all its sites, an outlay that adds up quickly for a business with offices in multiple countries. For substantial software projects that will be used across the whole company, there is a great deal riding on getting the assessment right.

It is not simply a matter of ticking boxes on a checklist; every business is unique and will have its own particular costs to consider. The key to being effective with TCO is to monitor its variables constantly. This avoids cost increases arriving unexpectedly, and allows leaders to pivot and make changes at the right point, while also ensuring the software purchased continues to align with strategic goals and stays on track to achieve the returns originally hoped for.

Measuring the return once a project is embedded

Once software is embedded in the business, this is the point at which the ROI calculation comes into its own. Keeping indicators simple yet meaningful highlights the most important gains a project has achieved. Have internal costs reduced as a result of implementation? Is the business providing a better service, reflected in customer numbers? Is that translating into more revenue?

These are the kinds of practical questions ROI is meant to answer, and they should be asked deliberately rather than left to impression. A project that feels successful is not the same as one that can be shown, with figures, to have delivered value.

The role of AI in TCO and ROI analysis

With the abundance of data now held within businesses, artificial intelligence can help create more advanced analyses for financial forecasting. The banking industry, for example, already uses machine learning to analyse markets, predict trends, identify fraud and enable better risk management, showing what is possible when large volumes of financial data are put to work.

AI could offer a business a tangible way to predict risks and rewards based on its own figures, mapping how projects might unfold year on year. The caveat is always ethical: business leaders must consider carefully what data they feed into these systems and whether it should be used to train them, given that this is, in essence, what is happening even as the tools do impressively clever things at speed. Using TCO and ROI calculations in strategic planning is the sensible approach, but applying human common sense alongside the figures is what makes the predictions genuinely useful.

Best-practice checklist

  1. 1. List every direct cost of the purchase

    Include software licences, maintenance, subscriptions and any planned expansion, so the initial purchase figure reflects the true outlay, not just the headline price.

  2. 2. List every indirect cost across the lifetime

    Add operational costs such as power and broadband, implementation costs such as integration and data migration, and ongoing maintenance and compliance costs.

  3. 3. Budget for training from the outset

    Include training costs in the TCO calculation, since a solution that staff cannot use effectively will not deliver the return it was purchased for.

  4. 4. Set a review point for ROI

    Around two years after implementation is generally considered a reasonable point to assess whether a project has delivered on its promise; put this date in the plan in advance.

  5. 5. Monitor TCO variables continuously

    Track costs regularly rather than only at purchase, so unexpected increases are caught early and the project can be adjusted before it drifts from its original goals.

  6. 6. Choose a small number of meaningful ROI indicators

    Pick indicators tied to real outcomes, such as reduced internal costs or improved service reflected in customer numbers, rather than tracking everything indiscriminately.

Common pitfalls

  • Treating the purchase price as the whole cost, and overlooking implementation, training and maintenance
  • Calculating TCO once at the start of a project and never revisiting it as circumstances change
  • Skipping the ROI assessment because the project felt successful, without figures to confirm it
  • Rolling out large, organisation-wide software without the scrutiny that its scale and cost warrant
  • Feeding sensitive business data into AI analysis tools without considering how that data will be used

What to measure

Metrics for TCO and ROI for IT
Total cost of ownershipSum of purchase, operational, implementation, training and maintenance costs over the asset's life
Return on investmentExpressed as a percentage; positive means the benefit exceeded the cost
ROI review pointTypically assessed around two years after implementation
Cost variance against original TCO estimateShould be monitored continuously, not just at the review point
Training completion before go-liveTrack to confirm staff can use the solution as intended

Select any column heading to sort.

Frequently asked questions

What is the difference between total cost of ownership and return on investment?
Total cost of ownership sums every direct and indirect cost of a purchase over its lifetime, such as licences, implementation, training and maintenance. Return on investment instead measures, after the fact, whether a completed project delivered value relative to what it cost, usually expressed as a percentage.
When should return on investment be measured after an IT project goes live?
Around two years after implementation is generally considered a reasonable point to assess whether a project has delivered on its promise, since that gives enough time for benefits such as reduced internal costs or improved service to show up in the figures.
What costs are often missed when calculating total cost of ownership for software?
Training costs are frequently underestimated, along with operational costs such as power and broadband, and ongoing maintenance costs covering technical support, updates, cybersecurity and compliance, all of which continue well beyond the initial purchase.
Why does TCO need to be monitored continuously rather than calculated once?
Costs and business needs shift over a project's lifetime. Monitoring the variables constantly avoids unexpected cost increases, allows leaders to pivot in good time, and keeps the software aligned with the strategic goals it was purchased to support.
Can artificial intelligence help with TCO and ROI calculations?
Yes, AI can analyse the data a business already holds to support financial forecasting and risk prediction, similar to how banking already uses machine learning for market analysis. The caveat is ethical: leaders need to consider carefully what data is fed into such systems.

Sources

Independent, standards-body and peer-reviewed material. None of these sources is affiliated with 247connect.

Putting it into practice

This guide is deliberately product-neutral. If you want to see how one implementation handles these requirements — attended and unattended access, named operator accounts, AES-256 encryption, audit logs and fixed pricing — the reference pages on this hub document 247connect in detail, and the product itself lives at 247connect.cloud.

More best-practice guides