Don't just hand an integration plan to functional leaders post-close. Involve them early in the process as co-architects. Their input is crucial for validating financial models and strategic assumptions, ensuring realistic expectations and fostering ownership of the deal's success.

Before hunting for acquisitions, the internal business owner (deal sponsor) must write a thesis answering "what problem are we solving?" This prevents reactive M&A driven by inbound opportunities and ensures strategic alignment from the start, separating the "why" from the "who."

To ensure Day 1 alignment and retain key talent, treat integration planning as a collaborative process. Share the developing integration plan with the target's leadership during due diligence. This allows them to validate assumptions, provide critical feedback, and feel like partners in building the future company, rather than having a plan imposed on them.

Combining strategy, M&A, and integration under a single leader provides a full lifecycle, enterprise-wide view. This structure breaks down silos and creates a "closed-loop system" where post-deal integration performance and lessons learned directly feed back into future strategy and deal theses, refining success metrics beyond financials.

Palo Alto Networks' M&A playbook defies convention. Instead of integrating an acquisition under existing managers, they often replace their own internal team with the acquired leaders. The logic is that the acquired team won in the market with fewer resources, making them better equipped to lead that strategy forward.

To get buy-in from skeptical, business-focused stakeholders, avoid jargon about user needs. Instead, frame discovery as a method to protect the company's investment in the product team, ensuring you don't build things nobody uses and burn money. This aligns product work with financial prudence.

During a merger, prioritize people over process. Technical integration is secondary to building trust between teams. Use simple, cultural activities like joint happy hours and "show-and-tells" about the tech stack to humanize the engineering effort and foster empathetic collaboration early on.

When acquiring a business, don't rely on a single outcome like achieving a growth target. Instead, seek assets that offer multiple ways to win. Even if the primary goal is missed, the acquired data, technology, or talent could create significant value for other business units, providing built-in insurance for the deal.

When engineering teams claimed they could build a solution themselves, Nexla's founder agreed. He then reframed the problem not as a one-time technical challenge, but as an endless, repetitive maintenance task that was not a "career growing trajectory" for talented engineers, making the "buy" decision a strategic move for the engineering manager.