IT costs and TCO: what IT really costs, and where money leaks away
What each system costs over its whole life, and how to stop money leaking away unnoticed.
In this topic: IT and data 18
Software is easy to buy and hard to stop paying for. A team lead signs up for a tool on a company card. Ten extra licences are added in March and cannot be reduced until the contract renews. A contract rolls over because its notice date fell in the busiest month of the year. None of this feels like an IT decision, so none of it gets reviewed, and together it explains why IT costs rise every year without anyone deciding that they should.
Control starts with an overview, not a cost-cutting round: every system with its owner, users, renewal date and cost over its whole life. With that list, comparing options on total cost of ownership (TCO), managing cloud bills and allocating costs to departments become routine, in a growing company as much as in a business unit inside a group.
IT costs are more than supplier invoices: internal time, training, downtime and the cost of leaving count too. Compare options on their total cost over the same period, and give every system one owner who watches its users, contract and renewal date. Show departments what they use before you charge them for it.
- Hidden costs
- TCO
- Licences
- FinOps
- Allocation
What counts as IT costs: the visible and the hidden part
Some IT costs arrive as invoices. Others hide in salaries, project budgets and lost hours, and never carry the label IT.
Above the waterline in the figure are the costs that reach accounts payable: licences and subscriptions, hardware, cloud consumption and support contracts. Much business software is now SaaSSaaSSoftware as a service: software you use over the internet and rent per user per month or year. The supplier runs and updates it., rented rather than bought. Even these visible costs slip past the IT budget when they are paid by company card or claimed on expenses.
Below the waterline sit costs that are real but rarely booked as IT: the office manager who creates accounts, the key user who answers questions one day a week, training and the slower weeks after a change, security, an afternoon without the order system, links between systems that break after an update, and the cost of leaving.
Value each of them, even roughly: internal hours at an internal hourly rate, downtime at the output lost per hour.
Total cost of ownership: compare options over the same period
Total cost of ownership (TCO) adds up every cost of a system over the years you use it, from selection to the day the last data is safely deleted.
A quote shows the price; TCO shows what owning it costs. Buying puts a large amount up front, while a subscription never stops and grows with every user and price increase.
- 1
Fix one periodChoose the period you expect to keep the system, for example five years, and calculate every option over that period.
- 2
List every cost per yearUse the iceberg as a checklist, and value internal hours at an internal rate so they compare with invoices.
- 3
Count the way in and the way outImplementation, migration, training, running two systems for a while, and the cost of leaving. In the EU, the Data Act is set to remove the charges for switching cloud provider, including those for moving your data out, from 12 January 2027 (source: European Commission, December 2025); amendments have been proposed, so check the current rules.
- 4
Compare total, timing and riskLook at the total, at when the money goes out, and at what the numbers miss, such as outage risk and the freedom to grow or stop.
The figure shows a firm with thirty users replacing its project software: buy a licence and run it on its own server, or subscribe to the cloud version. On the software quotes, buying looks cheaper. Add server, management, backup, an upgrade, internal hours and the exit, and subscribing costs less over five years.
With an existing server that has spare capacity, the answer flips back. The toolkit has the full calculation; for the wider choice, see cloud or your own server.
Where IT money leaks away: licences, renewals and shadow IT
The leaks look much the same in most organisations. Each one is small, which is exactly why nobody notices it.
Licences that outlive their users
Someone leaves, the account closes and the licence keeps billing. Licences bought through Microsoft's partner programme, for example, can be added at any time but reduced only within seven days of being added, otherwise at renewal (source: Microsoft, August 2026).
Renewals nobody chose
Many software contracts renew automatically unless notice is given by a set date. Miss it and a new term starts, at whatever price then applies.
Shadow IT
The UK National Cyber Security Centre (NCSC) describes shadow ITShadow ITSoftware, cloud services or devices used for work without the knowledge of the people who manage IT. as unknown assets used within an organisation for business purposes (source: UK NCSC, August 2026). Typically, a free tool becomes a paid plan on someone's card, with company data that nobody looks after.
Hardware kept too long
Postponing replacement costs money too. Microsoft ended support for Windows 10 on 14 October 2025, and organisations can buy paid security updates for at most three years, at a price that doubles every year (source: Microsoft, November 2025).
Duplicate tools are the fifth leak: three video-call services, two ways to share files. The NCSC advises a simple process for staff requests and no unnecessary lockdowns of company IT (source: UK NCSC, August 2026); a quick answer to a request prevents much of both. For savings beyond IT, see cost reduction.
One owner per system: the IT cost register
One list that finance and IT both use: every system and contract, each with a named owner in the business.
The owner decides who gets access, which features are worth paying for and whether to renew. The IT department or partner keeps the system running and secure, but does not decide whether the business still needs it. Finance checks each invoice against the register.
The register shows the leaks at a glance: unused licences, a notice date that is close, a tool nobody owns. Make it the only route for buying software.
- 1
Collect a year of spendingFilter the ledger, card statements and expense claims on software, cloud, telecom, hardware and IT services.
- 2
Add licences and real useRecord licences paid and users who signed in over the last ninety days; admin portals and your IT partner can supply both.
- 3
Name the owner and the datesOne business owner per system, plus the renewal date, the notice period and the last day to give notice.
- 4
Review every quarterGo through the list with the owners, and remove licences on a leaver's last working day.
Cloud cost management with FinOps
Cloud bills follow usage, so they can grow every month without a single purchase decision. FinOps is the practice that keeps them in check.
The FinOps Foundation describes FinOps as an operational framework and cultural practice in which engineering, finance and business teams work together to get the most business value from technology and share financial accountability (source: FinOps Foundation, November 2026). Put simply: those who use the cloud see what it costs, finance understands why, and together they decide what is worth it. The foundation applies it to SaaS, licensing and data centres too (source: FinOps Foundation, November 2026).
Three of its principles matter most to a director: everyone takes ownership of their technology usage, business value drives technology decisions, and cost data should be accessible, timely and accurate (source: FinOps Foundation, November 2026). In practice: report the cost per order or per customer next to the total bill.
- A label on everything: every cloud resource carries an owner and a cost centre.
- Budgets with alerts: a budget per project, and a named person who acts on an alert.
- Switch off what sleeps: test environments rarely need to run at night or at weekends.
- Clean up: old backup snapshots, unattached storage and copies of data nobody uses.
- Right-size: capacity based on measured use, not on the first estimate.
- Commit only to the steady base: commitment discountsCommitment discountA lower cloud price in return for committing to a fixed amount of use or spend for a set period. You pay for the commitment even if you use less. pay off only for usage you are certain to keep.
Allocating IT costs to departments: showback or chargeback
When every IT cost sits on one central cost centre, nobody feels responsible for it. Allocation puts the costs where the decisions are made.
| Aspect | Showback | Chargeback |
|---|---|---|
| What it is | Each department sees the IT costs that belong to it | Those costs are charged to the department's budget |
| Budget effect | None; the costs stay central | The costs land in the department's result |
| Fits when | As a first step, and wherever awareness is the aim | Business units are steered on their own result |
| Watch out for | A report nobody reads | Disputes about the key, and buying around the rules |
The FinOps Foundation treats showback as always required, chargeback as a choice that depends on accounting policy, and neither as more mature (source: FinOps Foundation, November 2026). With one or a few easily allocated cost centres, formal chargeback may not be worth the effort (source: FinOps Foundation, November 2026).
Charge licences and department-specific systems on actual use. Split shared costs such as network, service desk and security with a simple key: proportional, fixed or an even split (source: FinOps Foundation, November 2026). Never charge security by use, or departments will save on it. Run showback for a few quarters first, and put the IT lines per owner in the business budget.
Bought servers and licences are usually capitalised, then depreciated or amortised; subscriptions are operating expenses. Because EBITDAEBITDAEarnings before interest, taxes, depreciation and amortisation: operating profit before financing costs and before writing down assets. leaves out depreciation and amortisation, moving to subscriptions lowers it even at the same total cost. Check bonus schemes and bank covenants before you switch.
How well do you control your IT costs?
Eight statements from this guide. Answer them for your own organisation and see where to start.
- 1We know our total IT costs per year, including internal time and costs paid by card.
- 2We compare IT options on their total cost over the same period, not on the first-year quote.
- 3Our business cases include the cost of leaving, such as data export and migration.
- 4Licences of people who leave are removed on their last working day.
- 5The last day to give notice on every contract is in a shared calendar.
- 6Every system has one named business owner who decides on users, features and renewal.
- 7Every cloud resource has an owner and a cost centre, and someone acts on budget alerts.
- 8Department heads see the IT costs of their department at least once a quarter.
Related guides
IT cost scan, twelve savings checks and a five-year TCO example
Below you will find a cost scan worksheet per system, twelve checks that find savings before the next renewal, and a five-year worked example of buying versus subscribing, line by line.
Frequently asked questions
How much should IT cost as a share of revenue?
What is the difference between a software licence and a subscription?
Do we need a software tool to manage licences and subscriptions?
Can we capitalise the implementation costs of a cloud system?
- FinOps Foundation: What is FinOps? (November 2026)
- FinOps Foundation: Invoicing and Chargeback capability (November 2026)
- UK NCSC: Shadow IT (August 2026)
- Microsoft Learn: Create customer subscriptions in Partner Center (August 2026)
- European Commission: Data Act explained (December 2025)
- KPMG: Cloud computing arrangements (November 2026)