To get honest customer feedback during diligence, IFS has the target's CEO make warm introductions to a third-party firm under the guise of a routine "operational feedback session." This allows the acquirer to assess churn risk and product sentiment without revealing the M&A context.
For certain acquisitions like Poker, IFS deliberately avoids full integration to retain the target's agile, entrepreneurial culture. Instead, they use product connectors and provide access to parent company resources, allowing the startup to maintain its dynamism while leveraging scale.
To prevent knowledge gaps between deal execution and integration, IFS makes the same internal expert responsible for a specific workstream (e.g., product, GTM) during commercial diligence and the subsequent integration phase, creating end-to-end accountability.
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.
The rapid evolution of AI means traditional private equity M&A timelines are too slow. PE firms and their portfolio companies must now behave more like venture capitalists, acquiring earlier-stage, riskier AI companies to secure necessary technology before it becomes unaffordable or obsolete.
When owned by multiple private equity firms with varying exit horizons, IFS mitigates conflicting priorities by ensuring acquisition targets, even strategic ones, have a robust business plan to achieve profitability within 18 months to two years.
IFS uses a framework of four deal archetypes—Product Bolt-on, Customer Migration, Market Entry, and New Strategic Platform—to clarify the investment rationale and pre-determine the integration strategy for every acquisition, ensuring strategic alignment from the start.
To retain the culture of an acquired Silicon Valley startup, IFS made practical exceptions to corporate policy. Allowing the team to keep their MacBooks and use specialized development tools, while seemingly minor, was crucial for preserving their preferred, fast-paced way of working.