Loading
Start and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-side
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add wondelai/skills --skill cold-start-problem -a cursor -y
Start and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
Start and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
A framework for starting and scaling products that live or die by network effects — marketplaces, social apps, messaging, and collaboration tools — distilled from Andrew Chen's The Cold Start Problem. Use it to launch products that are worthless until other users show up, to sequence growth network by network, and to navigate the five stages: the cold start, the tipping point, escape velocity, hitting the ceiling, and the moat.
Network effects start as a liability, not an asset. Value lives in connections between users, and on day one there are none — the same force that makes a dense network unstoppable makes an empty one useless. You don't escape by launching to a market; you escape by building one tiny, complete, self-sustaining network at a time, solving its hard side first, then tipping adjacent networks with a repeatable playbook until the market follows.
Goal: 10/10. Rate launch plans and growth strategies for networked products 0-10 against the principles below. Report the current score and the specific changes needed to reach 10/10.
Core concept: A networked product connects people with each other — buyers with sellers, creators with audiences, coworkers with coworkers — and becomes more valuable as the right people join. Network effects come in three distinct forms: the acquisition effect (the network pulls in its own new users), the engagement effect (more users make each session more valuable), and the economic effect (density improves monetization and unit economics). A product can be strong in one and weak in the others.
Why it works: Treating "network effects" as a single magic property hides where growth actually comes from and where it breaks. Metcalfe's law (value grows with n²) is an oversimplification — it counts nodes, not active, relevant connections, and a million scattered users can be worth less than five thousand in one dense community. Every large network is really a network of networks: Uber is hundreds of city-level markets, Slack is millions of team-sized networks. Density and quality of each sub-network beat raw user counts.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Metric design | Replace totals with density measures | Track weekly active networks, not registered users |
| Growth diagnosis | Attribute growth to the three effects separately | Viral factor vs. session frequency vs. conversion, each per network |
| Strategy review | Map the product as a network of networks | A marketplace is one network per city-category pair |
See references/case-studies.md for three end-to-end worked scenarios — a B2B tool finding its atomic network, a services marketplace seeding one city, a social app recovering from a big-bang launch — when you want a full example to model a plan on.
Core concept: An atomic network is the smallest network that is stable and self-sustaining — just enough of the right people that the product delivers its core value and the group keeps returning on its own. Slack needs roughly three users inside one team, Zoom needs two, a marketplace may need a single zip code or category. Pick a network, not a market, and build the killer product for that tiny group — even when it looks unscalably niche.
Why it works: Networks succeed or fail one network at a time. A product that works completely for fifty people in one community proves the loop and can be replicated; one that half-works for fifty thousand scattered users proves nothing and dies of emptiness. Tiny complete networks also expose the magic moment — the experience that shows the network working (the car arrives, the teammate replies) — which becomes the activation bar for every network that follows.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Launch scoping | Pick a network, not a market | "Agents in one Austin brokerage," not "the US housing market" |
| Activation | Define and instrument the magic moment | New member posts and gets a teammate reply within minutes |
| Empty side | Flintstone missing supply manually | Founders personally fulfill the first 100 marketplace orders |
Ethical boundary: Flintstoning means doing real work manually behind the scenes — never fabricating fake users, reviews, or activity that deceives the people on the network.
See references/atomic-networks.md when scoping the first launch — it has the 5-step minimum-size derivation, the actor/action/response/time magic-moment template, instrumentation and zero-rate steps, honest-flintstoning rules, single-player fallbacks, and a launch checklist.
Core concept: Every network has a hard side — a small minority who do disproportionate work and are disproportionately hard to attract and keep: sellers, creators, drivers, hosts, organizers. They have better alternatives and higher expectations, and without them the easy side finds an empty product. Understand their motivations — money, status, utility — and build the product and economics for them first.
Why it works: The easy side shows up when the hard side delivers value, not before. A content app without creators, a marketplace without supply, a collaboration tool without the organizer who sets it up — all are empty rooms. "Come for the tool, stay for the network" is the classic hard-side wedge: a single-player tool (Instagram's filters, OpenTable's reservation book) recruits the hard side one by one before any network exists, and then the network makes leaving unthinkable.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Marketplace seeding | Recruit and subsidize supply before demand | Guarantee cleaner earnings for eight weeks pre-launch |
| Social or content app | Court creators with status and reach | Early-follower advantage, featuring, creator funds |
| B2B collaboration | Give the organizer single-player value | Project tracker useful alone; inviting the team makes it better |
Ethical boundary: Hard-side economics must be honest — present launch subsidies as temporary incentives, and never build people's livelihoods on terms you plan to quietly degrade.
See references/hard-side.md when designing supply-side acquisition and economics — it maps money/status/utility motivations to product investments and details three named playbooks (tools-first, content-first, subsidies).
Core concept: Once the first atomic network works, growth becomes a repeatable playbook for tipping the next network, and the next — each launch cheaper than the last. The core tipping tools: invite-only mechanics (curation + scarcity + social proof), paying up for launch (subsidies, guarantees, pre-committed supply), and influencer or community seeding. After tipping, escape velocity is not a milestone but an operating model: continuously amplifying the acquisition, engagement, and economic effects.
Why it works: Invite-only launches look exclusionary but build density by design — every invitee arrives with at least one connection already inside, the network copies in along real social graphs, and scarcity manufactures the social proof that pulls the next cohort. Paying up converts money into density, the one asset rivals can't copy. Big-bang launches do the opposite: Google+ pushed hundreds of millions of signups into empty rooms, and the weak networks never retained.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Consumer launch | Invite-only with a referral tree | Waitlist plus five invites per active user; track invite-graph density |
| Marketplace city #2 | Pay up to manufacture liquidity | Ninety-day driver earnings guarantee, tapered as fill rate rises |
| Post-tip growth | Staff the three forces as workstreams | Referral loop, digest re-engagement, take-rate optimization |
Ethical boundary: Scarcity and exclusivity must be real — fake waitlists and manufactured "limited spots" are deception, not strategy.
See references/tipping-playbooks.md when planning network #2 onward — invite-only and referral-tree mechanics, paid-launch and supply pre-commitment tactics, market selection, anti-patterns, and the liquidity metrics to gate on.
Core concept: Growth always stalls. Rocketship curves are a sequence of S-curves, and each flattens against a ceiling: market saturation, channel degradation (CAC creep, banner blindness, viral fatigue), hard-side revolts, and quality collapse at scale — spam, overcrowding, context collapse. The moat is the network itself: defend the hard side, expect rivals to cherry-pick your densest segments, and remember that bundling fills the easy side but rarely wins the hard side.
Why it works: Every acquisition channel decays as audiences habituate and competitors pile in — the first banner ads clicked through at double-digit rates; today's average is a fraction of a percent. Networks also degrade from within: scale attracts spam and collapses the intimate contexts that made early networks valuable, so quality work becomes growth work. And competition between networks is asymmetric: challengers win by applying atomic-network discipline to one underserved niche — which is exactly how incumbents get unbundled.
Key insights:
Applications:
| Context | Application | Example |
|---|---|---|
| Stalled growth | Diagnose which ceiling hit first | Separate saturation, CAC creep, and quality-decay churn per network |
| Quality at scale | Fund trust and curation loops | Ratings, verification tiers, spam filters as a growth workstream |
| Competitive defense | Hold the hard side in dense niches | Match a rival's subsidies for top sellers before they multi-home |
Ethical boundary: Fixing revolts and spam means addressing root causes for users — not silencing legitimate hard-side grievances with PR.
See references/scale-ceiling-moat.md when growth stalls or a rival appears — it runs the three forces as growth workstreams, diagnoses which ceiling hit first, and details quality interventions and cherry-picking defense at scale.
| Mistake | Why It Fails | Fix |
|---|---|---|
| Launching to a market instead of a network | Users arrive scattered; nobody finds anybody | Pick one atomic network and saturate it |
| Counting signups instead of density | Vanity totals mask empty rooms | Measure weekly active networks, fill rate, time-to-match |
| Treating both sides equally | The hard side is the bottleneck and the flight risk | Build product and economics for the hard side first |
| Big-bang launch | Fast fill, weak networks; hype lands on emptiness | Tip network by network with a repeatable playbook |
| Faking scarcity or activity | Users discover the deception; trust collapses | Flintstone with real work; keep invite scarcity real |
| Cloning network #2 before #1 is stable | Replicating a broken loop multiplies failure | Gate expansion on magic-moment and retention bars |
| Assuming network effects strengthen forever | Spam, overcrowding, and context collapse compound too | Fund quality, trust, and curation as growth work |
| Ignoring cherry-picking rivals | Niche players peel off your densest segments | Over-serve dense niches; defend hard-side economics |
| Question | If No | Action |
|---|---|---|
| Can you name your first atomic network (who, where, how many)? | You're launching to a market, not a network | Constrain by geography, org, or interest until self-sustaining |
| Is the magic moment defined and instrumented? | You can't tell live networks from dead ones | Define it, measure it per network, gate expansion on it |
| Do you know who your hard side is and why they stay? | Supply churns and the easy side follows it out | Map money/status/utility motivations; build for them first |
| Does the product deliver value to its very first user? | Pure chicken-and-egg with no wedge | Add come-for-the-tool value or flintstone the gap |
| Is there a written playbook for tipping the next network? | Every launch is an expensive one-off bet | Codify invites, subsidies, and seeding from launch #1 |
| Are you measuring liquidity (fill rate, time-to-match)? | Growth optics hide network health | Add per-network density metrics to the core dashboard |
| Do you know which ceiling will hit first? | The stall will arrive as a mystery | Model saturation, CAC creep, and quality decay now |
| Is anything defending the hard side from rivals? | Cherry-pickers will peel off your best segments | Deepen hard-side economics and pro tooling |
Andrew Chen is a general partner at Andreessen Horowitz, where he invests in consumer technology, and previously led the rider growth team at Uber. His long-running essay series on growth, metrics, and network effects — read across the tech industry — became the foundation for The Cold Start Problem.