How to plan a hardware refresh cycle for your small business

It usually happens on a Monday. The computer at the front desk, the one everybody has known was slow for a couple of years, won’t turn on. Someone drives to an electronics store at lunch and buys whatever is on the shelf. It comes with Windows Home, so it can’t be set up the way the rest of the office is, and the files that lived on the old machine’s drive are now a data recovery quote. The front desk is mostly back in business by Wednesday. Nobody budgeted for any of it, and three more computers in the office were bought the same month as the one that died.

A hardware refresh cycle keeps that week from happening. You decide ahead of time how long each kind of device stays in service, you keep track of how old everything is, and you set money aside every year so replacements happen on your schedule. None of it is complicated. Most small businesses never get around to setting it up, so every replacement arrives as a small emergency.

This is written for owners and office managers at businesses of roughly 10 to 150 people, whether or not you work with an IT provider. It’s part of a series on technology planning that also covers the IT roadmap, the annual IT budget, and the quarterly technology review.

Short answer

A hardware refresh cycle is a plan for replacing computers, servers, and network equipment on a set schedule, before they fail. Typical service lives are 3 to 4 years for laptops, 3 to 5 years for desktops (four is a common target), 5 to 7 years for servers, and 5 to 7 years for firewalls, switches, and wireless access points. Age is only the starting point, though. A device that no longer gets security updates is due for replacement no matter how well it runs, so support dates often decide more than the calendar does. To avoid one large bill every few years, replace a share of the fleet every year: on a four-year cycle, that’s about a quarter of your computers annually. Keep every device’s purchase date, warranty end, and end of support date in one inventory, look at it in each quarterly review, and flag replacements six to twelve months before they’re due. Planned replacement costs less than waiting for failures because you buy at a normal price, choose the model, move the data without a deadline, and nobody loses a day of work waiting for a new machine.

Hardware refresh cycles at a glance

Question	Short version
What is it?	A schedule for replacing devices before they fail, with an inventory behind it and money set aside each year.
What does it cover?	Laptops, desktops, servers, firewalls, switches, access points, and the gear around them: UPS batteries, docks, monitors, printers.
How long should a laptop last?	3 to 4 years. Heavy users and people who travel sit at the short end.
And a desktop?	3 to 5 years, with four a common target.
Servers and network gear?	5 to 7 years, and usually decided by the vendor’s support dates.
How do you avoid a big bill every few years?	Replace a share of the fleet every year and set money aside every month.
Lease or buy?	Either can work. It’s a cash flow decision for whoever runs your finances.
What do you need to track?	Purchase date, warranty end, end of support date, who uses it, and how it’s holding up.
How far ahead should you plan?	Six to twelve months for computers. A year or more for servers and network equipment.
What happens to the old devices?	Their data gets wiped or the drive destroyed, they come out of every management system, and the inventory gets updated.

What a hardware refresh cycle is

A refresh cycle has three parts, and each one is useless without the other two.

The schedule. A target service life for each kind of device: four years for laptops and desktops, six for servers, or whatever fits how your business uses them. The schedule also needs a few rules for exceptions, like when a device gets replaced early and when it’s allowed to run a year longer.

The inventory. A list of every device, how old it is, and when its warranty and support run out. Without this, the schedule is a guess, because you don’t know which machines it applies to this year.

The budget. Money set aside every year for the replacements the inventory says are coming. Without it, the schedule turns into a list of things you’d like to replace, and the old machines stay in service until they break.

The cycle covers the hardware your business owns and depends on: computers, servers, and network equipment, plus the things around them that wear out on their own timelines, like UPS batteries, docks, monitors, printers, and company phones. Software subscriptions are a separate list with separate dates, and managing software licenses and renewals covers that one. The two inventories end up feeding the same budget and the same quarterly review, so it helps to keep them side by side.

Why replacing hardware after it fails costs more

Waiting until something breaks feels like the cheap option, because nothing gets spent until it has to be. The costs are still there. They’re spread across places that don’t show up as a hardware line in the budget.

