Which licence, and which laptop—decided from a blank page each time instead of once.
“What laptop and licence do we actually buy for the next five hires?”
Write the decision down once. Stop re-making it per hire.
Onboarding already tells one new starter which licence and device fits their role. This page turns that same judgment into a written standard—so buying gets faster and more consistent as the team grows, instead of becoming its own research project every time.
Match the role, not the title
A starting point for the next hire’s licence and device.
| Role pattern | Typical licence fit | Typical device fit | Still worth checking |
|---|---|---|---|
| Everyday office work | A standard Microsoft 365 business licence covering mail, meetings, and Office apps. | A mainstream laptop with enough memory for normal multitasking. | Whether spare hardware already covers this before buying new. |
| Heavy spreadsheet, data, or design work | The same core licence, occasionally paired with one add-on app licence. | More memory and a faster processor than the everyday standard. | Whether that specific app carries its own licensing outside Microsoft 365. |
| Frontline, shared, or part-time roles | A lighter-weight licence built for shared or limited use. | A device shared across shifts, or a phone-only setup. | Whether the role needs a personal device at all. |
| A departing employee’s freed-up seat | A licence to reassign on purpose, not renew by habit. | A device to reclaim and reset—see employee onboarding and offboarding. | Whether the next hire’s role actually matches the last one. |
Signs a written standard is overdue
None of these need a crisis to be worth fixing.
A standard is most useful before the next hiring round, not during it.
A higher tier assigned “to be safe” during a busy month, still quietly billing today.
Some laptops are new, some are years overdue, with no rule for which comes first.
Several roles are about to be filled at once, and nobody has written down what each one gets.
Before you rely on this guide
What a buying standard is—and is not.
- Does the desk negotiate pricing with Microsoft or a hardware vendor?
- No. Reseller and vendor pricing conversations are a separate commercial relationship, not part of everyday desk support.
- Does the desk decide our budget?
- No. The desk can name what a role typically needs; approving the spend stays a business decision.
- Is this the same as the budget-planning check-in?
- Related, not identical. Budget planning looks at renewal timing and current spend; this guide is about the buying decision ahead of the next hire.
- Does every role need the top licence tier, just to be safe?
- No inflate-to-be-safe advice is given here. Matching the tier to the actual role is the entire point.
Common questions
Timing, exceptions, and a first written standard.
How far ahead should we actually buy?
Enough to avoid a same-week scramble—usually once a hiring plan is reasonably confirmed, not a year of inventory sitting idle.
What if a role genuinely needs more than the standard?
Naming the exception once, with a reason, is enough. It does not need to quietly become the new unwritten default for everyone.
Can the desk help write our first standard if we don’t have one yet?
Yes. Writing down a sensible first default is the same judgment already applied one hire at a time—just done once instead of repeatedly.