Answer

What mistakes should a solo founder avoid when trying to when should a solo founder hire their first employee?

The traps that waste a solo founder's runway when trying to when should a solo founder hire their first employee. This page focuses on the mistakes that waste runway for "What mistakes should a solo founder avoid when trying to when should a solo founder hire their first employee?" Below are 7 concrete answers drawn from practitioner playbooks, each citing the brick + source. This is a focused sub-question of "When should a solo founder hire their first employee?".

Answer 1

In terms of the mistakes that waste runway: PART VI — THE MOAT

**Ch. 29 — Wimdu versus Airbnb.** If your product has network effects, your competitors likely do too. **Wimdu** — a near-exact Airbnb clone from the Samwer brothers' Rocket Internet (2011), launched with $90M funding, 400+ employees, "ten times bigger than Airbnb on paper." Airbnb was then 2.5 yrs old, 40 employees, USD-only. Wimdu scraped Airbnb listings, posed as guests to recruit Airbnb hosts, built 50,000+ listings — then **went to zero** by 2014–2018. **"All supply isn't created equal"** (Airbnb employee #17): "Wimdu's top 10% of inventory was at the bottom 10% of Air…

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 2

In terms of the mistakes that waste runway: Cross-cutting takeaways most relevant to BizBuilder (solo founders / vibe-coders seeking first traction)

1. Start with one small, dense atomic network — **never a Big Bang launch**. The first network always looks like a tiny market. Embrace unscalable, hustle-driven early tactics. 2. **Density beats raw size** ("all supply isn't created equal"). Build the Expectations Gap → exceed low expectations → high NPS → organic word of mouth. 3. **Ignore vanity metrics** — top-line counts mean nothing if users churn; quality is visible only from inside the network. 4. Pick the right entry point — **high economic value per transaction** and/or **high frequency/stickiness**. 5. **Acquisit…

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 3

In terms of the mistakes that waste runway: Conclusion — The Future of Network Effects

Uber's "War Room" was renamed the "**Peace Room**" ("Uber 2.0," 25,000+ employees, slowing growth, profitability emphasis). The Silicon Valley "circle of life": entrepreneurial employees leave big companies to seed new ones (PayPal/Google/Yahoo alumni founded YouTube, Instagram, LinkedIn, WhatsApp, Salesforce). Networked products have reinvented software and reorganized industries. **Crypto** is "one of the most important new technologies, with networks at its core" — soon "every software developer will have to think about network effects as part of building products."

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 4

In terms of the mistakes that waste runway: Introduction — Uber as the master case

Network effects are invoked thousands of times in tech with no depth, no metrics, no playbook; the book aims to be the practitioner's guide. Uber numbers: HQ 1455 Market St, SF; 20,000+ employees in under a decade; a permanent 24/7 "War Room"; NACS strategy meetings run by CEO Travis Kalanick. Lyft driver referrals "give $250 / get $250"; in West Coast undersupply TK proposed "$750/$750." Uber vs. Didi in China burned ~$1B/year on incentives; spent hundreds of millions on driver referrals, ~$1B on paid marketing. Trips: 1B (Mar 2016, 5 yrs post-launch) → 2B (Oct 2016) → 5B …

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 5

In terms of the mistakes that waste runway: PART II — THE COLD START PROBLEM

**Ch. 4 — Tiny Speck / Slack.** Tiny Speck spent 4 yrs 10 mo, raised $17M, hired 45 people on the multiplayer game **Glitch** — Butterfield: "97% who signed up would be out of there within five minutes" (leaky bucket). Relaunched as **Slack** → 20M DAU, ~1M businesses, exited to Salesforce for ~$26B, $800M+ revenue. Slack grew from an internal IRC-based "frankentool" (Slack = Searchable Log of All Conversation and Knowledge). **[BIZBUILDER]** Butterfield personally signed up 45 companies in private beta — "I just had friends at other companies" — and personally handled the …

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 6

In terms of the mistakes that waste runway: Quick-reference — named tactics and when they work/fail

| Tactic | Works when | Fails when | |---|---|---| | **Atomic network** | Pick the tiniest specific group at a specific time; build density | "Peanut-buttering" across a whole geography/industry | | **Solve a Hard Problem** | Product nails the hard side's unaddressed need (Tinder for women) | Hard side churns → degrades for everyone | | **Come for the Tool, Stay for the Network** | Tool + network tightly integrated (Dropbox folders) | Tool/network divergent → low conversion | | **Invite-Only** | Curated connected users invite connected users | Used purely for hype; or kills…

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md

Answer 7

In terms of the mistakes that waste runway: Semantic

- relates-to: [[first1000-pmf-patterns-library.md]] — both treat the 0→first-users problem; Cold Start Theory is the structural backbone, First-1000 is the pattern library; complementary, not overlapping - relates-to: [[greg-isenberg-bootstrap-distribution.md]] — distribution-first growth; Cold Start adds the atomic-network discipline beneath it - relates-to: [[bizbuilder-v1-research-instrument.md]] — BizBuilder's reason to exist (getting vibe-coders past 0 traction) IS the Cold Start Problem; this book is its product playbook - relates-to: [[perf-marketing-playbook.md]] — …

Source: src/lib/bricks/sources/andrew-chen-cold-start-problem.md