End-of-Life Hardware Is a QBR Conversation, Not an Emergency

Hardware refresh is the most predictable revenue an MSP has, and the most consistently mishandled. Every machine has a knowable end date. Every operating system has a published end-of-support date. None of it is a surprise.

And yet the typical refresh conversation happens at exactly the wrong moment: after a failure, in a hurry, with the client annoyed and the MSP quoting under pressure. The machine that died was seven years old and out of warranty for three of them. Everyone could have seen it coming. Nobody was counting.

The fix is unglamorous. Count the estate, attach dates, and put it on a calendar rather than in an incident.

The Four Clocks Running on Every Endpoint

Machines age along several axes at once, and they mean different things commercially.

Operating system support. The date the vendor stops shipping security updates. This is the hardest deadline and the easiest to defend, because it is published, external, and not your opinion. After it passes, the machine is a compliance and insurance problem regardless of how well it runs.

Warranty. The date the manufacturer stops fixing it. An out-of-warranty machine is not broken — it is uninsured. Failure means your labor, a scramble for parts, and downtime that is now your problem to explain.

Age. Rough, but useful. Most MSPs treat four years as the point where support cost starts exceeding replacement value, and six as the point where the argument is over.

Capacity. The quiet one. A machine with a disk that has been above 90% for months, or memory permanently at ceiling, is generating tickets that look like software problems. It is not end-of-life by date, but it is end-of-life by experience — and the ticket volume is the evidence.

The strongest refresh case combines them: nine machines that are past OS support, out of warranty, and over five years old. Three independent reasons is not a sales pitch. It is a finding.

Counting It

Your RMM already holds most of this. Pull the inventory with OS version and build, manufacturer and model, serial number, and disk and memory utilization.

Two things need care.

OS end-of-support dates are external. Your RMM knows the build number; it does not necessarily know that a specific build stopped receiving updates on a specific date. That mapping has to come from the vendor's lifecycle documentation, and it needs to be current — dates get extended, and quoting a date that has moved undermines the whole report.

Warranty status usually requires a lookup. Manufacturer serial lookups are the reliable route. If you cannot get warranty data, say so rather than guessing. A refresh list marked "warranty unknown for 12 of 40 devices" is credible. One that silently assumes out-of-warranty is not.

Then group by client and sort by how many clocks have run out on each machine.

What It Is Worth, and to Whom

Hardware refresh margin varies enormously depending on whether you resell hardware, so the revenue that matters is often not the device.

The device. Whatever your procurement margin is — for many MSPs, thin.

The labor. Imaging, migration, data transfer, installation, disposal. Frequently larger than the hardware margin and entirely yours.

The attach. A refresh is the natural moment to move a client onto a better endpoint security tier, add a backup for a machine that never had one, or standardize a fleet that has drifted across four models and three OS versions.

The avoided emergency. Harder to invoice, easy to describe: an unplanned failure on an out-of-warranty machine costs the client a day and costs you a scramble.

Present the count, not the quote: "Fourteen machines are past OS support. Nine are also out of warranty. Here is what a phased replacement over three quarters looks like."

Why This Belongs in the QBR

Refresh is the single best QBR topic available to an MSP, for a reason that has nothing to do with hardware.

Every other QBR item is either reactive (here is what broke) or promotional (here is what we could sell you). Refresh is neither. It is a shared calendar problem with a fixed external deadline that neither party controls. That makes it the easiest conversation in the meeting to have as a peer rather than a vendor.

It also budgets well. Clients cannot approve $47,000 of hardware in a QBR. They can approve a plan that spends $12,000 a quarter for four quarters, and they can take that plan to their own board. An MSP who supplies a phased plan aligned to the client's fiscal year is doing something a hardware quote can never do.

This is the core of an annual technology plan, and it is why the plan is worth building even for clients who never buy anything from it: it converts you from someone who reacts to their problems into someone who forecasts them.

How to Phase It

Rank by consequence, not age. The oldest machine is not necessarily the most urgent. A five-year-old laptop belonging to the finance director who travels matters more than a seven-year-old machine in a spare office.

Lead with the compliance-forced group. Machines past OS support have a deadline nobody can argue with, and cyber insurance questionnaires increasingly ask about unsupported operating systems directly. Start there and the rest follows more easily.

Standardize while you replace. A fleet on two models and one OS build is materially cheaper for you to support than one on nine models. Some of the refresh margin should be understood as a reduction in your own future cost.

Keep the list live. Machines age continuously. A refresh plan built once and never updated is stale within a quarter, and stale plans train clients to ignore them.

Frequently Asked Questions

The client says the old machines "work fine." How do we respond?

Do not argue about performance — you will lose, because the machine does turn on. Argue about support and insurance. "It works" and "it receives security updates" are different claims, and only the second one is on their cyber insurance renewal. Then show the ticket volume for those specific machines, which is usually higher than anyone expects.

Should we push a refresh when the client is cost-constrained?

Show the plan anyway and let them choose the pace. A client who declines a phased plan has still received a forecast, which is worth something the day a machine dies. Document the decline with a date. Circumstances — and CFOs — change.

How do we get warranty data at scale?

Manufacturer serial lookups, generally through their partner APIs or portals. If a device's warranty status cannot be determined, report it as unknown rather than assuming. Reports that guess get one wrong entry and then get disbelieved entirely.

Isn't this just a hardware sale dressed up?

Only if you present it as one. A list of machines with dates attached, phased across quarters and aligned to the client's budget cycle, is planning. A quote for fourteen laptops is a sale. The same information becomes either one depending on how it arrives — which is precisely why the counting has to be done before the meeting, not during it.

---

MSProspector is built by Marketopia, the MSP channel's growth partner since 2014. Client Upsell reads your RMM read-only and reports machines past OS end-of-life, out of warranty, over four and six years old, and under disk or memory pressure — per client, with dates. See how it works.