Indie Hacker Launch Checklist

Launch to an audience, not to silence. A waitlist built before the product is done is worth 10x the traffic you’ll get on launch day without one. This phase builds the engine.

The Recipe

Act as a growth marketer and lean startup strategist. I am building a new micro-SaaS / digital product and want to launch a pre-order or waitlist landing page to gauge real market demand before finalizing development.

My product idea is: [INSERT IDEA]
My target audience is: [INSERT TARGET AUDIENCE]

Please design a comprehensive landing page framework and pre-launch blueprint, including:
1. The High-Converting Hero Section: Write a punchy, benefit-driven headline, a sub-headline that specifies the exact mechanism of the tool, and a compelling Call to Action (CTA).
2. The "FOMO"/Scarcity Lever: Recommend a sustainable strategy to incentivize early signups (e.g., lifetime discount, early-bird pricing tiers, beta access tokens).
3. The 3-Email Nurture Sequence: Draft three concise, automated emails to send to waitlist signups over 2 weeks to maintain high intent, share behind-the-scenes building progress, and prep them for launch day.

Keep the copy entirely free of corporate jargon and tailored to indie hacker aesthetics (clean, direct, and human).

The three deliverables

Output	What it gives you
Hero Section	Headline + sub-headline + CTA — ready to drop into any landing page builder
FOMO Lever	A sustainable early-bird incentive that doesn’t cheapen the product
3-Email Sequence	Automated nurture over 2 weeks — keeps intent hot until launch day

The FOMO lever options (ranked by sustainability)

1. Lifetime deal — highest conversion, highest perceived value, riskiest for margins
2. Early-bird pricing tier — clean, easy to communicate, easy to close
3. Beta access tokens — works well for tools with a waitlist-gated beta

Phase 1 → Phase 2 handoff

Once your waitlist is live and collecting signups, start building Phase 2 positioning assets. You’ll need them ready before launch day arrives.

Product Hunt and Hacker News have completely different cultures. Copy-pasting the same pitch to both is how you get downvoted on HN and ignored on PH. This phase writes them separately, optimized for each community.

The Recipe

Act as an expert copywriter and launch strategist who has successfully launched multiple Top #1 products on Product Hunt and Hacker News. I am preparing my launch assets and need to optimize my positioning for the indie developer community.

My product name is: [INSERT NAME]
The core problem it solves is: [INSERT PROBLEM]
My unique angle/advantage is: [INSERT ADVANTAGE/STACK]

