Back to Blog

indiehackers: A Feature Guide for Solo Founders

How to use indiehackers.com as a solo founder: post milestones, build a product page, mine interviews, and run it all in a 90-minute weekly routine.

Anatolii Kharchuk
Anatolii KharchukCofounder, CPO · November 14, 2026

Key takeaways

  • indiehackers.com is a free community where solo founders share revenue numbers, milestones, and interviews about getting their first 100 paying users.
  • Follow the 90/10 rule: comment on three posts for every one you write and never drop a link unless someone asks.
  • Create a free product page as your build-in-public home base, then post short milestone updates to resurface in feeds without a new launch.
  • Mine the interview archive by filtering for founders at your revenue level and turn repeated distribution channels into a one-test-per-week list.
  • Cap indiehackers.com at 90 minutes a week; if four weeks of posting produce zero profile visits or product page views, reallocate the time to shipping.

indiehackers.com is a free community where solo founders post milestones, list products, and read interviews with people who got their first 100 paying users. This guide walks through where each feature actually lives, the posting norms that keep you from being ignored, and a weekly routine that costs you under two hours.

What Is indiehackers.com and Who Is It Actually For?

Indie Hackers is a community site where solo founders and small teams share revenue numbers, post milestones, and interview each other about what actually worked. It was started by Courtland Allen and later acquired by Stripe, and today it bundles forums, product pages, milestone posts, and a large archive of founder interviews on its own site. If you shipped something on Lovable, Bolt, Cursor, or Replit and have zero users, it is relevant for one reason: the people posting there are a few steps ahead of you and describe their first 100 paying users in specifics. Read the interviews for tactics, post your own milestones to build in public, and treat the comment threads as free distribution research. We also cover how to read early-user signals in our guide to activation milestones with only 30 users.

How Is indiehackers.com Organized? A Map of the Key Features

Indie Hackers splits into four areas you'll actually use: the community feed, product pages, the interview archive, and newsletters with pods. Knowing what each one is for stops you from posting in the wrong place and wondering why nobody replied.

The community feed and groups

The main feed is a rolling stream of posts across topics like marketing, product, and revenue. Groups narrow this by niche or stage, so a pre-revenue solo builder gets more from a small niche group than shouting into the general feed.

Product pages and milestones

Every founder can create a product page listing what they built, revenue charts, and milestones like "first 100 paying users." Milestones are public updates other founders follow, which makes them a low-effort build-in-public channel.

The interview archive

Indie Hackers' original asset is thousands of written founder interviews, searchable by revenue and topic. Treat them as a tactic library: filter for businesses at your size and steal their first-distribution moves, then track which signals matter before 100 users (https://heycatch.ai/blog/9-ai-search-visibility-signals-to-track-pre-100-users).

Newsletters and pods

Curated newsletters resurface top posts, and pods are small circles that comment on each other's updates.

AreaWhat it's forTime cost
Feed and groupsQuestions, feedback15 min/day
Product pagePersistent home for your product30 min setup
InterviewsTactic mining30 min/week
Newsletters and podsReach and replies10 min/week

How Do You Post on Indie Hackers Without Getting Ignored?

What a good first post looks like

Skip the launch announcement. A first post that works is a specific question or a short build-in-public update with one number in it: "Shipped on Lovable, 0 users, here's my plan for the first 100 paying users." Posts that admit where you're stuck get replies; posts that only promote get scrolled past. The community norms on Indie Hackers consistently reward specificity and honesty over polish.

The 90/10 rule applied to community posting

The 90/10 rule means 90% of your activity is helping other people, and 10% is about your own product. Comment on three posts for every one you write. Answer questions in your niche, share what worked, and never drop a link unless someone asks for it. If you track this like you track your product metrics, you'll see why it matters: the signals worth watching before 100 users are mostly reply quality, not impressions. AutoMod-safe means exactly that: no link stuffing, no copy-pasted intros.

Milestone posts vs. question posts

Milestone posts (first paying user, $100 MRR) earn visibility but teach nothing unless you explain the how. Question posts earn trust faster because they start conversations. Alternate them, and always end a milestone post with what you'd do differently.

Should You Create a Product Page on Indie Hackers?

Yes, if you want a single URL that shows what you shipped, what changed, and whether anyone cares. The product page is free, takes under an hour, and doubles as your build-in-public home base. It will not bring users on its own, but it gives every Reddit comment and X post somewhere to point.

What to include on your product page

Lead with a one-line description a stranger understands, then screenshots or a Loom-style demo of the core flow. State what you built it with (Lovable, Cursor, Bolt) because indiehackers readers respect that. Skip the pricing table until you have something to price.

Using milestone updates as a public roadmap

Post short updates: first paying user, feature shipped, churn lesson learned. Each update pushes your product back into feeds without a new launch. Track which updates get traction instead of guessing; the reason traffic numbers lie about what works is covered in content performance tracking.

