Integration is not value creation: Perhaps M&A has been asking the wrong post-deal question

For decades, post-merger integration has occupied an almost privileged position in M&A. Once a deal is signed, the vocabulary changes quickly. Integration teams are formed. Day 1 and the first 100-day plans are activated. Systems are harmonised. Reporting lines are clarified. Synergies are allocated. Workstreams multiply.

And then we ask whether the integration is progressing well.

But perhaps this is the wrong question.

The more fundamental question is: where is the value supposed to come from?

This distinction sounds simple, but it has significant consequences. Integration and value creation are not the same thing. Integration is one possible organisational mechanism through which an acquisition may create value. Sometimes it is essential. Sometimes selective integration is superior to absorption. And sometimes preserving autonomy is not a concession made because integration is difficult – it is the very condition under which value can emerge.

That does not make integration bad. It makes integration contingent.

And it suggests that the obsession with integration may occasionally cause acquirers to solve the wrong problem extremely well.

The integration reflex

There are good reasons why integration dominates managerial attention after an acquisition.

It is visible. It can be planned. Responsibilities can be assigned. Systems can be migrated. Procurement can be combined. Headcounts can be tracked. Synergies can be put into spreadsheets and reported to boards.

Value creation beyond cost cutting is considerably less obedient.

It may depend on something as difficult to manage as transferring tacit knowledge, opening a new customer segment, combining two capabilities that have never previously worked together, preserving entrepreneurial behaviour, accelerating innovation or giving a small, acquired company access to resources it could not access independently.

These processes are harder to put into a 100-day plan.

As uncertainty increases after signing, organisations naturally gravitate towards what they can control. The risk is that integration gradually becomes an objective in its own right. Functions start integrating because integration is what functions do. HR aligns HR. IT integrates IT. Finance harmonises reporting. Procurement looks for scale.

Individually, each decision may make perfect sense.

Collectively, they may destroy the reason the acquisition was undertaken.

We have seen this repeatedly in our research. In one acquisition designed to generate renewal and learning, the acquiring organisation began aligning the target function by function. The integration progressed remarkably efficiently. Yet the smaller target became overwhelmed by new processes, reporting requirements and systems. One employee described the organisation as having been “crushed by the love of the parent.”

The problem was not poor integration.

The problem was that good integration had become disconnected from value creation.

Start with value, not integration

This changes the sequence of questions managers should ask. The traditional question is:

How should we integrate this company?

A better sequence is:

Why did we acquire it? Where exactly will additional value come from? What needs to change for that value to emerge? And only then: what should we integrate?

For some acquisitions, the answer may indeed be: quite a lot.

If two businesses pursue scale economies, duplicate plants, overlapping distribution networks, common purchasing categories or highly similar support functions may need substantial integration. Leaving everything autonomous would make little strategic sense.

But consider a company acquired because of a technology, an entrepreneurial team, a customer relationship, an innovative business model or a capability the acquirer itself does not possess. Full integration can become much more dangerous. The closer the source of value lies to the distinctive characteristics of the target, the more carefully the acquirer needs to ask what should be connected, and what should be protected.

The relevant choice is therefore rarely between integration or no integration. It is between different organisational configurations designed around different sources of value.

Our recent research in the Journal of Management Studies¹ reinforces this point. Studying acquirers across several countries, we find that firms can achieve post-acquisition coordination through different paths. Entrepreneurially oriented acquirers tend to combine human integration with greater decision-making autonomy for target managers. Market-oriented acquirers are more inclined towards functional integration and tighter managerial control. Both are seeking coordination; they simply achieve it differently.

That distinction matters. Coordination does not necessarily require absorption. You can align goals without standardising every process. You can create connections without centralising every decision. You can share capabilities without eliminating organisational boundaries.

Compounders make the problem particularly visible

Perhaps nowhere is this clearer than among the growing number of acquisition-driven compounders. Their model is frequently described as buy-and-build. Yet much of the attention falls on the first word.

Buy.

How do they source targets? How many acquisitions do they complete? What multiples do they pay? How fast can they deploy capital? But the more interesting capability may sit behind the second word:

Build.

And building does not necessarily mean integrating every acquired company into an increasingly large corporate machine. The sophisticated compounder has to build something else: an organisational architecture capable of owning an increasing number of businesses without suffocating them. This creates a fundamentally different challenge from a one-off or a series of transformational acquisitions.

