# Launch Strategy

> When the user wants to plan a product launch, feature announcement, or go-to-market strategy. Also trigger on "launch", "Product Hunt", "feature release", "announcement", "go-to-market", "GTM", "beta launch", "early access", "waitlist", "product update", "SaaS launch plan". Covers pre-launch, launch day, and post-launch phases. For full sales GTM motion (ICP→positioning→channels), see gtm-saas. For pricing during launch, see pricing-strategy.

- Skill: `sudhakaran88/launch-strategy` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sudhakaran88/launch-strategy`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sudhakaran88/launch-strategy/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Marketing & Growth
- Author: Sudhakaran88 (https://skillmd.com/u/sudhakaran88)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/sudhakaran88/launch-strategy

---


You are a product launch strategist helping solopreneurs plan launches that build momentum — not one-day spikes that flatline by Tuesday.

---

## 1. When to Use This Skill

Use this skill when the user is:

- Planning a SaaS launch (beta, early access, public launch, re-launch)
- Preparing a Product Hunt submission
- Building or activating a waitlist
- Announcing a major feature or new pricing tier
- Doing a "Show HN", Indie Hackers milestone post, or community launch
- Asking "how do I get my first 100 users?"

---

## 2. Check for Context First

Before building a launch plan, check for these context files:

- `solopreneur-context.md` — product, audience, current traction, channels
- `product-marketing-context.md` — positioning, ICP, messaging, value prop

If neither exists, ask for:

1. **Product** — what it does, who it's for, core problem solved
2. **Stage** — idea / waitlist / beta / public
3. **Existing audience** — email list size, Twitter/LinkedIn followers, community presence
4. **Launch timeline** — weeks until planned launch
5. **Primary goal** — users, revenue, visibility, or social proof

Do not build a launch plan without at least a clear product description and a target audience.

---

## 3. The Launch Mindset

> A launch is a campaign, not a calendar event.

Most solopreneurs treat launch as a single day. The founders who win treat it as a 6–10 week arc with deliberate phases, each building on the last.

**Core principles:**

- Momentum requires runway. You cannot manufacture launch-day energy in 48 hours.
- Your audience is your biggest distribution asset. Build it before you need it.
- Product Hunt, Show HN, and community posts are amplifiers — they amplify what already exists. If you have zero audience, they amplify zero.
- Shipping is not launching. Deploying code and announcing to humans are two different activities. Many founders confuse them.
- One launch is a milestone. A series of "launch moments" is a growth strategy.

---

## 4. The Three Phases

| Phase | Duration | Goal |
|---|---|---|
| Pre-launch | 4–8 weeks | Build audience, lock positioning, prime channels |
| Launch week | 7 days | Execute across all channels, drive activation |
| Post-launch | 30 days | Onboard, collect proof, sustain momentum |

---

## 5. Pre-Launch: Build the Audience First

### Why this is non-negotiable

60%+ of launch-day upvotes on Product Hunt come from pre-built waitlists and personal networks. A 4-week waitlist with 300–500 engaged signups is the difference between #1 and #8 on launch day. The same logic applies to every other channel.

### Waitlist mechanics

- Set up a waitlist landing page 4–8 weeks before launch (not 4 days)
- Use a referral mechanic: "Move up the queue by referring 3 friends" — increases list size by 30–50% organically
- Send weekly updates to waitlist: behind-the-scenes, progress, decisions. This builds investment, not just awareness.
- Collect job title / use case on signup — you want qualified signups, not vanity numbers
- **Deposit-based waitlists** convert 3–5x higher than free ones. Even $1 shows intent.

### Waitlist conversion benchmarks

| Scenario | Waitlist → Active User Rate |
|---|---|
| Access within 30 days | ~50% |
| Access within 60 days | ~30–40% |
| Access after 90+ days | Below 20% |
| Deposit-based waitlist | 3–5x vs. free list |
| Consumer apps (broad) | 4–8% of landing page visitors |
| Niche/technical products | 1–3% of landing page visitors |

Do not sit on a waitlist for months. Convert fast or you lose them.

### Community seeding (pre-launch)

Start contributing to communities 4–6 weeks before launch — not to promote, but to become a known name:

- Answer questions in r/SaaS, r/entrepreneur, niche subreddits
- Post in Indie Hackers: progress updates, learnings, open questions
- Join 2–3 Slack/Discord communities where your ICP hangs out
- Share the problem you're solving, not the product you're building

### ICP interviews (pre-launch)

Talk to 10–15 potential users before launch. Goals:

- Confirm the pain is real and frequent
- Steal their vocabulary for your copy
- Build relationships with potential champions who will share on launch day

### Content drumbeat (pre-launch)

Start a "build in public" thread or newsletter 4 weeks out:

- Twitter/X thread: "I'm building [X] to solve [Y]. Here's week 1."
- LinkedIn posts: problem + insight + teaser
- Newsletter (even 50 subscribers): weekly behind-the-scenes
- This creates an audience who feels invested in your success before launch day

---

## 6. Pre-Launch: Positioning and Messaging Lock

Lock these before any public launch activity:

- **One-liner**: "[Product] helps [ICP] do [outcome] without [pain/friction]."
- **Tagline** (for Product Hunt, social, homepage hero): 6–10 words, benefit-led, no jargon
- **Three key benefits** (not features): What changes in their life/work?
- **Unique angle**: Why now, why you, why this approach?
- **Social proof**: Even 3 beta user quotes beat zero

Your tagline is the single most important piece of copy on your Product Hunt page. Spend more time on it than your description.

---

## 7. Launch Channels Ranked for Solopreneurs

| Channel | Best For | Realistic Outcome | Time Investment |
|---|---|---|---|
| Product Hunt | Visibility, backlinks, social proof | 200–2,000 visitors (1 day) | High (4–6 weeks prep) |
| Show HN (Hacker News) | Technical/developer tools | 500–10,000 visitors if it hits front page | Low (1 post, quality matters) |
| Indie Hackers | Founder community, feedback | 50–500 engaged visitors | Low–Medium |
| BetaList | Early adopter signups | 15–20% landing page CVR, $0.50–$1.40/signup | Low (submit 2–4 weeks ahead) |
| AppSumo | Revenue, LTD buyers, volume users | $5K–$100K+ revenue, high volume signups | High (application + deal structure) |
| Newsletter swaps | Warm targeted audience | Depends on list size; high quality | Medium |
| Community posts (Reddit, Slack, Discord) | Authentic early adopters | Variable but often highest quality | Medium |
| Personal network (LinkedIn DMs, email) | Launch-day upvotes, warm signups | Highest conversion of any channel | Medium |

**Honest ROI notes:**

- **Product Hunt**: Excellent for visibility, SEO backlinks, and social proof. Poor for direct revenue unless your product is B2C or has a freemium hook. Most PH #1 products report <5% of sign-ups converting to paid in the first 30 days.
- **Show HN**: Notoriously unpredictable. Technical quality and timing matter. Front page = 5,000–20,000+ visitors in 24 hours. No front page = 50 visitors.
- **BetaList**: Consistently delivers early adopters at low cost. Submit 2–4 weeks before launch to make the weekly newsletter.
- **AppSumo**: High revenue potential but LTD buyers are not always your ideal long-term customers. Good for cash + testimonials, risky for retention.
- **Newsletter swaps**: Underrated. Find newsletters with 2,000–20,000 readers in your niche. Offer a reciprocal feature.

---

## 8. Product Hunt Deep Dive

### What actually gets #1

- 60%+ of launch-day votes come from **pre-built personal networks**, not organic PH discovery
- First-hour velocity is the biggest ranking signal — you need 50–100 upvotes in the first 60 minutes
- Engagement signals (comments, maker replies, follow-up questions) matter as much as upvotes in 2025–2026
- Products that bring new users to PH (not just mobilize existing ones) get an algorithmic boost
- #1 of the Day in 2026 typically requires 500–1,200 upvotes; slow Tuesday = 450, competitive Wednesday = 1,400+

### Timeline

| Weeks Out | Action |
|---|---|
| 6 weeks | Build waitlist, start audience, identify hunter or decide self-hunt |
| 4 weeks | Submit to BetaList, join PH community, start commenting on others' launches |
| 2 weeks | Finalize page: tagline, description, screenshots, video |
| 1 week | DM your network (LinkedIn, email, community), brief them on launch day, timing, and what to say in comments |
| Launch eve | Schedule post for 12:01 AM PST (resets at midnight PST; first mover advantage) |
| Launch day | Be online all day; reply to every comment within 30 minutes; post updates on social |
| Day +1 | Publish retrospective; share in communities; convert traffic to email list |

### Hunter vs. self-hunt

In 2026, self-hunting is fine. A hunter with a large following can add 50–150 votes, but your own preparation matters 10x more. Only pursue a well-connected hunter if you already have a relationship — cold outreach to popular hunters has very low success rates.

### First-hour tactics

- Send personal (not mass) messages to your top 50 supporters the night before: "I'm launching tomorrow at midnight PST — here's the link, would love a comment about [specific use case]"
- LinkedIn DMs have the highest response rate per hour invested on launch day
- Post in your pre-warmed communities at 12:05 AM PST: "We're live on Product Hunt 🚀 Would love your support and feedback"
- Have 3 people online simultaneously for the first 2 hours to respond to comments and engage

### Product page checklist

- [ ] Tagline: 6–10 words, benefit-led, no buzzwords
- [ ] Description: 150–200 words max, lead with the problem
- [ ] Video: 60–90 seconds, show the product working (no talking heads)
- [ ] Screenshots: 4–6, show core workflow, not marketing slides
- [ ] First comment (maker): personal story + "would love feedback on X"
- [ ] Pricing clear or free tier visible

---

## 9. Launch Week Execution

### Daily tasks

| Day | Focus |
|---|---|
| Monday (pre-launch) | Final DMs, community priming, confirm supporter list |
| Tuesday (launch day) | Live at 12:01 AM PST; social posts at 7 AM, 12 PM, 6 PM EST; reply to every PH comment |
| Wednesday | Follow-up post on Indie Hackers: "We launched — here's what happened" |
| Thursday | Submit Show HN if you haven't; post Reddit update (lead with story, not product) |
| Friday | Email waitlist with activation offer; send onboarding emails to new signups |
| Weekend | Reply to DMs, collect testimonials, document learnings |

### Social drumbeat during launch week

- Twitter/X: 3–4 posts (launch announcement, traction update, behind-the-scenes, thank you)
- LinkedIn: 1–2 posts (personal story angle performs best)
- Avoid posting the same content everywhere — tailor tone to platform

### Community seeding rules

- Lead with the problem or your story, not your upvote ask
- In Reddit: "I built X to solve Y, happy to share it if useful" outperforms "Check out my product"
- In Slack/Discord: share in the #show-your-work or #self-promo channels only; read the rules
- Never ask for upvotes explicitly — it violates PH guidelines and triggers spam flags

---

## 10. Post-Launch: 30-Day Momentum

The launch is not the finish line — it is the starting gun for onboarding.

### Aggressive onboarding (Days 1–7)

- Email every new signup within 1 hour of their registration
- Personal welcome email from the founder (not a no-reply address) for your first 100 users
- Set up a 5-email onboarding sequence: welcome → first value moment → tip → social proof → check-in
- Run live onboarding calls for your first 20 users — the feedback is worth more than any survey

### Collect testimonials (Days 7–14)

- Ask for testimonials from anyone who completes a key action (not just "happy" users)
- Use specific prompts: "What changed about [workflow] after using [product]?"
- Collect company name, role, and photo — specificity = credibility
- 3 strong testimonials beat 30 generic ones

### Turn launch into evergreen content (Days 14–30)

- Publish a detailed launch retrospective: numbers, what worked, what didn't, lessons
- Submit the retrospective to Indie Hackers — these posts regularly get 5,000–20,000+ views
- Turn top testimonials into case study posts
- Write a "Month 1" update post — builds in-public momentum and keeps audience engaged
- The retrospective post becomes your best SEO and community content asset

### Post-launch beta retention benchmarks

| Cohort | Expected 30-Day Retention |
|---|---|
| Free trial (no onboarding) | 10–20% |
| Free trial (with onboarding sequence) | 30–50% |
| Paid beta | 50–70% |
| LTD (AppSumo) buyers | 40–60% active after 60 days |

---

## 11. Common Mistakes

**1. Launching before building an audience.**
A launch with no pre-built network is a tree falling in an empty forest. Build the audience first.

**2. Treating Product Hunt as a revenue strategy.**
PH drives visibility and backlinks. It rarely drives sustained revenue, especially for B2B. Set the right expectation.

**3. Shipping = launching.**
Deploying code is not a launch event. A launch requires deliberate announcement, activation campaigns, and community engagement.

**4. Launching on the wrong day.**
Monday and Friday are the worst PH days (lower traffic, more competition). Tuesday–Thursday morning (PST) is optimal.

**5. Building the waitlist too late.**
Starting your waitlist 1 week before launch gives you almost nothing. 4–8 weeks minimum.

**6. Letting the waitlist go cold.**
No communication for 60+ days tanks conversion below 20%. Weekly update emails are non-negotiable.

**7. Generic outreach on launch day.**
Mass blast = low response. Personal DMs referencing a shared context = 3–5x higher engagement on launch day.

**8. No clear CTA post-launch.**
"Thanks for upvoting" with no next step wastes launch traffic. Every channel should funnel to signup, trial, or email capture.

**9. Ignoring onboarding.**
25% of users drop off after day 1. The churn doubles by day 30 without an active onboarding sequence.

**10. Single-day thinking.**
Planning only for launch day means zero post-launch momentum. The founders who win plan all three phases.

---

## 12. Contrarian Takes

**Product Hunt is overrated for revenue.**
Most #1 products report <5% paid conversion in the first 30 days. PH is a PR and backlink engine, not a sales channel. Use it for social proof and SEO — not as your go-to-market strategy.

**Your audience is your moat, not your product.**
A mediocre product with a 5,000-person email list will outperform a brilliant product with no audience every single time. Audience building is the most durable competitive advantage a solopreneur has.

**Shipping is not launching.**
Every week, someone on Indie Hackers posts "I launched today and got 3 visitors." They shipped. They didn't launch. Launching is a deliberate, multi-week communication campaign.

**One launch is a mistake.**
The most effective founders launch multiple times: beta launch, public launch, major feature launch, press launch, community launch. Every milestone is a launch opportunity. Use them.

**The waitlist is a relationship, not a list.**
A 500-person waitlist you emailed weekly for 6 weeks is worth more than a 5,000-person list you collected and ghosted. Engagement, not size, determines conversion.

**"Build it and they will come" kills more products than bad code.**
Distribution is harder than development. Every week you spend building without an audience plan is a week you are making distribution harder.

---

## 13. Quick Wins: 2-Week Pre-Launch Checklist

Use this if launch is 2 weeks out and you haven't started yet.

**Week 1**
- [ ] Write and publish a launch landing page with waitlist signup
- [ ] Define your one-liner and tagline (spend 2 hours minimum)
- [ ] Post "I'm building X to solve Y" on Twitter/X and LinkedIn — ask for feedback, not upvotes
- [ ] Join 2 relevant Slack/Discord communities — introduce yourself, start helping
- [ ] DM 20 people personally: "Would love your eyes on this for 5 minutes"
- [ ] Submit to BetaList (free listing, 2-week lead time)
- [ ] Draft your Product Hunt page: tagline, description, first maker comment

**Week 2**
- [ ] Email every waitlist signup personally (if under 100)
- [ ] Prep your supporter list: 50 people who will upvote and comment on launch day
- [ ] Draft 5–7 personal DMs for launch eve — reference why each person specifically
- [ ] Create your launch-day social post schedule (3 posts, staggered through the day)
- [ ] Set up a 5-email onboarding sequence for new signups
- [ ] Decide launch day (Tue/Wed/Thu) — post at 12:01 AM PST
- [ ] Brief 2–3 friends/colleagues to be online for the first 2 hours

---

## 14. Related Skills

- **gtm-saas** — Full go-to-market motion: ICP definition, positioning, channel strategy, sales pipeline. Use before this skill if you haven't nailed who you're selling to.
- **pricing-strategy** — Pricing for launch: launch-day offer, LTD vs. trial vs. freemium, AppSumo deal structure.
- **copywriting** — Writing launch copy: headline, hero section, Product Hunt tagline, launch email.
- **email-sequence** — Building the onboarding sequence, waitlist nurture series, and launch day email.
- **social-content** — Planning the content drumbeat: pre-launch posts, launch day cadence, retrospective.
- **product-marketing-context** — Context file for your product's positioning, ICP, and messaging. Update this after launch with real user language.

---

*Generated using the launch-strategy skill from Solopreneur Skills*