Your acquisition strategy is solid. What about your integration approach?
Acquisition announcements are good news days. New capability, new headcount, new possibility. What barely makes the announcement is what happens in the months after … when the teams that held everything together through the deal quietly start to unwind.
It's a familiar pattern. The due diligence is rigorous. Weeks of scrutiny on the numbers, the contracts, the structure. But even where the process is thorough, one question rarely gets the same rigour as the balance sheet:
are the people and behaviours actually ready to operate as one organisation, not just legally combined, but genuinely working as one?
That's not the same as asking whether the target has a leadership team, or an engagement score, or an HR function. Most do. It's asking something more specific: has anyone mapped what leadership needs to look like in the combined business, not in either business as it was before?
The slow leak, not the crash
Most integration failures don't look like a crash. They look like a slow leak.
A few months in, some of the exact people you acquired (the ones whose capability justified the price) start leaving. Research consistently points to people and culture as the single biggest reason acquisitions fail to deliver on what they promised, more often than financial or legal issues combined. And a pattern that shows up again and again: departures cluster around the twelve-to-eighteen-month mark, right when retention incentives finish vesting and people finally act on what they've been feeling since day one.
That timing matters. It means the warning signs were visible long before the resignation letters arrived. Nobody was looking in the right place.
This isn't usually because the deal itself was bad. It's because nobody defined what leadership behaviour actually needed to shift for two organisations to work as one, different decision-making habits, different definitions of accountability, different unwritten rules about how things get done. Without that, the capability you paid for walks out the door, and the revenue attached to it goes with it.
What standard diligence tends to miss
Good diligence processes are built to answer: who is here, what do they cost, and what's the risk of losing them?
They're rarely built to answer: what will it actually take, in how people lead and work day to day, for this to function as one business rather than two businesses sharing a logo?
That second question is a different exercise. It's not about retention risk scoring or org charts. It's about specific, observable leadership behaviour — how decisions get made, how conflict gets handled, how autonomy gets negotiated — mapped and addressed before day one, not discovered by accident three months after close.
What we do differently
We help COOs and integration teams map leadership and team dynamics before day one post-close, rather than after the damage is already visible. We work alongside you to get specific about what needs to shift in how people operate, not in the abstract but in the day-to-day decisions that determine whether the combined business actually works. Then we help build the accountability that makes it stick, rather than a plan that quietly gets deprioritised once the deal is done.
We don't arrive with a template. Every acquisition brings a different pair of cultures, a different set of leadership habits, a different set of assumptions about how work gets done. Our job is to help you see clearly what's actually happening and to work through, with you, what needs to change.
Where this leaves you
If you're growing by acquisition, it's worth asking honestly whether this has had the same scrutiny as the deal itself, before the attrition curve shows up on your bottom line, not after.
Let's talk about your integration timeline and your post-merger 100-day plan. We can map what's at risk, and what's possible if you get the people side right from the start.
If you have questions before that conversation, we're glad to talk them through.