A device rollout looks like a shipping problem and behaves like a configuration problem. The boxes arrive in a morning. Getting three hundred machines enrolled, named, updated, locked down and in the right room is the part that takes the week.
The work is per device, and the rate falls
Setting up one laptop and setting up three hundred are not the same job repeated. Most of the thinking happens once: which accounts, which apps, which policies, what the naming looks like, who signs for the trolley. After that each device is a repeat of a known procedure.
That is why our per-device rate falls as the count rises, and why it falls on every device rather than only on the ones past a threshold. A hundred-device order is not priced as twenty-four at one rate and seventy-six at another.
Where the work happens changes the price
Three options, and they cost differently for real reasons.
Remotely, if the devices can be shipped to their users and enrolled over the air. In our hands, if you would rather send them to us — we collect or you drop off, and the quote carries cover for hardware in our care. On your site, which is usually right for a school: a trolley of Chromebooks is easier to do in the room it lives in.
On-site work adds days and travel, and both appear as their own lines. A large order implies on-site days whether or not anyone asked for them, so the configurator works out how many rather than letting you discover the gap later.
Questions worth settling before the boxes arrive
Who owns the accounts? Google Workspace for Education, Microsoft 365 or something else — the answer decides enrolment, and the licensing is yours either way unless you have asked us to bill it through.
What happens to the old devices? Wiping and certified disposal is a line you can add. It is worth deciding before the replacements land, because the old machines otherwise sit in a cupboard for a year.
Shared or assigned? A device one student uses is configured differently from a device thirty do. Kiosk and shared modes are a different setup, not a setting.
Who is on site, and when? Access is the single most common cause of a rollout slipping. A locked room at 8am is a day nobody can bill back.
What you get at the end
Devices enrolled and managed centrally, accounts and email working, printers and Wi-Fi configured, updates and encryption on, screen locks set, and the apps your staff actually use installed before anyone is handed a machine.
If you want the fleet kept that way afterwards rather than drifting, that is device management — a separate service, and one worth reading about before the rollout rather than after.