You pay more for the machine. An emergency purchase is whatever can be delivered this week, at whatever it costs this week. Often that’s a consumer model like the one at the front desk. Windows Home can’t be joined to Microsoft Entra ID or a company domain, so someone has to pay for an upgrade to Pro and set it up by hand. It’s also one more model in the office with its own drivers and quirks.

Someone loses their working day. Usually more than one person does. The person whose computer died can’t work, and someone else drops what they’re doing to deal with it. Setting up a replacement properly takes anywhere from an hour to most of a day, depending on how automated your setup is.

The data may not come with it. If files were saved to the old machine’s drive and not to OneDrive or a server, a dead drive turns into a recovery job, and recovery isn’t guaranteed or cheap.

The slow years cost money too. An aging computer rarely fails without warning. It gets slow first, often for a year or two. Say an old laptop costs its user ten minutes a day in slow startups, frozen calls, and restarts. Over about 230 working days, that’s close to 40 hours a year. At a loaded cost of $40 an hour, it’s around $1,500, most of the price of a new business laptop. The person using it almost never reports any of it, because by then the slowness feels normal.

Old machines generate more support work. Older devices produce a bigger share of tickets. In the example from how to run a quarterly technology review, 11 of 30 computers were more than five years old and produced over half of one quarter’s tickets.

Security gets worse every month after support ends. Once a computer, server, or firewall stops getting security updates, every new vulnerability found in it stays open. That’s also the kind of thing cyber insurance applications ask about, and a wrong answer on the form can become a problem when you file a claim.

The IT budgeting guide puts the planned cost of laptop replacement for a 30-person office at about $20,000 a year, accessories included. Replacing the same machines one emergency at a time usually costs more, because the emergency version pays all of the above on top of the hardware.

How long each kind of device should last

These are typical service lives for a small business. Use them as a starting point and adjust for how your people use their equipment.

Device	Typical service life	What usually decides it
Laptops	3 to 4 years	Battery wear, damage from travel, warranty end
Desktops	3 to 5 years (four is common)	Operating system support, performance for the role
Servers	5 to 7 years	Warranty and parts, operating system end of support
Firewalls	5 to 7 years	Firmware and security subscription support
Switches	5 to 7 years, business grade often longer	Firmware support, power capacity for phones and access points
Wireless access points	5 to 7 years	Whether they keep up with the devices connecting to them
UPS units	3 to 5 years, batteries sooner in a warm room	Battery self-test results
NAS and backup appliances	3 to 5 years	Drive age, vendor support
Monitors and docks	5 to 7 years	Usually outlast the computers they’re attached to
Printers	4 to 6 years	Parts, toner, and the cost of service calls
Company phones	2 to 3 years	Battery health and operating system updates

The network rows get a lot more detail in when to replace your business network equipment, including how vendor support windows work and how to tell whether the equipment is the problem.

Laptops and desktops

Laptops wear out faster because they get carried around. They get dropped, packed into bags, opened and closed thousands of times, and their batteries lose capacity every year they’re charged. A desktop sits under a desk in the same spot for its whole life, and the main thing that retires it is software asking more of it than it can give.

Within each type, the job makes a difference. Someone who spends the day in design software, large spreadsheets, or video calls with a dozen tabs open needs a newer machine sooner than someone who mostly uses email and a browser-based system. Many businesses set two targets: three years for power users and four or five for everyone else.

The support date usually comes first

Every device runs on three clocks:

• The warranty. When it ends, a hardware failure becomes a purchase.
• The manufacturer’s support. When the maker stops releasing firmware, driver, and security updates for the model, problems found after that date stay unfixed.
• The operating system’s support. When the operating system stops getting security updates, everything running on it is exposed, however healthy the hardware is.

The two support clocks are hard limits: once updates stop, the device is due however well it runs. A five-year-old switch that works perfectly but hasn’t had a firmware update in two years is due. So is a fast, well-kept computer that can’t run a supported version of Windows. The warranty is softer. A machine past its warranty can keep working for years, but the next failure is a purchase, not a repair.

