Slide Deck Template for M&A Integration Planning

Post-merger integration is where acquisitions succeed or fail. McKinsey's analysis of hundreds of acquisitions finds that 70% fail to create the value projected at deal close — and the primary cause is not a bad deal thesis, but under-resourced, under-managed integration. The first 100 days post-close are disproportionately important: decisions made (and not made) in this window shape the combined company's culture, talent retention outcomes, customer retention, and systems architecture for years.

The integration planning deck is the operating document of the Integration Management Office (IMO). It is not a slide deck for a one-time board presentation — it is a living document that the IMO updates weekly and uses as the source of truth for workstream governance. This template covers the structure of that document, from Day 1 priorities through synergy tracking and cultural integration assessment.

---

Section 1: Integration Thesis — Why This Acquisition Creates Value

Before planning the integration, document the value creation thesis with specificity. The integration plan should be derived from the thesis — every workstream priority and resource allocation decision should trace back to one or more of these value drivers:

Revenue synergies — cross-sell opportunities (which of Acquiree's customers will buy Acquirer's products, and vice versa?); geographic expansion (does the acquisition open new markets?); product capability expansion that unlocks new use cases or removes deal blockers.

Cost synergies — headcount consolidation in overlapping functions (Finance, HR, Legal, IT, Marketing); technology rationalization (decommission redundant systems — SaaS subscription overlap, duplicate data warehouses, redundant ERP modules); real estate consolidation (overlapping offices); vendor contract renegotiation (combined scale enables pricing improvements).

Technology and IP — does the acquisition accelerate your own roadmap by 12–18 months? What specifically: the engineering talent, the proprietary data, the trained models, the patents?

Talent — key engineering, product, or sales talent that the acquisition secures. Acqui-hire logic, but at company scale.

Synergy timing: Revenue synergies are almost always slower than the model. Cost synergies, particularly headcount, are faster but create morale and retention risk. Present the model assumptions explicitly: which synergies are in Year 1, Year 2, Year 3, and what the cumulative NPV requires from each.

---

Section 2: Day 1 Readiness

Day 1 is the first day after regulatory approval and deal close — the moment the organizations legally combine. Day 1 failures create lasting damage. Prepare this section at least 60 days before close.

Employee communications:

• CEO message to all employees from both organizations — due within 2 hours of close announcement
• Key messages: what is the vision, what does this mean for each employee's job, what happens next and when
• FAQ document available to managers before the all-hands — managers will be asked questions they need to be able to answer
• Town hall meeting scheduled for within the first week
• Common failure: corporate-speak messaging that employees correctly interpret as "we haven't decided yet." If you haven't decided, say that explicitly and provide a timeline for decisions.

Customer communications:

• Top 20 customers by revenue: personal call from account executive or executive sponsor before the public announcement
• Broader customer base: email within 24 hours of close, from the CEO or GM of the relevant business unit
• Key message: continuity of service, named customer point of contact, who to call with concerns

Systems access and security:

• SSO federation: Acquiree employees need access to Acquirer systems and vice versa from Day 1
• Revocation of access for departed employees (any RIF announced at close requires immediate access revocation on the day of departure notification, not after IT processes the ticket)
• Network segmentation decisions: how long will the networks remain separate before full integration?

Legal and financial:

• Bank account restructuring
• Benefits enrollment timeline for Acquiree employees
• Payroll system transition plan
• IP assignment documentation

---

Section 3: Integration Workstream Structure

The IMO governs integration through parallel workstreams, each with a dedicated leader, a weekly standup, and a shared tracker. Standard workstreams:

People and Culture

• Organizational design: who reports to whom in the combined structure; announcement timeline for leadership decisions
• Retention agreements: key person identification and offer letters (within 30 days of close — talent loss accelerates rapidly if key engineers or account executives see uncertainty)
• Benefits harmonization: Acquiree employees typically transition to Acquirer benefits at the next open enrollment, with bridge coverage in the interim
• Cultural integration program (see Section 6)

Technology and IT

• Systems inventory: map all technology in use at both companies
• Rationalization roadmap: which systems survive, which are decommissioned, timeline
• Data migration: customer data, product data, financial data
• Security posture alignment: patch levels, endpoint management, network monitoring

Finance and Legal

• Close the books as a combined entity from Day 1
• Intercompany elimination setup for consolidated reporting
• Contract novation: Acquiree's customer contracts may need to be assigned or novated to Acquirer
• Insurance: notify carriers of the acquisition; coverage implications for D&O, E&O, Cyber

Go-to-Market

• Sales territory and account ownership decisions (one of the most politically charged integration activities)
• CRM merge: lead, contact, opportunity, and account data migration
• Pricing harmonization: if Acquiree and Acquirer sell competing or complementary products to the same customers, pricing needs to be rationalized
• Marketing and brand: co-branding timeline, brand sunset schedule for Acquiree brand (if planned)

