The acquisition question nobody asks early enough

Some years after a tier-one investment bank acquired a market-leading trading platform, I was asked to assess why the integration of their operations teams had yet to bear fruit. Both sides were capable. Both sides were acting in good faith. The stakes were unambiguous: every minute of platform downtime carried a six-figure P&L impact. And yet the teams circled each other, integration stalling, value unrealised.

The root cause was not culture, tooling or headcount, although all three were blamed at various points. It was that nobody had answered the question that should be asked before any integration begins: how integrated should this acquisition actually be?

The integration scale

Every acquirer holds precedents at both ends of a scale. At one end, the acquisition is fully absorbed: its processes, tools and teams become standard parts of the parent's framework. At the other, it remains largely autonomous, keeping its own operational independence behind a compliance perimeter. Both are legitimate. Most acquirers have examples of each. The failure mode is not picking the wrong point on the scale; it is never explicitly picking one, so every team negotiates its own answer, one meeting at a time, indefinitely.

Product teams versus service providers

There is usually a deeper structural difference hiding underneath. Acquired businesses, particularly product businesses, tend to run vertical, product-focused teams with end-to-end ownership: one close-knit group accountable for the whole platform, built on pride and speed. Large acquirers tend to run horizontal, as-a-service functions that deliver consistency and compliance at scale across a huge portfolio. Neither is wrong; they are optimised for different things. But drop one into the other without acknowledging the difference and each side reads the other as either reckless or bureaucratic. That mutual misreading is where integrations go to die.

What good looks like

The way through is deliberate rather than default. Name the difference openly; it defuses more tension than any team-building exercise. Place the acquisition on the integration scale explicitly, decided by the executive, not discovered by attrition. Then focus effort on convergence points: the specific places where the two operating models must genuinely meet, such as governance, security and compliance evidence, and leave the rest alone until there is a reason. Done well, integration becomes a two-way exchange, where the acquirer adopts what made the acquisition worth buying, rather than smothering it.

The pattern is fractal, incidentally. The same dynamic plays out when a ten-person business buys a three-person rival, when a franchise group absorbs an independent, and when two departments merge after a restructure. The numbers change. The question does not.