Windows 10 and Windows Server 2016

Two of those operating system dates deserve their own mention because they catch a lot of small businesses.

Windows 10 stopped getting free security updates on October 14, 2025. Businesses can keep Windows 10 machines patched for up to three more years through Microsoft’s Extended Security Updates program, at $61 per device for the first year, $122 for the second (October 2026 to October 2027), and $244 for the third, which ends in October 2028. That’s a reasonable bridge for a machine you’ll replace within months. The program is cumulative, so a business that didn’t enroll last year pays for both years to join now, $183 per device. For a computer that’s already five or six years old, that money is usually better spent toward the replacement. And a machine that can’t move to Windows 11 at all, which mostly means it lacks a TPM 2.0 chip or has a processor older than about 2018, needs replacing either way.

Windows Server 2016 reaches the end of its extended support on January 12, 2027. If a server in your office still runs it, the decision about what replaces it should already be on the table, because a server replacement takes months, not weeks. Paid extended updates exist for servers too, but treat them as time to finish the move.

Buy hardware that will last the cycle

A refresh cycle only works if the machines you buy can still do the job in their final year.

Buy business models. The business lines from Dell, Lenovo, and HP (Latitude, ThinkPad, and EliteBook laptops, for example, and their matching desktops) stay on sale longer, come with longer warranty options, usually ship with Windows Pro, and are built to be managed centrally. Consumer models change every few months, and an office full of different consumer laptops is harder to support than the low price suggests.

Don’t buy the minimum. In 2026, a laptop meant to last four years should have at least 16GB of memory and at least a 512GB solid state drive. Memory prices rose sharply this year as AI data centers bought up supply, and PC makers raised their prices to match, so the 8GB configuration looks tempting at checkout. It’s also the one most likely to feel slow by year three.

Buy the warranty for the whole cycle. If you plan to keep laptops for four years, buy a four-year warranty with the laptop. Business models from the major manufacturers offer coverage for three, four, and sometimes five years at purchase, and adding it later usually costs more, if the manufacturer will extend it at all. For laptops that leave the office, accidental damage coverage tends to pay for itself. Matching the warranty to the cycle means a failure in year three is covered.

Standardize. Pick two or three models and stick with them for a few years: a standard laptop, a more powerful one for heavy users, and a desktop if you still use them. Fewer models means fewer surprises, faster setups, and spare parts and chargers that fit more than one machine.

Keep a spare or two. A small pool of ready-to-go machines turns a failure into a swap and covers a new hire who starts before their laptop arrives. For a 30-person office, one or two spares is usually enough.

Automate the setup if you can. If your computers are managed through Microsoft Intune with Windows Autopilot, a new laptop can ship straight to the person who’ll use it and configure itself when they sign in, as long as the seller registers it with Autopilot, which business resellers can do when you order. That shrinks the setup work for every replacement, which makes a steady refresh much cheaper to run. Setting up a new remote employee’s laptop shows what that process looks like.

How to budget for replacements without one big bill

The biggest objection to planned refresh is the size of the bill. Thirty laptops at once is a serious amount of money, and spreading the purchases out takes care of most of it.

Replace a share of the fleet every year

Divide the fleet by the length of the cycle, and that’s how many devices you replace each year. Thirty laptops on a four-year cycle means seven or eight a year. At $1,800 each, that’s about $13,500 a year, every year, with no spikes. You can buy them all in one month or a few at a time each quarter, whichever suits your cash flow. Buying a few each quarter also means each batch comes up in a quarterly review before you order it.

If everything was bought at once

Plenty of offices can’t start with a smooth schedule because the whole fleet is the same age. Maybe everyone got new laptops in the same quarter when the office moved, or when the business grew quickly, or when a previous provider replaced everything in one project. Those machines will all age out together, and waiting until they fail makes it worse, because they’ll start failing in the same few months.

