Every device in a UK SME has a fifth year that nobody planned for. The warranty ended in year three. By year four, the battery barely holds a charge. By year five, the laptop may be holding the only copy of something the business needs.
Refresh decisions are often postponed until a machine fails at the worst possible moment, at the worst possible price. Mid-November is when this pattern becomes visible: budgets are being set, the refresh is the first line deferred and the last one revisited. But this is not simply a purchasing decision. It is a question of compliance, resilience and finance, and it needs a strategic answer before procurement begins.
A device moves through phases that few organisations name: new, standard, ageing, tolerated, load-bearing and finally unowned. The shift from tolerated to load-bearing often happens without anyone deciding it. The older laptop becomes the one used for despatch, payroll or a key customer process, not because it was selected for the job but because it was there.
That creates three questions for the business. Can you prove every device in use is known, supported and patched? What happens if three fail to boot on the same morning? And are you funding capability you cannot use, or paying emergency prices to restore it? A consultancy-first approach starts by answering those questions, then sets the refresh plan and the infrastructure needed to deliver it.
For compliance, a device register is more than a list of serial numbers. Cyber Essentials addresses supported software, patching and device configuration. An operating system that has passed end of support remains a finding, however smoothly the laptop appears to run. ISO 27001 assessors may sample asset registers and evidence of patching and lifecycle management. A device missing from the register is harder to manage and evidence than one recorded and clearly flagged for action.
The NCSC’s asset management guidance notes that systems grow organically and can become difficult to understand and maintain. Knowing when support will end lets an organisation plan upgrades rather than continue with vulnerable legacy kit. The NCSC also makes the point that assets no longer needed become liabilities: decommission them properly, removing data and disabling associated accounts and credentials.
The NCSC guidance on keeping devices and software up to date explains why updates matter and why support does not last indefinitely. Its advice on obsolete products is equally clear: continued use is not risk-free, and any decision to accept that risk should be revisited. A planned refresh turns an end-of-support date into a decision with an owner and a timetable, rather than a surprise discovered during an audit.
Disaster Recovery planning often concentrates on servers, cloud backups and cyber incidents. Hardware failure is more ordinary, more predictable and often less rehearsed. A warranty response time can become an untested business continuity assumption. Next-business-day support may be adequate for a general office laptop; it may not be adequate for the machine running the despatch desk when orders need to leave today.
Consider where local files actually live. Does anything important exist only on a laptop, in a downloads folder or on a desktop no one backs up? Some businesses can restore a server from the cloud but cannot put a working device in front of the right person on Monday morning. Two or three prepared spare laptops may cost less than a lost trading day, particularly when a standard build and secure access process make them usable quickly.

This is one practical reason to review the business’s core systems as well as its hardware. Dynamics 365 Business Central is browser-based, so a properly configured cloud core can make a dead laptop replaceable: the disruption may be an afternoon rather than a week. Device and access standards can be managed centrally through the tenant, rather than relying on each individual machine to carry the whole burden.
Through the Dynamics 365 Jump Start, a business can assess whether modernising its core systems supports its operational and financial priorities. Migration still needs a considered plan for data, integrations, user roles and continuity. Device management does not disappear; it changes shape. The strategic case is not that cloud solves every hardware problem, but that a replaceable endpoint can reduce dependence on one ageing machine.
The same fifth-year problem appears in a different form with IBM i. A POWER server is not a laptop, but it has a lifecycle, and it is often the least questioned box in the building precisely because it has been reliable for years. For specialist IBM i Management, the useful question is not whether the machine still works, but whether anyone could rebuild the environment if it did not.
Hardware maintenance can lapse or be quietly cancelled as a cost saving, leaving the business less prepared when a component fails. Operating system and firmware levels are tied to hardware models, so a refresh is a project rather than a purchase. Third-party software and integrations may be pinned to specific releases. A new machine may not behave like the old one until those dependencies have been understood and tested.
Testing matters. Running old and new environments in parallel can help verify applications, data and interfaces before cutover, but it requires planning, time and suitable expertise. The person who knew the hardware details may have retired, and their understanding may never have made it into system documentation. Reliability is valuable, but it should not be mistaken for a recovery plan.

Technology Expense Management is how a refresh becomes a funded plan rather than an emergency. Look for devices still being paid for under a lease that has ended, mobile connections attached to devices nobody has, software licences for machines already replaced, and extended warranties renewing automatically on kit that has been written off. Add the cost of buying replacements one at a time in a panic.
Tracing what is actually being paid for per device turns a vague concern into a number a finance director can act on. A refresh funded in a planned round is almost always cheaper than buying the same number of machines individually in a bad week. It also makes it possible to prioritise by business impact and support status, rather than by which machine has just failed loudly.
The ticket log is valuable evidence in this process. Helpdesk Support that records device age, warranty status and fault history turns a judgement call into a decision with a paper trail. A device generating repeat faults has already told you it may need replacing. Managed IT Services can provide the operational execution behind the strategy, including a standard build, data migration and a clear replacement process. Without those steps, a refresh can become a fortnight of lost productivity.
Network Solutions and Voice and Connectivity need lifecycle attention too. Switches, firewalls and desk handsets have a fifth year of their own. An unsupported handset or switch raises the same compliance and resilience question, arriving through a different door.
A practical starting point is to count devices honestly, including the ones nobody asked IT about. Record each device’s age, warranty, support status and owner. Treat anything past end of support as a dated decision, not a permanent exception. Agree a refresh round, budget and standard build, and hold a small number of spares sized to the business. Then diarise the review so the fifth year is planned six months before it arrives.
A Fractal IT Director can help bring that lifecycle view together with Cloud Solutions, Disaster Recovery and wider IT consultancy, so spending follows operational priorities instead of last-minute failure. For a broader view of the Evestaff group’s services, visit evestaff.co.uk.
A device does not become a risk on the day it fails; it becomes a risk the day it stops being supported and nobody noticed.
Join The Discussion