How to Launch & Get Your First Users

Why Most Launches Fail

The "Post and Pray" Problem

The most common launch strategy among solo founders: finish the product, post it on Product Hunt and a few subreddits, tweet about it, and wait.

This is not a strategy. It's hoping.

Here's what actually happens with "post and pray":

• Product Hunt: buried on page 3, 12 upvotes (8 from friends)
• Reddit: removed by automod for self-promotion, or 3 upvotes and 1 comment saying "cool"
• Twitter: seen by your 87 followers, who are mostly other founders also launching products
• Result: 0 signups, demoralization, product abandoned within 2 weeks

The Right Mindset

A launch is not an event. It's a process. Your goal is not "go viral" — it's "find 10 people who will actually use your product and tell you what sucks about it."

The goal of your first launch:

1. Get 10-50 real users (not other founders, not your friends)
2. Learn which acquisition channel works for your specific audience
3. Collect enough feedback to make the product better

Everything else — upvotes, traffic spikes, "going viral" — is a bonus.

---

Channel Strategy: Where to Launch

The Four Channels That Actually Work

Channel Selection Matrix

Which channel you use depends on your product type:

Developer tool → Show HN first, then relevant subreddits
B2B / Productivity → Product Hunt first, then LinkedIn/Twitter
Consumer / Community → Reddit first, then Twitter
Niche professional → That specific community first, nothing else matters
AI product → Product Hunt (AI category is hot) + Show HN

---

Channel Playbooks

Show HN

What it is: Hacker News' "Show" section where makers share what they've built. The audience is developers, founders, and tech-savvy early adopters.

When to launch: Tuesday, Wednesday, or Thursday, 7-10 AM ET. Monday people are catching up. Friday afternoon nobody is reading. Weekends are quiet.

How to prepare:

1. Your title must describe what the product does, not what it is. "Show HN: I built a tool that generates weekly reports from Slack and Jira" beats "Show HN: OnePerson — an AI-powered reporting platform."

2. The first comment is everything. Before you submit, write a detailed first comment that covers:

   • Why you built this (the problem you experienced)
   • Who it's for
   • What's different from existing solutions
   • What you're looking for (feedback? users? both?)
   • Tech stack (HN loves knowing what you built it with)

3. Have the product ready. HN users will:

   • Try every feature
   • Check your pricing page
   • Read your source code if it's open
   • Point out bugs in the comments

4. Don't ask for upvotes. Don't tell your friends to upvote. HN's voting ring detection is aggressive and accurate. Organic votes only.

What to expect:

• If it hits the front page: 5,000-20,000 visitors over 2-3 days
• If it gets 10-30 upvotes: 500-1,500 visitors, still worth it
• If it gets <5 upvotes: delete and try again in 2 weeks with a better title and first comment

The traffic is nice. The comments are better. HN commenters are brutally honest and technically literate. Their feedback is worth more than the traffic.

Product Hunt

What it is: A daily leaderboard for new products. The audience is founders, product people, marketers, and early adopters.

When to launch: Tuesday, Wednesday, or Thursday. Never Monday (too many launches) or weekends (dead). Launch at 12:01 AM PT — the earlier you launch, the more time you have to collect votes.

How to prepare (start 2-4 weeks before):

1. Find a hunter or launch yourself. If you know someone with a large PH following, ask them to hunt your product. Otherwise, launch it yourself — self-launching is fine in 2026.

2. Prepare your assets:

   • Tagline (60 chars max): One sentence describing what it does and for whom
   • Description: A few paragraphs about the problem, your solution, and what makes it different
   • First comment: A personal story about why you built this
   • Images/GIFs: 3-5 screenshots or a product demo GIF (the GIF matters most)
   • Maker comment: Introduce yourself and what you're looking for

3. Line up your supporters (ethically). Reach out to 10-20 people who already know about your product and ask: "I'm launching on Product Hunt on [date]. If you find the product useful, I'd appreciate your support on launch day." Do NOT ask for upvotes. Do NOT create a "swap upvotes" group. PH detects and penalizes this.

4. Engage on launch day. Reply to every comment within minutes. Thank people for feedback. Answer questions. PH rewards engagement.

What to expect:

• Top 5 finish: 1,000-5,000 visitors, 50-200 signups
• Top 10 finish: 500-1,000 visitors, 10-50 signups
• Below top 10: 100-500 visitors, minimal signups
• Product Hunt users rarely convert to paying users. They're evaluating products, not buying them.

Reddit

What it is: Topic-specific communities (subreddits) where you can share your product if it genuinely helps the community.

When to post: Weekday mornings, US time. Check each subreddit's traffic stats on Reddit's analytics.

How to prepare:

1. Find the RIGHT subreddits. Not r/startups or r/SideProject — those are full of other founders, not users. Find the subreddits where your target users complain about their problems.

Examples:

• A tool for Notion users → r/Notion, r/productivity
• A tool for freelancers → r/freelance, r/Upwork
• A tool for teachers → r/Teachers, r/education

