Indie Hackers Submission Guide: What to Prepare First

4 min read

Indie Hackers Submission Guide: What to Prepare First

Indie Hackers is the largest founder community, which makes it a different kind of channel: a post that helps other founders can outperform any directory listing for credibility.

The short answer

Submit to Indie Hackers if its category page is indexed and the listings beside yours are followed. Skip it if a site: search on the directory returns nothing — a listing on an invisible page is a form you filled in, not a citation.

Before you touch the form

Decide what you are willing to publish about your own numbers before you join. This audience rewards specifics, and a post written to avoid disclosing any figure has nothing left to say.

Submitting, in order

  1. Choose one number worth sharing
  2. Write the post around it
  3. Add what you learned
  4. Post in the right group
  5. Reply for a day

What Indie Hackers is

Indie Hackers is a community and knowledge base for independent founders, with product pages, forums and posts about building businesses.

One thing that catches people out

Threads here are indexed and quoted for years. A post asking for feedback on a half-finished product becomes the page people find when they search the name, and it stays that way.

Mistakes that waste the submission

  • Posting only when you have something to promote
  • Writing an announcement where a lesson was expected
  • Hiding the numbers that would have made the post credible
  • Answering criticism with a feature list
  • Leaving the thread after the first hour

Checking what you actually got

  • Count replies rather than views; engagement is the number that predicts recall
  • Check whether the thread is still open a week later
  • Harvest the feature requests in the comments before they scroll away
  • Search the post title to see whether anyone syndicated it
  • Note whether anyone asked for a link, which is the closest thing to a warm lead

What this audience rewards

Numbers, context and candour. A post that says what you built, what it cost, what failed and what the revenue is will outperform any announcement, because the community's currency is specificity. Directory-style listings on Indie Hackers are close to invisible by comparison — the product page exists, but nobody browses it looking for software.

How to use it without burning goodwill

Participate before you promote. Answer questions in your area for a few weeks, then post something useful that happens to mention the product. Founders who arrive with a launch post and nothing else get ignored, and the community remembers which accounts only appear when they want something.

What a good first post looks like

A specific number, the context behind it, and what you would do differently. Revenue, churn, time-to-first-customer, cost per signup — anything measurable, presented honestly, with the mechanism explained. Posts that read as lessons get engagement; posts that read as announcements get scrolled past.

Deciding what to publish next

Follow the questions your own product raises. A pricing change, a stack migration, a support pattern you noticed in the inbox — each is a post, and each is easier to write than a summary of the last quarter. Publishing cadence matters less than specificity, so keep the list of candidate posts longer than the list of ideas you can already defend.

Where the product page fits

It is a citation and a landing surface, not a discovery channel. Nobody browses Indie Hackers looking for payroll software, but people do click a profile after reading a good post. Fill it in, link it from your posts, and expect nothing from the page itself.

Reading the response

Views say almost nothing. The signals that matter are the questions people ask in the thread, how many ask how to try it, and whether anyone quotes your numbers back later. Write those down after each post; after three posts the pattern is obvious, and it is usually not the story you expected to land.

Where SaasHunt fits

Indie Hackers rewards the story of building; SaasHunt rewards the fact of shipping. Run the story where founders read it and the launch where buyers browse, instead of asking one audience to do both.

Submit your product

FAQ

Do community links pass equity?

Content and profile links on community platforms are typically nofollow. The value is audience and feedback rather than link equity.

Should I post a launch or a story?

A story. Posts that explain what you built, what it cost and what failed do better than announcements, because the audience reads for lessons rather than for products.

Follow for new blogs

Subscribe to our blog

RSS

Subscribe to Newsletter

Subscribe to our newsletter to get the best products weekly.