The market map is not a commitment — it is a set of options. The discipline is knowing which lane to enter first, which second, and which to leave on the map until the foundation can support them.
scroll ↓
[ 01 ]The market map
Entering all eight at once spreads resources too thin. The map exists to force one question: which lane first, and why?
AI Layer
Models, inference, fine-tuning, and the assistants built on top.
↳ Intense competition, real compute costs, hard differentiation.
Productivity
Writing, organizing, planning — where work actually happens.
↳ Crowded, and habits are fragile. Genuine friction reduction wins.
Communication
Messaging, voice, video, async collaboration.
↳ Severe cold-start problem. Network effects are real but hard to ignite.
Identity
Single login, unified profile, a trust signal across products.
↳ Unglamorous but foundational. Carries the heaviest trust burden.
Financial Services
Payments, invoicing, lending, and the money side of work.
↳ The most regulated lane. Compliance is a design constraint from day one.
Consumer Devices & Apps
Hardware, OS surfaces, and consumer applications.
↳ Low hardware margins and long cycles; apps scale fast but churn fast.
Developer & Infrastructure
APIs, developer tools, and cloud services.
↳ Developers evaluate reliability, docs, pricing, and commitment — ruthlessly.
Enterprise & Business Tools
CRM, HR, analytics, workflow automation.
↳ Long sales cycles and high switching costs in both directions.
[ a ]lanes on the map
[ b ]structural forces
[ c ]lane entered first
[ 02 ]Why an ecosystem can be worth more than its parts
Reduced friction
One identity across tools drops switching effort. Not cosmetic — a real economic benefit.
Shared context
An assistant that knows your documents, messages, schedule, and finances is structurally more useful than a standalone one. This compounds over time.
Cross-product distribution
Each product becomes a channel for the others — cheaper than paid acquisition, more trusted because the relationship already exists.
Bundled value
The bundle is worth more than the sum of its parts — but only when integration reduces effort rather than trapping users in complexity.
Network effects — where they genuinely exist
Messaging and marketplaces have them. Productivity tools and AI assistants don't automatically. Overstating them breeds strategic overconfidence, so we are precise.
Economies of scope
Identity, payments, and the AI stack built once serve every product. This is the genuine structural advantage of ecosystem building.
Switching costs — earned, not engineered
Valuable when data and workflows are embedded, dangerous when users feel trapped. Trust must keep being earned after the switching costs exist.
These forces activate only when the first product is retained, the second product connects to it in a way users actually notice, and the identity and data layer underneath is built with enough care that people trust it with more of their lives over time.
[ the route ]
A map is only useful
with a route through it.
[ → ]Continue reading