A purchasing sheet lists processor, memory, storage and price. The colleague who will use the laptop asks a different set of questions: can I read the screen by the window, connect the projector, join a call without a headset problem, and get a replacement charger quickly?
Both sets of questions belong in the decision. For a small fleet, a repeatable purchasing process is often more valuable than finding a different bargain for each person.
Describe the job first
Group people by the work they do. A browser-based operations role, a developer compiling software, and someone working with large design files have different requirements. Record the actual applications, typical files, external displays and travel needs.
Check the software vendors' current requirements for those applications. Avoid treating a processor family name as a complete specification: generation, power limits and the rest of the machine affect the result. If the workload is important, ask to test a representative device with representative files.
Include the working environment. Someone who spends most of the day at a desk may benefit from a suitable monitor and keyboard more than a thinner laptop. Someone moving between client sites may care more about battery condition, weight and charging flexibility.
Price the complete seat
The laptop price is only one line. Add the equipment and setup needed for the person to work: operating-system licensing where applicable, docking or adapters, display, keyboard, headset, configuration and delivery.
Then ask what happens when the device needs repair. Does the supplier collect it? Is the warranty local? Is there a clear turnaround arrangement? Who provides a temporary replacement? Do not infer these answers from the brand badge.
| Item | What to confirm |
|---|---|
| Exact model | Full model or part number, not just a product family |
| Condition | New, refurbished or used; how that affects the warranty |
| Display | Size, resolution and suitability for the working environment |
| Ports | Actual monitor, network and peripheral connections needed |
| Warranty | Provider, coverage, location and claim process |
| Setup | Accounts, updates, security settings and application installation |
| Repair route | Contact, transport, data handling and replacement arrangements |
Resist accidental variety
Buying a different device every time can create a collection of incompatible chargers, docks and spare parts. Standardizing a small number of suitable models can simplify support and onboarding. It should remain a practical choice, not a rule that forces a specialist into an unsuitable machine.
Keep a record of the exact model, serial number, assigned user, purchase date, warranty information and accessories. Store account recovery information in the approved credential system rather than the asset spreadsheet.
A modest spare-device plan can be worth discussing if an employee cannot do useful work during a repair. Decide how that spare is updated and checked. A forgotten laptop that cannot sign in is not much of a contingency.
Inspect before accepting a batch
Use a short acceptance checklist. Confirm the delivered model and specification against the quotation. Check the screens, keyboards, ports and chargers. Verify the agreed software and account setup, and test the peripherals people will actually use.
For used or refurbished devices, agree the condition standard in advance and include battery condition in the discussion. Avoid vague assurances such as “as good as new” when you can ask for an explicit inspection result and warranty.
Make the next purchase easier
After a few weeks, ask users what did and did not work. Was the screen suitable? Were adapters missing? Did the configuration create extra support calls? Add the answers to the purchasing checklist.
That feedback is more useful than defending the original choice. Your next quotation can then describe a working setup, complete with the assumptions and support needs, instead of another row of impressive numbers.
Have a version of this problem?
Let’s talk it through.