A business buys the cheapest available branded PCs for a round of office upgrades — the invoice looks like a win. Three years later, half the fleet has needed at least one repair, two machines were replaced outright because the specific proprietary part needed wasn't available locally, and nobody ever added up what those repairs and the associated downtime actually cost against what a different initial choice would have meant. The real cost of that purchase decision was never on the original invoice. It showed up later, spread across support tickets and lost productivity that nobody connected back to the original buying decision.
The direct answer: total cost of ownership means purchase price plus support and repair costs plus downtime cost plus resale value at the end of a typical three-to-four-year business refresh cycle — and the cheapest quote up front isn't reliably the cheapest total number once the rest of that calculation is actually run. A representative standard business workstation — Core i5-14400, 16GB RAM, 512GB storage, no dedicated GPU — prices at ₦2,090,466 at Sephora's August 2026 prices, a real number worth anchoring the rest of this calculation against rather than an abstract one.
What TCO Actually Includes
Four real components make up an honest TCO calculation, and most procurement conversations only look at the first one. Purchase price is the number on the invoice, real and immediate. Support and repair cost is what it takes to keep the machine running over its service life — parts, labour, and how quickly a fix can actually happen. Downtime cost is the productivity lost while a machine is out of service, which is real money even when nobody itemises it as such. Resale or disposal value is what the machine is worth (or costs to responsibly dispose of) at the end of its service life. Skip any of these and you're not calculating total cost — you're calculating purchase price and calling it something bigger.
None of the three factors beyond purchase price are hard to estimate — they're just easy to skip, because purchase price is the one number that arrives already calculated, on an invoice, at a moment when the decision feels finished. The other three only show up later, spread across support tickets, lost hours, and an eventual disposal or resale conversation that rarely gets connected back to the original purchasing decision that shaped it. Treating TCO as a real calculation, not just the invoice total, means deliberately pulling those later costs forward into the decision, before the purchase, not after.
A Real Example, Priced
Rather than argue this in the abstract, here's one real, sourced anchor point: a standard business workstation — Core i5-14400, a B660 motherboard, 16GB DDR5-5600, a basic air cooler, a 550W 80+ Bronze PSU, an mATX case, 512GB of PCIe 4.0 NVMe storage, and Windows 11 Pro — prices at ₦2,090,466 at Sephora's August 2026 prices. That's a real, itemised number, not a marketing estimate. Every component in it is a standard, individually-sourceable part — which is precisely what makes the repair side of the TCO calculation different from a sealed or proprietary OEM equivalent: any single failed component can be replaced on its own, at that component's real cost, rather than triggering a full-unit repair or replacement.
| TCO factor | Standard components (custom build) | Proprietary components (some OEM lines) |
|---|---|---|
| Single-component failure | Replace that part alone, at its real cost | May require a full-unit service exchange |
| Repair turnaround | Limited by part availability, often local | Can require a specific proprietary part, sometimes imported |
| Upgrade path | Standard sockets and slots, genuinely upgradeable | Often limited or locked to what shipped originally |
| End-of-life resale | Verifiable standard parts, easier to value | Harder for a buyer to verify what's actually inside |
Repairability: The Line Item Most Quotes Don't Show You
A standard-component build fails one part at a time, and one part at a time is exactly how it gets fixed — a failed RAM stick or PSU is a known-cost, known-turnaround replacement, not a mystery. Some OEM business lines use proprietary boards, connectors, or cooling assemblies specifically to simplify their own manufacturing, which can mean a single failed component requires replacing more of the machine than the failure alone would justify, or waiting on a specific part that isn't stocked locally. Neither approach is dishonest — but the cost difference is real, and it belongs in the TCO calculation, not left out because it's harder to itemise upfront than the purchase price is.
Warranty Terms, Read Carefully
Warranty length alone doesn't tell you the real support cost — what matters is what's actually covered, where it's serviced, and how long a real repair takes in practice, not on paper. A three-year warranty that requires shipping a unit overseas for a covered repair carries a real downtime cost that a shorter but locally-serviced warranty might not. Read the service-location terms as carefully as the coverage length before treating either number as the actual reflection of support cost.
Support Locality and the Standardisation Multiplier
Our custom-vs-OEM procurement guide covers the local-support-location question in more depth — it's a real input to the TCO calculation above, not a separate consideration. And if you're pricing this across a fleet rather than one machine, our fleet-standardisation guide and our bulk procurement guide cover how the support-time and resale-value factors above compound (favourably) once a fleet is standardised rather than a scattered mix of individually-sourced machines.
How to Actually Run This Calculation for Your Business
The four-factor framework above is only useful once it's applied to your specific fleet size and refresh cycle, not left as an abstract list. Start with the purchase price for your actual spec and quantity. Estimate support and repair cost using a realistic failure rate over your planned service life — even a rough estimate beats ignoring the line entirely. Estimate downtime cost using your team's actual hourly cost and a realistic repair-turnaround assumption, informed by the warranty-service-location question covered above. Estimate resale value based on how verifiable and standard the components are. Add the four together per machine, multiply by fleet size, and compare that total — not the purchase price alone — against the alternative you're weighing it against.
Common TCO Miscalculations
The most common mistake is running this calculation once, at purchase time, and never revisiting it — a TCO estimate is a planning tool, and it's worth checking against what actually happened once a refresh cycle completes, so the next calculation starts from real data rather than the same assumptions as last time.
The second is estimating downtime cost using only the repair time itself and ignoring the queue time before a repair even starts — the real gap between "machine breaks" and "machine works again" includes reporting the issue, getting it assessed, and waiting for parts, not just the hands-on repair minutes.
The third is comparing TCO across fleets of different ages as if they're the same calculation. A three-year-old fleet nearing end of life has a different resale-value and remaining-support-cost profile than a fleet purchased last month — compare like-for-like service-life stages, not just like-for-like specs.
The fourth is treating the cheapest quote and the lowest-TCO option as automatically the same choice, when the whole point of running the calculation is that they often aren't. A quote that wins on purchase price but loses badly on repairability or support locality can easily lose the overall comparison once the other three factors are added in — which only shows up if the calculation is actually run, not assumed from the invoice total.
Nigeria Context: FX Volatility Hits Repair Cost Differently
A standard component sourced locally — the kind used in the ₦2,090,466 example above — has a real, checkable current price, and a replacement part follows the same landed-cost-plus-margin logic as the original build. A proprietary part that has to be imported specifically for one OEM model carries the same FX exposure as any import, but without the option of substituting a comparable standard part if pricing or availability shifts. That's a real, structural difference in how the two paths handle currency movement over a multi-year service life, not just a one-time purchase consideration.
It's worth factoring this into the repair-cost estimate specifically, not just the original purchase decision: a repair budget planned in naira for a proprietary, import-dependent part is a budget exposed to FX movement at an unpredictable future date, while a repair budget for a standard, locally-sourced component is exposed to the same market but with a substitution option if pricing moves unfavourably. Over a three-to-four-year service life, that flexibility is worth real money, even if it never shows up as a line item on its own.
What We'd Actually Recommend
Run the full calculation — purchase price, expected support and repair cost, downtime risk, and resale value — before treating the cheapest quote as the cheapest real option. For most Nigerian businesses, standard-component builds win this calculation on repairability and support-cost predictability alone, though the honest answer depends on your specific comparison, not a rule that applies universally. Sephora Systems, a custom PC and workstation builder based in Abuja with an experience centre in Gwarimpa, builds exclusively with standard, serviceable components for exactly this reason.
Want the real TCO numbers for your specific fleet size and refresh cycle? Talk to us about your business's actual numbers rather than relying on a generic estimate.