How to Get Your First 100 Users for Indie Hacker Projects
Most indie hackers build first, then scramble for users. Here's why that's backwards -- and the exact frameworks, prompts, and strategies to get your first 100 users before you waste months building something nobody wants.
The Problem: "Build First, Market Later" Is Killing Your Projects
You've probably experienced this:
- Spent 3 months building a "perfect" MVP
- Launched to... crickets
- Realized you have no idea how to get users
- Project dies in obscurity
The truth? 95% of side projects fail not because of bad code, but because founders never figured out distribution.
The Distribution-First Framework
Instead of asking "What should I build?", start with "How will this get its first 100 users?"
The 3 Questions Every Indie Hacker Must Answer BEFORE Building
- Where do my target users already hang out? (Reddit, Twitter, Discord, newsletters?)
- What problem are they actively complaining about? (Search for pain points in communities)
- How will I reach them without a marketing budget? (Content, community, or product-led?)
These questions shape everything: what you build, how you build it, and which distribution channel you optimize for.
The Community-First Launch
Best for: B2C tools, developer tools, productivity apps
Step-by-Step:
1. Identify 5 communities where your target users are active
- Reddit subreddits (r/SideProject, r/indiehackers, r/SaaS)
- Discord servers
- Twitter communities
- Slack groups
2. Become a valuable member FIRST (2-4 weeks before launch)
- Answer questions
- Share insights (not your product)
- Build genuine relationships
3. Soft launch with value
- Share your journey ("I'm building X because I struggled with Y")
- Ask for feedback, not sales
- Offer early access to engaged community members
Lovable Prompt Template for Community-First Apps:
Build a [type of app] that solves [specific problem] for [target audience]. DISTRIBUTION REQUIREMENTS: - Include a "Share to Twitter" button with pre-written copy - Add a "Invite friends" referral system with tracking - Create an embeddable widget for community sharing - Build a public roadmap page for community feedback COMMUNITY FEATURES: - User profiles with public activity - Upvoting/commenting on feature requests - Integration with Discord for notifications
The SEO-First Launch
Best for: Tools, calculators, directories, content-heavy products
Step-by-Step:
1. Find low-competition keywords your target users search for
- Use tools like Ahrefs, Ubersuggest, or even Google autocomplete
- Target "how to [problem]" and "[solution] for [audience]"
2. Build SEO landing pages INTO your MVP
- Don't add them later -- bake them in from day one
- Each page targets one keyword cluster
3. Create 10 content pieces before launch
- Blog posts answering common questions
- Comparison pages (Your Tool vs. Alternatives)
- Tutorial content showing your tool in action
Lovable Prompt Template for SEO-First Apps:
Build a [type of app] for [target audience]. SEO REQUIREMENTS: - Generate 5 SEO-optimized landing pages targeting: 1. "[primary keyword] tool" 2. "how to [solve problem]" 3. "[competitor] alternative" 4. "best [category] for [audience]" 5. "[problem] calculator/checker" - Each page must include: - H1 with primary keyword - Meta description under 160 characters - FAQ section with schema markup - Internal links to other pages - Clear CTA above the fold TECHNICAL SEO: - Sitemap.xml generation - robots.txt configuration - Open Graph tags for social sharing - Page speed optimization
The Product Hunt Launch
Best for: Polished MVPs, tools with visual appeal, B2B SaaS
The 30-Day Product Hunt Playbook:
Days 1-14: Pre-Launch
- Build your Product Hunt profile
- Connect with 50+ hunters and makers
- Prepare all assets (logo, screenshots, demo video)
- Write your tagline (under 60 characters)
- Draft your maker's comment
Days 15-28: Community Building
- Share "building in public" updates on Twitter
- Collect 20+ testimonials from beta users
- Create a launch announcement email
- Build a list of 100+ people to notify on launch day
Launch Day
- Launch at 12:01 AM PST
- Post maker's comment immediately
- Notify your email list and community
- Respond to EVERY comment within 30 minutes
- Share updates throughout the day
Lovable Prompt Template for Product Hunt Launch:
Build a [type of app] optimized for Product Hunt launch. LAUNCH PAGE REQUIREMENTS: - Hero section with animated product demo - "Featured on Product Hunt" badge placeholder - Testimonial carousel (minimum 6 slots) - Pricing section with "Launch Special" badge - FAQ section addressing common objections VIRAL FEATURES: - "Tweet about us" button with pre-written copy - Referral tracking system - Early adopter badge for first 100 users - Public user counter showing social proof LAUNCH ASSETS TO GENERATE: - 5 tagline variations (under 60 characters each) - Product Hunt description (under 260 characters) - Maker's comment template (personal story + value prop) - 3 social media announcement posts
Case Study: From 0 to 127 Users in 14 Days
The Project: A simple habit tracker for developers
The Distribution Strategy:
- Week 1: Posted daily "building in public" updates on Twitter
- Week 2: Shared in r/SideProject with genuine story (not promotional)
- Day 10: Launched on Product Hunt (finished #4 of the day)
- Day 14: Hit 127 users with 23% week-1 retention
"First-time founders focus on building. Second-time founders focus on distribution."
Your Distribution-First Toolkit
Every prompt on Lovable Prompts includes:
- Built-in growth mechanisms
- SEO landing page templates
- Social sharing features
- Launch content generation
- Product-channel fit analysis
Start With Distribution, Not Code
The old way: Build → Launch → Hope for users
The distribution-first way: Identify channel → Validate demand → Build with distribution baked in
Your Next Step:
- Pick ONE distribution channel (Community, SEO, or Product Hunt)
- Spend 1 week validating before writing any code
- Use prompts that include distribution from day one
Written by
