A failed server and no warranty
A client's file server fails on a Wednesday. The engineer calls the manufacturer and learns the warranty ended a year ago. A replacement is needed in a hurry, at whatever price and lead time the distributor can manage, and the client is annoyed that nobody told them it was coming.
Across the client base, there are laptops from several generations, some well past the point where they struggle with current software, and nobody has a list. The QBR slides mention hardware refresh as a general suggestion, without saying which devices or when.
Why refreshes are reactive
The data that would allow planning (serial numbers, purchase dates, warranty end dates) is scattered, and warranty lookups are tedious to do one device at a time.
- Serial numbers are in the RMM, purchase dates in old invoices, warranties with manufacturers.
- Warranty lookups are done by hand when something breaks.
- Devices bought by the client directly never pass through your procurement.
- Refresh age rules differ by device type and client, and are not written down.
- Clients' IT budgets are set without a forward view of hardware.
What reactive refresh costs
| Reactive pattern | Effect |
|---|---|
| Server fails out of warranty | Urgent purchase, downtime and a difficult client call |
| Old laptops kept too long | More tickets, slow machines, frustrated users |
| Surprise hardware bills | Clients feel ambushed |
| Rushed orders | Less choice and less time to plan deployment |
| No forward plan | Refresh never budgeted properly |
The warranty and refresh plan we build
- Serial numbers, models and first-seen dates pulled from your RMM for every client device.
- Warranty status looked up automatically for manufacturers that provide warranty APIs, with manual entry for the rest.
- Purchase dates from your procurement records where you supplied the device.
- Refresh rules you set per device type and client tier (for example, age thresholds for laptops and servers), applied to every device.
- A forward plan per client: which devices fall out of warranty or reach refresh age in each coming quarter, with an indicative replacement.
- Alerts to the account manager for critical devices (servers, firewalls, switches) approaching warranty end, and a hardware section for QBR packs.
Refresh ages are your recommendation to clients, not a rule we impose. The plan shows the options and the client decides what to replace and when.
Budget season with a forward plan
Before each client's financial year, the account manager sends the forward plan: which laptops and which server are due for replacement over the next four quarters, and which devices fall out of warranty. The client can budget, spread replacements across quarters, or choose to extend warranties where manufacturers allow.
The file server that failed would have appeared on the plan a year ahead, with a note that its warranty was ending. Replacements become planned projects, ordered calmly and deployed out of hours.
On your side, procurement has a pipeline of expected orders, and the service desk can see which ageing devices are generating extra tickets.
The plan also handles the awkward middle cases. A laptop that is out of warranty but only three years old and working well can be marked to keep, with the reason, so it is not raised again every quarter. A server that must stay for a line-of-business application that will not run elsewhere can be flagged for an extended warranty or a spare parts plan, which is a conversation for the client and the application vendor. Operating system end-of-support dates can sit alongside warranty dates, because a device that cannot receive updates is a refresh candidate whatever its warranty says.
Because the data refreshes from the RMM, devices added during the year appear without anyone updating a spreadsheet, and retired devices drop off.
Signs your refreshes are reactive
- You find out about warranty expiry when something fails.
- Clients are surprised by hardware costs.
- Nobody has a list of devices past your refresh age.
- Warranty lookups are done one device at a time.
- QBR hardware recommendations are general rather than specific.