Plans bootstrapped SaaS product launches: builds waitlists, preps Product Hunt, coordinates launch week, sequences go-to-market, sustains post-launch momentum.
npx claudepluginhub whawkinsiv/solo-founder-superpowers --plugin solo-founder-superpowersThis skill uses the workspace's default tool permissions.
A launch is not a moment — it's a 6-week campaign with a peak in the middle. This skill helps you build a waitlist, coordinate launch day across multiple channels, and sustain momentum for 30 days after.
Provides Ktor server patterns for routing DSL, plugins (auth, CORS, serialization), Koin DI, WebSockets, services, and testApplication testing.
Conducts multi-source web research with firecrawl and exa MCPs: searches, scrapes pages, synthesizes cited reports. For deep dives, competitive analysis, tech evaluations, or due diligence.
Provides demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation for multi-location retailers managing 300-800 SKUs.
A launch is not a moment — it's a 6-week campaign with a peak in the middle. This skill helps you build a waitlist, coordinate launch day across multiple channels, and sustain momentum for 30 days after.
Waitlist Setup Checklist:
- [ ] Landing page live with clear value prop (see landing-page)
- [ ] Email capture with incentive ("Get early access" or "Join 500+ founders")
- [ ] Confirmation email with share mechanic ("Move up the list by sharing")
- [ ] Weekly update email to keep waitlist warm
- [ ] Social proof counter ("1,247 founders waiting")
Tools: Waitlist-specific (LaunchList, GetWaitlist) or simple email capture (ConvertKit, Buttondown).
Tell AI:
Build a waitlist landing page for [product]. Include email capture,
a "why join" section with 3 bullets, social proof counter, and a
share-to-move-up mechanic. Use [framework/stack].
You need at least 100 people who will show up on launch day. Sources:
Launch Asset Checklist:
- [ ] Product demo video or GIF (60-90 seconds max)
- [ ] 5-8 screenshots showing key workflows
- [ ] Founder story (why you built this — 3 paragraphs)
- [ ] One-liner description (under 10 words)
- [ ] Short description (2-3 sentences)
- [ ] Long description (2-3 paragraphs)
- [ ] Launch-day pricing (consider a launch discount or extended trial)
- [ ] Social media post drafts (Twitter thread, LinkedIn post)
- [ ] Email to waitlist (announcement + special offer)
- [ ] Direct messages to 20 supporters asking them to engage on launch day
Tell AI:
Write launch copy for [product]. I need:
1. A one-liner under 10 words
2. A 2-sentence description
3. A 3-paragraph description with founder story
4. A Twitter/X launch thread (5-7 tweets)
5. A LinkedIn launch post
Target audience: [ICP description]
Product Hunt is optional but high-leverage for B2B SaaS. If you do it, do it right.
Product Hunt Prep:
- [ ] Hunter lined up (someone with followers, or self-hunt)
- [ ] Tagline written (60 chars max, no buzzwords)
- [ ] 5-8 gallery images (first image is most important)
- [ ] Maker comment drafted (authentic, tell your story)
- [ ] "Launching tomorrow" posts scheduled for social media
- [ ] Email to waitlist scheduled for launch morning
- [ ] 20+ supporters committed to upvote and comment on day 1
- [ ] Responses pre-drafted for common questions
Hour-by-hour:
Product Hunt is one channel. A coordinated multi-channel launch works for any SaaS:
Day -7: Teaser post on social media. "Something's coming."
Day -3: Share a behind-the-scenes look. Screenshots or demo video.
Day -1: "Launching tomorrow" post. Email waitlist with exact time.
Day 0 (Launch Day):
Day +1 to +3: Share user reactions, testimonials, quick wins.
Day +7: "One week later" post with learnings, stats, what's next.
Day +14: Feature update based on launch feedback. Shows you listen.
Day +30: "One month in" retrospective. Share real numbers.
| Channel | Effort | Impact | Best For |
|---|---|---|---|
| Email to waitlist | Low | High | Converting warm leads |
| Twitter/X thread | Medium | High | Dev tools, B2B, indie |
| Product Hunt | High | High | B2B SaaS, tools |
| LinkedIn post | Low | Medium | B2B, professional tools |
| Indie Hackers | Low | Medium | Bootstrapped SaaS |
| Hacker News (Show HN) | Low | High (if it hits) | Technical products |
| Reddit (relevant subs) | Medium | Medium | Niche products |
| Email to personal network | Low | Medium | Any product |
| Partner cross-promotion | Medium | High | If you have partners |
If you're not ready for a public launch, run a beta:
Beta Program Checklist:
- [ ] Define beta size (10-50 users is ideal for solo founder)
- [ ] Set beta duration (2-4 weeks)
- [ ] Create feedback mechanism (Typeform, in-app widget, or just email)
- [ ] Write beta welcome email explaining what you need from them
- [ ] Schedule check-in emails at day 3, day 7, day 14
- [ ] Define "beta exit criteria" (what metrics/feedback mean you're ready)
- [ ] Plan beta-to-launch transition (discount for beta users, testimonials)
Beta users are not free users. They are partners. Treat them like advisors:
Pick ONE. Don't stack discounts.
Most founders launch, celebrate, and go quiet. The winners keep pushing:
Week 1: Share user feedback, testimonials, day-one stats. Fix critical bugs immediately.
Week 2: Ship one feature that users asked for during launch. Announce it publicly.
Week 3: Write a "lessons learned" post. Share honest numbers. Build in public.
Week 4: Transition from "launch mode" to "growth mode." Set up ongoing acquisition channels (see growth-plg, content-marketing, paid-acquisition).
| Mistake | Fix |
|---|---|
| Launching with zero audience | Spend 4-6 weeks building an audience first |
| Launching everywhere over weeks | Coordinate everything on the same day |
| Asking for upvotes only | Ask for comments and genuine engagement |
| Going silent after launch day | Plan 30 days of post-launch content |
| Waiting until it's "perfect" | Launch when core value works; polish later |
| No launch pricing incentive | Give early adopters a reason to act now |
| Treating beta users as testers | Treat them as partners and future advocates |