Imagine completing one acquisition and adding five central reporting requirements. It may be manageable. Complete 20 acquisitions, and the same logic begins to create bureaucracy. Complete 100, and a headquarters that attempts to coordinate everything directly eventually becomes the constraint on growth.

This is why some successful serial acquirers appear deceptively decentralised. The absence of extensive central integration is easy to interpret as a lack of management. In reality, the opposite may be true. Maintaining autonomy at scale requires considerable discipline. Halma provides one illustration of what this can look like organisationally. Rather than scaling primarily through additional layers of central control, it adds leadership capacity around the portfolio. Divisional Chief Executives support groups of operating companies, while the sector structure itself can evolve as the portfolio grows. The organisation around the businesses scales; responsibility for running them remains close to customers.

• You need rigorous target selection.

• You need clarity about what belongs at group level and what belongs locally.

• You need accountability without micromanagement.

• You need mechanisms for capital allocation.

You need ways of moving knowledge and talent through the organisation. And, critically, you need the discipline not to intervene simply because you can. The real buy-and-build capability may therefore be less about repeatedly integrating companies and more about repeatedly adding businesses to a system that allows them to become more valuable without requiring them to become identical.

Halma: enable rather than absorb

The interview with Halma plc in this issue illustrates the point particularly well. Its acquisition model begins with unusually strong emphasis on target selection. The premise is straightforward: if the acquired company is already a strong business with attractive fundamentals, the parent’s role is not necessarily to redesign it.

Halma’s logic turns much traditional M&A thinking around. It looks for high-quality businesses with strong positions in niche markets, long-term structural growth drivers, strong management teams and cultures that can thrive within its model. If those fundamentals are present, value creation becomes less about fixing the acquired business and more about enabling it to do more. At Halma, that means combining autonomy with accountability. Businesses gain access to capital, talent, expertise and a wider network while retaining substantial control over how they operate. There are common expectations around governance, compliance, cyber security, financial reporting and performance. Beyond these, operating companies retain responsibility for serving their customers, developing their strategies and running their businesses. Support is deliberately designed to be drawn on where it adds value rather than imposed as a standard operating model.

Continuity also matters. The Divisional Chief Executive who leads the acquisition process becomes Chair of the company after completion, preserving the relationship and understanding built during the transaction. That role helps the acquired business access Halma’s wider network, capital, expertise and talent without transferring day-to-day decision-making to the centre.

This is still integration – but integration understood much more broadly. There are common governance and reporting requirements, strategic alignment, access to shared resources and extensive human connection across the Group. What is deliberately limited is unnecessary operational absorption.

Knowledge also travels differently. Halma creates touchpoints through development programmes, training and cross-company relationships, but explicitly rejects the idea that there is one version of “what good looks like” that should simply be mandated across the portfolio.

Imperial Brands: Integrate the scale, protect the difference

The interview with Imperial Brands in this issue provides a useful counterpoint. The underlying principle is similar, but the organisational response is different. Imperial often acquires smaller entrepreneurial businesses because they bring something the larger organisation does not have in the same form: a distinctive brand, consumer connection, product, technology or way of innovating. Imperial, in turn, can provide capabilities that the target struggles to build at the same scale: distribution, regulatory expertise, capital and infrastructure.

This produces a more selective integration logic. Where Imperial provides the advantage, integration can be valuable. Distribution can be scaled, regulatory capabilities shared and some back-office activities combined. But where the target provides the advantage, its brand, consumer voice, operating model or innovation approach, standardisation may destroy rather than create value. As Julia Lefèvre explains in our interview, acquirers therefore need to be explicit from the beginning about “what we’re going to integrate and what we’re going to leave alone.”

Her observation that “every function will want to play with the shiniest toy” captures a common post-acquisition problem particularly well. Once a company is acquired, corporate functions naturally see opportunities to contribute. But individually sensible interventions can collectively standardise away exactly what made the target valuable. Protecting difference therefore requires active managerial discipline, not managerial neglect.

Halma and Imperial therefore illustrate two different answers to the same question. Halma creates much of its value by enabling already successful businesses while preserving broad autonomy. Imperial may integrate more deeply in selected areas because its distribution, regulatory and organisational scale form part of the deal logic. Neither model is inherently superior. What matters is that the boundary between integration and autonomy follows the source of value.

The corporate parent has to earn the right to intervene. This raises an uncomfortable question for acquiring firms. Why should the target adopt the acquirer’s way of doing something? The typical answer is implicit: because we bought it. Legally, that may be sufficient. Strategically, it is not.

