Day One, Everyone Works: Device Logistics for Roll-Ups and Carve-Outs
The integration plan has workstreams for finance, systems, and branding. The workstream that decides whether day one *feels* like a functioning company is the one that usually isn't in the plan: getting a working device in front of every employee.
Every acquisition has a day one, and day one has an audience.
The employees of the acquired company show up that morning making a judgment they'll never articulate in a survey: is the new owner competent? They form it from small evidence. Whether their login works. Whether the laptop in front of them connects to the systems they were told to use. Whether the person onboarding them knows where their device is. Deal decks talk about synergy capture; the employees are watching whether anyone can get them a working computer.
When they can't work, the cost is not abstract. It's payroll paid for idle days, customer-facing staff going dark during the exact window when customers are most nervous, TSA clocks burning on services the deal is paying to exit — and, most expensively, the acquired team's first data point about the new owner being "they weren't ready for us."
Day one is a device logistics event. Almost nobody plans it as one.
Why device readiness slips through the integration plan
Integration planning is organized by workstream — finance, legal, HR, systems, brand. Devices sit in the seam between HR (who's coming over), IT (what they'll access), and physical operations (what's on their desk). Seams are where things fall.
Three failure patterns repeat across deals:
The fleet is a rumor. Diligence produced a device count from a spreadsheet last updated at the seller's previous refresh. Nobody knows which machines exist, which employees have them, what's leased versus owned, or what has to be returned to a seller under the TSA. You cannot stage a day one against an inventory you don't trust — and building inventory truth takes weeks, which means it has to start well before close, not the Monday after.
Everything depends on the close date, which moves. Device provisioning has real lead times: procurement, imaging, kitting, shipping. Integration plans schedule those backward from a close date that then slides — twice — and the device workstream either eats the compression or misses day one. The fix is to make readiness stageable: devices built and kitted early, held in inventory, released to ship the moment the date is real.
The people doing it have day jobs. The platform company's IT team — often a handful of people — is expected to absorb a hundred-person onboarding wave on top of running the existing business. They can do it once, heroically. A roll-up thesis that acquires four companies a year cannot run on heroics; the third deal arrives before anyone has recovered from the second.
What day-one readiness actually requires
Treated as a logistics program, day one decomposes into work that can start before close and repeat across deals:
- Inventory truth first. Physically reconcile what the target actually has — serials, assignments, ownership, condition — against what the spreadsheet claims. This is also the moment leased assets and seller-owned equipment get flagged for the return path they'll need later.
- Decide keep / replace / retire per person, not per fleet. Some inherited devices are fine to re-provision. Some are lease returns. Some are three generations old and cheaper to replace than to fight. The output is a per-employee device plan, not a blanket policy.
- Build ahead, hold, release. Devices for the incoming team are imaged to the platform standard, kitted per person, and staged in inventory — so a moving close date changes a ship date, not a readiness date.
- Ship to the person, not the project. Distributed workforces mean day one happens at kitchen tables, too. Direct-to-employee shipping with tracking, clear instructions, and someone watching the exceptions is what makes a remote day one indistinguishable from an office one.
- Run the reverse leg. Every keep/replace decision creates a return: seller equipment going back, lease returns, retired units needing certified wipe before disposal. The deals that skip this discover it during the working-capital true-up or the first audit.
The roll-up multiplier
For a single acquisition, engineered device logistics is the difference between a smooth day one and a rough month. For a roll-up, it compounds into something more valuable: a repeatable integration asset.
The second deal reuses the first deal's playbook — the inventory process, the imaging standards, the kitting spec, the shipping and returns machinery. Each integration gets faster and cheaper than the last, and "we can integrate in weeks, not quarters" quietly becomes part of the platform's edge in competitive processes. Meanwhile the ongoing operation — every subsequent new hire, exit, and refresh across the growing platform — runs through the same pipeline the deals do.
Day one stops being a recurring emergency and becomes a product the platform owns.