Buy-and-build remains one of private equity’s most attractive routes to value creation.
The logic is compelling. Acquisition targets can be identified. Synergies can be modelled. Multiple arbitrage can be underwritten. Scale can often be created faster, and with greater visibility, than through organic growth alone.
But the investment case usually models what will be acquired more precisely than who will have to run it.
That distinction matters.
A management team that successfully operates a £40 million platform may be perfectly capable of completing the first and second add-on. The businesses can remain relatively autonomous. Reporting can stay separate. Acquired founders can continue carrying much of the operational load.
Performance remains strong. The strategy appears validated. Yet little may actually have been proved.
The organisation has demonstrated that it can own several businesses. It has not necessarily demonstrated that it can operate one increasingly complex group.
The problem tends to become visible later, when complexity compounds faster than the leadership model evolves. We think of this as the acquisition three problem.
Not because the third acquisition represents a universal breakpoint. In some businesses the strain appears after the second; in others, not until the fifth. Acquisition three is not a magic number. It is a useful clock: the point at which a board should stop assuming the model scales and start requiring evidence that it does.
The question is no longer simply whether management can execute another transaction. It becomes whether the organisation being built can absorb it.
The first add-on can often be held together through attention.
The CEO stays close to both businesses. The acquired founder remains. The CFO creates a consolidated reporting pack. Customers see little disruption. Everyone works harder.
The second can still be managed by exception. The businesses retain separate systems, commercial terms and local ways of working. A few central appointments are made. The board sees revenue growth, a larger EBITDA number and a healthy pipeline.
The evidence appears to confirm the thesis. But what appears to be integration may simply be coexistence subsidised by management effort.
By the third acquisition, the arithmetic changes. It is no longer one business absorbing another. It is several operating histories colliding at once: different systems, commercial practices, incentive structures, reporting conventions, customer relationships and leadership expectations.
At first, this complexity is absorbed informally. The CEO resolves disagreements. The CFO reconciles the numbers. Strong functional leaders stretch across several businesses. Founders retain responsibility for their operations.
That model works until it does not.
The management layer that was already thin at the platform is now carrying four sites. The CEO is personally holding relationships that once belonged to several founders, some of whom have left. Group initiatives compete with local priorities. Decisions slow down, but remain concentrated around the same small number of people.
Meanwhile, the core business still has to perform and the next target is already in diligence.
This is why early financial success can be dangerous. Revenue rises. EBITDA rises. The pipeline remains attractive. Yet underneath, integration debt is accumulating: unreconciled systems, unresolved accountabilities, duplicated processes, temporary reporting workarounds and decisions repeatedly deferred because the leadership team lacks the bandwidth to make them.
The latest acquisition may be performing. The more important question is whether management capacity is increasing at the same rate as organisational complexity.
Private equity often calls the first asset a “platform” on the day it is acquired. That language is premature.
A strong company is not automatically a platform. A platform is a company with the repeatable organisational capacity to absorb other companies without losing control of the core.
It has sufficient management depth. It has reliable data. It has clear decision rights. It has an explicit operating model. It has integration routines that do not depend on the CEO remembering everything or personally resolving every issue. Most importantly, it has leaders who can transfer accountability beyond themselves.
That distinction is easily missed because the qualities that make a business attractive at entry can become constraints during the build.
A successful mid-market CEO is often close to customers, product and operations. They know the organisation intimately. Decisions are fast. Information travels informally. Problems reach the CEO because the CEO knows how to solve them.
Those are genuine strengths in the original business. They may be precisely why it looked worth backing. They can also conceal concentration risk.
The sponsor may believe it has bought an organisation when it has bought an exceptional operator surrounded by a thin management layer. It may believe it has acquired a scalable system when it has acquired a collection of relationships held in one person’s head.
The first two add-ons increase the leader’s span. The third exposes the absence of an operating system.
Buy-and-build progressively changes the CEO role.
At entry, the CEO is asked to improve a known business. Soon afterwards, the same person is expected to become an acquirer: support sourcing, lead diligence, win over founders, communicate the equity story and protect the base business.
After completion, the role changes again. The CEO must become an enterprise architect.
They must spend less time personally solving problems and more time designing an organisation capable of solving them without them. They must build management layers, allocate capital between businesses, integrate acquired leadership teams, establish common standards without destroying local entrepreneurial energy, and decide what remains decentralised and what becomes group-led.
Those are not additional tasks around the edge of the original role. They are a different job.
Operating a good company and building a multi-business group are different executive challenges.
This is not an argument that operators cannot become platform CEOs. Many do. Nor is it an argument for replacing the incumbent as soon as the business grows. It is an argument for recognising that the leadership specification has changed. When a platform starts to strain, the diagnosis is often framed as a performance problem: the CEO has not integrated quickly enough, delegated enough or built sufficient bench strength.
Sometimes that is true. More often, the board has changed the job without acknowledging it. The implication is not that the original CEO has failed. It is that the role may have changed faster than the incumbent has.
Boards should therefore avoid asking only: Is our CEO performing?
The more useful question is: Is this still the job we originally backed them to do?
And, if it is not:
What will the job need to become before the next acquisition closes?
The conventional answer to integration risk is more standardisation. That is not always right.
Some acquisition strategies create value by preserving local autonomy. Specialist businesses may depend on local customer relationships, strong founder cultures or entrepreneurial decision-making. In those cases, imposing a uniform model can destroy the qualities that made the businesses valuable.
A decentralised model is not failed integration. It is a conscious operating choice with different economics. It may forgo some central synergies in order to protect local accountability, customer intimacy and acquisition capacity. But it still requires disciplined capital allocation, comparable performance information and strong local leaders.
An integrated model makes a different trade. It pursues common systems, unified commercial practices, shared services, procurement leverage and cross-selling. It may create more enterprise-level value, but it demands greater change capacity and more authority at the centre.
Both models can work.
The dangerous model is the unspoken mixture: underwrite central synergies, operate as a federation, and hold the CEO accountable when neither approach produces the expected economics.
If the deal case assumes common pricing, cross-selling and overhead removal, leaving businesses semi-autonomous is not cultural sensitivity. It is failure to execute the underwriting.
Equally, if the value lies in local brands, specialist expertise and founder-led accountability, forcing integration may erode the very advantage that was acquired.
The operating model must therefore precede the acquisition sequence. For each material decision – brand, customer ownership, pricing, systems, procurement, talent, capital expenditure and P&L accountability – the board should know what will be common, what will remain local and when the change will happen.
“Integrate where sensible” is not an operating model. It is a deferral.
When pressure becomes visible, the usual response is to add management capacity. A Group COO. An Integration Director. A stronger CFO. A Chief Commercial Officer. A Chief People Officer.
Sometimes that is exactly what is required. But additional people do not automatically create additional organisational capacity. The critical issue is authority.
Consider the appointment of a Group COO. The board believes the CEO needs support. The incoming executive has operated larger organisations, understands integration and carries the scars from previous buy-and-build programmes.
They arrive to discover that business-unit leaders still report directly to the CEO. Capital decisions remain with the CEO and CFO. Acquired founders continue to use their direct relationship with the sponsor. Group initiatives can effectively be declined by individual businesses.
The COO has responsibility for integration but limited authority to enforce it. Twelve months later, the appointment appears unsuccessful. The person may not have been the problem. The organisation never gave them the job it thought it had recruited them to do.
This is an authority problem wearing a recruitment costume.
It can be tested surprisingly simply. Before making a senior appointment, ask:
What decisions will this person be able to make on Monday morning that somebody else makes today?
If the answer is unclear, the organisation is probably adding a layer rather than redistributing authority. And layers are rarely the answer to excessive complexity.
If the answers are vague, the business is not recruiting an integration executive. It is recruiting a coordinator who may ultimately absorb the blame.
Before appointing an integration leader, the board should be able to answer five questions:
If the answers are vague, the business is not recruiting an integration executive. It is recruiting a coordinator who may ultimately absorb the blame.
Every buy-and-build programme has a transaction clock: sourcing, diligence, financing, signing and completion.
It needs an organisational clock alongside it. The organisational clock defines when leadership, governance, systems and decision rights must change if the investment case is to remain executable.
That does not mean installing the infrastructure of a £200 million group into a £40 million business on day one. It means working backwards from the destination and agreeing the points at which the organisation must evolve.
If the thesis assumes five acquisitions, several geographies and a business three times its current size, what will eventually be required to run it? Which capabilities become critical? Which roles will change most? What must remain local? What needs to become group-led?
The current organisation should not automatically become the blueprint for the future one.
The board should define explicit organisational triggers:
Waiting for financial performance to expose the answer is usually too late.
The most practical intervention may also be the most countercultural: after the second acquisition, pause the machine. Not indefinitely but long enough for the Chair, CEO and sponsor to determine whether the first two deals have created a repeatable capability or merely consumed spare capacity.
Before approving acquisition three, the board should require evidence – not confidence – on seven points:
If those conditions are absent, the answer is not necessarily to abandon the next deal. It may be to change its structure, reduce the integration ambition, add capacity, revise the timing or price the execution risk properly.
What should end is the assumption that acquisition cadence is determined by pipeline and debt capacity alone.
Financial capacity is routinely modelled before another acquisition. Leadership capacity rarely is. Yet every transaction consumes executive bandwidth through diligence, integration, founder management, organisation redesign, systems decisions and recruitment.
Management attention is a finite resource. Once too much of it is borrowed from the same executives, decision speed slows and the base business starts paying the interest.
Buy-and-build is often discussed as an M&A capability. It is equally an organisational capability.
A platform premium is usually justified by the number of add-ons available. That is only half the calculation. The real premium should reflect the organisation’s capacity to convert those add-ons into an enterprise.
A target-rich market without a scalable leadership system is not a platform opportunity. It is a queue of transactions competing for the same finite management bandwidth.
This changes the conversation for each party around the board table.
The relevant question before the next acquisition is not simply:
Do we like the target?
It is:
What will owning this business require our organisation to become?
That question brings leadership into the investment thesis rather than treating it as a problem to solve afterwards.
Acquisition three does not cause the problem. It removes the disguise. By then, the sponsor has usually proved it can buy businesses. The harder question is whether the portfolio company has learned to absorb them.
Sometimes the CEO who built the platform can make that transition. Sometimes they need different capability and authority around them. And sometimes the responsible decision is to acknowledge that the person who was right for the original company is not the person required for the build.
The mistake is not changing the leadership model.
The mistake is waiting until performance forces you to.