Operations

• Vendor and procurement consolidation
• Facilities: office strategy for overlapping locations
• Quality systems alignment (for manufacturing or regulated industries)

---

Section 4: Integration Governance and Cadence

IMO structure:

• Integration Management Officer: typically the COO or a dedicated senior executive; full-time role for 6–18 months depending on integration complexity
• Workstream leads: one per workstream, senior enough to make day-to-day decisions without escalation
• Executive Steering Committee: CEO + relevant C-suite; meets monthly to review progress and resolve escalations
• Board reporting: IMO provides integration status at each board meeting for the first year

Reporting cadence:

• IMO weekly all-hands: 30 minutes, all workstream leads, status on milestones and blockers
• Monthly integration scorecard to executive steering committee: RAG (red/amber/green) status per workstream, synergy progress vs. model, headcount changes, key risks
• Quarterly board update: synergy realization vs. plan, integration completion percentage, retention outcomes for key talent

Decision log: Maintain a single decision log for all integration decisions — what was decided, who decided it, and on what date. This prevents the "I thought we decided X" problem that plagues integrations and creates inconsistent communications.

---

Section 5: Synergy Tracking

Synergy realization must be tracked as a financial metric, not as a completion percentage of activities. "We migrated 80% of customers to the new platform" is an activity metric. "We achieved $2.3M of the $4M Year 1 cost synergy target" is a financial metric.

Synergy tracker structure: | Synergy | Category | Year 1 Target | Realized to Date | Projected Full-Year | Owner | Status | |---------|----------|--------------|-----------------|--------------------|----|--------| | Finance headcount consolidation | Cost | $800K | $600K | $800K | CFO | On track | | SaaS contract rationalization | Cost | $400K | $0 | $200K | IT | At risk — vendor contract termination fees higher than modeled |

Reporting to board: Monthly actuals vs. model, with commentary on any synergy that is tracking below plan and the recovery action.

Common synergy modeling errors to highlight:

• Revenue synergies modeled at full run-rate in Year 1, without accounting for sales capacity ramp, product integration work, or customer approval cycles
• Cost synergies without accounting for severance, real estate termination fees, or system migration costs that erode the net number
• Synergies modeled from customer count overlap without accounting for churn induced by the integration itself

---

Section 6: Cultural Integration

"Culture eats strategy for breakfast" — the Drucker aphorism exists because it keeps proving true in post-merger integrations. Cultural failure shows up in attrition data before it shows up in revenue data.

Cultural assessment: Conduct a structured cultural assessment of both organizations before close using a validated instrument (Denison Culture Survey, Hogan Assessment, or a custom values/behavior framework). The assessment identifies where the two cultures align and where they diverge across dimensions like: hierarchy vs. autonomy, risk tolerance, customer vs. internal orientation, process vs. outcome focus.

The assessment output is not a judgment about which culture is "better" — it is a diagnostic of where to invest integration energy and where to expect friction.

30/60/90-day integration survey: Pulse survey deployed at each milestone to all employees, segmented by company of origin. Track: sentiment toward the integration, clarity about their role, perception of how leadership is handling the integration, intent to stay. A 10-point drop in intent-to-stay in the Acquiree population between Day 30 and Day 60 is a five-alarm signal.

Cultural integration initiatives:

• Cross-company team projects (not social events — work creates relationships)
• Leadership exchange: Acquirer executives spending time in Acquiree locations and vice versa
• Shared onboarding for new hires from both populations
• Explicit conversation about which elements of Acquiree culture are worth preserving — acquirers who assume their culture is default often destroy the capability that made the acquisition attractive

---

Section 7: Integration Risk Register

Integration has its own risk register, distinct from the enterprise ERM:

| Risk | Impact | Likelihood | Owner | Mitigation | |------|--------|-----------|-------|-----------| | Key engineering talent departures | High — delays product roadmap | Medium | CPO | Retention agreements offered to 12 key engineers within 30 days; equity vesting acceleration for 2-year cliffs | | Top 5 Acquiree customers churn due to acquisition | High — $2.4M ARR | Low-Medium | CRO | Executive call within 7 days of close; multi-year contract incentives offered to top 10 | | ERP migration delay | Medium — delays consolidated financial reporting | Medium | CFO | Parallel systems for 6 months; extend migration deadline by 90 days | | Regulatory approval delay (HSR or foreign) | High — delays Day 1 planning | Low | General Counsel | Remedies pre-negotiated; contingency planning for extended pre-close period |

---

Building This Deck in Slide-Deck.io

The M&A integration template in slide-deck.io structures the IMO's core reporting document with the sections above. Update it weekly by dropping in your synergy tracker numbers, workstream RAG status, and retention survey data. The AI layout engine keeps the visual presentation consistent across updates. Export to PDF for board reporting.

Free to use. No design experience required.