Framework
Recent funding rounds
Analyze companies that have recently secured significant investment, identifying
Framework
Unbundling
Breaking down a bundled product or service into separate, standalone offerings,
Framework
Industry timing arbitrage
Apply newly developed technology from one industry to another that hasn't yet ad
Framework
Acqui-Deaths
Identify opportunities created when large companies acquire startups, potentiall
Framework
Three-Star reviews
Find business opportunities by analyzing moderately satisfied customers' feedbac
Framework
Niche down
Focus on a highly specific market segment or customer base, becoming a specialis
I send a newsletter every week — free, no spam, unsubscribe anytime.
— Mark Twain, attributed"History doesn't repeat itself, but it often rhymes."
| Dimension | Ideal conditions |
|---|---|
| Founder profile | Intellectually curious generalists with a habit of reading industry history, patent archives, or pre-digital trade publications. You need the patience to study how things worked before the current paradigm and the technical fluency to recognize which old constraints have been eliminated. Domain outsiders with engineering backgrounds are often the best fit — they lack the industry's inherited assumptions. |
| Stage | Ideation and concept validation. This framework is most powerful when you're searching for what to build. It's less useful once you've already committed to a product direction, though it can inform pivots when your current approach stalls. |
| Market conditions | Best when a mature industry has consolidated around a single dominant paradigm for decades, creating complacency. Look for industries where incumbents are optimizing the existing approach rather than questioning whether the approach itself is correct. Sectors undergoing a major technological inflection — electrification, AI, mobile ubiquity, blockchain-based trust — are especially fertile. |
| Competitive environment | Ideal when incumbents are large, slow, and deeply invested in the current paradigm. Their sunk costs in existing infrastructure become a liability — they can't pivot to the revived approach without cannibalizing their core business. The bigger the incumbent's investment in the status quo, the wider your window. |
| Inputs needed | Industry histories, patent databases (Google Patents, USPTO), trade journal archives, museum collections, academic papers on technology transitions, interviews with retired industry veterans, and a clear map of which enabling technologies have changed since the original solution was abandoned. |
| Blind spot | What goes wrong |
|---|---|
| Nostalgia bias | You fall in love with the elegance of the historical solution and underestimate why it actually lost. Not every abandoned approach was ahead of its time — some were genuinely inferior. The Betamax myth (that the better technology lost) is itself often a myth. You must rigorously verify that the original failure was due to a constraint that has since been removed, not due to a fundamental flaw in the concept. |
| Constraint misidentification | You correctly identify that an old solution failed, but you misdiagnose why. You assume it was a technology problem when it was actually a demand problem, a regulatory problem, or a cultural problem. If the constraint hasn't actually been removed, you're repeating history rather than learning from it. |
| Ecosystem dependency | The historical solution required an ecosystem that no longer exists and would be prohibitively expensive to rebuild. Early electric cars, for instance, needed charging infrastructure — Tesla had to build the Supercharger network at a cost of billions before the revived concept could work at scale. If the ecosystem cost is too high, the revival stalls. |
| Incumbent awareness | You assume incumbents are blind to the historical approach, but they've already studied it and concluded (correctly or not) that it won't work. Worse, they may be quietly developing their own version. The historical insight is only valuable if you can act on it before the industry catches up. |
| Romanticizing simplicity | Early industry solutions were often simple because the problem was simple. The modern version of the problem may have layers of complexity — regulatory, safety, scale — that the historical solution never had to address. You can't just "add technology" to a 1910 concept and ship it in 2025. |
Airbnb applied the Narrative mental model
Airbnb applied the Scale mental model
Airbnb applied the Quality mental model
Airbnb applied the Environment mental model
Airbnb applied the Cost mental model
Airbnb applied the Prototype mental model