Company PC Replacement: Refresh Cycle & Lease vs Buy (2026)

Replacing company PCs means swapping out work machines on a planned cycle rather than waiting for them to fail. In practice the target is four to five years, which is roughly when warranties expire, failure rates start climbing, and OS support windows close. Per-machine cost is typically ¥100,000–180,000 for the hardware plus setup labour, so refreshing ten machines often lands around ¥1.5M–2.2M all-in. The companies that "buy when it breaks" end up paying more, because downtime and emergency purchases cost more than the hardware ever did.

PCs fail on a curve. Battery wear, storage wear, and clogged fans compound, so from year four or five onward you start seeing slow boots and random shutdowns — and if the fleet was bought all at once, those failures arrive all at once too.

The problem is how the cost shows up. Reactive replacement carries three hidden charges:

- Downtime: with no spare machine, that employee simply cannot work until the replacement is ready. One person idle for one day already costs tens of thousands of yen in loaded labour
- Emergency premium: you buy from whatever is in stock, compromising on both spec and price
- Data recovery: if the storage is what failed and there is no backup, recovery runs from tens of thousands into hundreds of thousands of yen

How to triage a machine that suddenly stops working is covered in PC won't boot or connect — a triage guide, but a planned refresh cycle reduces how often you need that guide at all.

There is no need to standardise on a single number. Shorten the cycle for demanding roles and lengthen it for light ones — you keep the total down while replacing the machines that actually cause trouble first.

OS and software end-of-life dates also drive the cycle. The risk of running unsupported software in production is covered in Preparing for end-of-life.

Even before a machine hits its cycle, any of the following justifies moving it forward. Equally, a five-year-old PC showing none of them does not need to be thrown out in a hurry.

- Boot and app launch times are long enough that staff treat waiting as normal
- Battery does not last half a day, or is visibly swollen (swelling means stop using it immediately)
- Fans run flat out constantly and performance drops (thermal throttling)
- Storage is permanently near-full and staff delete files to get work done
- Manufacturer or extended warranty has expired
- OS or line-of-business software support ends within a year
- The machine falls below the required spec of software you actually use, and behaves unreliably

Hardware price varies with spec, but business laptops generally fall into these bands. Figures are 2026 ballparks and move with exchange rates, component prices, and vendor promotions.

The add-ons are what people miss. Pick the cheaper machine on hardware alone and the totals can invert once you add docks, extended warranty, setup, and disposal of the old unit. Compare on total cost per machine — hardware plus peripherals plus labour plus disposal.

There are four main procurement routes. Which one is right depends on your cash flow and on how much of the operational work you can absorb in-house.

For companies with no IT staff, a monthly model that bundles setup, fault handling, and collection/disposal is often the practical choice. But vague scope invites later charges, so confirm in writing whether loaner machines are provided, what the response window is, and whether data erasure is included. The same review discipline applies as in What to check in a maintenance contract.

1. Inventory what you have: unit count, purchase year, warranty expiry, user, and role on a single sheet. Without this you cannot size either the order or the budget
2. Narrow the scope: prioritise machines past four to five years or showing the signs above. Avoid replacing the whole fleet at once — that is what concentrates cost
3. Pick standard models: two or three models by role. Procurement, setup, and fault handling all get easier. Buying a different machine every time is the most expensive option
4. Decide who does setup: in-house means one to two hours per machine; outsourced means per-unit labour on the invoice
5. Decide how data moves: if everything already lives in the cloud, migration is light. If files live locally, missed data is the single biggest source of trouble
6. Decide disposal up front: data erasure plus disposal or trade-in. Defer this and abandoned machines pile up in the office
7. Update the inventory sheet: record new units and warranty dates, and put the next refresh window on the calendar

That sheet works better when PCs are tracked alongside accounts and licences. IT asset management for SMBs covers a minimal way to start.

The accidents in a refresh happen with the old PCs, not the new ones. They still hold customer data, quotes, and HR records.

- Emptying the recycle bin or running a factory reset can still leave recoverable data. Use dedicated erasure software or physical destruction
- If you outsource, require a certificate of data erasure. Avoid vendors who cannot issue one
- On lease returns, the contract usually still leaves erasure responsibility with you
- For machines returned by leavers or transfers, disable the accounts at the same time (Offboarding cloud accounts)
- Machines kept "as a spare because they still work" tend to sit on the network unsupported. Decide how many spares you keep and what they are for

A refresh bill that spikes in one particular year is the echo of a fleet bought all at once. Break that pattern at the next refresh and future budgets become predictable.

- Split the refresh across fiscal years: twenty machines becomes five a year for four years, with roughly the same amount budgeted annually
- Mix in a monthly model: lease or subscribe part of the fleet instead of buying all of it, converting spend to a fixed cost
- Name a "PC refresh" line in the annual IT budget: without a line item, every refresh starts from a fresh approval round (How SMBs should set an IT budget)
- Use subsidies and tax measures where they fit — but do not delay a refresh the business needs while waiting on a programme timetable

- Purchase year, warranty expiry, user, and role listed for every machine
- Machines past four to five years, and those showing failure signs, identified
- Standard models narrowed to two or three by role
- Compared on total cost including peripherals, warranty, setup, and disposal — not hardware alone
- Purchase / lease / rental / subscription compared against your own cash flow
- For monthly models, fault-handling scope, response window, and loaner availability confirmed in writing
- Migration targets enumerated: local files, mail, browser settings, software licences
- Erasure method for old machines decided, and certificate requirement settled
- Next refresh window on the calendar
- Budget split across fiscal years to avoid a single-year spike

PC replacement is decided less by which model you pick than by settling when, how many, and for how much. Put purchase year and warranty expiry for every machine on one sheet, then refresh anything past four to five years in yearly batches. Do that and both burdens — emergency failures and single-year cost spikes — get lighter at the same time.

And design the disposal of the old machines with the same care you give the new ones. Data leaving the building on a drive you did not erase stops being a budget conversation entirely.