We scan new podcasts and send you the top 5 insights daily.
Trying to perfectly integrate everything before closing is an anti-pattern for serial acquirers as it kills deal flow. Instead, classify tasks into "must-do pre-close" (e.g., banking, payroll) and "can-do post-close" (e.g., vendor consolidation) to maintain speed and focus.
To maintain speed in a high-volume M&A environment, you sacrifice the luxury of sequential processes. The key is to front-load diligence by identifying the five to ten critical items that could kill a deal and immediately testing for them.
Contrary to standard M&A practice where integration begins post-close, Brad Jacobs makes immediate, unrestricted access to a target company's employees and operations a non-negotiable term upon signing. This allows his team to begin the integration process weeks or months earlier.
To maintain momentum, Cisco makes critical integration decisions—like site strategy or system consolidation—during diligence, not after close. These decisions are embedded into the final deal commitment materials, preventing post-close paralysis and emotional debates, allowing teams to execute immediately.
Many M&A teams focus solely on closing the deal, a critical execution task. The best acquirers succeed by designing a parallel process where integration planning and value creation strategies are developed simultaneously with due diligence, ensuring post-close success.
Deals fail post-close when teams confuse systems integration (IT, HR processes) with value creation (hitting business case targets). The integration plan must be explicitly driven by the value creation thesis—like hiring 10 reps to drive cross-sell—not a generic checklist.
To ensure integration is considered from the start, embed a preliminary plan directly into the business case template. This forces the deal team to define key milestones for major workstreams (e.g., branding, IT, finance) before the deal is approved, creating a solid backbone for post-close execution.
A separate Integration Management Office (IMO) creates a risky handoff. A better model for agile teams is for the Corp Dev professional who sourced and led the deal to pivot and own the integration plan post-close. This ensures the original deal thesis is carried through execution without loss of context.
To avoid post-close surprises and knowledge loss, marry diligence and integration leads before an LOI is even signed. This ensures real-world operational experience informs diligence from the start. The goal is to have a drafted integration thesis by LOI and a near-complete plan by signing, not after closing.
A process where the deal team hands off a signed transaction to a separate integration team is flawed. State Street integrates business and integration experts into the deal team from the start. This ensures diligence is informed by integration realities, timelines are realistic, and synergy assumptions in the deal model are achievable.
A detailed, rigid integration plan is fragile. A better approach is to create an "integration thesis" that sets clear "goalposts" and timelines for making key decisions. This allows for flexibility and data-informed choices (e.g., using A/B tests post-close) rather than locking into pre-deal assumptions.