Indie Hackers: How to Share Progress Without Self-Promoting
The norms of founder communities like Indie Hackers: what gets upvoted, what gets ignored, and how to share numbers without it reading as a pitch.
Published 2026-09-22 · 4 min read
Founder communities have a specific tolerance: real detail welcome, promotion not. The distinction is not subtle once you see it, but founders cross the line constantly because the communities are friendly and the friendliness reads as permission.
This describes the norms of founder-progress communities generally — Indie Hackers and its equivalents — rather than any one site's current rules, which you should read before posting.
What the community actually wants
- Numbers with context. Revenue, users, conversion — but with the sample size, the timeframe and what caused the change. A bare number is a brag; a number with a mechanism is a lesson.
- Failures described specifically. What you tried, what it cost, what you concluded. These are the highest-value posts in any founder community and the rarest.
- Decisions and their reasoning. Especially decisions that turned out wrong. The reasoning is what other founders can reuse.
- Tactics that worked, with enough detail to copy. Not "we did content marketing" but what, where, how often, and what it produced.
- Honest assessments of tools and platforms, including the ones you like. Especially those.
What gets ignored or pushed back on
| Pattern | How it reads |
|---|---|
| A milestone post with no analysis | An announcement wearing a progress report's clothes |
| "Feedback wanted" on a landing page | A request for free marketing work |
| Detail-free success claims | Unverifiable, and the community has seen many |
| The same product posted repeatedly | Astroturfing, whether intended or not |
| Asking for upvotes or support | Immediately reclassifies the post as promotion |
| Answering every comment with a link | The fastest way to lose standing you spent months building |
The formats that work
- 1
The monthly update, done properly
What changed, the actual numbers with their baseline, what worked, what did not, what you are trying next. Include the flat or declining months — a series that only reports growth is not believed, and a series that reports everything is.
- 2
The failure post-mortem
One thing that did not work, in full. What you believed, what you did, what it cost, what you now think. This is the post most likely to be referenced years later.
- 3
The tactic breakdown
One channel or technique, described in enough detail that someone could copy it. Include what it cost and what it returned.
- 4
The honest comparison
You evaluated three tools for something and here is what each was actually like. Naming where the expensive one won is what makes it credible.
- 5
The question you genuinely cannot answer
Asked plainly, with what you have already tried. These get the best responses of any format, because the community is good at solving stated problems.
Where your product belongs in the post
Mentioned once, factually, without a link unless asked. The convention exists because everyone in the community has a product, so the product is never the interesting part — the reasoning is.
- First mention: what it is, in a clause. "We run a scheduling tool for clinics" is enough.
- No link in the body unless the post is specifically about the product and the community's rules permit it.
- In your profile instead. That is what the profile is for, and people who care will look.
- If asked, answer fully. Someone asking "what is the URL" is the ideal outcome and should be answered immediately and without additional pitching.
Participating before posting
The communities reward history. A first post from a handle nobody recognises gets less attention than the same post from a handle that has spent a month answering other people's questions.
- Two weeks of replies minimum before your first substantive post. Answer questions in your area; the answers are read by the people who later read your post.
- Comment on other people's milestone posts with something useful rather than congratulatory.
- Read the top posts of the last month before writing yours. The format and the level of detail are visible, and matching them is not copying.
What these communities are not for
- Customer acquisition. The audience is founders — your peers, not your buyers. Useful for feedback, partnerships and morale; close to useless for revenue.
- Validation. Everyone there is building something and is predisposed to be encouraging. Approval from founders is the weakest validation signal available.
- A substitute for buyer communities. The month you spend here should run alongside, not instead of, the community where your actual customers gather.
Founder communities are where you learn how to run a business, not where you find customers. They are worth the time for the first reason and are often mistaken for the second.
More in Community playbooks
- How to Find and Join AI Newsletter CommunitiesNewsletter authors and their reader communities are a reachable audience for a new AI product. How to find them, get on their radar, and get mentioned.
- Product Hunt Community: How to Engage Before You LaunchA launch-day platform rewards the people who were already there. How to build standing in a launch community in the months before you need it.
- How to Answer Questions in Public Without SellingThe helpful-answer channel: how answering strangers' questions builds an audience for an AI product, what a good answer contains, and where the line is.