IT ops playbooks
Hardware refresh cycles: pick a cadence, budget it, never firefight again
By Nico De Muynck · Updated July 18, 2026
The cycle lengths that work in practice
A refresh cycle is a promise: no device in this category runs longer than N years. The right N balances three clocks, performance decay, vendor support windows, and warranty economics. Sensible defaults: laptops 4 years (battery + OS requirements), servers 5-6 years (support contracts get expensive after 5), network gear 6-7 years (but let the vendor's EOL dates override the default: a switch whose Last Date of Support lands in year 5 gets a 5-year cycle), and firewalls 5 years, driven by firmware support more than hardware.
Stagger it. The whole trick in one paragraph
Replace a fixed fraction every year instead of everything at once: on a 4-year laptop cycle, refresh 25% of laptops annually. Spending flattens into a predictable line item, the fleet's average age stays constant, deployment work spreads evenly, and a bad hardware generation only ever touches a quarter of your estate. The catch: staggering only works when you know every asset's age and EOL date. The fraction you refresh each year should be the oldest and riskiest quarter, not a random one. (That's the tracking problem, and spreadsheets handle it badly.)
Staggered refresh budget calculator
Enter your fleet, get your annual refresh count and budget per category.
| Category | # of assets | Avg. unit cost (€) | Cycle (years) | Per year | Annual budget |
|---|---|---|---|---|---|
| Total annual refresh budget | - | - | |||
Rule of thumb output, planned pricing, excluding labour and disposal. Round units up: replacing the oldest devices first is the point.
Turning the number into an approved budget
Finance teams approve flat, predictable lines and resist spiky ones, which is exactly why the staggered model wins. Present it as: current fleet value, the annual refresh figure from the calculator, and what the alternative costs (an emergency replacement runs a multiple of a planned one once downtime, expedited shipping and weekend labour are counted). Then anchor the schedule to reality: each year, the refresh list is whatever your tracker says is oldest or closest to its EOL date, not a guess. MSPs: this same table, filtered per client, is your QBR budget slide.
The one prerequisite
Every refresh strategy, staggered or not, assumes you know what you own and when each item's clock runs out. That's a one-afternoon setup: inventory the fleet (the free template structures it), look up the dates (vendor guides, OS calendar), and let something watch the calendar for you. The full method: hardware lifecycle management, the practical way.
Know which quarter of your fleet is next
Track every asset's EOL date and get warned months ahead. The refresh list writes itself.
Start free, up to 5 assetsNo credit card · no agents · set up in minutes