Build
Rollouts
Old laptops, an outdated software version or a new phone system, replaced in waves: a pilot group first, then team by team, planned around your deadlines.
Fifty new devices are fifty small switchovers.
Replacing a firm’s laptops, moving everyone to a new software version or handing out new phones looks like shopping. It isn’t. Each device has to arrive set up like every other one, with the software its owner’s work runs on, the printers they use and their files where they left them, and each person has to be able to carry on working. Done by hand, that’s an afternoon per device and a different result each time. A rollout with us is a Build project: one tested standard, a pilot group that finds what the standard missed, then waves planned around your deadlines, and the old devices wiped and on record at the end.
The route
One standard, a pilot, then waves.
A rollout follows the same route as every Build project. Its switchover is split into waves, so that no deadline meets a whole floor of new devices at once.
-
Kick-off: who gets what, when
Which teams, which devices or versions, which software each role needs, and the deadline calendar that decides the order of the waves. Agreed in writing, with who signs off each wave.
-
Access and safeguard
Every person’s files and settings backed up before their old device is touched, and the old version kept available until the new one is confirmed. Nothing is wiped before there’s a way back.
-
The standard, built once
One device build with the baseline, the software by role and the printers by team, set up by tested scripts that check before they change anything. Every device of the wave comes out the same.
-
The pilot group
A few people who do the work every day get the new device or version first, for a fixed time. What they find changes the standard before anyone else sees it.
-
Waves around your deadlines
Team by team, never the whole firm in one week, and never the team with a submission on Friday. Each person gets their device set up, their files in place and a short handover, and carries on working.
-
Old devices out, then daily operations
Each old device wiped and its removal on record, licences moved or ended. Then into Manage, where the new devices are patched, monitored and kept to the standard.
On record
In the project order and the handover documentation.
- The standard: the device build, the software by role, the printers by team
- The waves, with each team’s date and sign-off
- What the pilot group found, and what changed because of it
- Every new device by owner, and every old one wiped, with the date
- The licences moved or ended
The device list afterwards is the one your evidence file and your insurer’s questionnaire draw on: every device, its owner, its protection and its patch level.
What usually goes wrong in a rollout.
-
Boxes delivered, not workplaces
The devices arrive and each one is set up by hand, differently, over weeks. Half the firm works on the new standard and half on the old, and nobody knows which problem belongs to which.
-
No pilot
The first time anyone works a full day on the new build is the day the whole floor gets it. What a pilot group would have found in a week, fifty people find at once.
-
Old devices in a cupboard
The replaced laptops sit unwiped in a drawer, still signed in, still holding client files. They stay in the device list until someone asks why the count is wrong.
Also under Build
- Provider exits and takeovers Access secured, systems documented and the switchover planned around your deadlines, even when the handover isn’t friendly.
- Microsoft 365 and Azure migrations Servers and VPNs in the office retired where they no longer earn their keep, service by service.
- Mergers and carve-outs One tenant or two, turned into the structure the deal needs by the legal date, nobody stopping work.
- CAD and BIM environments Workstations, project shares and licence servers built for working across sites, so models stay fast and in sync.
- Office moves and new sites Network, internet, phones and printing ready before the first desk is occupied, with a plan B for the line.
Questions we get
Does everyone get the same device?
The same standard, not necessarily the same hardware: a CAD workstation and an office laptop differ, but each is set up by the same scripts, to the same baseline, with the software its owner’s role needs. The standard is written down, so the next device is set up the same way.
Can we buy the devices ourselves?
Yes. What matters is that every device ends up on the standard, and the same scripts set it up whoever bought it. Whether the devices come through us or from your own supplier is agreed in the project order, like everything else.
How does the software end up on the devices?
Through tested scripts that run in your device management, check what’s installed and change only what differs. Nothing installs unless its fingerprint or its vendor’s signature checks out, and every script runs on a pilot group at your firm before it reaches everyone.
What about a software version change without new hardware?
The same route, shorter: the new version tested on a pilot group for a fixed time, then rolled out in waves by script, with the old version kept until the new one is confirmed. Small ones run inside Manage from the same price list; a change that touches every team’s working day runs as Build.
Start
Devices or software due for replacement?
In a first call we go through what’s due, which teams have deadlines when, and what the first wave would look like.
- No first level
- No surprises
- Pilot before you buy