AgentAlley

Skills · Business & ops

The Cold Start Problem

Unverified●25/40

Describe how you plan to launch your marketplace, app, or community and get back a scored plan with the exact fixes that will help the first users actually stick.

Originally by wondelai · MIT

Claude Code◐PartialHas SKILL.md but declares no allowed-tools — Claude Code will ask for permission each time
Cursor◐PartialPlain prose you can paste in — but no Cursor rules file
Codex◐PartialPlain prose you can paste in — but no AGENTS.md
Gemini CLI◐PartialPlain prose you can paste in
Copilot◐PartialPlain prose you can paste in — but no Copilot instructions file
npx agentalley add cold-start-problem

This command does not work yet — the CLI is still being built. Until then, use Raw in the reader below to take the file.

Who is stuck, and on what

You're launching something that only works once enough people are on it, but the early days feel like an empty room and you don't know how to fill it. You keep chasing signups when what you really need is a plan to get one small group active and coming back.

What it gives you

A written review that scores your launch plan out of 10 and lists the specific changes needed to get your first group of users active and returning.

When NOT to use it

It will not build the app, run the ads, or recruit users for you — it reviews and improves your plan only.

The whole source

No sign-in, no blur, nothing truncated
cold-start-problem/SKILL.md189 lines18.5 KBRawView on GitHub
Frontmatter — 4 properties
namecold-start-problem
descriptionStart 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.
licenseMIT
metadata author: wondelai version: "1.2.0
1---
2name: cold-start-problem
3description: '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.'B1 — Line is 791 characters — unreadable by eye
4license: MIT
5metadata:
6 author: wondelai
7 version: "1.2.0"
8---A5 — No allowed-tools declared — no way to tell what this skill may touch
9 
10# The Cold Start Problem
11 
12A 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.
13 
14## Core Principle
15 
16**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.
17 
18## Scoring
19 
20**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.
21 
22- **9-10:** Named atomic network with an instrumented magic moment, hard side solved first, repeatable tipping playbook, density/liquidity metrics, explicit ceiling and moat plan
23- **7-8:** Clear atomic network and hard-side focus, but tipping tactics are ad hoc or metrics still track totals over density
24- **5-6:** Network effects acknowledged, but the launch targets a broad market and both sides are treated equally
25- **3-4:** Generic user-acquisition plan; network thinking limited to "add invites and hope it spreads"
26- **0-2:** Big-bang launch to everyone at once, vanity signups, no hard-side strategy, no liquidity measures
27 
28## Framework
29 
30### 1. Network Effects Fundamentals
31 
32**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.B1 — Line is 506 characters — unreadable by eye
33 
34**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.B1 — Line is 534 characters — unreadable by eye
35 
36**Key insights:**
37- The three effects decouple: viral acquisition can mask dead engagement — downloads up, rooms empty
38- Metcalfe counts nodes; value lives in active connections — measure density, not totals
39- Anti-network effects are real: the dynamics that compound growth in a dense network compound emptiness in a sparse one
40- The network, not the feature set, is the moat — competitors can copy the product but not the people on it
41- Aggregate metrics lie; cut every metric by sub-network (city, team, category) to see true health
42 
43**Applications:**
44 
45| Context | Application | Example |
46|---------|-------------|---------|
47| Metric design | Replace totals with density measures | Track weekly active networks, not registered users |
48| Growth diagnosis | Attribute growth to the three effects separately | Viral factor vs. session frequency vs. conversion, each per network |
49| Strategy review | Map the product as a network of networks | A marketplace is one network per city-category pair |
50 
51See [references/case-studies.md](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.
52 
53### 2. The Cold Start: Atomic Networks
54 
55**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.
56 
57**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.
58 
59**Key insights:**
60- Smaller is better: find the minimum size at which the product works, then over-deliver for exactly that group
61- Constrain the first network hard — one company, one campus, one neighborhood, one collector niche — so density is achievable with founder-level effort
62- Define the magic moment precisely and instrument it; gate all expansion on networks reaching it
63- Killer products for tiny networks look like toys (Facebook at Harvard, eBay's collectibles) — niche optics are the cost of density
64- Flintstone the empty side: founders manually supply content, inventory, or matchmaking until the network stands alone
65 
66**Applications:**
67 
68| Context | Application | Example |
69|---------|-------------|---------|
70| Launch scoping | Pick a network, not a market | "Agents in one Austin brokerage," not "the US housing market" |
71| Activation | Define and instrument the magic moment | New member posts and gets a teammate reply within minutes |
72| Empty side | Flintstone missing supply manually | Founders personally fulfill the first 100 marketplace orders |
73 
74**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.
75 
76See [references/atomic-networks.md](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.
77 
78### 3. Solve the Hard Side
79 
80**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.
81 
82**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.
83 
84**Key insights:**
85- Identify the hard side by work done, not money paid: a few percent of users create most of the value on Wikipedia, YouTube, and most marketplaces
86- Map motivations explicitly: money (drivers, sellers), status (creators, top reviewers), utility (organizers who need the tool anyway) — each demands different product investments
87- Build pro workflows and economics for the hard side first; the easy side mostly needs a clean consumer experience
88- Subsidize the scarce side early — guarantees, bonuses, zero fees — and publish the taper so trust survives the rollback
89- Early hard-siders professionalize fast: plan power tools, analytics, and payout improvements for month three, not year three
90 
91**Applications:**
92 
93| Context | Application | Example |
94|---------|-------------|---------|
95| Marketplace seeding | Recruit and subsidize supply before demand | Guarantee cleaner earnings for eight weeks pre-launch |
96| Social or content app | Court creators with status and reach | Early-follower advantage, featuring, creator funds |
97| B2B collaboration | Give the organizer single-player value | Project tracker useful alone; inviting the team makes it better |
98 
99**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.
100 
101See [references/hard-side.md](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).
102 
103### 4. Tipping Point and Escape Velocity
104 
105**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.B1 — Line is 509 characters — unreadable by eye
106 
107**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.
108 
109**Key insights:**
110- Invite-only does three jobs at once: curates early culture, creates scarcity buzz, and imports each user's social graph
111- Subsidies are network CAC: spend to manufacture liquidity, measure cost per active network, taper on a published schedule
112- Big-bang launch is the canonical anti-pattern — fast fill, weak networks; press spikes land on emptiness and never return
113- After tipping, run the three forces as named workstreams: acquisition (viral loops, referrals), engagement (reinforcing loops, re-engagement), economic (conversion, subsidy rollback, pricing)
114- Each tipped network lowers the cost of the next: spillover awareness, a portable playbook, reusable supply relationships
115 
116**Applications:**
117 
118| Context | Application | Example |
119|---------|-------------|---------|
120| Consumer launch | Invite-only with a referral tree | Waitlist plus five invites per active user; track invite-graph density |
121| Marketplace city #2 | Pay up to manufacture liquidity | Ninety-day driver earnings guarantee, tapered as fill rate rises |
122| Post-tip growth | Staff the three forces as workstreams | Referral loop, digest re-engagement, take-rate optimization |
123 
124**Ethical boundary:** Scarcity and exclusivity must be real — fake waitlists and manufactured "limited spots" are deception, not strategy.
125 
126See [references/tipping-playbooks.md](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.
127 
128### 5. The Ceiling and the Moat
129 
130**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.
131 
132**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.B1 — Line is 542 characters — unreadable by eye
133 
134**Key insights:**
135- Plot growth as stacked S-curves; start the next curve (geography, segment, use case, product) before the current one flattens
136- CAC creep and viral fatigue are laws, not failures — plan the next channel while the current one still works
137- Watch for hard-side revolt signals: take-rate complaints, multi-homing, organized protest — the hard side leaves first and takes the network with it
138- Quality interventions — curation, ranking, verification, spam fighting, sub-grouping — are growth investments at scale, not cost centers
139- Defend against cherry-picking by over-serving your densest niches; that is precisely where a David will attack your Goliath
140- Bundling buys distribution, not devotion — it fills seats on the easy side, while depth of engagement stays with whoever holds the hard side
141 
142**Applications:**
143 
144| Context | Application | Example |
145|---------|-------------|---------|
146| Stalled growth | Diagnose which ceiling hit first | Separate saturation, CAC creep, and quality-decay churn per network |
147| Quality at scale | Fund trust and curation loops | Ratings, verification tiers, spam filters as a growth workstream |
148| Competitive defense | Hold the hard side in dense niches | Match a rival's subsidies for top sellers before they multi-home |
149 
150**Ethical boundary:** Fixing revolts and spam means addressing root causes for users — not silencing legitimate hard-side grievances with PR.
151 
152See [references/scale-ceiling-moat.md](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.
153 
154## Common Mistakes
155 
156| Mistake | Why It Fails | Fix |
157|---------|-------------|-----|
158| Launching to a market instead of a network | Users arrive scattered; nobody finds anybody | Pick one atomic network and saturate it |
159| Counting signups instead of density | Vanity totals mask empty rooms | Measure weekly active networks, fill rate, time-to-match |
160| Treating both sides equally | The hard side is the bottleneck and the flight risk | Build product and economics for the hard side first |
161| Big-bang launch | Fast fill, weak networks; hype lands on emptiness | Tip network by network with a repeatable playbook |
162| Faking scarcity or activity | Users discover the deception; trust collapses | Flintstone with real work; keep invite scarcity real |
163| Cloning network #2 before #1 is stable | Replicating a broken loop multiplies failure | Gate expansion on magic-moment and retention bars |
164| Assuming network effects strengthen forever | Spam, overcrowding, and context collapse compound too | Fund quality, trust, and curation as growth work |
165| Ignoring cherry-picking rivals | Niche players peel off your densest segments | Over-serve dense niches; defend hard-side economics |
166 
167## Quick Diagnostic
168 
169| Question | If No | Action |
170|----------|-------|--------|
171| 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 |
172| 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 |
173| 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 |
174| 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 |
175| 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 |
176| Are you measuring liquidity (fill rate, time-to-match)? | Growth optics hide network health | Add per-network density metrics to the core dashboard |
177| Do you know which ceiling will hit first? | The stall will arrive as a mystery | Model saturation, CAC creep, and quality decay now |
178| Is anything defending the hard side from rivals? | Cherry-pickers will peel off your best segments | Deepen hard-side economics and pro tooling |
179 
180## Further Reading
181 
182- [*"The Cold Start Problem: How to Start and Scale Network Effects"*](https://www.amazon.com/Cold-Start-Problem-Andrew-Chen/dp/0062969749?tag=wondelai00-20) by Andrew Chen
183- [*"Platform Revolution"*](https://www.amazon.com/Platform-Revolution-Networked-Markets-Transforming/dp/0393249131?tag=wondelai00-20) by Geoffrey Parker, Marshall Van Alstyne & Sangeet Paul Choudary
184- [*"Blitzscaling"*](https://www.amazon.com/Blitzscaling-Lightning-Fast-Building-Massively-Companies/dp/1524761419?tag=wondelai00-20) by Reid Hoffman & Chris Yeh
185 
186## About the Author
187 
188**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*.
189 

Reviews

Installed this one?Write the first review and take the Trailblazer badge.

Reviews only open after a real install, so this is empty — and we leave it empty rather than invent one.

Alternatives

Also in Business & ops
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.Business & ops · Business · MIT●····●37/40Claims Drafting: The Core Patent SkillDescribe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.Business & ops · Business · MIT●····●36/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.Business & ops · Business · MIT●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.Business & ops · Business · MIT●····●35/40