What is Acqui-Deaths?

Identify opportunities created when large companies acquire startups, potentially leading to a loss of innovation or focus in the acquired company's original product or service.

Which companies use Acqui-Deaths?

Companies that exemplify the Acqui-Deaths framework include Instagram - Acquired by Facebook, maintaining its brand but losing independence, Waze - Bought by Google, integrated into Google Maps while keeping some distinct features, LinkedIn - Purchased by Microsoft, retaining its identity but aligning more closely with Microsoft's ecosystem.

How do you use Acqui-Deaths?

To apply Acqui-Deaths, start by understanding the key components of the framework and mapping them to your specific business context. The framework works best when used systematically as part of a broader strategic analysis.

When should you use Acqui-Deaths?

Acqui-Deaths is most useful when evaluating strategic options, analysing competitive dynamics, or making resource allocation decisions. It provides structure to what might otherwise be an intuitive or ad-hoc process.

Acqui-Deaths: Framework Explained

Acqui-Deaths: Framework Explained | Faster Than Normal

Acqui-deaths describe the phenomenon where a large company acquires a startup and the acquired product slowly dies — not through malice, but through integration friction, talent dispersal, and strategic deprioritization. For founders and investors, each acqui-death creates a vacuum: an underserved user base, a validated demand signal, and a window to build the replacement.

Section 1

How It Works

The cognitive shift is this: instead of viewing a major acquisition as the end of a competitive story, you treat it as the beginning of a new opportunity. When Google acquires a beloved productivity tool, or when Meta absorbs a social app, the acquiring company almost always optimizes the acquired product for its own strategic priorities — not for the users who loved it in the first place. Features get deprecated. Roadmaps get redirected. The founding team earns out and leaves. What remains is a shell wearing the original's brand.

The mechanism is predictable. Large acquirers buy startups for one of three reasons: talent (acqui-hire), technology (IP absorption), or competitive elimination (removing a threat). In all three cases, the acquirer's incentive is to extract value from the acquisition and redirect it toward the parent company's core business. The acquired product's original users are, at best, a secondary consideration. At worst, they're an afterthought. This creates a reliable pattern: acquisition → integration → degradation → user frustration → exodus.

The underlying principle is that large companies are structurally incapable of maintaining the innovation velocity of the startups they acquire. The startup's speed came from a small team with singular focus, existential urgency, and direct accountability to users. Post-acquisition, that team reports into a product org with different KPIs, different timelines, and different definitions of success. A feature that took two weeks to ship at the startup now takes two quarters inside the acquirer. The product doesn't die overnight — it dies by a thousand committee meetings.

This creates a specific, exploitable opportunity. The acquired product's user base has already been educated on the value proposition. They know what they want. They're actively looking for an alternative. Your job is to be that alternative — to rebuild the thing they loved, without the corporate overhead that killed it.

"We don't have a monopoly. We have market share. There's a difference."
— Steve Ballmer, former Microsoft CEO

Acqui-Deaths

Continue exploring

How It Works

This connects to...

Continue exploring

Get playbooks like this in your inbox

How It Works

This connects to...