Home / Drivers / Acquisition
D/02

The deal closed.
Now make it operable.

The acquisition case was built on growth, consolidation or complementary capability. Realising it now depends on two sets of systems, data and operating assumptions becoming one coherent business.

What changed

The organisation chart changed faster than the operation.

An acquired company arrives with more than applications and databases. It has unwritten rules, customer commitments, reporting definitions and people who know how to recover when the official process fails.

A rapid standardisation programme can remove duplication, but it can also erase the capability that justified the acquisition. Doing nothing preserves local performance while delaying shared visibility, cross-selling, control and economies of scale.

The real challenge is not moving both businesses onto the same software. It is deciding what the combined operation should become, then making the systems support that choice.

What is at stake

The same event can create exposure or advantage.

The fear

The expected value never survives integration.

Teams continue operating as separate companies, shared reporting remains disputed and forced migration damages service or loses the acquired company's advantage.

The ambition

The combined business becomes more capable than either company alone.

Leaders gain shared control where it matters while preserving valuable local knowledge, customer commitments and operating strengths.

Warning signs

How the constraint shows up.

01

Management cannot produce one trusted view of customers, orders, margin or capacity.

02

The same entities have different identifiers and definitions in each business.

03

Teams are manually translating work between platforms.

04

A central system has been selected before the combined operating model is understood.

05

Synergy targets depend on process changes that no current system supports.

06

Key people in the acquired business fear that integration means losing how they work.

The usual response

A migration plan is not yet an integration strategy.

01

Move everything to the buyer's platform

This simplifies the estate only if that platform can carry the acquired operation without damaging service or value.

02

Leave both companies alone

Local continuity is protected, but shared customers, data and decisions remain expensive to coordinate.

03

Connect everything

Interfaces can preserve optionality, but indiscriminate integration may institutionalise duplicated processes and poor definitions.

Before commissioning software

Integrate the operating model, not just the applications.

Before selecting the target systems, make explicit which capabilities should become common and which differences create value.

Q/01

Which deal assumptions depend on operational or data integration?

Q/02

What must remain uninterrupted for customers during the transition?

Q/03

Which processes are genuinely duplicated, and which reflect different customer promises?

Q/04

Where would a temporary integration buy evidence before an irreversible migration?

The right answer may be to change the process, configure a product, integrate what you already have, modernise one part or build an owned capability. ORBN helps make that decision before it helps deliver it.

Own how you operate

Own the choices that determine what the combined business becomes.

The technology plan should carry the acquisition thesis into day-to-day work. It should not allow whichever platform is hardest to move to dictate the operating model by default.

OWN / 01

Shared definitions for customers, products, orders, performance and risk.

OWN / 02

An explicit boundary between common capability and valuable local variation.

OWN / 03

A transition path that preserves service, evidence and the ability to change course.

Relevant evidence and capabilities
Other reasons the question begins

What else changed?

What changed?

Make the acquisition
work as one business.

Tell us what the deal is meant to unlock and where the two operations currently disagree. We will help shape the integration decision.