How Do You Mine the Interview Archive for Distribution Tactics?

The indiehackers interview archive is a searchable record of how founders got their first 100 paying users, filtered by real revenue numbers. Use it as a research database, not entertainment.

Filtering interviews by revenue and product type

Sort for founders whose product and revenue match yours: a $0-500 MRR solo tool built on no-code teaches you more than a $50k SaaS exit story. Read the "how did you get your first customers" answers across 10-15 interviews and write down every channel named. Patterns repeat fast: one channel shows up in half the stories for products like yours.

Turning interview tactics into a weekly test list

Pick one channel per week, run it, and log the result. Keep it to one so shipping doesn't stall. If your test lives on Reddit or another community, follow the 90/10 self-promotion guidance before you post anything.

Track tests in a simple spreadsheet. If you want the "which tactic next" step planned for you, HeyCatch does that planning (see https://heycatch.ai/pricing).

How Much Time Should indiehackers.com Actually Take Each Week?

Ninety minutes a week, capped. Indie Hackers works as a listening and posting channel, not a full-time job, and the founders who get value treat it like a scheduled errand.

A 90-minute weekly routine

Split it into three blocks. 45 minutes on Monday: scan the top posts in your niche's communities, save two threads worth answering, and draft one post of your own (a milestone, a build in public update, or a lesson from shipping on Lovable or Cursor). 30 minutes midweek: reply to your two saved threads with specific, useful answers. No link drops, just help. 15 minutes on Friday: update your product page metrics if anything moved, and note which post got replies so next week's draft starts from what worked.

Set a timer for each block. When it rings, close the tab and go back to shipping.

Signals it's time to drop the channel

If four straight weeks of replies produce zero profile visits, zero product page views, and zero conversations, stop posting and reallocate the 90 minutes. Same if your posts only get engagement when you ask for it. A channel that never converts attention into product visits is costing you shipping time, and at your stage, shipping is the growth strategy.

Indie Hackers vs. Posting Manually Everywhere Else

Where indiehackers fits next to Reddit, X, and directories

Indie Hackers is the only channel where "I shipped X and got my first 10 users" is the native content format, not spam. On Reddit, the same post gets you banned unless you follow the 90/10 rule and each subreddit's rules, which vary wildly and are enforced by AutoMod. X rewards daily posting volume, which is rough when you're solo. Directories get you a backlink and then silence. Use Indie Hackers for build-in-public storytelling, Reddit for finding where your target users actually hang out, and directories as a one-time setup.

When a tool beats manual browsing

Manual works until it costs 3h/day. If Reddit becomes your main channel, a monitoring tool like Oetzi AI watches subreddits for relevant threads so you reply when it matters instead of doom-scrolling. Indie Hackers has no equivalent problem: it's small enough to read in one sitting, which is exactly why it fits a solo founder's week.

Common Indie Hackers Mistakes First-Time Posters Make

The biggest time sink is treating your product page as a landing page. Write it like copy and nobody follows it; write it like a build-in-public log with real numbers and people check back.

Second mistake: dropping launch announcements into threads that are clearly conversations. Indie Hackers rewards replies that answer the actual question. If your first ten posts are all about your product, you're the person everyone skips.

Third: reading interviews passively. Skim for the tactic, note the channel, close the tab. Reading 20 interviews without acting on one is entertainment, not distribution.

Last: skipping the 90/10 rule. Spend 10% of your weekly time here posting and 90% shipping. A founder with zero users who posts daily but ships weekly has it backwards.

FAQ

Is indiehackers.com free to use?

Yes. Creating an account, posting milestones, building a product page, and reading the interview archive all cost nothing. The site makes money elsewhere, so you never hit a paywall mid-research. Your only real cost is time, which is why the 90-minute weekly cap matters.

Does posting on Indie Hackers actually get you your first 100 users?

Not by itself. It gets you replies, profile visits, and product page views from founders a few steps ahead, plus a searchable archive of how similar products found their first customers. Treat it as a listening and distribution-research channel, and expect zero direct signups if four weeks of posting produce none.

Can I promote my Lovable or Bolt-built app on Indie Hackers without getting banned?

Yes, if you follow the 90/10 rule: comment on three posts for every one you write, and never drop a link unless someone asks. Build-in-public updates with real numbers are the native content format here, unlike Reddit where the same post gets AutoMod-banned. State what you built it with; readers respect that.

Is Indie Hackers still active, or has everyone moved to X and Reddit?

It's smaller than X or Reddit, which works in your favor: the feed is readable in one sitting, and "I shipped X and got my first 10 users" is normal content there, not spam. Use it for build-in-public storytelling while Reddit tells you where your target users actually hang out.

You shipped a product.

Let's get it earning.

Get started