Technology Refresh Cycles: Plan Hardware Replacement Without Budget Shocks

Most growing companies do not have a hardware replacement plan. They have a pile of laptops bought in two or three waves, each wave timed to a hiring push or a good quarter, and each wave reaching the end of its useful life at the same moment. When that moment arrives, the CFO gets a request for a large, unbudgeted purchase with a deadline attached. Nobody was careless. Nobody was ever asked to plan it.

The fix is not complicated, and it does not require spending more. It requires turning a lumpy, reactive purchase into a predictable annual line item. This article explains how.

Why Refresh Costs Arrive as Shocks

Hardware does not fail on a schedule that matches your fiscal year. It ages quietly, and the cost of that aging stays invisible until something forces a decision. At a 25 to 200 employee company, three patterns create the shock.

Devices are bought in batches, so they expire in batches. A company that hires 30 people in a strong year buys 30 laptops that year. Three or four years later, all 30 are aging together. The cost that was spread across a growth cycle lands in a single budget cycle.

Nobody owns the replacement date. The internal IT person or the managed service provider knows which machines are old, but replacement is a budget decision, not a support decision. Without someone accountable for the multi-year plan, the default is to keep running everything until it breaks.

Vendor deadlines are set by someone else. Software and operating system support dates do not care about your budget. Microsoft ended support for Windows 10 on October 14, 2025. Organizations that had not planned for it faced a choice between replacing devices on short notice and paying for extended coverage on every machine that could not move to a supported version.

What a Forced Deadline Actually Costs

Microsoft's Extended Security Updates program for Windows 10 is a clean example, because the pricing was published and the structure is easy to model. For commercial customers, the first year of coverage was priced at $61 per device. The price doubles each year, to $122 in year two and $244 in year three, and the coverage is cumulative, so a company that starts in year two pays for year one as well.

Apply that to a 100-person company with 110 devices that cannot run a supported operating system:

Coverage Period	Cumulative Price Per Device	Total For 110 Devices
Year one only	$61	$6,710
Through year two	$183	$20,130
Through year three	$427	$46,970

That spend buys no new capability. It buys the right to keep running hardware the company already owns, and it climbs every year the replacement gets postponed. Compare that to the alternative of having already moved those devices onto a staggered schedule, where the same money would have gone toward machines that are faster, covered by warranty, and supported by the vendor.

The lesson is not specific to one operating system. Every refresh deadline has this shape. The longer a company waits, the more it pays for the privilege of waiting.

The Hidden Costs of Aging Hardware

The purchase price of a laptop is the smallest part of its lifetime cost. The rest shows up in places a budget does not label.

Support time. Older machines generate more tickets. Every ticket costs the employee's time and the support team's time.
Lost productivity. A laptop that takes four minutes to boot and stalls during video calls costs a few minutes a day per person. Multiplied across a team and a year, it becomes real money.
Warranty gaps. Once manufacturer coverage lapses, every repair is billed. Replacement parts for older models can take days to arrive, and the employee waits.
Security exposure. Devices that cannot run supported operating systems or current security features cannot meet the baseline that cyber insurers and enterprise customers increasingly ask about.
Compatibility drift. New software versions assume newer hardware. A company that holds devices too long finds that a routine software upgrade becomes a hardware project.

None of these costs require an exact figure to be useful. A leadership team that tracks its own ticket volume and repair spend by device age will see the pattern within a quarter.

The Framework: A Staggered Refresh Plan

A staggered plan replaces a fixed share of the fleet every year, so the budget stays flat and no single year carries the whole bill. Building one takes six steps.

Build a complete device inventory. Record every laptop, desktop, monitor, dock, phone, and network device, with purchase date, model, assigned user, and warranty end date. Your managed service provider or your endpoint management tool usually holds most of this already. The goal is one list that leadership can read.
Set a target lifespan by device class. Laptops used heavily by field staff or executives justify a shorter cycle than a shared conference room machine. A common planning range for business laptops is three to five years, with the right number set by how hard the devices are used and how much support they consume. Servers and network equipment follow vendor support dates more than calendar age.
Check each device against vendor support dates. Record the end-of-support date for each operating system and each hardware model. This is the date that can override your target lifespan, so it belongs in the plan from the start.
Divide the fleet into annual cohorts. If you choose a four-year cycle for 110 laptops, plan to replace about 28 devices each year. Start with the oldest machines, and let the cohorts balance over the first full cycle.
Budget the annual amount, plus a small reserve. Multiply the cohort size by a realistic fully loaded cost per device, including peripherals, setup labor, and data migration. Add a reserve of roughly five to ten percent for accidental loss, damage, and growth hires.
Review the plan quarterly. Headcount changes, vendor announcements, and failure rates all move the schedule. A short quarterly review keeps the plan accurate without turning into a project.

