Total Cost of Ownership
Total Cost of Ownership isn't the sticker price—it's everything you pay, plus everything you give up. Most people optimise for the wrong number.
- TCO = upfront + ongoing + hidden (switching costs, lock-in, opportunity cost)
- Sticker price is usually the smallest piece of the pie
- The best "cheap" option often costs more over 3–5 years
- If you can't enumerate the costs, you can't make a defensible decision
Real-world example
The $50 inkjet vs. the $250 laser printer
You need a printer for home. The inkjet is cheap upfront. The laser costs five times more. Which is the better deal?
- Inkjet: $50 upfront. Ink cartridges: ~$60 every 2–3 months. Year 1 TCO: ~$350+ and climbing.
- Laser: $250 upfront. Toner: ~$80 once a year. Year 1 TCO: ~$330. Year 2: still ~$80. Year 3: same.
- By year 2, the "cheap" inkjet has cost more. By year 3, it has cost nearly twice as much.
The sticker price lied. TCO told the truth.
Total Cost of Ownership is the full cost of acquiring, operating, and retiring a solution—including money, time, and risk.
- Upfront capex: obvious (sticker price, implementation)
- Ongoing opex: licensing, maintenance, support, training—sometimes visible
- Hidden costs: vendor lock-in, switching cost when you outgrow it, integration tax, opportunity cost of build vs. buy
- Switching cost: how much does it cost to leave?
- Lock-in: can you take your data and workflows elsewhere?
- Integration tax: does it plug into your stack, or do you build custom glue?
- Opportunity cost: if you build instead of buy, what do you not build?
- Cost of wrong assumptions: a "cheap" tool that breaks at scale forces a rebuild—and that rebuild cost counts.
Stop optimising for price. Optimise for TCO over your actual horizon (3–5 years is common).
- List every cost bucket
- Assign rough numbers
- Stress-test the assumptions
The goal isn't precision—it's clarity. When you can enumerate the costs, you can defend the decision.
- Treating capex and opex differently without a discount rate
- Ignoring support and training
- Assuming "we can always switch later" without sizing the switch
- Confusing "cheapest" with "best value"
- Not writing it down—if the model lives in someone's head, it's not a model
See it in action
Want to build a TCO model for your decision?