Buying for a Circular Economy

Five ways procurement, finance and HR can give employee laptops a second life.

Choosing the laptops your employees use every day is one of the largest circular-economy decisions an organization makes, though it is not always recognized as one. That is because circular thinking usually starts at the other end, with a recycling vendor, a take-back program or a donation drive. These are worthwhile steps. They are also late. Whether a device gets a second life, and what that life looks like, is settled years earlier, in the purchase decisions that chose the device and the terms it arrived on.

Whoever makes those decisions, whether a dedicated procurement team, an IT leader or a finance manager, can only optimize against the criteria the organization hands them. If the requirements, the budget and the refresh policy are all built around a three-year horizon, the buying function will deliver a three-year outcome, and deliver it well.

The five strategies below are ways for an organization to change what it asks of those responsible for buying its devices, and to give finance, HR and IT a defined part in the answer. None requires a new program, though several need a named owner or a new measure. Each is a change to a decision that is already being made.

1. Standardize the fleet before you optimize the spec

In plain terms, standardizing the fleet means buying from a short menu of approved models, for example one standard laptop, one for power users and one rugged option for field staff, rather than adding a different device for every request. How deliberately those models are chosen varies widely. Some organizations have no plan. Some have a plan that is not enforced. Others keep the plan current, and some go further and help employees adapt when it changes. Without that ongoing attention, models accumulate one reasonable exception at a time, until an organization that intended to run three is supporting fifteen. Each exception was justified in isolation. The cost of the variety as a whole often does not show up on any single report, because no single decision created it.

That cost is real and it compounds across the lifecycle. Every additional model means another set of spare parts, another configuration to maintain, more for the support team to learn and a smaller lot when the devices are eventually sold. Secondary-market buyers pay for consistency; two hundred identical units are worth more than two hundred mixed ones, because the buyer can grade, refurbish and resell them as a block. Redeployment inside the organization is easier for the same reason. A returned device that matches most of the fleet can go to almost any open role.

The goal is not the smallest possible catalog. With too few models, some roles get devices that do not fit their work, and exceptions and workarounds follow. With too many, the extra spare parts, support effort and weaker resale value described above come right back. The right catalog is the smallest set that genuinely covers the work people do, and the exception process is where that balance either holds or slips. Best practice is to treat the catalog as a managed portfolio with an owner, a review cadence and a visible cost for each addition. HR has a role here that is often missed: if device tiers are mapped to role families such as sales, engineering or field service, device choices are based on the job rather than on personal preference or who is asking, and a new role inherits a device decision that has already been made. Mergers and acquisitions deserve a specific mention, because an acquired organization arrives with its own catalog, and the choice to consolidate or coexist is a lifecycle decision with a long tail.

2. Buy for the second user, not just the first

A device specification is usually written for its first assignee. The developer’s configuration reflects the developer’s needs, the frontline worker’s reflects the frontline, and each is sensible for year one. Far fewer ask who will use the device in year three or four, and so the second life is left to chance. A related question is worth asking too: whether the first user’s needs will hold for the length of the assignment. Technology moves quickly. On-device AI features, heavier collaboration tools and new security software can all raise the demands on memory, processing and storage within a single assignment, and a device specified only for today’s work can fall short before its first user is finished with it. The aim is not to buy for every possible future, but to leave enough headroom that the device stays useful long enough to reach a second user.

Buying for the second user means deciding before the purchase which devices will go on to a second user, and specifying those devices for the harder of the two assignments. If a device will move from a corporate desk to a field location, its durability should reflect the field. If it will move from a specialist to a general role, its configuration should serve both without over-serving either. The measure that makes this visible is cost per usable year rather than cost per unit: the total cost to acquire, deploy, support, repair and retire a device, less the value it returns at exit, divided by the years it spends in productive use. It only appears in the evaluation if someone asks for it, and it is what justifies the higher upfront price on the devices that will be redeployed.

The obstacle is more often organizational than technical. A device assigned to a team tends to stay with that team, even when it sits idle, because the manager who has it faces a cost to give it up and no cost to keep it. Where devices are funded from departmental budgets, that tendency is stronger still. A central redeployment pool with agreed rules, so that a returned or idle device belongs to the organization rather than to the last team that used it, is what makes a second user possible at all. Finance is often best placed to own that decision. HR has a direct interest in it too, because the internal mobility, contractor and new-hire flows that a redeployment pool serves are HR processes, and a standing pool of ready devices changes how quickly those processes can move.

3. Score repairability like you score price

When a device fails, the organization makes a repair-or-replace decision, and the design of the device has already weighted the outcome. A modular device with accessible components and a supported parts supply is a service ticket. A sealed device with proprietary parts is far more likely to become a retirement event. The decision feels operational in the moment, but the odds were set at purchase.

The economics of that moment are worth examining. Service teams are often measured on resolution time, and replacement is usually faster than repair. Warranty terms may cover the part but not the turnaround, so a repairable device can still be replaced because the employee cannot wait. The cost of that downtime lands on the business unit, not on IT, and it often goes untracked. An organization that wants repair to win more often needs the device to be repairable, the parts to be available on a reasonable timeline and a spare pool that removes the pressure to replace. Those are three separate decisions, and only the first is about hardware.

