Buy & Build Strategy
Why buy-and-build behaves less like a growth strategy and more like a system under load
Two platforms acquire similar companies on similar timelines with similar theses. Five years later, one is compounding — larger, more integrated, better able to absorb the next deal — and the other is visibly stalling, with the last two acquisitions quietly underperforming and the CEO spending more time in integration reviews than building the next thing.
Most of the time, the deals don’t explain the difference. In the platforms I’ve followed long enough to see the divergence, the theses were sound, the targets were reasonable, and the diligence caught what it was meant to catch. What separated the two platforms was something the investment memos didn’t model: whether the organisation itself kept compounding capability as it absorbed more complexity, or whether it quietly lost capability each time the acquisition load went up.
That distinction is what this section is about. Most writing on buy-and-build focuses on transactions — sourcing, pricing, synergies, capital structure. Those elements matter; they also explain only part of why some platforms compound value over time while others slow down, fragment, or stall even when the deals themselves look similar.
This section treats buy-and-build differently: as a coordinating logic that governs how complexity is introduced, absorbed, and managed as the organisation grows, rather than as a set of acquisition tactics.
Buy-and-build as a system, not a sequence of deals
On the surface, buy-and-build looks linear: acquire a platform, execute add-ons, integrate, repeat. From an operating vantage point it isn’t linear at all. Each acquisition introduces new interfaces — between people, systems, processes, and decision rights — and those interfaces interact. Their effects compound. What initially feels like incremental growth becomes a change in how the organisation actually functions.
The central strategic question isn’t “can we execute the next acquisition?” It’s “what kind of system are we building as complexity accumulates?”
Sequencing as a design choice
In buy-and-build, order matters. Early acquisitions shape routines, expectations, and integration norms. Later acquisitions get absorbed into whatever system those earlier choices created — for better or worse.
That makes sequencing a design decision rather than a timing optimisation. Well-sequenced platforms let learning consolidate between acquisitions. Poorly sequenced platforms accumulate unresolved strain. Over time, the difference shows up as declining decision quality, slower execution, and more reliance on escalation — rarely as a single visible failure.
Integration capacity as the binding constraint
Financial models often assume integration is repeatable. Operating reality suggests otherwise. Integration draws on finite resources: leadership attention, decision clarity, organisational trust, and the ability to resolve ambiguity under pressure. These resources don’t scale automatically with deal volume.
As acquisitions accumulate, integration capacity often becomes the binding constraint — long before capital or opportunity does. Understanding buy-and-build therefore requires understanding where that constraint sits, how it shifts over time, and what happens when it is exceeded.
What this section examines
The essays in this section work through buy-and-build as a system under load: why platforms with similar deal strategies diverge over time, how sequencing shapes the organisation’s ability to absorb complexity, and why integration capacity rather than deal quality often determines outcomes. The focus is on the underlying logic that governs whether complexity compounds into capability or collapses into friction. (If you’re new here, How to Read This Project lays out the full structure and the recommended reading paths across sections.)
What the essays share is one question: what changes about the organisation as it grows through acquisition, and is that change something the system can sustain? That question is the central one for anyone running, funding, or advising a buy-and-build platform — and it governs most of what follows from here.