You can break a bunched fleet into groups over two or three years. Take 30 laptops bought within a few months of each other in 2022, all reaching four years old now:

Year	Laptops replaced	Cost at $1,800 each	Which ones
Year 1	12	$21,600	Heavy users, the worst batteries, the machines behind the most tickets
Year 2	10	$18,000	The middle group
Year 3	8	$14,400	Light users with healthy machines and clean ticket histories
Year 4	4 or 5	About $8,000	The heavy users from year 1, now on a three-year cycle

The year 3 group runs to nearly six years, so choose it carefully: light users, machines in good condition, still on a supported version of Windows, with an extra year of warranty bought if the manufacturer offers it. The groups then come due again in roughly the same order, so the smoothing carries into the second round. Keep letting condition move a few machines a year earlier or later, and the numbers settle near seven or eight a year.

Set money aside every month

Even with a smooth schedule, some years will be heavier than others. A server comes due, the firewall and the switches line up, or a batch of machines turns out to need replacing early. A refresh reserve evens that out. Give every device class an annual amount, even in the years nothing gets bought: a $25,000 server that lasts six years is about $4,200 a year, and a firewall is a smaller number. Add those up, set aside a twelfth of the total every month, and draw on it when replacements happen. Then the money is there the year the server is due. How to plan technology spend for the year covers where that reserve sits in the annual budget and how to present it.

Buy, lease, or pay per device

There are three common ways to pay for the hardware itself:

• Buying outright. The business owns the equipment and usually depreciates it. Talk to your accountant, because tax rules such as Section 179 can change how the purchase hits your books.
• Leasing or financing. A fixed monthly payment over a set term. Match the term to your refresh cycle, and read what happens at the end of it.
• Device as a service. The manufacturer or a provider supplies the hardware, the warranty, and some of the setup and retirement work for a monthly fee per device. It’s predictable, and over the full term it can cost more than buying. Ask exactly what’s included and what happens to the devices at the end.

Which one is right depends on your cash position and how you want the cost to land in your accounts, so it’s a decision for whoever runs your finances. The annual budgeting guide explains the capital and operating expense side of that choice, and how to evaluate technology vendors helps when you’re comparing offers.

Budget for the setup work too

A replacement laptop costs more than the laptop. Someone has to set it up, move the user’s files and settings, collect the old one, and retire it properly. Add docks, monitors, and accessories when they’re due, and the shipping for remote staff. If you work with a managed IT provider, ask whether setting up replacement devices is covered by your agreement or quoted separately, so the budget has the right number in it.

How to track device ages and plan ahead

Everything above depends on knowing what you have. Most small businesses don’t, at least not in one place.

What to record for each device

Field	Why you need it
Device type, make, model, and serial number	So you can look up its warranty and support status
Who uses it, and where	So you know whose work stops if it fails, and who to plan the swap with
Purchase date	The starting point for the schedule
Warranty end date	When a failure becomes a purchase
Manufacturer end of support date	When updates stop, often before the hardware wears out
Operating system and version	Whether it’s still supported, and whether it can move to the next version
Condition notes	Battery health, repeated problems, anything the user complains about
Planned replacement quarter	Turns the inventory into a plan

Purchase date, warranty end, and end of support are the same fields the IT roadmap inventory asks for, and end of support is the one it calls out as almost nobody tracking.

Where the information comes from

If you have an IT provider, most of this already exists. The remote monitoring and management tools providers use report every managed computer’s model, serial number, operating system, and hardware specs automatically. Purchase dates usually aren’t in there, and warranty dates only are if the tool pulls them from the manufacturer. You can fill both in from invoices, or from the manufacturer’s warranty lookup, which Dell, Lenovo, and HP all offer by serial number.

Network equipment, printers, and anything in a closet often aren’t in those tools at all. Walk the office once, write down what’s there, and add it to the list.

For an office of 15 people, a spreadsheet does the job. Past about 50 devices, use the asset tracking built into your provider’s tools, or a dedicated one, so the list updates itself instead of depending on someone remembering to edit it.

