Latest / The Acquisition Talk with Fexingo: Mergers, Buyouts, and Business Sales for Operators / Why the Tuck-In Merger Often Fails
Transcript
- Lucas: Let's talk about tuck-in acquisitions. The classic move: a big company buys a smaller, fast-growing business and folds it into an existing division. Sounds clean on paper. But the data says these deals fail more often than they succeed. Luna: Define 'fail' here. Do you mean the acquisition doesn't generate the returns that were projected? Lucas: Exactly. McKinsey did a study back in 2024 — looked at 400 tuck-in deals across tech, healthcare, and industrials. Two-thirds of them destroyed shareholder value within three years of closing. That's a brutal hit rate. Luna: So sixty percent of deals would have been better off not happening. That's worse than standalone acquisitions, isn't it? Lucas: Significantly worse. For standalone acquisitions — where the target operates as a separate unit — the failure rate is around fifty percent. Tuck-ins push that to sixty. And the reason is almost always the same: integration friction that kills the very thing you bought. Luna: The classic innovator's dilemma problem. You buy a nimble startup, then bury it under corporate processes. Lucas: Right. But there's a more specific mechanism at play. When you buy a company to tuck in, you're not just buying its product — you're buying its culture, its talent, its way of making decisions. And the moment you force that into your existing org chart, you risk crushing the very innovation that made the target attractive. Luna: Let's ground this in a real example. Microsoft's acquisition of LinkedIn — that was supposed to be a tuck-in into their productivity division, right? Lucas: That's a fascinating case. Microsoft bought LinkedIn for $26.2 billion in 2016. It was the largest acquisition in Microsoft's history at the time. The stated logic was to integrate LinkedIn's professional network data into Microsoft's Office and Dynamics products. But they kept LinkedIn as a largely independent unit — they didn't fully tuck it in. Luna: So they avoided the classic trap by not really tucking it in. Was that a success? Lucas: It's been a mixed bag. LinkedIn's revenue has grown nicely — it hit about $15 billion in 2024 — but the deep integration synergies that Microsoft projected, like embedding LinkedIn data into Outlook and Teams to drive sales, never fully materialized. The two systems have different data architectures, different privacy rules, different cultural approaches. Microsoft essentially got a good financial asset, not the strategic tuck-in they pitched. Luna: That actually illustrates the tension well. If you fully tuck in, you risk breaking the target. If you keep it at arm's length, you don't get the synergies. Lucas: Exactly. And that's the core tension. Now contrast that with Adobe's acquisition of Magento in 2018. Adobe bought the e-commerce platform for $1.68 billion and tucked it aggressively into Adobe Experience Cloud. Luna: Aggressively how? Lucas: They killed the Magento brand. They rebranded it as Adobe Commerce. They forced a migration from Magento's legacy codebase to Adobe's cloud infrastructure. They mandated that all new development go through Adobe's product roadmap process. On paper, that's the textbook approach to a tuck-in: full integration, no dual identity. Luna: But that also sounds like a recipe for losing the Magento developer community, which was a huge part of its value. Lucas: And that's exactly what happened. Magento had a vibrant ecosystem of third-party developers and agencies. Adobe's more centralized, enterprise-focused approach alienated many of them. By 2022, several prominent Magento agencies had pivoted to Shopify and BigCommerce. Adobe's market share in e-commerce actually declined in the mid-market segment post-acquisition. Luna: So the aggressive tuck-in preserved internal consistency but destroyed the external ecosystem. Lose-lose. Lucas: That's the pattern. McKinsey's study identified three specific failure modes. First, talent flight — the people who made the target special leave because they don't want to work in a big company. Second, cultural clash — the target's speed and risk tolerance clashes with the acquirer's processes. Third, and this is the subtle one, internal competition. Luna: Internal competition meaning the acquirer's own existing products compete with the target's products for resources and attention? Lucas: Exactly. Imagine you're a product manager at Microsoft responsible for Dynamics CRM. Then Microsoft acquires LinkedIn Sales Navigator, which is a competing tool for salespeople. Whose product gets the engineering resources? Whose sales team gets the leads? The acquirer often ends up cannibalizing its own acquisition. Luna: Is there a case where a tuck-in actually worked well? I'm thinking of Facebook's acquisition of Instagram in 2012 — that was more of a standalone, but they eventually integrated the ad tech. Lucas: Instagram is a good example of a partial tuck-in. Facebook kept the product and brand independent but integrated the advertising infrastructure. That's a smart hybrid model. Another one that's less known: Charles Schwab's acquisition of TD Ameritrade in 2020. Schwab tucked TD Ameritrade's retail brokerage into its own platform, but it kept TD's thinkorswim trading platform as a separate brand for active traders. Luna: So they preserved the differentiated asset while eliminating the back-office duplication. Lucas: Right. And that's the key strategic insight. The successful tuck-in isn't about full integration or full independence. It's about identifying which parts of the target are truly differentiated and must be protected, and which parts are redundant and can be absorbed. Most acquirers get this wrong because they start from the premise that integration must be complete. Luna: Which is driven by the synergy math. The deal only pencils out if you show big cost savings from eliminating overlapping functions. Lucas: Bingo. And that's where the fatal error happens. The cost synergies are easy to calculate — you just count the duplicate salaries you'll cut. The revenue synergies are much harder, and they're often overstated. McKinsey found that in tuck-in deals that failed, revenue synergy projections were on average three times higher than what was actually achieved. Luna: So the deal model itself is built on an illusion. No wonder the failure rate is so high. Lucas: And here's the thing — if today's conversation was useful to you, if you're someone who thinks about these deal dynamics, the way this show stays ad-free is listener support. People who get value from it chip in at buy me a coffee dot com slash fexingo. Luna: Yeah, I think that's one of those things where if you've ever been in a deal room or run a P&L, you know how rare it is to get this level of detail without a sales pitch attached. Lucas: Exactly. So if it's moved your thinking forward in some small way, that's the link. Buy me a coffee dot com slash fexingo. Just a low-key way to keep this going. Now, back to the failure modes — there's one more that's worth digging into, which is the timing trap. Luna: The timing trap — do you mean integrating too fast versus too slow? Lucas: Both, but I'm thinking specifically of the '100-day plan' mentality. Many acquirers set aggressive integration deadlines — they want to have the target fully absorbed within three months. The problem is that the target's key talent sees that clock ticking and starts updating their LinkedIn profiles before the deal even closes. Luna: So the fast integration creates a self-fulfilling prophecy. You rush to integrate, the best people leave because they feel the culture shift, and then you're left with an empty shell. Lucas: Precisely. One of the more successful tuck-in models I've seen is what private equity firms call 'slow integration with fast cultural alignment.' You take your time on the systems and processes, but you move immediately on defining the combined team's values, decision-making norms, and communication rhythms. Luna: Let's talk about a specific private equity example. Thoma Bravo is known for doing tuck-in acquisitions in the software space. How do they approach it? Lucas: Thoma Bravo has a pretty disciplined playbook. They typically acquire a platform company first, then do smaller tuck-ins into that platform. But they rarely force full integration. Instead, they keep the acquired products as separate modules within the platform, with separate engineering teams, but shared go to market. That way the target's culture stays intact while the revenue synergies from cross-selling can still be captured. Luna: So it's a modular approach rather than a melting pot. Lucas: Exactly. And the data backs it up. A 2023 study by Bain & Company looked at 200 software tuck-ins and found that deals where the acquirer kept the target's engineering team intact and independent had a 40% higher probability of hitting their three-year revenue targets. Luna: That's a huge difference. So the lesson seems to be: protect the engineering and product talent at all costs, even if it means slower integration of back-office functions. Lucas: Absolutely. The back-office integration can happen over twelve to eighteen months. But the cultural and talent integration has to be handled in the first ninety days. If you lose the key people in that window, the deal is already dead — you're just waiting for the financial statements to reflect it. Luna: What about the board's role? I imagine many boards push for quick integration because they want to see immediate EPS accretion. Lucas: That's a real tension. The CFO is under pressure to show cost synergies hitting the income statement. So they push for rapid headcount reduction and system consolidation. But the best boards understand that in a tuck-in, the value comes from the top line, not the bottom line. You're buying growth, not cost savings. Luna: Yet most deal models show cost synergies as the primary driver. That's the disconnect. Lucas: Right. And that's why I think the most important question an acquirer should ask before a tuck-in is not 'What costs can we cut?' but 'What will we do to retain the target's key people and preserve their decision-making speed?' If you can't answer that with a concrete plan, you should probably structure the deal as a standalone acquisition instead. Luna: Or don't do the deal at all. Sometimes the best M&A decision is walking away. Lucas: Exactly. And that's the note I'd leave on. The next time you hear about a big company buying a small startup and promising 'seamless integration,' ask yourself: are they protecting the thing that made the startup valuable, or are they about to crush it under the weight of their own processes?