Most businesses don't have a hardware refresh policy — they have a default, which is to replace a laptop when it stops working or when someone complains enough. It feels like the frugal choice. In practice, it usually means the business is paying for the true cost of ageing hardware anyway, just spread out invisibly across support time, lost productivity and security exposure, rather than as a predictable, budgeted expense.
Why "Until It Breaks" Is More Expensive Than It Looks
A laptop nearing the end of its useful life doesn't usually fail cleanly. It slows down. Battery life drops to an hour or two. It takes longer to boot, longer to open applications, longer to do anything. None of that generates a support ticket on its own — staff just quietly work more slowly and assume that's normal. Multiply a few minutes of daily friction across every ageing device in the business, and the productivity cost is real even though it never appears as a single number anyone budgets against.
There's a second, less visible cost: older devices are disproportionately responsible for support time. A five-year-old laptop with degraded storage and an ageing battery generates far more helpdesk tickets than a machine bought last year, simply because more things are wearing out at once. That support time has a direct cost, whether it's billed hourly or absorbed into a fixed managed IT contract.
The Security Dimension
Older hardware doesn't just run slower — it's frequently a security liability too. Devices past a certain age often can't run the latest operating system version, meaning they miss out on security features built into newer releases. Some older CPUs don't support hardware-level protections like virtualization-based security that modern Windows versions rely on for defence against certain classes of attack. And a machine held together by an ageing battery and a failing hard drive is simply more likely to fail at an inconvenient moment — which becomes a business continuity problem, not just an inconvenience for one employee.
The manufacturer warranty cliff: Most business laptops carry a 3-year warranty as standard. Once that expires, any hardware fault becomes an unbudgeted repair cost rather than a covered replacement — often at a point in the device's life when faults start becoming more frequent, not less.
What a Sensible Refresh Cycle Looks Like
There's no single right answer — it depends on device usage and business risk tolerance — but general patterns hold up well across most SMEs:
- Standard office laptops: A 3-4 year cycle is typical, aligning with standard manufacturer warranty periods and the point where performance and battery degradation start noticeably affecting productivity.
- Heavy-use or specialist devices (design, development, data-intensive roles): Often justify a shorter cycle, since the productivity cost of an underpowered machine compounds daily for these users.
- Servers and network hardware: Typically 5-7 years, though this varies significantly with usage and increasingly many SMEs are moving these workloads to the cloud rather than refreshing physical hardware at all.
Budgeting Properly: Rolling Replacement vs Big-Bang
The other common mistake is buying an entire fleet of laptops at once, which feels efficient but creates a cliff-edge problem: every device becomes due for replacement in the same year, creating a large, lumpy capital cost the business has to absorb all at once, and a fleet that ages in lockstep going forward.
A rolling replacement approach — refreshing roughly a quarter or a fifth of the fleet each year on a defined cycle — spreads the cost predictably, avoids a large one-off spend, and means the business is never running its entire fleet at end-of-life simultaneously. Many businesses achieve this through leasing or Device as a Service (DaaS) arrangements, which convert a capital cost into a predictable monthly operating expense and often bundle in support and eventual replacement.
What to Actually Track
- Device age and warranty status for every machine in the fleet, not just a general sense of "some of these are getting old"
- Support ticket volume per device, which tends to spike noticeably as hardware approaches end of life
- Operating system compatibility — whether each device can run the current and next major OS release, given Microsoft's release cadence and support timelines
- A defined budget line for hardware refresh, planned annually rather than treated as an unexpected cost when something finally fails
Questions worth asking your IT provider: How old is our device fleet on average, and how many machines are past or approaching end of warranty? How much support time is going into our oldest 20% of devices compared to the newest? Do we have a rolling replacement plan, or are we heading for a cliff-edge replacement year?
The Bottom Line
Hardware refresh isn't really a technology decision — it's a budgeting decision that happens to involve technology. A planned, rolling cycle costs more visibly on the balance sheet than "run it until it breaks," but it almost always costs less in total once lost productivity, support time and security exposure are counted honestly.