The 100-Day Leadership Plan: Staffing Integration Before You Need It

Every acquisition has a 100-day plan for systems, customers, and operations. Far fewer have one for who's actually going to run the combined organization — and that gap is where a lot of deal value quietly leaks out.

It's tempting to treat integration leadership as something that sorts itself out once the deal closes — the existing team absorbs new responsibilities, someone steps up, the org chart settles. In practice, ambiguity about who's in charge of what during the first 100 days is one of the most common reasons a well-underwritten deal underperforms. Decisions stall while people wait to see who has authority. Customers notice service gaps. The best people on both sides — the ones with other options — start looking around.

Naming an integration leader after close means that person spends their first weeks learning the business instead of running it. Naming one before close means they can start making decisions on day one.

A workable plan identifies three things before signing: who owns integration overall, which roles are duplicated across the two organizations and how that gets resolved, and which critical roles have no clear owner at all in the combined structure. The integration lead doesn't have to be a new hire — sometimes it's an existing executive from the buyer's side, sometimes it's a seller's employee who's earned the buyer's confidence — but the role has to be assigned, not assumed.

For gaps that can't be filled internally, the search needs to start well before close, not after. A leadership search run in parallel with due diligence can have a candidate in the wings by the time the deal signs, instead of starting from zero in week one of a business that already needs decisions made.

A 100-day plan that only covers systems and operations is half a plan. The other half is knowing, before the ink is dry, exactly who is accountable for making the combined business work.