1. Be a community member first. Spend 1-2 weeks answering questions, commenting, being helpful. Redditors check your post history. If you only post about your product, you'll be ignored or banned.

2. Frame your post as "I made something that might help" rather than "Check out my product." Share the problem first, then the solution.

Good Reddit post structure:

Title: I got tired of [pain point], so I built [simple description]

Body:
- The problem I experienced (1-2 sentences)
- What I built to solve it (1-2 sentences)
- Who it might help
- Link
- "Would love feedback if you try it"

What to expect:

• A good post in a relevant niche subreddit (50K-200K members): 20-100 signups
• A post in r/webdev or r/programming: 0-10 signups (too broad)
• A post removed for self-promotion: if this happens, you didn't engage enough before posting

Twitter/X

What it is: A real-time platform where building in public and sharing your journey can attract users over time.

When to post: This is an ongoing strategy, not a launch-day tactic. Start posting 2-3 months before your launch.

How to prepare:

1. Build in public. Share your progress, decisions, and mistakes. People follow journeys, not products.

2. Types of content that work:

   • "I asked 20 [target users] about [problem]. Here's what surprised me."
   • "Built [feature] this week. Here's the before/after."
   • "A user told me [unexpected feedback]. Changed my entire roadmap."
   • Screenshots of early versions with commentary

3. Don't just post about your product. Reply to other people's posts about the problem space. Be helpful first, promotional second.

What to expect:

• With <500 followers: expect 0-10 signups per launch-related post
• With 1,000-5,000 followers: 10-50 signups
• Twitter is a long game. Don't expect launch-day results.

---

The Launch Week Playbook

Day -14 to -7: Preparation

• Pick your primary launch channel
• Prepare all assets (screenshots, demo video/GIF, written copy)
• If Product Hunt: set up your upcoming page and start collecting "notify me" subscribers
• If Reddit: start engaging in target communities
• Set up analytics (at minimum, know where signups come from)

Day -7 to -1: Final Testing

• Have 5 people test your product end-to-end and report every bug
• Fix critical bugs (ignore cosmetic issues, fix anything that blocks core flow)
• Write your launch posts and have someone review them
• Prepare your "first comment" or "maker story"
• Set up a simple onboarding flow (users should understand the product in 30 seconds)

Launch Day

• Post at the optimal time for your channel
• Immediately add your detailed first comment
• Stay online and respond to every comment/feedback for the first 4-6 hours
• Share the launch link with people who previously expressed interest (NOT "please upvote")
• Monitor for bugs and critical issues

Day +1 to +7: Follow Through

• Personally email every new signup within 48 hours
• Ask: "What made you sign up? What almost stopped you?"
• Track which channel brought the most engaged users (not just the most visitors)
• Fix the top 3 issues users report
• Write a "launch retrospective" to share on your secondary channel

---

Common Launch Mistakes

Mistake 1: Launching Too Early

Your product doesn't need to be perfect. But if the core flow is broken or the landing page doesn't explain what you do, wait.

The fix: Have 5 strangers try your product and watch them without helping. If 3/5 can complete the core flow, you're ready.

Mistake 2: Launching Too Late

The opposite problem. You keep adding "one more feature" and never launch. Six months go by.

The fix: Set a hard launch date 4 weeks out. Tell people publicly. The social pressure will force you to ship.

Mistake 3: Targeting Other Founders

Launching on r/startups, r/SideProject, Indie Hackers, and founder Twitter. You get upvotes and encouragement from people who will never be your customers.

The fix: Launch where your users are. If you're building for accountants, find the accountant communities. If you don't know where they hang out, return to Discovery.

Mistake 4: No Call to Action

A beautiful launch post with no clear next step. "Check it out" is not a CTA. "Sign up and generate your first report in 2 minutes" is.

The fix: Every launch post should have exactly one clear action you want people to take. Sign up. Try a demo. Join the waitlist. One action. One link.

Mistake 5: Defending Instead of Listening

HN commenter: "This is just a wrapper around GPT." You: "No it's not, we also have..." — don't do this.

The fix: When someone criticizes your product, say "Thanks for the feedback. What would make it not feel like a wrapper to you?" Feedback is a gift. Defensiveness is a waste.

Mistake 6: Launching and Leaving

You post, you get some traffic, and then you go back to building. The signups trickle to zero because nobody is actively pulling them in anymore.

The fix: Launch is the start of distribution, not the end. After launch week, dedicate 30-60 minutes daily to distribution: engage in communities, reply to relevant posts, share updates.

---

What Success Looks Like

A successful first launch is NOT:

• #1 Product of the Day
• 10,000 signups
• Going viral on Twitter

A successful first launch IS:

• 10-50 real users actively using your product
• You know which channel brought your best users
• You have a list of the top 5 things to fix or improve
• At least one user has told you "I need this" without prompting
• You have the energy and feedback to keep building

---

Launch Channel Quick Reference

---

Next Step

After launch, shift from "getting users" to "keeping users and learning from them." Move to Operations — track your metrics, reduce churn, and build what your users actually need.