Please generate the following launch copy and media assets:
- Product Hunt Tagline: 3 options under 60 characters that instantly communicate the value and utility.
- The First Comment (The Maker's Story): Write a vulnerable, authentic, and compelling introductory comment detailing *why* I built this, the personal pain point that sparked it, and a special discount/offer for the Product Hunt community.
- Hacker News "Show HN" Pitch: Draft a text-based pitch optimized for the HN crowd. Ensure it focuses heavily on utility, technical implementation/architecture simplicity, and avoids aggressive, salesy marketing speak.

Platform tone differences

Platform	What the audience wants	What kills your launch
Product Hunt	Clean value prop, relatable backstory, community offer	Generic SaaS speak, no maker presence
Hacker News	Technical honesty, specific implementation detail, low hype	Marketing language, vague claims, no architecture context

The maker story formula

Product Hunt rewards vulnerability over polish. The best first comments follow this structure:

1. The personal pain — what problem were you actually experiencing?
2. The failed alternatives — what did you try first that didn’t work?
3. What you built and how long it took — specificity builds trust
4. The offer — a real discount or perk, not a “check it out”

Phase 2 → Phase 3 handoff

Before launch day, seed the communities your audience already lives in. Phase 3 is how to do that without getting banned.

Communities are the highest-ROI distribution channel for indie hackers — and the most dangerous if you do it wrong. Spam kills your reputation in communities that took years to build. This phase shows how to give value first and mention your product second.

The Recipe

Act as an organic growth hacker and community specialist. I want to seed my product inside niche communities (e.g., subreddits, Discord servers, X/Twitter circles, Indie Hackers groups) without getting banned for blatant self-promotion or spamming.

My product niche is: [INSERT NICHE]
The spaces my target audience hangs out in are: [INSERT COMMUNITIES/PLATFORMS]

Please build an organic distribution playbook containing:
- The "Value-First" Post Template: Create a template for a high-value community post that solves a common community problem using a case study or lesson learned from my building journey, where my product is only mentioned casually as the tooling infrastructure.
- 3 Cold DM/Email Swipes: Write three ultra-short, frictionless outreach templates targeting early adopters or industry micro-influencers. Focus on asking for feedback rather than asking for a sale.
- Community Guidelines Check: Give me a quick, 4-step checklist to evaluate whether a platform is safe to post to, and how to build rapport with community moderators beforehand.

The value-first post structure

A community post that works isn’t a product announcement — it’s a useful piece of content where your product is a footnote:

1. Lead with the lesson — something you learned while building that genuinely helps the community
2. Show the work — numbers, screenshots, specific details that prove it’s real
3. Mention the tool — one casual sentence: “I built [X] to solve this for myself”
4. End with a question — invites replies, signals you’re there to contribute

The cold DM rule

Ask for feedback, never a sale. “Would you be willing to try this and tell me what’s broken?” converts better than any discount code.

Phase 3 → Phase 4 handoff

With community posts scheduled and outreach sent, lock in your launch day War Room checklist. Phase 4 is the 24-hour operational guide.

Launch day is not the time to figure things out. The difference between a smooth launch and a chaotic one is a written protocol you follow before the adrenaline takes over. This phase builds that protocol for your specific stack.

The Recipe

Act as an agile operations manager and systems architect. I am launching my product today. I need an hourly "War Room Checklist" to handle the technical, administrative, and promotional chaos over the crucial first 24 hours of going live.

My launch platforms are: [INSERT PLATFORMS, e.g., Product Hunt, X, LinkedIn, Newsletter]
My technical stack is: [INSERT STACK, e.g., Next.js, Supabase, Stripe, Vercel]

Please map out a chronological 24-hour launch roadmap, specifying:
- Hour 0 (The Drop): Technical sanity checks (Stripe webhooks, production database scaling, error log tracking) and initial platform publishing sequence.
- Hours 1-6 (The Momentum Phase): Exact protocols for responding to early comments, tracking server load, and managing social media amplification loops.
- Hours 12-18 (The Global Pivot): Pushing secondary updates to account for European/Asian time zones waking up.
- Hour 24 (The Wrap): A template for a transparent "Launch Day Retrospective" post to share metrics, revenue, and major lessons learned with my audience.

The four phases of launch day

Phase	Hours	Priority
The Drop	0	Technical stability — nothing else matters if the site is down
The Momentum Phase	1–6	Engagement amplification — respond to everything, fast
The Global Pivot	12–18	Secondary push for EU/Asia time zones waking up
The Wrap	24	Retrospective post — transparency builds the next audience

Hour 0 technical checklist (always run these)

Before you hit publish anywhere:

• Stripe webhooks firing correctly in production
• Error tracking live (Sentry, Logtail, or equivalent)
• Database connection limits appropriate for burst traffic
• Vercel/hosting environment vars confirmed for production

The retrospective post (Hour 24)

The best thing you can do after a launch is write publicly about what happened — real numbers, what broke, what you’d change. This post often gets more traction than the launch itself and builds trust with future buyers.

Phase 4 → Phase 5 handoff

The first 24 hours are about acquisition. Phase 5 is about making sure those new users don’t churn before they experience the product’s core value.

Most products lose 40–60% of new users in the first week. The problem is almost never the product — it’s the onboarding. This phase builds the retention system that turns launch-week signups into long-term users and eventual advocates.

The Recipe

Act as a product manager and customer success specialist for early-stage startups. My launch week is complete, and I have a fresh influx of new users and signups. Now, I need to pivot from acquisition to retention, ensuring these users don't churn immediately.

My user metrics from launch week are: [INSERT SIGNUPS/PAID USERS OR CURRENT RETENTION STATE]

Please design a post-launch retention system featuring:
- The First-Time User Experience (FTUE): A framework to optimize my onboarding flow so users hit their "Aha! Moment" (the core value realization) within the first 2 minutes of logging in.
- The Feedback Loop Protocol: An automated mechanism to segment my users into three buckets (Active Users, Power Users, and Churned Users) and distinct email templates to send to each to extract feature requests, bug reports, or exit interviews.
- The Referral Flywheel: A simple, low-code referral or affiliate setup that rewards current users for bringing in their peers, turning my initial launch traction into a sustainable growth engine.

The three user buckets

Bucket	Definition	Email goal
Active Users	Logged in 2+ times, used core feature	Feature requests — what do they want next?
Power Users	Daily/weekly active, high engagement	Referral ask — they’re the ones who’ll convert friends
Churned Users	Signed up, never returned or cancelled	Exit interview — what went wrong?

The Aha Moment framework

The Aha Moment is the specific action inside your product where the user first feels the value. Every step between signup and that moment is friction that needs to be removed:

1. Identify the moment — what’s the one action that makes users say “ok, this is worth it”?
2. Count the steps to get there — how many clicks, forms, or decisions does it require?
3. Eliminate everything before it — can you get users to that action within 2 minutes?

Referral flywheel options (by complexity)

• Simplest: Manual referral code via ConvertKit or Gumroad — one afternoon to set up
• Mid: ReferralHero or GrowSurf — plug-and-play referral tracking
• Full: Rewardful or FirstPromoter — commission-based affiliate programs for paid products

---

Finished the 5-phase lifecycle? Ship the retrospective, read the feedback, and start Phase 1 again for your next feature or product.