Growth by acquisition is a business strategy. Technology chaos is its side effect.
Every company you acquire comes with its own IT environment. Their own ISPs. Their own firewall vendors. Their own WiFi configurations. Their own ticketing system, or no system at all. Their own way of doing things, built up over years by people who are no longer around to explain it.
Multiply that across a dozen acquisitions and you end up with what I inherited: a global fleet of 145 vessels and 83 offices where no two locations worked the same way. Different SSIDs. Different VLANs. Different POS systems. Different vendors. Different contracts with different end dates. A support call from any location started with "first, let me figure out what they're running."
After years of integrating acquired companies into a unified operation, here is the playbook I use.
Phase 1: Inventory before strategy
The temptation after an acquisition is to start fixing things immediately. Resist it. You cannot fix what you do not understand, and you cannot prioritize what you have not inventoried.
Document what exists before anything else. Every ISP contract. Every piece of network equipment. Every configuration. Every vendor relationship. Every recurring cost. This is tedious work, and it is the most important work. You are building the map every future decision will reference.
When we tackled ISP consolidation across 78 US sites, the first step was site surveys at every location. That inventory revealed about $25,000 in unreturned equipment that nobody had tracked. The inventory pays for itself before the strategy even starts.
Phase 2: Define the standard before you touch anything
Once you know what exists, define what should exist. This is where the technical decisions live: standard VLAN structure, standard firewall rules, standard SSID naming, standard rack layout, standard connectivity architecture.
The key word is "standard." Singular. Not "standards for vessels" and "standards for offices" and "standards for the dining division." One standard that covers every environment, with documented exceptions only where physically necessary.
The global standardization playbook I built covered everything from network configurations to Toast POS systems to vendor WiFi to connectivity architecture. One document. One standard. If it is not in the playbook, it does not get deployed.
Phase 3: Prove it small before you scale it
Do not roll the new standard out across 83 offices on day one. Pick a manageable subset. Prove that the standard works in practice, not just on paper. Find the gaps between your design and reality before you stake the fleet on them.
The NYC Ferry standardization was the proving ground. 38 vessels, 8 months, one standard. By the time we expanded to global operations, the methodology was tested and the team knew how to execute. The mistakes we made on ferry #3 did not happen on vessel #103.
Phase 4: Consolidate vendors and contracts
Acquisitions create vendor sprawl. Every acquired company had their own ISP, their own equipment vendors, their own support contracts. The result is a procurement landscape where nobody has leverage because the spend is fragmented across too many relationships.
Consolidation is how you reclaim leverage. We took 78 sites from a patchwork of ISPs down to two: one aggregator and Comcast. The result was about 50% reduction in ISP spend, dramatically simpler vendor management, and consistent service levels across every location.
The same principle applies to hardware vendors, software licenses, and support contracts. Fewer vendors. Bigger relationships. Better pricing. Simpler management.
Phase 5: Build the playbook for the next acquisition
The final step is not about the current integration. It is about the next one. If your company grows by acquisition, this will not be the last time you do this. Build the playbook so the next integration is faster, cheaper, and less disruptive than this one.
The new build playbook now covers every scenario: new vessel, new office, new port, new acquisition. The team does not reinvent the process each time. They follow the standard. They execute the checklist. The new location comes online looking identical to every other location in the fleet.
That is the real product of integration work. Not the integration itself. The repeatable system that makes the next integration boring.
The discipline behind the playbook
Inventory before strategy. One standard, not many. Prove small before you scale. Consolidate for leverage. Build for repetition. None of these are technical insights. They are operating disciplines, and the difference between an integration that compounds and an integration that gets reabsorbed into the chaos comes down to whether the disciplines hold.
Post-acquisition technology chaos is inevitable. Staying in that chaos is optional. The playbook exists. The only question is whether you are willing to do the disciplined, unglamorous work of executing it.
Adam Cooper is a Technical Director writing about distributed IT operations, maritime technology, and AI in production environments. Connect on LinkedIn or get in touch.