Redeploy or replace: how to build a redeploy pool from your own fleet

Why a working laptop is worth more at a due desk than on a pallet

The resale market gives the first number. Sage Sustainable Electronics reported, in its 2026 benchmarking data, that a laptop resold through IT asset disposition averaged $125.31 in 2025, up from $93.50 the year before, and a desktop averaged $44.41. Forrester, in its 2024 study of Windows 11 Enterprise for Microsoft, used $1,200 as its hardware cost assumption per device, and both Gartner and IDC expect average PC prices to be about 17 percent higher in 2026 than in 2025. Retiring a working two-year-old laptop recovers something over a hundred dollars. Putting it on a desk that was about to receive a purchase order avoids something over a thousand.

That comparison is ours, drawn from those sources rather than stated by any of them, and it only holds when a matching seat exists. A redeploy pool is the list of devices for which it does. Building it is a data exercise, and the data is already in your tenant.

Finding the supply: healthy devices with more capacity than their users need

Check the device's health and its current user's workload. Then confirm that a due seat elsewhere needs its class. Inventory and reliability data establish condition; application-use evidence establishes workload fit. The refresh plan establishes demand.

Microsoft's resource performance report in Advanced Analytics is the strongest neutral signal. Microsoft defines CPU usage above 50 percent and RAM usage above 75 percent as spikes. The report averages the percentage of usage time spent in spikes over 14 days. A workstation with a professional GPU, 64 GB of memory and no spike in 14 days, running an office suite and a browser, is the textbook candidate. Microsoft describes the report's purpose as extending the life of devices with no performance problem and replacing underperforming devices sooner, which is exactly the two halves of a redeploy decision.

Finding the demand: due seats of the same class

The demand side is the list of due seats that need a replacement in the candidate device's class. For a Right-size seat, match against the replacement class the user needs, rather than the class of the outgoing device. A due Engineer seat whose current workstation has crashed eleven times in 90 days and cannot take Windows 11 is a replace verdict and a redeploy target. A due Engineer seat whose user runs CAD all day on a healthy five-year-old machine is a keep verdict and not a target, because moving a newer workstation there saves nothing.

Match within class and within reach. A Houston workstation redeployed to a Houston seat costs a desk visit; one shipped to Rotterdam costs freight, a reimage and a customs form. Keep site in the matching key. Matching across classes downward is a right-size move and is counted differently, as the price difference between the class bought and the class needed, so keep it on its own line.

A midlife refurbishment makes more devices eligible

Gartner, in a December 2025 note on extending hardware budgets by giving PCs a second life, states that extending laptops to five years and beyond requires careful planning, product selection and, in almost all cases, a midlife refurbishment. For a redeploy pool that usually means three parts. A battery, where Microsoft's battery health report shows capacity below 80 percent of design. A solid-state drive, where the device still boots from a hard disk; Microsoft notes such drives typically boot three to four times slower than SSDs and recommends the upgrade. And memory, where a free module slot appears in the physical memory inventory.

Price the refurbishment into the pool as a cost per device and the pool still clears by a wide margin against a new purchase at 2026 prices. Devices that fail refurbishment criteria, soldered memory at 8 GB for example, leave the pool and go to the right-size or replace cohort.

Counting it honestly: upside, never floor

A redeploy saves money when a machine has moved, been reimaged and landed on a desk that no longer needs a purchase order. Until then it is a plan. The verdict model therefore shows the redeploy pool separately from the savings floor and labels it "up to". The floor is made of deferred purchases, avoided wrong-size purchases and provisioning hours removed, which remain identified until execution and finance confirmation. The pool is counted as each move is executed, and the ledger moves the line from identified to executed to banked.

In our sample report on a fictional 7,400-device fleet, 1,185 due devices qualify for the pool, each with a due seat that needs its class, and the upside is shown as up to $1,996,700 beside a floor of $2,574,284, never added to it. If you want the two numbers for your own fleet, the initial report produces them from an export, and the readout call spends most of its time on which moves are realistic in your sites.

Running the moves without breaking the service desk

Batch by site and by quarter, reimage with Autopilot or your task sequence rather than hand-building, and give each move a ticket that references the two device identifiers and the verdict that caused it. Record the avoided purchase order number against the move once procurement confirms the order did not go out. Finance signs that record at year end, and it separates a saving someone claimed from a saving the company can show.

Keep the asset register honest as you go. The serial number from the system enclosure inventory follows the device to its new desk, the user assignment changes in Intune or in the collection membership, and the old desk gets its Knowledge Worker device logged as a right-size purchase rather than a like-for-like one. Targets are easiest to find in the Windows feature update device readiness report, where a Replace device status on a due workstation marks a seat the pool can fill. Devices leaving the pool for disposition get the data wipe and the certificate of destruction your policy requires, and the resale value, small as it is, goes on the ledger too.

Common questions