The value of an acquisition depends partly on what the combined enterprise becomes capable of doing. Systems integration supports that ambition, but the operating choices must come first.
Translate the deal thesis into operating choices
Market access, new capability, scale and cost efficiency imply different integration priorities. Establish which part of the thesis depends on a common process, shared information or coordinated decision—and which depends on preserving local strengths.
A single platform is not itself an integration thesis. The leadership team needs a view of the future operating model, the decisions that belong at group level and the differences that matter to customers, markets and operations.
Create visibility before demanding uniformity
Early group reporting can expose incompatible definitions: customer, revenue, margin, inventory, service performance or project progress. Leaders may see apparently comparable figures that describe different realities.
Agree the minimum shared meaning needed to govern the combined business. Name the data owners and reconciliation responsibilities. Some visibility can be established before full harmonisation, provided the limitations and adjustments are understood. This gives leadership a basis for decisions while longer-term design proceeds.
Sequence around continuity and value
Map the dependencies behind each integration workstream. A procurement synergy may rely on common supplier records, contract decisions, approval responsibilities and planning information. A cross-selling ambition may depend on customer consent, account ownership, product availability and service capability.
Prioritise what unlocks the thesis without creating disproportionate operating exposure. Define intermediate states clearly: which team owns the work, which system holds the record and how exceptions cross the boundary during transition.
Make people and authority explicit
Integration creates uncertainty about roles, local autonomy and the future of established practices. Delayed decisions can leave teams maintaining two ways of working without the authority to resolve conflicts.
Give process and service owners a clear mandate. Explain why a change is required, where local judgement remains and how concerns are escalated. Involve the people who understand the acquired operation; the knowledge that made it valuable must survive the integration.
Test readiness for the next acquisition
Measure progress against the operating and economic thesis, not only the completion of interfaces or migrations. Separate one-off integration cost from ongoing cost, and forecast synergy from realised improvement.
Capture what can become repeatable: a data onboarding approach, control framework, integration architecture, role model and decision process. The stronger outcome is an enterprise that can absorb future growth with greater clarity, rather than beginning each integration from the same uncertainty.