Integration & Execution
How execution strain emerges when systems, cadence, and capacity collide
Integration is where the deal stops being about the target and starts being about the organisation that bought it. The thesis was about the target — what we’d do with it, what it would add, what the combined footprint would look like. From the moment of close, the thesis is a secondary consideration. The primary question is whether the organisation doing the integrating can actually do it, given what it was already carrying.
Despite that, integration is widely framed as a phase to be managed, a set of workstreams to be coordinated, or a checklist to be completed. Execution is framed as a matter of discipline — something that naturally improves once systems and processes are aligned. This section works from a different premise: integration and execution are organisational problems first. Process and structure support them; they don’t explain them. Most of what determines whether they work is invisible to the governance built to track them.
Why integration deserves its own section
In buy-and-build strategies, integration is a recurring stress on the organisation — one that compounds with each acquisition. Every deal consumes leadership attention, disrupts informal coordination, introduces new assumptions and routines, and alters the system that must absorb the next one.
What works in early integrations often fails later. Capacity gets quietly depleted while complexity keeps rising — and the team that handled the last integration isn’t the same team on the next one, even if the names are the same. Execution degrades gradually, as absorption limits are exceeded, rarely as a single visible failure.
The tension this section works on
Across PE, corporate development, and founder-operator acquisitions, the same pattern shows up: organisations are well-structured for integration but poorly prepared to absorb it. PMI offices, steering committees, and dashboards create the appearance of control, while leadership bandwidth, decision clarity, and trust quietly fray. Execution frameworks promise leverage; applied too early, they harden fragility.
This section works on where that tension breaks, and why. The focus across all three essays is on organisational absorption, leadership judgment under load, sequencing of change, and the conditions under which execution finally works.
What the section covers
Three essays build intentionally on each other:
• Why Integration Fails — reframes integration failure as a structural and capacity problem rather than an execution one.
• The First 30–90 Days: What Actually Matters — examines early integration as a stabilisation challenge where leadership behaviour matters more than systems.
• From Integration to Execution: When Systems Finally Matter — explains the transition point where execution creates leverage instead of locking in fragility.
Taken together, they describe integration as a system to manage over time rather than a phase to complete. The underlying claim is demanding: execution only works after absorption, and absorption is a leadership responsibility that cannot be outsourced. Every essay in this section tests that claim against operating reality.
(If you’re new here, How to Read This Project lays out the full structure and the recommended reading paths across sections.)
This section is written for operators carrying integration responsibility, investors evaluating execution risk, and leaders navigating post-close ambiguity without playbooks that fit. If you’ve lived through an integration that looked fine and still underperformed — as I’ve watched happen in more than one platform — the patterns here should feel familiar.