The manufacturing industry differs from other sectors on a point that is often underestimated: most of the value is tied up in physical processes that cannot be relocated from one day to the next. Shutting down a production line to migrate systems costs production days. Shift schedules, maintenance programs and supplier contracts continue, regardless of whether the acquisition has already been processed in the administration. Where in services an integration is largely a matter of systems and people, in manufacturing a third layer is added: machines, inventory and physical throughput. That layer cannot be accelerated with a project plan.
That changes the order of decision-making. In many sectors, an integration starts with organizational structure or customer systems. In manufacturing, the first question is often an operational one: which plant, which line, which shift is affected first, and what happens if it comes to a standstill. Anyone who skips that question and starts immediately with synergies on personnel costs only discovers the operational dependencies once the planning is already fixed.
Synergy calculations in industrial deals lean heavily on shared procurement, shared capacity and economies of scale on raw materials. That is real, but realizing it runs through people on the floor who operate machines, carry out quality controls and plan maintenance according to their own rhythm. A synergy baseline that only adds up procurement volumes and overhead misses the question of whether two production locations apply the same quality standards, the same certifications and the same supplier relationships. Without that check, the synergy remains a figure on paper.
The question of whether two floors should even be combined is not rhetorical here. Two plants with different production philosophies, different degrees of automation or different customer segments can retain more value side by side than combined. A synergy baseline that explicitly tests this prevents a merger of lines from going ahead simply because it looks good on the balance sheet.
In many sectors, Day 1 means a communication plan and access to email. In manufacturing, Day 1 mainly means: does the line keep running, do suppliers keep delivering, does quality assurance remain intact. A Day 1 plan that does not fix this order runs the risk of treating operational continuity as a given while the actual integration pressure, such as shared ERP systems or joint planning, has not yet been prepared.
This bottleneck is not unique to this sector, but its form differs. Where the transport sector gets stuck on scheduling of vehicles and drivers, manufacturing gets stuck on scheduling of machines and shifts. The underlying question is the same: what must not come to a standstill on Day 1, and who is responsible for that once ownership changes.
A merger of two manufacturing companies brings dependencies that are rarely included in an integration plan: shared use of molds, shared certifications with customers, or a single key supplier that already served both companies before the deal. The integration office that maps these dependencies must look beyond organizational structure and systems. It must ask what happens if a line is merged, a certification has to be reapplied for, or a supplier cannot keep up with the combined demand.
These dependencies are similar to what is at play in the agricultural sector, where seasonal production and physical logistics drive integration planning, and different from professional services, where the main dependency is often the client team rather than a physical process. Anyone who does not factor these differences into the Day 100 plan risks applying the same approach to a sector that has different bottlenecks.
The question of whether everything should be integrated is sharper in manufacturing than in sectors without physical production. Merging two ERP systems is an IT project. Merging two production lines is an operational risk with consequences for delivery time and quality. A decision list that fixes per component what is and is not integrated prevents an integration plan from being executed as a package deal while some components function better kept separate, at least for a period that fits the operational reality.
This kind of choice requires distinguishing between what has to work in the short term and what can follow later, and that distinction is not the same as what works in retail, where integrating point-of-sale systems is relatively quick to do, or in education, where oversight and accreditation impose different timelines.
An integration plan says little about how much capacity is actually needed to carry it out. Before the synergy baseline, the Day 1 plan and the Day 100 plan are filled in, it is useful to know which part of the work coming to the teams is repeatable enough to automate and which part remains human work. The werkscan (work scan) from FTE TO AI calculates this per task, so that it becomes clear which part of the integration burden can be taken over by AI and which part requires capacity that you still need to free up.
Vraag maar wat er op Day 1 moet staan, of wat integreren juist kapotmaakt.
Answers come from this site’s knowledge base. Not tailored advice, and not a scan of your company.