Answer

What mistakes should a solo founder avoid when trying to find my first 10 customers as a solo founder?

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

Answer 1

In terms of the mistakes that waste runway: B006 — Classify every target by network role: Connector (attracts others) / Condensator

Classify every target by network role: Connector (attracts others) / Condensator (accumulates knowledge) / Bridge (connects networks) / Gatekeeper (blocks access). Work through bridges, find condensators, avoid gatekeepers. **Tool candidates:** T066 LinkedIn Sales Nav + T060 Apollo. **Note:** Currently manual. Could be L1 with LinkedIn graph analysis, but LinkedIn API restrictions make this hard.

Source: _reference/bricks/README.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: 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 4

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 5

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 6

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

Answer 7

In terms of the mistakes that waste runway: PART V: BIZBUILDER MATCHING ALGORITHM SCHEMA

For BizBuilder to surface relevant case studies, index by these dimensions: ``` { "company": "string", "market_type": "marketplace | saas | social | consumer | b2b | content | fintech | health", "product_type": "platform | tool | app | service | hardware", "gtm_motion": "1-12 (from taxonomy)", "stage": "pre-launch | first-100 | first-1000 | scaling", "channel": "forums | community | PR | influencer | paid | organic | viral | street-team | build-in-public", "constraint_type": "no-money | no-network | no-product | no-market | geographic | regulatory", "trust_requirem…

Source: src/lib/bricks/sources/first1000-pmf-patterns-library.md