When to replace laptops and IT hardware in an SME — without the marketing fluff

· 7 min read · SilverData team

"This laptop still works" is the most expensive sentence in a Polish SME. Not because the hardware is bad, but because nobody counts what its slow death actually costs. An IT refresh cycle isn't a luxury or a whim — it's simple maths: hours lost to booting, dropped calls on Teams, a helpdesk you burn instead of working.

In most SMEs, the decision to replace a laptop only comes when the hardware physically dies — the drive fails, the keyboard crumbles, someone spills coffee on it. That's a reaction, not a policy. The result is always the same: you buy 8 laptops in a panic, pick whatever the reseller has on the shelf, pay more and end up with hardware that will fall into the same cycle again in four years.

This piece is about how to get out of that loop. Without vendor marketing, without paranoia — just common sense.

Why an 8-year-old laptop costs more than a new one

On one project we ran a hardware inventory for a 28-person law firm near Warsaw. Average laptop age: 6.5 years. Rule of thumb — if the average is 6, part of the fleet is 8-9 years old. And it was.

We measured three things: boot time, time to open a typical file (for them, a client dossier in a 30 MB PDF) and the number of helpdesk tickets per laptop over the last six months. The results: average boot 4 minutes 20 seconds (a new laptop does it in 25 seconds), file open 45 seconds vs. 3 seconds, 4.2 helpdesk tickets on the old hardware vs. 0.3 on the newer.

Do the maths with us. A lawyer boots twice a day (morning and after lunch). That's 8 minutes. Opens 20 files a day. Another 14 minutes. That's 22 minutes a day — roughly 1 hour 50 minutes a week — staring at a spinner. Across 28 people, 51 hours a week. Monthly, 200+ hours of waiting. Lawyer billing rate — you can do the rest.

Replacing 22 laptops (the oldest of the fleet) cost them around 130,000 PLN net. Payback calculated on pure recovered time: four months. Before counting helpdesk tickets, lost meetings and frustration.

When to actually replace

Rule of thumb we recommend for 10-50 person companies:

A 4-year cycle means, at 30 people, you replace 7-8 laptops a year on average. That's a budget you can plan and pull into a P&L forecast, instead of fighting it as an emergency.

What to do with the old hardware

An old laptop isn't worthless. It still has 12-24 months of sensible life ahead — if it lands in the right seat:

What NOT to do: hand old laptops down to employees "as a personal device" without formally removing them from the register and wiping the drive. That laptop still carries your company policy and cached credentials. Two years later it can come back to you as an attack vector — we've seen it happen.

Standardisation isn't provincialism

The second mistake, after too long a lifecycle, is the model zoo. A 25-person company ends up with 14 different laptop models, because each department bought "whatever was in stock". The result: every helpdesk ticket starts with "what model do you have", the helpdesk maintains drivers for 14 models, and when someone leaves there's nowhere to reassign the hardware.

Sensible standardisation for a 10-50 person company means 2-3 models in the portfolio:

The rest — desktops, external monitors, headsets, docks — also from a short list. Not to limit people's choice, but so the helpdesk's first question isn't "what ports does yours have".

Standard image and onboarding

If you already have hardware standardisation, the next step is a standard configuration image. On Windows 11, the simplest path is Windows Autopilot + Intune — the employee gets a new laptop in the box, signs in with their company account and the machine configures itself. Apps, security policies, printers, everything.

Without it, onboarding one employee is 3-4 hours of IT work — internal or yours. With Autopilot, 30 minutes, of which 25 are the install running in the background while the person makes coffee and reads their welcome email. At a churn of 5-8 people a year, that's 20-30 hours of your time saved annually.

How not to over-buy

The most common mistake in the other direction: the company hears "we need a refresh", writes a list of 25 new laptops and sends the order. Along the way someone adds "and while we're at it, let's replace the monitors, docks and the server". The bill balloons to 400k, the decision derails, the project stalls.

The sensible approach: replace in tranches. 30% of the fleet a year. Year 1 — oldest laptops plus most critical seats. Year 2 — next 30%. Years 3-4 — the rest. In four years you're on a steady refresh cycle, the budget is predictable, no one chokes on a one-off CAPEX.

Add a simple hardware register — purchase date, model, user, planned replacement date. Excel is fine (RMM or a dedicated tool is better). Without one, in three years you'll again not know what you have or what to replace.

Signals it's time to act

If any of these are happening at your company, the refresh is already overdue:

Each of these signals is money quietly leaking out. It's not visible on the P&L, because there's no line item called "time lost on old hardware". But it's there.

If you don't know where to start — instead of guessing, do an inventory, measure a few things (boot, file open, ticket count) and count. We can help with that audit in a week — without selling you any hardware along the way.

A hardware refresh cycle isn't a luxury spend — it's the cost of not replacing, which simply doesn't show up in the P&L.

← Back to blog