Why a standard laptop fleet costs less to support

Walk into many offices and you will find a little of everything: a few laptops bought in bulk four years ago, some picked up at a big-box store when someone new started on short notice, a couple of personal machines that drifted into business use, and whatever the last IT person preferred. Each one works, more or less. Together they are one of the quietest drains on an IT budget I know of.

I spend a lot of my time designing how devices are bought, set up, supported and retired for the organizations we manage. The single most effective decision is also the least glamorous: pick a small number of standard models, manage every one of them the same way, and replace them on a plan.

What a mixed fleet costs, beyond the invoice

The purchase price is the visible part. The real cost of a mixed fleet shows up in support time, and it rarely gets attributed to the hardware:

• Drivers and firmware multiply. Every model has its own driver set, BIOS updates and quirks. A firmware security fix that takes one rollout on a standard fleet becomes a dozen separate tasks on a mixed one.
• Knowledge does not transfer. When a technician solves a docking problem on one model, that fix only helps the people with that model. On a standard fleet, every fix helps everyone.
• Accessories stop matching. Docks, chargers and monitors that work with one laptop do not work with the next, so hot desks and meeting rooms become a puzzle.
• Consumer models lack business features. Retail laptops often have shorter warranties, depot-only repairs, limited remote management and no guarantee the model will still be sold next year.
• Onboarding is slower. Each new machine needs to be checked, tuned and tested individually before it can be handed over.

None of these is large on its own. Added up across a year of tickets, they are often larger than the money saved by buying whatever was cheapest that week.

What standard actually means

Standardizing does not mean everyone gets the same machine regardless of their work. It means a short, deliberate catalogue. For most organizations, two or three models cover almost everyone:

• A standard business laptop for most staff.
• A higher-spec model for people who run heavy software, such as design, engineering or data work.
• Optionally, a lighter model for people who travel constantly.

Stick with business-class product lines from one vendor where you can, because they stay on sale longer, receive firmware updates for years and come with on-site warranty options. Standardize the accessories too: one dock, one monitor model, one headset.

Most importantly, standard configuration should come from policy, not from a hand-built image. Security settings, apps, encryption and updates are applied by your device management platform, the same way every time. That is what makes the fleet consistent, and it is what makes zero-touch provisioning possible.

What zero-touch provisioning really buys you

Zero-touch provisioning gets talked about as if it were magic. It is not, but it is very useful when the groundwork is right. In short: when you buy a laptop through a channel that registers it to your organization, the device knows who it belongs to before it leaves the warehouse. It can ship directly to the employee. When they turn it on and sign in, it joins your environment, encrypts itself, applies your security policies and installs the standard apps.

Here is what that buys you in practice:

• No imaging bench. Technician time goes into improving the standard instead of setting up machines one by one.
• Remote hires get the same experience. Someone starting in another province gets the same configured device as someone at head office, without anyone shipping it twice.
• Reset becomes a repair tool. A misbehaving laptop can be wiped and rebuilt to the known standard remotely, often faster than troubleshooting it.
• Security from the first boot. The device is encrypted and under policy before the user ever saves a file.

And here is what it does not do:

• It does not fix weak policies. It applies whatever standard you have, good or bad, very efficiently.
• It depends on how devices are bought. Hardware needs to be registered by the vendor or reseller, or registered manually, before it is handed out.
• It needs a decent internet connection on first sign-in, because everything is downloaded then.
• Some specialized applications still need manual licensing or activation steps.

Planning lifecycle and refresh

Laptops do not fail on a schedule, but you can still plan for them as if they do. Most organizations plan on a working life of three to five years for laptops, depending on how hard they are used. Whatever number you pick, the point is to choose it in advance and budget for it.

A workable lifecycle plan has a few parts:

1. An asset register. Every device, its serial number, purchase date, warranty end date and current user, kept up to date automatically by your management tools wherever possible.
2. Warranty that matches the life. If you plan to keep laptops for four years, buy four years of warranty with the device. Out-of-warranty repairs are where mixed fleets hide their worst costs.
3. Refresh in cohorts. Replace a share of the fleet each year based on purchase date, instead of everything at once. It smooths the budget and keeps the workload manageable.
4. Watch operating system support dates. Windows 10 reached end of support in October 2025, and many organizations discovered at the last minute that older machines could not run Windows 11. Known end dates belong in the plan years ahead.
5. Retire devices properly. Remove them from management, wipe them securely, record the disposal and recycle them responsibly. A laptop sold or donated with company data still on it undoes years of good security work.

Handling the people who need something different

There will always be the developer who works best on a Mac, or the field technician who needs a rugged device. That is fine. Standard is about how devices are managed, not only what brand they are. Those machines are still bought through the same channel, enrolled in the same management platform, encrypted, patched and reported on. The exception is the model, not the controls.

Getting from a mixed fleet to a standard one

You do not need to replace everything at once. The path I usually recommend is simple:

1. Enrol every existing device in management now, whatever model it is, so security and patching are consistent today.
2. Agree the standard models and accessories, and make every new purchase follow them.
3. Replace the oldest and most troublesome machines first, then follow the refresh cycle.
4. Within one full cycle, the fleet becomes standard without any single expensive year.

How Ceifa approaches device standards

Device lifecycle is part of how we run IT for our clients. Through our hardware procurement service we help you choose standard models, buy them so they arrive ready for zero-touch setup, and keep the asset register current. Under our managed IT services, those devices are then patched, monitored and supported the same way every day, and retired securely at the end. If your fleet has grown into a collection, let us know and we can help you plan the way back to a standard.

Frequently asked questions

Should we buy the cheapest laptop that meets the specs?

Usually not. Business-class models cost more up front but come with longer support, better warranty options, remote management features and stable model availability, which all lower the cost of supporting them over their life.

Can zero-touch provisioning work with laptops we already own?

Often, yes. Existing devices can be registered manually and then reset, after which they go through the same automated setup as new ones. Very old hardware may not meet current operating system requirements, which is a good signal it belongs early in the refresh plan.

How many laptop models should we standardize on?

Two or three covers most organizations: a standard model, a higher-spec model for demanding work, and optionally a light travel model. More than that and you start losing the benefits of a standard.

What should happen to old laptops at the end of their life?

They should be removed from management, securely wiped, recorded in the asset register as disposed of and recycled through a provider that can confirm data destruction.