Synergy Obsession vs. Orchestration Reality: Why M&A Automation Engines Often Fail
All posts
Synergy estimates find favour with boards because they present financial benefits such as "£2 million in IT cost savings." The numbers disappear when integration projects encounter complexity and change resistance because there is no realistic orchestration roadmap.
The Disconnect
- Wishful Integration: Overestimating API availability and underestimating legacy approvals.
- Workflow Bloat: Over-engineered automation pipelines that nobody adopts.
- Change Management Vacuum: The absence of training and ownership and governance leads to scripts being abandoned by users.
Lessons in Synergy Overreach
Research conducted on LinkedIn shows that 70–90% of M&A deals fail to meet synergy expectations because integration expenses including IT alignment and employee training and regulatory fees were omitted from the original model.
A Pragmatic Orchestration Roadmap
- Phase 1 — Lightweight Orchestration Layer (e.g. n8n): The implementation of a streamlined automation engine should begin with 2–3 minimum-viable processes (e.g., incident remediation, user provisioning).
- Phase 2 — Prove ROI: Requires proof of ROI through weeks of savings before expanding to more workflows.
- Phase 3 — Governance & Adoption: Version control together with stakeholder champions and training should be implemented to prevent orphaned automations from occurring.