How to build an audience for your indie project

Start with a follow button, not a newsletter

Most builders make the same mistake: they build the product but give visitors no way to stay connected. Someone lands on your site, thinks "interesting," and leaves — forever. That visitor is gone unless you had a way to capture them.

The lowest-friction capture mechanism is a simple follow button on your public project page. No email required, no confirmation flow, no "join 10,000 subscribers" pressure. Just "Follow this project for updates" — and when you publish something worth sharing, they get notified.

Start here before anything else. Even 20 people who follow your project are worth more than 2,000 random Twitter followers, because they've specifically opted in to hearing from you about this thing.

Ship a changelog, even when nothing is "ready"

The biggest mistake indie developers make with audience building is staying silent between big releases. People who follow your project want to see it move. A weekly or biweekly changelog entry — even one paragraph — keeps you in people's minds and gives followers a reason to stay.

What counts as a changelog entry:

• A new feature, even a small one ("Added a CSV export")
• A bug fix that affected users ("Fixed the login issue on iOS Safari")
• A direction update ("Pausing the social feature to focus on analytics — here's why")
• A milestone ("Reached 100 users today")

Consistency matters more than frequency. One post every two weeks that ships reliably is better than ten posts in a row followed by two months of silence.

The "build in public" approach

Building in public means sharing your project's progress openly — numbers, decisions, failures, and wins — on platforms where your target audience hangs out. Done well, it's the most efficient audience-building strategy for indie developers because it attracts an audience that's already interested in the specific thing you're building.

What to share:

• Milestones: "Hit $500 MRR. Here's what changed in month 3."
• Failures: "Our first Product Hunt launch flopped. Here's what we'd do differently."
• Technical decisions: "Why we switched from Supabase to PlanetScale (and back)." Developers will share opinionated takes.
• User insights: "Our users told us X but actually use Y. Shows you." These get shared by people who recognize the same pattern.

Where to post: Twitter/X is the primary platform for this style of content among indie developers. Indie Hackers and Hacker News also work well. LinkedIn works if your product serves a professional audience.

Email subscribers vs followers: know which to prioritize

Email subscribers and project followers are different things with different purposes:

• Project followers — lower friction to capture, notified when you publish a changelog update, good for retaining casual interest. These people are in "discovery mode" — they haven't committed to caring about your product yet.
• Email subscribers — higher commitment from the subscriber, higher deliverability than in-app notifications, much harder to delete you from their life. These are your warmer leads.

For most indie projects at the early stage, project followers are more achievable and still very valuable. Build email when you have something specific to say — a launch, a major update, a community post. Don't build an email list just to have one.

Use launches strategically

Every major launch — Product Hunt, Hacker News Show HN, a big Reddit post — is an audience-capture event. The mistake is treating the launch as the end goal when it's actually just the acquisition moment. What matters is what you do to retain those new people.

After each launch:

• Make sure you have a follow button on your public page before you launch, so new visitors can stay connected
• Post a changelog entry about the launch itself ("We launched on Product Hunt today — 300 visitors, 47 signups")
• Follow up 2–3 weeks later with what happened next ("Update: 12 of those 47 are still using the product daily")

The follow-up post often gets more engagement than the launch itself.

The numbers that matter vs the ones that don't

Vanity metrics for indie projects: Twitter follower count, total page views, total signups.
Metrics that predict whether you're building a sustainable audience:

• Retained followers — people who followed you 30 days ago and still follow you today
• Open rate on changelog notifications — if 40% of your followers open your changelog emails, that's a highly engaged audience
• Returning visitors — the percentage of your weekly visitors who have been to your site before
• User-initiated shares — when someone shares your product without being asked

A project with 100 highly engaged followers is more valuable than one with 10,000 passive ones — because the 100 will tell people, while the 10,000 will forget you exist.

The compounding effect

Audience building compounds slowly and then quickly. The first 50 followers take more effort than the next 500, because at 50 you have no social proof — at 500, every new visitor sees that others have followed and is more likely to follow themselves.

The practical implication: don't optimize too early. Pick one channel (your public page's follow button + a regular changelog), do it consistently for 3 months, then evaluate. The results won't feel like much at month 1; they compound after month 3.

Related guides:

• How to turn your Git commits into a clean changelog
• How to make a free public page for your side project
• Where to share your side project launch