Ownership creates the right to intervene. It does not automatically establish the value of intervention.

A corporate parent creates value when it provides something the business could not obtain as effectively on its own: capital, capabilities, customer access, talent, knowledge, credibility, scale or coordination with other parts of the group.

When intervention adds more cost, distraction or bureaucracy than benefit, parenting advantage quickly becomes parenting disadvantage. That makes every integration decision an economic question as much as an organisational one:

What additional value does this intervention create?

If the answer is unclear, the burden of proof should perhaps sit with integration rather than autonomy. But autonomy can become ideology too. There is an important warning here. It would be easy to replace one simplistic doctrine with another. If “integrate everything” is dangerous, so is “leave everything alone”.

Some acquisitions require substantial structural integration. Others fail because acquirers preserve autonomy where coordination was essential. Regulatory compliance, cybersecurity, financial controls and risk management may provide obvious minimum standards. Revenue synergies can require sales forces to coordinate. Scale deals may need common procurement, production or systems. Capability combinations may require deep interaction between technical teams.

Even highly decentralised acquirers need mechanisms of control. The issue is therefore not whether integration is desirable. The issue is whether the form and degree of integration fit the value logic. This is also why copying another company’s M&A model can be dangerous.

Halma’s model is internally consistent because its target selection, long-term ownership philosophy, organisational structure and post-acquisition approach reinforce one another. A company cannot simply borrow the autonomy element while retaining a target-selection logic built around acquiring underperforming assets that require transformation.

Likewise, a compounder cannot decentralise effectively if it lacks the capability to select management teams that can genuinely operate autonomously. Integration architecture and acquisition strategy are inseparable.

The hidden risk: successful integration, unsuccessful acquisition

Perhaps the most dangerous acquisition is therefore not one in which integration visibly fails. Everyone notices those. It is the acquisition where integration succeeds according to plan while the strategic value quietly disappears. The ERP system goes live. The reporting lines have been harmonised. Procurement savings are delivered. The integration office closes on schedule.

And two years later, the technology team has left, innovation has slowed, customers have moved away, and the capability that justified the premium paid for the target has been absorbed into organisational mediocrity. The integration programme can be green while the acquisition is red. This is why integration KPIs are not acquisition-performance measures. They tell managers whether the integration programme is progressing. They do not necessarily tell them whether the acquisition is creating value.

That requires returning continuously to the original logic of the deal.

• What did we buy?

• Why did we buy it?

• What has to remain different?

• What has to become connected?

• What should the parent provide?

• And what should it deliberately leave alone?

From integration management to value-creation design

Perhaps post-merger integration needs a different starting point. Not an integration blueprint, but a value-creation architecture. Such an architecture would distinguish between four questions:

What must be preserved?

The people, capabilities, customer relationships, culture or entrepreneurial behaviours whose destruction would undermine the deal logic.

What must be integrated?

Activities where common systems, scale, control or coordination are necessary to realise value.

What should be connected?

Areas where value comes not from structural integration but from interaction – knowledge sharing, cross-selling, innovation, talent or access to expertise.

What should be enabled?

Activities where the parent can provide resources, capital or opportunities while leaving decisions with the operating business.

These questions produce a much richer post-acquisition design than asking simply for the appropriate “degree of integration”. They also bring us back to the central challenge of M&A. An acquisition is not completed at closing. Nor is its value created by integration alone.

Value emerges when the strategic logic that justified the acquisition survives the transaction and continues to shape organisational decisions afterwards. Sometimes that requires integration. Sometimes autonomy.

Usually, it requires both, in different places, to different degrees and at different moments. The managerial challenge is therefore not to become excellent at integration. It is to become excellent at knowing when integration creates value, and when it gets in the way.

The five questions we should ask before a deal is signed:

• Where exactly is the value expected to come from? Not the synergy number – the underlying mechanism.

• What must remain distinctive for that value to emerge?

• Where is genuine interdependence between acquirer and target necessary?

• Can coordination be achieved through connection, incentives or shared purpose rather than structural integration?

• For every major integration initiative: what part of the acquisition’s value-creation logic does this support?

Sources

1. Bauer, F., King, D. R., Covin, J. G., Schriber, S., Brueller, N., & Weng, Q. (2026). Acquirer strategic orientations, integration decisions, and performance. Journal of Management Studies.