add first-hand founder benchmarks section from podcast interviews
Browse files
README.md
CHANGED
|
@@ -157,6 +157,39 @@ Unlike "post on HN and pray" advice, this playbook provides **specific timing, t
|
|
| 157 |
- **Content SEO for OSS** — Documentation as SEO, tutorial content, changelog as blog posts
|
| 158 |
- **Global distribution** — Chinese developer community (Gitee, CSDN, 掘金, V2EX), Japanese/Korean developer channels
|
| 159 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 160 |
### Use Cases
|
| 161 |
|
| 162 |
- Early-stage open source project wanting its first 1,000 stars
|
|
|
|
| 157 |
- **Content SEO for OSS** — Documentation as SEO, tutorial content, changelog as blog posts
|
| 158 |
- **Global distribution** — Chinese developer community (Gitee, CSDN, 掘金, V2EX), Japanese/Korean developer channels
|
| 159 |
|
| 160 |
+
### What's New (July 2026): First-Hand Founder Benchmarks
|
| 161 |
+
|
| 162 |
+
Fresh benchmarks from founders who ran this playbook end-to-end — including numbers investors and pricing pages rarely make public.
|
| 163 |
+
|
| 164 |
+
**Open source → fundraising data chain.** One founder logged ~400 investor meetings over ~12 months for the angel round. After open-sourcing: ~6,000 stars in launch week (80% from overseas developers), 10K stars in 43 days, and an $8M Pre-A locked roughly one month after going open source (founder-reported). Two takeaways:
|
| 165 |
+
|
| 166 |
+
- Investors buy **star velocity, not absolute count** — a steep launch-week curve reframed the entire fundraising conversation.
|
| 167 |
+
- Some funds now run crawlers during due diligence to verify stars are organic. Coordinated-but-real community pushes pass; purchased stars do not.
|
| 168 |
+
|
| 169 |
+
**The Day One minimum kit.** Four assets that must exist before any promotion — nothing more:
|
| 170 |
+
|
| 171 |
+
| Asset | Bar to clear |
|
| 172 |
+
|:---|:---|
|
| 173 |
+
| One-liner website | A single sentence that says what it is |
|
| 174 |
+
| Illustrated README | 30-second value prop + a clear star CTA |
|
| 175 |
+
| One positioning article | "Open source X alternative" framing |
|
| 176 |
+
| Minimal dev docs | 4 pages is enough to start |
|
| 177 |
+
|
| 178 |
+
**6-step zero-budget cold-start SOP** (as practiced by founders, in order):
|
| 179 |
+
|
| 180 |
+
1. Study a predecessor's launch — how a comparable project actually broke out
|
| 181 |
+
2. README (per the kit above)
|
| 182 |
+
3. Publish the "open source X alternative" article
|
| 183 |
+
4. Directory submissions
|
| 184 |
+
5. DM the competitor's Twitter followers directly
|
| 185 |
+
6. Reddit
|
| 186 |
+
|
| 187 |
+
**Healthy week-1 star geography benchmark.** For a global-first launch, founders converge on: US 19–21%, China ~19–21%, top-4 EU countries 10–15% combined. The discipline behind it: **no domestic posting in week one** — home-market virality first skews the geography and weakens the "global developer adoption" signal investors read.
|
| 188 |
+
|
| 189 |
+
**Pricing test before the paid tier exists.** One founder shipped a deliberately vague pricing page with only a contact form — dozens of inquiries in 2 weeks, splitting roughly 70% free / 20% personal / 10% team (self-reported). Demand signal captured months before writing a single line of billing code.
|
| 190 |
+
|
| 191 |
+
> Source: distilled from 12 founder podcast interviews (2024–2026); figures are self-reported by the founders involved.
|
| 192 |
+
|
| 193 |
### Use Cases
|
| 194 |
|
| 195 |
- Early-stage open source project wanting its first 1,000 stars
|