The Platform-Wave Bet
Test platform dominance and standalone economics before betting on an emerging wave.
- Difficulty
- Advanced
- Time to result
- ~ongoing to results
- Steps
- 6
- Confidence
- 96%
A platform-wave opportunity requires two independent convictions: the underlying platform must become widespread enough to change behavior, and a third-party application must be able to capture substantial value on top of it. Because the correct market window may arrive years after knowledgeable observers recognize the technology's potential, founders need both early exposure and financial patience. A small, adaptable team can enter the space, learn from real users, and build intuition about where demand is moving without committing to a rigid plan. The team then watches for enabling infrastructure, distribution, customer readiness, and monetization to converge. When that window opens, it must already possess enough domain experience to ship quickly. Forethought survived long enough to pair a prepared presentation product with the mass adoption of graphical computing.
Origin
Extracted from Acquired's discussion of Forethought's long wait for graphical interfaces to mature and its eventual alignment with Macintosh and Windows adoption.
Core principles
- 01A promising technology is not necessarily a ready market.
- 02Platform adoption and application economics are separate risks.
- 03Operating in the market develops insight that desk research cannot provide.
- 04Lean teams preserve the runway needed to wait for the adoption window.
- 05The winning product must be ready when the platform becomes pervasive.
How to run it
- 1
Test Platform Dominance
Determine what must happen for the platform to become pervasive and alter user behavior. Identify measurable adoption milestones rather than relying on technical excitement.
Pro tip Separate signals from enthusiasts from evidence of mainstream workflow change.
Watch out Experts can correctly predict a technological direction while being many years early on timing.
- 2
Test Standalone Economics
Assess whether an independent application can acquire customers, monetize, and retain enough value despite the platform owner's power. Model both favorable and restrictive platform policies.
Pro tip Look for workflows where the application owns unique data, expertise, or customer relationships.
Watch out A huge platform does not guarantee a venture-scale opportunity for its applications.
- 3
Buy Learning Cheaply
Enter the market with a lean team and limited capital so that real usage can inform the thesis. Treat early products as instruments for acquiring market judgment.
Pro tip Choose experiments that reveal behavior, distribution, and willingness to pay simultaneously.
Watch out Do not mistake activity inside a niche enthusiast market for broad product-market fit.
- 4
Preserve Adaptability
Avoid commitments that prevent the company from moving toward newly viable use cases. Build reusable capabilities while remaining willing to change the product.
Pro tip Review the thesis whenever platform capabilities, pricing, or distribution change materially.
Watch out Adaptability does not mean pursuing every new feature or trend.
- 5
Recognize the Window
Watch for the moment when platform reliability, adoption, distribution, and customer demand become sufficient. Compare current evidence with the milestones defined at the outset.
Pro tip A major platform release can be the catalyst, as Windows 3.0 was for graphical applications.
Watch out Waiting for certainty can leave the market to a competitor already prepared to ship.
- 6
Scale Through the Opening
Once the window opens, focus resources on the validated product and distribute rapidly. Use the team's accumulated domain knowledge to execute faster than new entrants.
Pro tip Have the product, partnerships, and scaling plan ready before the catalytic platform event.
Watch out Continuing exploratory behavior after clear validation can waste the temporary lead.
In the wild
Forethought began pursuing graphical computing years before the mass-market window was ready. Its small PowerPoint team accumulated product knowledge on the Macintosh and remained positioned for the decisive expansion of graphical applications when a stable, widely adopted Windows release arrived.
→ PowerPoint entered the critical platform window with a mature product and became the dominant presentation application.
A two-person team builds lightweight tools across several professional AI workflows while model capabilities and enterprise policies remain unstable. It limits spending, measures repeat usage, and retains reusable integrations. When reliable multimodal models unlock one high-value workflow, it concentrates the company there.
→ The team reaches the new market before larger entrants without exhausting its runway during the exploratory period.
Common mistakes
Betting on Technology Alone
Technical inevitability does not establish when mainstream adoption will occur or whether an application can capture value.
Raising Beyond the Learning Need
Excess capital can create fixed costs and expectations that prevent a company from waiting or changing direction.
Entering Only After Certainty
A team that waits for complete validation may lack the market knowledge and product readiness needed when the window opens.
Is it for you?
Best for
It is best for founders evaluating new computing environments such as AI, spatial computing, mobile platforms, or developer ecosystems.
Not ideal for
It is not ideal for stable markets where platform adoption and monetization channels are already well understood.
From the transcript
“you sort of have to believe two things. You have to believe that that platform is gonna become super dominant, and that you know it's…”
“But you also have to believe that you can build a standalone venture scale business by just being on that platform and by being an…”
“can I only raise a little money? Can I stay super lean and nimble? And can I be first to jump onto new opportunities when…”
From the episode
PowerPoint