A Worked Example

Take a 100-person professional services firm with 110 laptops, bought in three waves over five years. At an assumed fully loaded cost of $1,200 per device, replacing everything in a single year costs $132,000.

The same fleet on a four-year staggered plan replaces about 28 devices a year, at roughly $33,600. That is the entire difference between a one-time emergency and a predictable line item. The total over four years is the same. What changes is when the money moves, and whether the CFO sees it coming.

The numbers above use assumed inputs. Substitute your own device count and cost per device, and the structure of the result stays the same: the staggered plan costs roughly one quarter as much per year as the single-wave replacement over a four-year cycle.

Beyond Laptops: What Else Belongs in the Plan

Laptops are the most visible part of the cycle, but they are not the only part. A complete plan covers:

Network equipment. Firewalls, switches, and wireless access points follow vendor end-of-support dates. Failures here take down the whole office, not one person.
Servers and storage. Even companies that have moved most workloads to the cloud often retain a small number of on-premises systems that age quietly in a closet.
Mobile devices. Phones fall out of operating system support faster than most companies track.
Peripherals and conference room equipment. These are small line items individually and a noticeable one in aggregate.
Software and licensing. Platform versions with fixed support windows belong on the same calendar as the hardware they run on.

Each category has a different natural cycle. Putting them on one calendar is what lets a leadership team see the whole year at once.

Who Should Own the Plan

A refresh plan fails when it sits between two groups that each assume the other owns it. Your internal IT staff or managed service provider can tell you what is old and what is failing. They are usually not the right people to decide how much the company should spend, or to defend that number to a CFO or a board.

That decision is technology leadership work. Someone has to connect the device inventory to the budget, weigh the cost of early replacement against the cost of waiting, and present a multi-year plan that finance can approve once and then track. At many growth-stage companies, nobody holds that responsibility. That is the gap Elevaire Systems fills through fractional IT leadership, working alongside the team that already keeps the environment running day to day.

Frequently Asked Questions

How often should a company replace employee laptops?

Many companies plan for three to five years. The right number depends on how heavily the devices are used, how much support they generate, and the vendor support dates for the operating system. Track ticket volume and repair spend by device age, and let that data set the cycle rather than a rule of thumb.

How much should a 100-person company budget for hardware refresh each year?

Divide the number of devices by the target cycle in years, then multiply by the fully loaded cost per device. A company with 110 laptops on a four-year cycle, at an assumed $1,200 per device, would budget about $33,600 a year for laptops alone, plus a reserve of five to ten percent and the cost of network and other equipment.

Is it cheaper to lease or buy hardware?

Leasing converts a large purchase into a predictable monthly payment and builds the refresh date into the contract. Buying usually costs less over the full life of a device you keep for its entire useful period. Which one fits depends on your cash position and how reliably the team would follow a purchase-based schedule. Compare the total cost over the full cycle, including end-of-lease terms, not just the monthly payment.

How does this work alongside our existing MSP or internal IT team?

Your managed service provider or internal IT staff keeps the inventory current, supports the devices, and handles deployment when new machines arrive. Fractional IT leadership adds the planning layer on top: the multi-year schedule, the budget case, and the decisions about what to replace and when. Nothing about the operational work changes.

What should we do with old devices when we replace them?

Securely wipe or destroy the storage before the device leaves your control, and keep a record that shows it was done. Many companies also resell or donate usable machines through a certified disposal vendor. Treat the process as a security task, not just a logistics one.

How do we get started?

Start with the inventory. List every device with its purchase date, model, user, and warranty end date, then sort by age. That single list shows how many devices are already past your target lifespan and how large the first-year cohort needs to be.