✍️ Essay
✓ Link checked
Free
Advanced
Why we picked it
Before you sweat which side to seed, Gurley helps you judge whether your marketplace is even structurally worth building. He lays out ten factors (fragmentation, frequency, payment flow, network effects) that separate marketplaces that snowball from ones that stay empty. It is the investor lens on why some two sided ideas never reach liquidity no matter how hard you push.
From
Above the Crowd
by Bill Gurley
20 min read
- Great marketplaces enhance a market, they do not just aggregate it
- High fragmentation on both sides makes a marketplace more defensible
- Being in the payment flow is far stronger than sitting outside it
Open
abovethecrowd.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
This is the constructive version of your strategy: use a single feature or channel to pull people in cheaply, then give them a reason to stay that you actually control. Dixon shows how OpenTable and others used a tool to reach critical mass, then built the durable relationship on top. It reframes platform reliance as a first step, not a resting place.
From
cdixon.org
by Chris Dixon
- Use the cheap channel to acquire, then earn the ongoing relationship.
- The tool gets the first users, the owned relationship keeps them.
- Plan your second act before the first channel dries up.
Open
cdixon.org →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Chen watched a whole generation of startups build on Facebook's platform and then get squeezed as the platform protected itself. He explains why a platform is structurally motivated to keep any app from getting too big, and how free distribution quietly turns expensive. It is a clear, first hand account of the exact trap you are describing.
From
andrewchen.com
by Andrew Chen
- Platforms will not let you become more valuable than they are.
- Cheap early distribution gets crowded and costly over time.
- Treat platform reach as rented, never owned.
Open
andrewchen.com →
✍️ Essay
✓ Link checked
Free
Beginner
Why we picked it
This is the canonical argument that you do not need a mass market to build something real, you need a small number of people who deeply want what you make. It is the cleanest way to see that a niche is not the same as being too small, because 1,000 people who buy everything you make is a business, while 100,000 people who half-care is not. Read it as a starting point for reframing what 'big enough' actually means.
From
The Technium (kk.org)
by Kevin Kelly
~15 min read
- A viable audience can be tiny if the fans are true: roughly 1,000 people spending about 100 dollars a year is a 100,000 dollar living.
- Depth of relationship beats raw headcount, so the question is not how many people know you but how many will actually pay.
- The math only works when you own the direct relationship, without gatekeepers taking most of each sale.
Open
kk.org →
✍️ Essay
✓ Link checked
Freemium
Intermediate
Why we picked it
Ben Thompson's framework explains why the sharpest modern businesses give the product away and win by owning the demand side, then monetise the layer beneath. It reframes your question: the free product is not charity, it is how you aggregate users and gain leverage over suppliers. Read the anchor essay first, then follow the linked pieces (Defining Aggregators, The FANG Playbook) for worked examples.
From
Stratechery
by Ben Thompson
- Old businesses won by controlling supply, aggregators win by controlling demand, which is why free-at-the-front is a strategy, not a giveaway.
- Zero marginal cost plus the best user experience creates a virtuous cycle that pulls in both users and suppliers.
- Once you see where the demand pools, you can reason about which layer beneath it is actually worth money.
Open
stratechery.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
Jin makes the case that the durable way to build on platforms is owning your audience, your monetization, and your direct relationships rather than renting attention. It is a useful lens for turning platform driven reach into something you keep. Good for thinking about how to convert followers into customers you control.
From
andrewchen.com (guest essay)
by Li Jin
- Build direct relationships, not just an audience on a platform.
- Own your monetization instead of depending on platform payouts.
- Direct ties are harder for a platform to strip away.
Open
andrewchen.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
This piece gives you a simple spectrum for judging how exposed you are, using the Zynga and Facebook story as the cautionary case. It helps you honestly rate your own dependency instead of pretending it is fine. Practical for deciding how urgently you need an owned channel.
From
Entrepreneur
by Tiger Henderson
- Rate your dependency on a spectrum, do not wave it away.
- The more the platform owns the user, the higher your risk.
- Zynga's collapse shows what full dependency can cost.
Open
entrepreneur.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
A clean, structured guide to spotting where your platform exposure lives and building a more resilient business around it. It reads like a checklist you can run against your own company today. Useful when you want to move from vague worry to a concrete assessment.
From
Stripe
- Map every platform your revenue quietly depends on.
- Diversify channels before any single one turns against you.
- Resilience comes from owning the customer connection.
Open
stripe.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
An investor's short, blunt take on why platform risk makes a company harder to back and how founders can reduce it. It helps you see your dependency the way a skeptical outsider does. A quick read that sharpens how you talk about and manage the risk.
From
itamarnovick.com
by Simeon Simeonov
- Investors discount businesses that lean on one platform.
- Reduce risk by owning distribution and customer data.
- Name the risk early instead of hoping nobody notices.
Open
itamarnovick.com →
✍️ Essay
✓ Link checked
Free
Intermediate
Why we picked it
This widens the question from data and code to the real issue: what does it mean to build your livelihood on ground you do not own. Frederick draws a sharp line between a thin add-on the platform can copy or crush at will and a thick product that solves a deep enough problem to survive on its own, which is the honest test for anything you build on Airtable, Bubble, or any hosted tool. Read it as a way to reframe your bet, not a rule that says never build on a platform.
From
Medium (Ryan Frederick)
by Ryan Frederick
6 minute read
- A thin wrapper that fills an obvious gap is the platform's to take back the moment it wants to; a thick product that owns a hard problem is far harder to displace.
- Platform dependency is a spectrum, not a yes/no, so the real question is how much of your value would survive if the platform changed the rules tomorrow.
- Owning the customer relationship and the core logic, even while renting the infrastructure, is what keeps you in charge of your own business.
Open
ryanfrederick.medium.com →
📄 Article
✓ Link checked
Free
Beginner
Why we picked it
The full, sourced account of how a single API pricing change killed thriving third party apps like Apollo in a matter of weeks. It is the clearest recent example of the exact scenario you fear, with dates and numbers attached. Read it as a case study, not a theory.
From
Wikipedia
- One pricing change ended years of work almost overnight.
- A 30 day window left no time to rebuild the business model.
- Users loved the apps, but the platform held all the control.
Open
en.wikipedia.org →
📄 Article
✓ Link checked
Freemium
Advanced
Why we picked it
This is the strategic backbone: how platform businesses take power from traditional pipeline businesses by orchestrating a community and owning the interactions. Understanding the model tells you why the platform behaves the way it does, and where a dependent business can still create value. Denser and more academic, but foundational.
From
Harvard Business Review
by Marshall Van Alstyne, Geoffrey Parker, Sangeet Paul Choudary
- Platforms win by controlling interactions, not resources.
- The community, not your product, is the platform's real asset.
- Know the model you are a supplier inside of.
Open
hbr.org →
📖 Book
✓ Link checked
Paid
Intermediate
Why we picked it
Once you accept that you have to define two customers, you need a deeper model of how the two sides pull on each other, and this is the book that laid the academic and practical groundwork for exactly that. Parker and Van Alstyne effectively founded the theory of two-sided networks, and Choudary translates it into practical platform design, so you get both the why and the how of balancing producer and consumer profiles. Read it after the shorter pieces, when you want the full framework rather than a quick tactic.
From
W. W. Norton
by Geoffrey G. Parker, Marshall W. Van Alstyne, Sangeet Paul Choudary
Book (about 350 pages)
- A platform serves distinct producer and consumer roles, and you have to design a clear profile and value proposition for each rather than treating them as one market.
- The two sides create value for each other through network effects, so a decision about one side (pricing, curation, quality) directly reshapes who your ideal customer on the other side is.
- Governance and quality control on the harder side are what keep a marketplace liquid as it scales, not just raw growth.
Open
amazon.com →
📄 Article
✓ Link checked
Free
Intermediate
Why we picked it
A customer acquisition playbook that helps you commit to a growth lane and get world class at it, backed by case studies. It is useful for turning scattered platform reliance into a deliberate acquisition strategy plus a plan to convert those users. Concrete frameworks, not platitudes.
From
First Round Review
by Dan Hockenmaier, Lenny Rachitsky
- Commit to a lane instead of chasing every channel.
- Great acquisition still needs an owned retention engine.
- Study companies that mastered one channel, then diversified.
Open
review.firstround.com →
Why we picked it
Written for small builders, this walks through real cases (Reddit, Twitter, and Meta API changes) where a pricing or policy shift gutted a business overnight. It is close to the ground and matches the scale most early founders operate at. Good for seeing the same pattern repeat across platforms.
From
Micro SaaS Bytes (Medium)
by Mohit Rathore
- API pricing changes can erase margins in one announcement.
- Small builders feel platform shifts fastest and hardest.
- Keep an exit route and an owned channel ready in advance.
Open
medium.com →
Why we picked it
The definitive playbook for network and community-led products, drawn from Andrew Chen's a16z experience and interviews with Slack, Uber, Tinder, Airbnb and more.
From
Harper Business
by Andrew Chen
Book (~368 pages)
- Build the smallest self-sustaining 'atomic network' before trying to scale.
- Focus on the hard side of the network and give it a magic moment.
- Networks are anti-viral until they cross a density threshold, so start narrow.
Open
coldstart.com →