Put the dates where decisions get made

The inventory only helps if someone looks at it on a schedule, so tie it to the calendar you already have:

• Every quarterly review. List every device due in the next four quarters, and decide on the ones due within two. That’s the quarterly review rule stretched for hardware, and it puts each computer in front of you six to twelve months before it’s due.
• Every September (or three to four months before your fiscal year starts). Update the full inventory before the next year’s budget is built, so next year’s replacements are in the budget from the start. The budget calendar already has this step.
• A year or more ahead for servers, firewalls, and anything that needs a project to replace.

Let condition move the date

Age sets the default, and condition adjusts it. Replace a machine early if its battery holds less than about half of its original charge, its drive is reporting errors, it keeps showing up in tickets, or the person using it changed roles and needs more power. Let a machine run longer if it’s in good shape, lightly used, still under warranty, and still supported. Write the reason down either way, so next year nobody has to wonder why one laptop is a year off schedule.

Passing machines down

When a power user gets a new laptop, their three-year-old one can go to someone who mainly uses email and a browser. That gets more value out of each purchase, and it’s a common practice. Wipe it and set it up fresh for the new user, so nothing of the previous person’s account or files comes along. Then update the inventory so the device’s history follows it. Don’t pass down a machine that’s close to the end of its support, since its new user will need a replacement within months.

Servers and network equipment need a longer runway

A laptop can be ordered and set up in a couple of weeks. Replacing a server takes far longer, because it means choosing what replaces it, ordering it, building it, moving the data and applications, testing, and scheduling the cutover around the business’s busy weeks. Three to six months is normal, so the planning starts a year out.

There’s also a bigger question to answer first: should it be replaced with another server at all? For a lot of small businesses, a server reaching the end of its life is the right moment to move what it does to the cloud, particularly when it’s mostly a file server. How much cloud migration costs helps compare the two paths. If the server does get retired, decommissioning old servers covers doing it without losing anything along the way.

Network equipment follows the same logic on a smaller scale. Firewalls usually carry a yearly security subscription, so plan the replacement for when that subscription is due, or you can end up renewing a year of protection for hardware you’re about to throw out.

Retiring old hardware

The refresh isn’t done when the new machine is running. The old one still holds your data and still has access to your systems, and it needs to come out cleanly:

1. Check the data has moved. Confirm the user’s files are in OneDrive, SharePoint, or wherever they belong, and that nothing important was saved only to the old drive.
2. Remove it from every system that knows about it. That includes Intune and Autopilot, Microsoft Entra ID, the provider’s monitoring tools, and the security software, so licenses are freed and the device can’t sign in again.
3. Wipe it or destroy the drive. Use a method that follows a recognized standard, such as NIST SP 800-88, or physical destruction for drives that held sensitive data. A factory reset by itself isn’t enough for a device that’s leaving the business.
4. Get it in writing. If a recycler or IT asset disposal company takes the hardware, ask for a certificate of destruction that lists serial numbers.
5. Update the inventory. Mark the device retired, with the date and how it was disposed of.

Healthcare businesses have their own rules for this under HIPAA’s device and media controls. Leased equipment needs the same wipe before it goes back. And a closet full of old laptops that nobody got around to recycling is a common finding in a first inventory, with each one still holding its data.

Hardware refresh planning for Tampa Bay businesses

Sequentur is headquartered in Clearwater, Florida, with a team in Tampa, and for clients around Tampa Bay the installations and swaps can happen on site. That applies whether you work with us for outsourced IT support in Clearwater or IT support in Tampa. We track hardware against each client’s inventory and flag devices six to twelve months before they’re due, and a few things about this area shape how that plan gets built.

Schedule the big swaps around hurricane season. The season runs from June 1 to November 30, and its busiest stretch is usually mid August through mid October. A server replacement, a firewall cutover, or an office-wide laptop change belongs in the spring or after the season ends. You don’t want to be halfway through moving a server when a storm closes the office.

