Answer

What does a solo founder need before they can what distribution channels work for a bootstrapped solo founder with no marketing budget?

The prerequisites that make what distribution channels work for a bootstrapped solo founder with no marketing budget actually work for a solo founder. This page focuses on what has to be in place first for "What does a solo founder need before they can what distribution channels work for a bootstrapped solo founder with no marketing budget?" Below are 7 concrete answers drawn from practitioner playbooks, each citing the brick + source. This is a focused sub-question of "What distribution channels work for a bootstrapped solo founder with no marketing budget?".

Answer 1

In terms of what has to be in place first: Framework-as-Diagnostic Overlay

Greg's 7-tactic framework overlaid on Yuri's current infra: | Tactic | Greg's framework says | We have | Verdict | |---|---|---|---| | 1. MCP server as sales team | Publish to Smithery/MCPT/OpenTools for $0 CAC discovery | Zero — neither BizBuilder/KPDD nor Solacian have an MCP server | **REAL GAP** — but applicability depends on whether the product answers a queryable question; Solacian (Maze-dissolving AI) plausibly does, KPDD (PMF discovery) plausibly does | | 2. Programmatic SEO at 10K-page scale | Next.js + Firecrawl + AI content for "best X for Y" patterns | Zero pro…

Source: src/lib/bricks/sources/greg-isenberg-bootstrap-distribution.md

Answer 2

In terms of what has to be in place first: 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 what has to be in place first: 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 4

In terms of what has to be in place first: 6. Manual Baseline — Testing Farm & Low-Capital On-Ramp (Reshetnikova)

Source: [[reshetnikova-traffic-growth-system.md]] | Raw: [[../knowledge-env/raw/2026-05-19-reshetnikova-traffic-lecture-raw.md]] **When to use**: the operator/solopreneur has a tiny budget and no marketing team, no AI plumbing yet, or operates in RU/CIS channels. This is what §1.3/§1.5/§4.0 *automate* — the human-team version of the same loop. **Core reframe**: scaling traffic is not "spend more" — it is the output of 5 continuous background processes: (1) testing farm, (2) channel search, (3) performer hiring, (4) daily analytics, (5) daily optimization. **Manual testin…

Source: src/lib/bricks/sources/perf-marketing-playbook.md

Answer 5

In terms of what has to be in place first: Cross-cutting takeaways most relevant to social / community growth

1. **Engagement Effect levers** — layer on new use cases, reinforce the core loop, reactivate churned users. 2. **Master the hard side (creators) first** — give them tools, monetization (even small — Twitch tipping, "$50/month was a big deal"), distribution. Homegrown native creators beat imported ones. 3. **Context collapse** is the central late-stage social problem — manage with networks-of-networks (channels, groups, finstas, Stories). 4. **Moderation must be built as software** — upvote/downvote/flag/block; Reddit's governance-as-city-planning model. 5. **Overcrowding &…

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

Answer 6

In terms of what has to be in place first: PART III — THE TIPPING POINT

**Ch. 11 — Tinder (Tipping Point).** The Tipping Point = a **repeatable strategy** to launch network after network. Tinder: 2B+ swipes/day, 1M dates/week, $1B+ revenue. Dating has naturally high churn (happy couples leave). **[SOCIAL][BIZBUILDER] The USC party tactic:** the team threw an incredible birthday party for a hyperconnected friend; to get in you had to download the Tinder app (bouncer checked) — highest one-day download spike, but what mattered was it being "**500 of the right people**" — the most social, hyperconnected people, on Tinder at the same time. **95% of…

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

Answer 7

In terms of what has to be in place first: Connections

- relates-to: [[../knowledge-env/synthesized/greg-isenberg-30-step-ai-saas-playbook.md]] — same author; 30-step playbook covers full SaaS build, this inject focuses on distribution layer only - relates-to: [[../knowledge-env/synthesized/perf-marketing-playbook.md]] — extends with bootstrap-first tactics for $0 budget - relates-to: [[../knowledge-env/synthesized/gtm-engineering-flows-combined.md]] — Cody Schneider's autonomous loops are a paid-traffic complement to Greg's organic-first stack - relates-to: [[../knowledge-env/synthesized/dickerson-vibe-marketing-system-one-sit…

Source: src/lib/bricks/sources/greg-isenberg-bootstrap-distribution.md