Synergy Obsession vs. Orchestration Reality: Why M&A Automation Engines Often Fail
Synergy estimates find favour with boards because they present clean financial benefits — "£2 million in IT cost savings" lands well in a deck. The numbers tend to disappear, though, when the integration projects that are supposed to deliver them encounter the actual complexity of merging two technology environments, and the reason is almost always the same: there was no realistic orchestration roadmap behind the estimate.
I have seen this pattern repeatedly. The synergy model assumes APIs are available and compatible, when in practice the legacy system on one side requires months of approval cycles before anything can connect to it. Automation pipelines get over-engineered to justify the synergy number, built to cover every conceivable workflow, and then nobody adopts them because they are too complex for the teams who are supposed to use them daily. Training is an afterthought, ownership is unclear, and governance is non-existent, which means the automation scripts that were supposed to save £2 million end up abandoned within weeks while both teams revert to their previous manual processes. Research consistently shows that 70–90% of M&A deals fail to meet synergy expectations, and the most common reason is that integration expenses — IT alignment, employee training, regulatory compliance — were omitted from the original model.
The alternative is to treat orchestration as something you prove incrementally rather than something you promise in a spreadsheet. Start with a lightweight orchestration layer — something like n8n or a similar low-code engine — and pick two or three minimum-viable processes where automation will deliver visible time savings quickly, incident remediation and user provisioning being the usual candidates. Run those for a few weeks, measure the actual savings against the predicted savings, and use that data to decide what to automate next. The temptation is always to build the grand unified integration platform on day one; the reality is that proving ROI on a small scale builds the credibility and institutional knowledge you need to expand later without building something that collapses under its own weight.
The third piece is governance, and it is the one that gets skipped most often. Automations without version control, without stakeholder champions who actually use them, and without training for the teams who inherit them become orphaned within months. I have walked into post-merger environments where the integration team built dozens of automated workflows during the first 90 days, declared victory, and moved on — and six months later the operational teams had quietly switched back to email and spreadsheets because nobody owned the maintenance. The orchestration roadmap that actually delivers synergy is the one that starts small, proves value, and invests in adoption alongside the tooling.