By patrick
Emberflow Launch Strategy
Solo founder, bootstrapped, limited budget and time. Every action must be high-leverage. No busywork.
The Emberflow Advantage
Most products have to fight for distribution. Emberflow's distribution is the product — skills get installed inside Claude Code, Cursor, Codex, and Windsurf. Every install is a publishing endpoint. Every published doc is a marketing page with your brand on it. This changes the playbook.
Your flywheel: Install skill → publish doc → share link (emberflow.ai branded) → viewer sees Emberflow → installs skill → ...
The entire launch strategy should be oriented around spinning this flywheel faster.
Phase Plan
Given you're solo and bootstrapped, collapse the five-phase model into three:
Phase 1: Seed (Weeks 1–2) — You are here
Goal: Get the first 50 real documents published by real users (not you).
| Action | Time | Details |
|---|---|---|
| Publish 5–10 showcase docs yourself | 2 hrs | Architecture docs, JSON payloads, dataset examples from real projects. These become your examples page AND proof the product works. Each one is a shareable URL |
| Personal outreach to 20 devs | 3 hrs | DM developers you know who use Claude Code/Cursor. Don't pitch — ask: "I built a thing, would you try publishing one doc and tell me if it sucks?" Frame as feedback, not marketing |
| Post in Claude Code community | 30 min | Share as a skill/tool you built. Developers who use Claude Code are your exact audience. Show a before (chat output) / after (live Emberflow doc) |
| Tweet/post your own launch thread | 1 hr | "I built a tool that publishes docs from Claude Code in one command. Here's what it looks like." Include a GIF of the workflow. Tag @AnthropicAI, @cursor_ai |
| Submit to skill directories | 1 hr | Get listed in Claude Code skill collections, MCP server lists, awesome-mcp-servers (84k stars), awesome-claude-skills (51k stars). This is free, permanent distribution |
Don't do yet: Product Hunt, Hacker News, paid ads. You need real usage data and a few testimonials first.
Phase 2: Validate (Weeks 3–4)
Goal: Reach 200+ published docs. Get 3–5 verbatim testimonials. Identify which use cases stick.
| Action | Time | Details |
|---|---|---|
| Collect feedback from seed users | 2 hrs | Short DMs: "What did you publish? Would you use it again? What's missing?" |
| Identify winning use case | — | Watch what people actually publish. Architecture docs? JSON payloads? Datasets? Double down on whatever sticks |
| Write 2–3 short blog posts | 3 hrs | SEO-targeted: "How to publish docs from Claude Code", "Share Mermaid diagrams without GitHub", "Lightweight alternative to Confluence for devs". Publish on your own blog + cross-post to dev.to |
| Reddit — targeted subreddits | 1 hr | r/ClaudeAI, r/cursor, r/ChatGPTCoding, r/webdev. Don't spam — share genuinely useful posts. "I was tired of my AI architecture docs dying in chat, so I built this" |
| Capture testimonials | 30 min | Ask 3–5 happy seed users for a one-sentence quote. Add to landing page. Even "This is so much faster than setting up a docs site" is gold |
| Set up basic analytics | 1 hr | Track: skill installs, docs published/day, unique publishers, doc views. You need these numbers for Phase 3 |
Phase 3: Launch (Weeks 5–6)
Goal: Maximum one-time visibility. Product Hunt + Hacker News on the same week.
Product Hunt
| Prep item | Details |
|---|---|
| Tagline | "Publish beautiful docs from your AI tools — one command, live link" |
| Description | Keep it short. Problem → solution → proof. "AI tools generate great docs but they die in chat. Emberflow publishes them instantly with diagrams, tables, and collaboration. One command from Claude Code or Cursor." |
| Visuals | 4–5 screenshots: (1) terminal running /ember-publish, (2) live rendered doc with diagrams, (3) JSON explorer, (4) Space with sidebar nav, (5) inline comments |
| Demo | 30-second GIF or video: describe doc → AI publishes → click link → rendered page. The speed is the message |
| First comment | Personal story: "I kept generating architecture docs in Claude Code that my team never saw. So I built Emberflow." Authentic > polished |
| Day-of | Respond to every comment. Ask commenters what they'd publish. Be present all day |
| Hunter | If you know someone with PH followers, ask them to hunt you. Otherwise self-hunt — it's fine for dev tools |
Hacker News — Show HN
| Item | Details |
|---|---|
| Title | "Show HN: Emberflow — publish docs from your AI tools in one command" |
| Post body | Technical, honest, concise. What it does, how it works, what stack it's built on. HN respects technical depth. Link to a live example |
| Timing | Tuesday–Thursday, 8–10am ET. Avoid weekends |
| Engage | Answer every question. Be technical. Share the architecture if asked |
Same-Week Amplification (free)
- Tweet thread with GIF walkthrough
- LinkedIn post (developer audience is growing there)
- Cross-post Show HN link to r/ClaudeAI, r/SideProject
- Email seed users: "We just launched on PH — if you've found it useful, an upvote helps"
Channel Strategy (ORB)
Owned (build once, compounds forever)
| Channel | Priority | Action |
|---|---|---|
| Blog / SEO content | HIGH | 2–3 posts targeting "publish docs from Claude Code", "AI documentation tool", "Mermaid diagram hosting". Long-tail, low-competition keywords |
| Examples page | HIGH | Already exists — keep adding real user-published docs as social proof |
| Changelog | MEDIUM | Public changelog signals active development. Even small updates ("Added dark mode toggle") build confidence |
| Email list | LOW for now | Add a lightweight signup on landing page. Don't invest in sequences yet — wait until you have something to sequence |
Rented (use for spikes, funnel to owned)
| Channel | Priority | Action |
|---|---|---|
| Twitter/X | HIGH | Your primary social channel for devs. Share: workflow GIFs, interesting docs people published, "TIL" moments. Build in public |
| HIGH | r/ClaudeAI (41k), r/cursor, r/ChatGPTCoding, r/webdev. Genuine participation — answer questions about AI tools, mention Emberflow when relevant | |
| Dev.to / Hashnode | MEDIUM | Cross-post blog content. Free distribution to dev audience |
| LOW | Only if you already have a developer network there |
Borrowed (other people's audiences)
| Channel | Priority | Action |
|---|---|---|
| Awesome lists | HIGH | awesome-mcp-servers (84k stars), awesome-claude-skills (51k stars), awesome-cursor. Submit PRs. Free, permanent, high-traffic |
| AI tool communities | HIGH | Claude Code Discord/forums, Cursor community, Windsurf users. Be a helpful member who also built a cool tool |
| Dev YouTubers / newsletter features | MEDIUM | After PH launch, reach out to 3–5 dev tool reviewers. "I launched this on PH, got X upvotes, here's a demo". Don't pay — offer early access or a feature |
| Podcast guest spots | LOW | Only if opportunities come naturally. Don't spend time pitching |
Content That Writes Itself
As a solo founder, you can't maintain a content calendar. But Emberflow has a unique advantage: every published doc is content.
- Feature a "Doc of the Week" from real users (with permission) on Twitter
- Screenshot interesting docs and share with commentary
- The examples page IS your content marketing — keep it fresh
- "Built with Emberflow" backlinks from user-published docs drive SEO passively
Budget Allocation (if spending anything)
| Item | Estimated Cost | Why |
|---|---|---|
| Product Hunt Ship page | Free | Pre-launch subscriber collection |
| Short demo video | $0–50 | Screen recording + basic editing. Loom or OBS is fine |
| Domain + hosting | Already covered | Railway |
| One promoted tweet | $20–50 | Boost the launch tweet to developer audience. Only on launch day |
| Custom OG images | $0 | Use the existing flame branding. Consistent og:image across all shared links |
Total suggested spend: Under $100
Everything else is time investment, not money.
What NOT to Do (Solo Founder Anti-Patterns)
- Don't build a waitlist page — your product works now. Let people use it immediately. Zero-friction first publish is your superpower
- Don't write a 10-email onboarding sequence — premature. Learn what users need first
- Don't do paid ads — you don't know your CAC, LTV, or conversion funnel yet. Burn money later when you know what works
- Don't launch on too many platforms the same day — Product Hunt + HN in the same week is the max you can handle solo
- Don't chase press/media — dev tools rarely get mainstream press. Your audience is in communities, not publications
- Don't create a Discord server yet — you can't moderate a community solo. Use GitHub Discussions or existing communities
- Don't spend time on logo/branding polish — the flame logo and orange accent work. Ship, don't polish
Success Metrics
Phase 1 (Seed) — Weeks 1–2
- 50+ docs published by non-you users
- 20+ unique publishers
- Skill listed in 2+ awesome lists
Phase 2 (Validate) — Weeks 3–4
- 200+ total docs published
- 3–5 testimonials captured
- 2–3 blog posts published and indexed
- Identified #1 use case
Phase 3 (Launch) — Weeks 5–6
- Product Hunt: Top 10 of the day (stretch: Top 5)
- Hacker News: Front page (stretch: 100+ points)
- 500+ docs published
- 100+ unique publishers
- Clear signal on what users will pay for
30-Day Post-Launch (Weeks 7–10)
- Publish comparison content: "Emberflow vs setting up a docs site"
- Add the winning use case prominently to landing page hero
- If testimonials are strong, add a social proof section to landing page
- Start thinking about pricing based on usage patterns you've observed
- Identify your top 5 power users — talk to them. They'll tell you what to build and what to charge
One-Line Summary
Seed real usage → validate with real feedback → launch for maximum one-time visibility → let the flywheel compound.