Use the refresh to move people to laptops. When the desktops at the front desk or in accounting come due, ask whether those people should get laptops instead. A laptop can leave the building when the office is closed for a week, and a desktop can’t. Swapping the desktops at their normal replacement date costs little extra, and it makes the whole office easier to keep running during a closure. What happens to your data if your office floods covers the rest of that picture.

Put UPS batteries on the schedule. Florida leads the country in lightning density, and the corridor from Tampa Bay across to Titusville is known as Lightning Alley. Summer storms bring power flickers, surges, and short outages that a UPS is there to absorb, and its batteries wear out whether or not you notice, often in two or three years in a warm closet. Put them on the replacement schedule like everything else, and check that your network closet and any server have one.

Watch the heat in the closet. Equipment in a closet with no proper cooling runs hot through a Florida summer, and heat shortens the life of electronics. If a server or the network gear lives in a closet that’s warm to walk into, plan for the shorter end of its service life, or fix the cooling.

Dispose of drives the way Florida law expects. The state’s data security law (Florida Statutes 501.171) requires businesses to dispose of customer records containing personal information by shredding, erasing, or otherwise making that information unreadable when the records are no longer to be kept. The law covers records in any physical form, and an old laptop drive holding client records with that kind of information (Social Security or driver’s license numbers, medical or health insurance details) fits that description. The retirement steps above, with the certificate kept on file, are a good way to show it was done.

Common mistakes

1. Replacing on failure and calling it a plan. “We replace things when they break” is the absence of a refresh cycle, and it’s usually the most expensive way to own hardware.
2. Treating “it still works” as the test. A machine that works but no longer gets security updates is due. Check support dates, not just whether it turns on.
3. Buying the cheapest configuration. The money saved on memory and storage comes back as a slow machine in year three and an early replacement in year four.
4. Replacing everything at once. It feels efficient and sets up the same big bill and the same crunch again in four years.
5. Keeping the inventory in someone’s head. If that person leaves, nobody else knows it. Write it down and put it where your IT provider can see it.
6. Budgeting for the hardware but not the work. Setup, data moves, accessories, and disposal all cost time or money. Leave them out and the budget runs short every year.
7. Pushing the whole refresh back a year when money is tight. Pushing back a few low-risk machines is reasonable. Pushing back everything makes next year’s bill bigger and the emergencies more frequent.
8. Paying for extended Windows 10 updates on machines that should be replaced. It’s a fair bridge for a few months. A second or third year on an old computer is usually better spent on the replacement.
9. Replacing a server with another server without asking why. Its end of life is the best moment to ask whether the workload should move to the cloud.
10. Letting retired devices pile up. Retire each one when it’s replaced, while someone still remembers what was on it.

How this fits the rest of your IT

A refresh cycle connects to most of the planning in this series. The replacement waves go on the IT roadmap as dated items. The yearly amount and the reserve go into the annual budget. Upcoming replacements get flagged and approved in the quarterly review. And when a refresh is treated as a rolling emergency, it’s one of the clearest signs IT is reacting to events. Aligning IT strategy with business goals covers how to change that.

Somebody has to own all of this, keep the inventory current, and bring the replacements up before they’re due. In many small businesses, that’s part of what a virtual CIO does. Virtual CIO services for small business shows how it fits into a full year of planning, including a payback test with a worked example comparing a planned and an emergency server replacement. If you don’t have a provider at all, managed IT services for small business explains what the full relationship covers.

What is next in this series

The next article covers technical debt, and why it’s costing your business money: what technical debt means for a small business (not just old code, but aging infrastructure, unsupported software, workarounds that became permanent, and systems held together by manual steps), how it builds up without anyone deciding to take it on, how to work out what it costs in staff time, security risk, and lost productivity, and how to start paying it down without a single large replacement project.

How Sequentur can help

If your computers are all aging at once, or you’re not sure how old half of them are, schedule a call and we’ll help you build the inventory and a replacement plan that fits your budget. Around Tampa Bay, from Clearwater to Tampa, we can do the swaps on site.