TAM Tomorrow
Build for the emerging market instead of judging only today’s demand
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 97%
TAM Tomorrow reframes market analysis around the environment in which a product’s distinctive strengths will matter. Begin by documenting today’s dominant market, incumbents, and buying criteria. Then identify an emerging use case whose constraints differ materially—such as mobile devices prioritizing low power rather than desktop software compatibility. Evaluate whether the technology possesses a structural advantage under those future constraints, not merely whether it can win the current market. Look for independent signals such as customer development, enabling infrastructure, complementary products, or early contracts. Finally, work backward from the expected adoption window so the product is ready without consuming all available capital too soon. The model avoids dismissing foundational technologies because their present market is small, while treating timing and survivability as explicit requirements rather than assuming every large future vision will arrive on schedule.
Origin
The hosts derive the model from ARM’s history: its processors struggled during the Wintel PC era but became foundational when mobile computing made low power and high performance critical.
Core principles
- 01Future market structure can matter more than current market size
- 02A technology can look inferior when judged against the wrong use case
- 03Changing constraints create openings for previously marginalized products
- 04Early technical readiness matters when a new market begins scaling
- 05Correct direction without correct timing can still exhaust a company
How to run it
- 1
Map today’s market
Document the current category, dominant incumbents, customer requirements, and ecosystem lock-in. Explain why the new technology struggles under those conditions.
Pro tip Distinguish technical weakness from incompatibility with an entrenched ecosystem.
Watch out Do not assume that superior benchmark performance automatically creates customer demand.
- 2
Specify the coming shift
Name the emerging platform, behavior, or constraint that could create a different market. Describe what customers will need if that shift occurs.
Pro tip Express the shift as observable changes rather than a broad slogan.
Watch out A future market that cannot be monitored is difficult to time or validate.
- 3
Test structural advantage
Compare the technology against future buying criteria. Confirm that its strengths arise from architecture or economics that competitors cannot copy cheaply.
Pro tip Use a constraint table comparing current and future markets.
Watch out Being different is not enough; the difference must solve an important future problem.
- 4
Collect independent signals
Seek prototype users, design wins, complementary technologies, regulatory changes, or infrastructure investment that support the thesis. Require more than one signal before scaling commitment.
Pro tip A customer contract is stronger evidence than generalized market enthusiasm.
Watch out Do not count several articles repeating the same prediction as independent validation.
- 5
Work backward from adoption
Estimate when the market could scale and what capabilities must be ready beforehand. Build the minimum lead needed to enter with a mature offering.
Pro tip Use staged investments tied to external milestones.
Watch out Arriving too early can be as fatal as arriving too late.
- 6
Protect the runway
Create interim revenue, partnerships, or funding gates that let the company survive timing uncertainty. Reassess the thesis whenever expected signals fail to appear.
Pro tip Set explicit dates for continuing, narrowing, or abandoning the bet.
Watch out A compelling long-term TAM does not excuse unlimited present-day losses.
In the wild
ARM’s architecture could not overcome the software network effects around DOS, Windows, and x86 PCs. Its low transistor count and low power consumption became decisive when PDAs and mobile phones emerged, leading to the Apple Newton project and then the Nokia 6110 design.
→ A technology marginalized in the PC market became foundational to the much larger mobile and embedded-computing wave.
A startup sees little current demand for offline inference in small appliances, but observes improving models, privacy requirements, and manufacturers adding dedicated accelerators. It develops a narrowly scoped engine, secures two design partners, and expands only when production commitments materialize.
→ The company reaches the emerging market with validated technology while limiting the cost of being early.
Common mistakes
Confusing a large vision with evidence
A theoretically enormous future market is not investable until specific technological, customer, and ecosystem signals support its formation.
Ignoring survival time
A correct prediction can still fail commercially when the company runs out of capital before adoption begins.
Using today’s criteria for tomorrow’s market
Judging a new technology solely by the incumbent market can hide advantages that become decisive under different constraints.
Is it for you?
Best for
It is best for founders and investors assessing enabling technologies near a credible platform or behavior shift.
Not ideal for
It is not ideal when the future market depends only on vague speculation, lacks adoption signals, or will emerge after the company’s resources are exhausted.
From the transcript
“People make the mistake of focusing on what your TAM is today versus the much more important question of what your TAM is tomorrow.”
“But it was the TAM tomorrow of the coming mobile wave that that was the opportunity, and that was what mattered.”
“Timing, timing, timing.”
From the episode
ARM & SoftBank