Skip to content
← Resources / Articles
Integration5 min read

M&A integration checklist: what has to happen, in what order

Day one, the first thirty days, the first hundred. A workstream-by-workstream list for the people who have to make the model real, written so that it can be handed to an owner rather than read by a consultant.

All M&A Research

Integration

Updated
Hand tools laid out across a workshop bench.
Hand tools laid out across a workshop bench.

Key takeaways

  • Day one is about continuity: people paid, customers served, systems accessible. Nothing clever happens on day one.
  • Name a single integration owner with decision rights before completion. Integration run by committee is integration that stalls.
  • Every synergy in the model needs a named owner, a date and a line in a budget, or it is a number in a spreadsheet.
  • Attrition is the main destroyer of value, and the window to prevent it is the first fortnight.

The short answer. Integration runs in three waves: day one (continuity), the first thirty days (control and communication), and the first hundred (the synergies in the model). The checklist below is ordered that way. The deeper argument about why this phase decides whether the deal was ever real is in the first hundred days; this page is the list.

Before completion

The work that cannot be started after signing.

  • Name one integration lead with authority to make decisions, not to convene meetings.
  • Write the day-one plan: a document, not an intention.
  • Map the synergies from the model to named owners, with dates and budget lines. Anything without all three is not a synergy.
  • Decide the operating model: absorbed, standalone, or something in between. Say it plainly, because the acquired team will infer an answer if you do not give one.
  • Identify the people you cannot lose and decide what each is being offered, before anyone resigns.
  • Draft the communications, staff, customers, suppliers, and anything public, with a release order and times.
  • Confirm the consents are in place: landlords, key contracts, licences, change-of-control approvals.
  • For a carve-out: agree every transitional service, its duration, its price and its exit criteria. This is the workstream that overruns.

Day one

The only objective is that nothing breaks.

  • Payroll confirmed for the next cycle, with the mechanism and the date known.
  • All-staff communication delivered in person or live, not by email alone, and followed by questions.
  • Customers contacted. The top twenty by named owner, the rest by letter the same day.
  • Suppliers notified where a change of control affects terms.
  • Systems access confirmed: email, finance, CRM, anything customer-facing.
  • Banking and signatories transferred, mandates updated.
  • Insurance in force under the new ownership.
  • Statutory filings made.
  • A named person each acquired employee can ask questions of.

Nothing on this list creates value. Everything on it destroys value if missed.

The first thirty days

Control, visibility, and stopping the leak.

People

  • Meet every member of the acquired management team individually, in the first week.
  • Retention conversations with the identified key people: completed, not scheduled.
  • Confirm what is not changing, in writing. Uncertainty is what causes resignations, and silence reads as bad news.
  • Complete any consultation obligations on roles that are genuinely changing.

Finance

  • Monthly reporting on a single basis, with the first consolidated month closed on time.
  • Cash and working capital visibility: daily if the business is seasonal.
  • Reconcile the acquired business’s actuals against the diligence model, and understand every variance. The quality of earnings work was a forecast; this is the first evidence.
  • Complete the purchase price adjustment process, or confirm the locked box leakage position.

Commercial

  • Speak to the top customers yourself. Churn in the first quarter is the signal that matters most.
  • Freeze pricing changes unless there is a specific reason. Pricing is where acquirers most often break something they did not understand.
  • Confirm the pipeline is real by talking to the people carrying it.

Operations

  • Day-to-day decision rights written down and circulated: what the acquired business decides, what needs approval, from whom.
  • Security and access review: joiners, leavers, privileged accounts, anything that was the former owner’s personal credential.

The first hundred days

Now the model.

  • Each synergy tracked individually against its date and budget, reported monthly to the same forum. Aggregate synergy reporting hides the ones that are failing.
  • Cost synergies actioned, with the one-off cost of achieving them recognised. These are the reliable ones.
  • Revenue synergies tested small before anyone forecasts them again. Cross-sell is the assumption that fails most often and is believed most readily.
  • Systems decision made: migrate, integrate, or leave alone. “Decide later” becomes “never”, and two finance systems is a permanent tax on every month-end.
  • Brand and market position resolved, externally as well as internally.
  • Attrition measured against the pre-deal baseline, for the acquired business specifically, not the group.
  • A written review against the investment case at day 100: what has been delivered, what has slipped, what was wrong. Said out loud, early, while there is still time to act.

The four things that go wrong

In order of how often they do:

  1. Nobody owns it. Integration is added to the day jobs of people who already have day jobs, and it quietly stops.
  2. The people leave. Attrition in the first quarter is the most common cause of a deal underperforming, and the window to prevent it is the first fortnight.
  3. Revenue synergies were never real. Cost synergies mostly land. Cross-sell mostly does not, and it is usually the larger number in the model.
  4. Transitional services overrun. On a carve-out, the parent’s incentive to exit the arrangement is weaker than yours, and the costs are real. IT separation is the usual culprit, and stranded personnel, vendor contracts and licences keep running long after completion.1 Buyers also tend to overrun their one-time cost budgets between signing and closing, most often by engaging too many vendors at once.2

One note on the arithmetic

A deal that looked accretive on the model is accretive only if the synergies arrive on the schedule assumed. Delay is not neutral: a synergy that lands in year three instead of year one has lost most of its present value, and the price was paid on day one.

That is the whole case for treating the first hundred days as part of the transaction rather than as what happens after it.

Sources

  1. Deloitte, The Art of Speed: accelerating the exit from IT Transition Service Agreements. ↩

  2. PwC, “How expediting transition service agreement exits can unlock deal value”. ↩