Computers don’t die. They get expensive quietly.

Almost no business laptop dies dramatically. It boots slower, drops a video call here and there, needs a charger by lunch, and generates one more support ticket a month, until the day it strands someone before a client meeting and suddenly becomes an emergency purchase at retail price with overnight shipping.

The fix isn’t a rigid replacement age. It’s a review habit: look hard at every machine at the three-year mark, then decide (keep, upgrade, or replace) on evidence rather than on failure.

Three years is a review date, not an expiration date

Hardware makers commonly plan business refresh cycles around three to four years, and three-to-five is a workable planning range for most office machines. But those are budgeting conventions, not deadlines. A reliable, supported three-year-old laptop doing light office work doesn’t owe anyone a replacement. What the three-year mark earns is a close look: warranty status, OS support runway, battery health, repair history, and whether the machine still fits the person using it. Write down the verdict and the next review date either way.

The first check is non-negotiable: security support

Before you think about speed, answer one question: can this machine run an operating system that still receives security updates? Once an OS falls out of support, new vulnerabilities stop getting fixed, and no endpoint product fully compensates for the unsupported layer underneath it. Security agencies on both sides of the Atlantic say the same thing: unsupported systems should be replaced or retired.

This is the case where a physically healthy computer still has to go. If the hardware can’t meet the next OS version’s requirements, its clock is running regardless of how it feels to use. Vendor extended-security programs can buy a planned transition some time; they are a bridge, not a destination. Have someone check OS support status across your fleet at least annually.

Match the machine to the work, and diagnose before you spend

An email-and-browser user can be perfectly happy on hardware that would make a CAD user miserable. Judge performance against the person’s actual workload: apps that crawl open, calls that stutter, having to close one program to open another. A slow startup once a week is an annoyance; delays all day are a payroll cost.

And don’t let “slow” automatically mean “old.” A stuffed drive, too little RAM, startup bloat, malware, overheating, or a dying storage device all mimic age, and several of those are cheap fixes. Get the cause diagnosed before approving a replacement. Just weigh any upgrade against the machine’s remaining support life: new RAM in a laptop that loses OS support next year is money down the drain.

Count reliability in dollars, not incidents

One repair doesn’t condemn a machine. A pattern does. Pull support tickets by device and add it up: repair bills, IT time, and the hours the employee couldn’t work. A repair that’s cheaper than a replacement on the invoice can still be the worse deal when the next fault is already queued up. Weight the math by role, too. A dead laptop costs more when it belongs to someone who travels, meets clients, or processes payments. A configured spare on the shelf is cheap insurance against exactly that day.

Watch the quieter factors as well: warranty expiration (review before it lapses, price the extension against the machine’s value), parts availability for your exact model, and batteries. A battery swap can genuinely extend a sound laptop’s life, though a swollen or overheating battery means stop using the device now and let someone qualified handle it.

Run it as a schedule, not a scramble

Keep a simple asset record: purchase date, model, user, warranty, OS, planned review year. Assign each machine a target replacement year and spread purchases across budget cycles instead of replacing a third of the fleet in one painful quarter. Standardize on a few models so docks and chargers interchange and spares stage quickly. Machines that no longer suit a heavy user can finish their service in a lighter role: wiped, reconfigured, re-inventoried, and only if they’re still supported and reliable. Handing a problem machine to someone else just relocates the problem.

Retire properly or it isn’t retired

Before the old machine leaves: data moved and verified, MFA and specialist apps confirmed working on the new one. Then remove the old device from management, monitoring, backups, and trusted-device lists, and reassign its licenses. And before any computer is sold, donated, or recycled, sanitize the storage properly. Deleting files and accounts does not erase data. Keep a disposal record with the serial number, date, and method. For companies with compliance obligations, which includes many of the defense-adjacent and biotech companies in North County, that record is the difference between a clean audit and an awkward one.