The Deal Thesis Told You Where the Value Was. Did Anyone Translate That Into What Actually Has to Change?

Start from the deal thesis, translate it into synergies with owners and timelines, then build Day 1 and Day 100 plans around it, in that order, so the integration plan traces directly back to why the deal was done in the first place. Integration plans built without this traceability tend to drift toward generic best-practice checklists that don't actually protect the specific value the deal was priced on.

Legal structure, contracts, payments, system access, and communication to customers and employees, plus a clear answer to who decides if something breaks that day, which is the item most Day 1 plans quietly skip. A Day 1 plan that covers the operational checklist but never names a single decision-maker for the inevitable unexpected problem leaves the organisation improvising exactly when it can least afford to.

The hardest decisions, placed early on purpose, deferring them is more expensive than making them unpopular but fast, because uncertainty during an integration has its own real cost in attrition and stalled decision-making across both organisations. A 100 day plan that defers the difficult calls to preserve short-term harmony usually just extends the period of uncertainty, which tends to cost more than the discomfort it was trying to avoid.

Maintain a synergy baseline with a source, owner, timeline, and testable assumption for every synergy, updated on a fixed cadence rather than revisited only when someone asks. A synergy without a named owner and a testable assumption behind it is really just a number in the original deal model, tracking it properly means being able to say, at any point, exactly what would have to be true for it to still be on track.

Because they're usually estimated on theoretical potential, not organisational feasibility, and the first delay is rarely built into the plan, so the schedule has no slack for the setback that almost always shows up somewhere. Deal models tend to assume synergies execute cleanly once the deal closes; the reality of combining two organisations' systems, people, and processes is rarely that clean, which is exactly the gap a synergy baseline is designed to close.

Use the same governance instrument as a transformation office, prioritisation, decision forums, cadence, benefit tracking, tuned to integration deadlines, which are typically tighter and less negotiable than a standard transformation timeline. The core governance logic doesn't change; what changes is the tempo, since an integration usually operates against a fixed synergy-realisation timeline the deal was priced on, with far less room to slip than an internally-driven transformation programme.

Map who carries the value and what makes them leave, and design communication and role clarity specifically around retaining them, rather than applying a generic retention bonus and hoping it's enough. The people who represent the most value in an acquired company typically also have the most external options, and they tend to leave in exactly the months when organisational uncertainty is highest, unless someone has deliberately designed against that.

Treat it as core integration work with a named owner, not a soft topic left to HR alone, since cultural friction shows up directly in retention, productivity, and how fast the combined organisation can actually start acting as one company. Leaving culture as an unowned, informal workstream is one of the most common reasons integrations that look clean on an org chart still struggle operationally for years afterward.

Design explicit roles and decision rights for the combined entity, deciding deliberately what integrates and what stays separate, rather than defaulting to whichever legacy structure happened to be larger before the deal. An organisation design built this way tends to reflect what the combined entity actually needs going forward, instead of simply reflecting which of the two pre-merger companies had more negotiating leverage during integration planning.

Build a repeatable integration machine, standard playbooks and a standard first 100 days that each new acquisition plugs into, rather than re-inventing the integration approach for every new deal. A buy-and-build strategy without a repeatable machine means re-learning the same integration lessons on every acquisition, at real cost in time and consistency, when a documented playbook would have captured what was learned the first time.

Where the acquired company's value comes from its own way of working, integrating it destroys the value you bought, a distinction that requires deliberately asking, for each function, whether the source of value is the underlying capability or the specific way it's currently delivered. Integrating everything by default, on the assumption that consistency is always an improvement, is one of the more common and more expensive integration mistakes.

Trace every synergy in the thesis back to a specific integration choice, owner, and timeline, so there's a direct, checkable line from the reason the deal was done to the specific actions the integration plan contains. A deal thesis that never gets translated this explicitly tends to fade into the background within a few months, replaced by whatever the integration team finds most urgent day to day.

Prioritise clear, early communication and role clarity, customer unrest during integration hits the exact revenue the deal was priced on, which makes it one of the highest-stakes and most avoidable risks in the entire process. Customers who don't know who their contact is anymore, or hear conflicting messages from the two legacy organisations, start looking at alternatives at precisely the moment the deal needs their revenue to hold steady.

It depends on the deal thesis and synergy complexity, the Day 1/Day 100 structure exists precisely to sequence what's urgent versus what can wait, rather than treating the whole integration as a single undifferentiated timeline. Some elements need to be resolved within days of closing; others can reasonably unfold over a year or more, and conflating the two into one deadline is a common source of unnecessary pressure.

Key-talent attrition, customer disruption, and synergies that were never translated into organisational action are consistently the three risks that do the most damage, usually because each one individually seems manageable while the combination compounds faster than any single workstream is tracking. A plan that addresses all three explicitly, rather than treating them as separate HR, sales, and finance concerns, tends to catch the compounding effect before it becomes visible in the numbers.