Repairability can be assessed at sourcing with factual questions: whether components are accessible, whether parts and documentation are available and for how long, whether repairs can be performed by third parties or only through the manufacturer. Repair requirements are appearing in law in some jurisdictions, and manufacturers increasingly publish repairability information in response. Buyers do not need to wait for that. A weighted repairability criterion on the scoring sheet, agreed with IT and finance, can change which bids win.

4. Negotiate the exit at the point of entry

Of the five strategies, this one carries the most direct financial consequence. Across a large fleet, the value devices hold when they leave can be material, depending on age, model and condition at exit, and it often goes under-recovered because it has no natural owner. Finance accounts for the device, IT operates it, procurement acquires it, and HR governs the moment most devices come back when an employee leaves. Recovery depends on all four, yet ownership is often left unassigned.

The first decision that shapes recovery is how the organization owns its devices at all. Buying outright keeps residual value with the organization, along with the burden of realizing it. Leasing at fair market value, where the device is returned or bought at its then-current worth, moves the disposal obligation to the lessor. It does not move the organization’s responsibility for the data on the device, or the charges that typically apply to devices returned late, damaged or incomplete. Subscription arrangements bundle acquisition, refresh and return into one recurring cost, which simplifies the budget but generally leaves whatever the device is worth with the provider. Each model places value and obligation in different hands, and the placement should be chosen deliberately rather than inherited from the last agreement.

Within whatever model is chosen, the exit terms deserve the same attention as the price: whether trade-in credits are fixed or tied to market value at return, who collects the devices and pays for processing, and whether warranty coverage follows a device to its next user. These are ordinary negotiating points that are often left out of scope in a sourcing event. Putting them in scope is a decision the organization makes, not one the buying function can make alone.

What the exit terms are worth is largely set by two things that happen outside the purchase. The first is condition. The secondary market prices devices by grade, and grade depends on how a device was handled at collection: whether it came back with its charger, whether it was stored properly, or whether it came back at all. A device that comes back still tied to its last user, through an activation lock, a firmware password or device-management enrollment, cannot be reused or resold until those are released.

An offboarding process that treats device return as a checklist item with a named owner produces a very different recovery rate than one left to the departing employee’s manager. For remote and hybrid employees, the return itself is a logistics task: packaging, prepaid shipping, tracking and follow-up. Recovery is won or lost early, by starting the return when notice is given rather than on the last day, and by arranging shipping for the employee rather than leaving it to them. HR leaders may not think of their exit process as a line in device economics, but it is, and it is one they control.

The second is timing. Market value declines steadily with age, and keeps declining while a retired device sits in storage waiting for a decision. That gap can be one of the largest avoidable losses in the recovery chain, and it is a coordination failure rather than a market one.

Finally, the exit terms a purchase secures reflect what the purchase is measured on. When success means savings against list price, the buying decision is reasonably optimized for the front of the transaction. Trading upfront cost against value that appears three or four years later requires leadership to change the measure, or add one, and to decide that full lifecycle cost, including what comes back, is the number that matters.

5. Choose hardware that can be sanitized, not just destroyed

A device can only go to a second user, or to a buyer, if the organization is certain it carries nothing from the first. When that certainty is missing, destruction becomes the default, and a device that could have served for years becomes recyclable material instead.

Security and legal teams set the data-handling policy, and they set it, sensibly, for the worst case. The problem arises when a policy written for the most sensitive systems is applied uniformly to every device in the fleet, including many that never held regulated data. A policy that distinguishes by data classification, requiring destruction where the risk warrants it and permitting certified sanitization where it does not, keeps far more hardware in circulation without lowering the standard where the risk is real. Certified sanitization here means erasure to a recognized standard such as NIST SP 800-88, verified and documented for each device. Choosing that policy is a governance decision, and it belongs to security, legal and finance together, because it trades a modest increase in process for a material change in what the organization recovers.

Hardware plays a smaller part, but a real one. Some storage and encryption designs allow a device to be verifiably wiped and certified clean; others do not, and push the organization toward physical destruction because nothing else can be proven. The useful change is to involve the security team at sourcing rather than at retirement, so that the fleet is chosen to fit the policy the organization wants to run.

To recap: the second life starts at purchase

Many organizations do not think about an employee laptop’s second life at the point of purchase. By the time the question comes up, the answer has already been decided.

The five strategies above build that second life into the purchase. Right-size and standardize the fleet so devices can move between roles. Specify for the second user, not only the first. Score repairability alongside price. Settle the exit terms, ownership model and return process before the contract is signed. Match the hardware to a data policy that permits reuse where the risk allows it. None of these requires the buyer to learn a new skill. Each requires the organization to ask for it, and to give finance, HR, security and IT a defined part in the answer.

Every one of these strategies depends on the same thing underneath it: an accurate record of each device, from the purchase order to its final disposition. That record has to connect to the HR events that signal when a device is due back, since offboarding is where it most often goes missing. Without it, redeployment and recovery cannot be managed or proven.

A practical first step is to pull the requirements from your last two laptop purchases and count how many criteria address anything after year three. If the answer is none, you are not alone, and you have found where the second-life decision has been hiding.

If you are reviewing device requirements or planning a purchase and want to think through what a full-lifecycle view would change, we would welcome the conversation. MCPC works with organizations on these decisions, from how a fleet is specified to what it returns when it leaves.