Post merger integration priorities should protect the business you bought before trying to capture every possible saving. Customers still need deliveries, employees need credible answers and finance needs reliable cash visibility. A signed transaction does not resolve those operating requirements.
The first 100 days are a useful planning horizon, not a guarantee that integration will be finished. At AB Consulting, a practical approach separates immediate continuity decisions from changes that need more evidence. The aim is to protect the deal’s value while making progress on the acquisition’s specific objectives.
This executive guide provides a sequence for the period after lawful completion of the transaction. Examples and calculations are illustrative, not AB Consulting client cases.
Set post merger integration priorities around the deal thesis
Write down the three reasons the acquisition made sense. Perhaps the buyer wanted a complementary product, access to a distribution network or more production capacity. Then identify what would destroy each benefit: losing the product team, confusing key customers or interrupting the plant.
Do not assume every function needs full integration. A specialist brand may need its own commercial identity while finance reporting becomes consistent. A shared purchasing programme may create value before a risky systems replacement. Choose the degree of integration deliberately.
BDC’s operational integration guidance describes the importance of selecting the appropriate integration level and giving stakeholders clarity about changes. Apply that principle to your deal’s objectives, rather than copying another company’s integration timetable.
Assign an executive sponsor and an integration lead with enough time to coordinate the work. Give each workstream an owner, an outcome and a decision route. The decision rights matrix helps distinguish who recommends a change from who can authorize it.
Sequence post merger integration priorities over 100 days
Days 1–10: protect continuity and remove uncertainty
Verify access to cash, payment authority, payroll, critical suppliers, customer commitments and essential systems. Prepare named contacts for urgent issues. Confirm what customers and employees need to know now, including where to raise concerns and which operating arrangements continue.
Talk directly with the people who hold key relationships and operational knowledge. Record their concerns and dependencies. Avoid promises about future roles or structures before the responsible leaders can support them with a decision. Silence and speculative answers both create uncertainty.
Days 11–30: establish a reliable baseline
Reconcile revenue, margins, receivables, inventory, headcount and cash across both businesses. Agree definitions before combining reports. A “customer” may mean a billing account in one system and a legal group in another; adding those counts can mislead management.
Review the assumptions inherited from due diligence. Confirm which savings require a contract renewal, process change or investment. Record customer and employee retention risks alongside the synergy pipeline. A saving that reduces service quality may damage the revenue the acquisition was meant to protect.
Days 31–60: implement changes with manageable dependencies
Select a small set of changes with clear owners and credible evidence. Examples include a common payment calendar, consistent management reporting or a supplier negotiation at renewal. Define a pilot and acceptance criteria before expanding a process across the combined business.
Test customer-facing handovers carefully. A new invoicing entity, bank instruction or support contact can cause payment delays and service confusion if introduced without clear communication. Coordinate finance, sales and delivery rather than treating each change as a separate administration task.
Days 61–100: verify benefits and decide what comes next
Compare actual outcomes with the baseline and approved plan. Review recurring benefits, one-off costs, delays and unintended effects. Close completed actions with evidence; carry unfinished work into a realistic next phase with a named owner and revised date.
Use the day-100 review to make decisions, not to declare the integration complete by convention. A major ERP move or site consolidation may require a longer horizon. Readiness should determine the timing.
Test post merger integration priorities against the cash impact
Illustrative example: an acquisition plan identifies €240,000 of annual supplier savings. The revised contracts begin after month three. Assuming equal monthly savings thereafter, the monthly run rate is €240,000 ÷ 12 = €20,000, while first-year savings are nine months × €20,000 = €180,000.
| Measure | Illustrative value |
|---|---|
| Annual savings run rate | €240,000 |
| First-year savings with three-month delay | €180,000 |
| One-off implementation payments | €90,000 |
| First-year net cash benefit under these assumptions | €90,000 |
The €90,000 net benefit assumes the savings become cash in the same year and the implementation payments occur in that year. It excludes tax, financing and other effects. A €240,000 annual run rate therefore should not be presented as €240,000 of first-year cash.
Track the €90,000 implementation payments in a weekly cash forecast if they occur before savings begin. A positive annual business case can still create an early funding requirement.
Give the integration review a decision agenda
Review customer issues, key-person dependencies, liquidity, overdue decisions and realised benefits. Escalate changes that exceed agreed cost or service limits. Require workstreams to present the decision needed, supporting evidence and consequences of delay.
Keep an integration action register with the expected result, owner, dependency, due date and acceptance evidence. Review it alongside business performance so the combined company can see whether integration is helping or interrupting its operations.
Protect the acquisition’s value with an integration plan the business can execute. Contact AB Consulting to discuss M&A and integration support, from operating continuity and governance to benefit tracking.
