M&A INTEGRATION

Integration starts with decisions, not systems.

Define how the combined business should operate before turning integration into a systems project.

OPERATOR NOTE · SEPTEMBER 27, 2026

Translate the thesis into operating choices

An acquisition creates possibilities, but those possibilities do not become an operating model automatically. Before choosing a common CRM, commerce platform or reporting stack, decide which parts of the businesses should actually become common.

The answer depends on the value-creation thesis. Cross-selling, shared delivery, procurement leverage and platform consolidation require different decisions and different levels of integration.

Make four sets of decisions explicit

Commercial: which customers, products, channels and pricing decisions should be shared?
Operating: which processes need to be consistent, and where should local variation remain?
Organizational: who owns the combined result, and who can resolve conflicts?
Technology and data: which systems and definitions must support those choices?

Protect the work that keeps the business running

Integration consumes attention from the same leaders who must deliver the current quarter. A plan that ignores this load can create a gap between the transaction rationale and business performance.

Separate the work required immediately from the work that can wait. Give customer continuity, financial visibility and critical operating dependencies clear ownership. Make the cost of deferred integration visible without treating every difference as an emergency.

Use milestones that reflect operating progress

A migrated database or consolidated application is an implementation milestone. It does not necessarily show that the business can sell, deliver or manage better.

Pair technical milestones with operating acceptance criteria. Can teams serve the intended customer journey? Do leaders use the same definitions? Is someone accountable for the process end to end?

Keep a decision record

Record the decision, the reason, the owner and the assumptions behind it. A lightweight record helps new leaders understand the intended operating model and gives teams a way to revisit choices when the facts change.

The integration agenda becomes more useful when it is a sequence of accountable business decisions, supported by systems work. The systems plan should support the business model rather than define it.

START WITH THE BUSINESS PROBLEM

What is standing between your business and its next stage?

Bring the constraint, the decision or the transition. We can work out whether a focused executive mandate is the right next step.