Indie hackers occupy an odd position on Reddit. They are simultaneously the audience most likely to buy small tools and the audience most saturated with people selling them. The communities that work are the ones where showing your project is the stated purpose rather than a tolerated exception.
Who is actually in these communities
The population skews toward technical people building small products alongside or instead of a job. Budgets are personal rather than corporate, which changes everything about how they buy: price sensitivity is extreme, free tiers matter enormously, and annual contracts are a non-starter. A tool at nineteen dollars a month is a considered purchase here.
It also means the sales cycle is short and the decision is made by one person in an evening. If your product solves a problem somebody described in a thread, and they can try it without talking to anyone, you can go from comment to signup the same day. That is rare in any other audience on this list.
The flip side is churn. This audience abandons projects constantly, and the tool goes with the project. Expect it and price for it.
Where indie builders congregate
These communities differ sharply in whether showing a project is the point or a violation. The distinction is the single most useful thing to know before posting.
| Subreddit | What gets asked there | Promotion tolerance |
|---|---|---|
| r/SideProject | Launch and show-your-work posts, feedback requests, early traction questions | Moderate — showing your project is the format |
| r/indiehackers | Revenue milestones, distribution experiments, pricing for small products | Moderate — with disclosure |
| r/microsaas | Tiny software businesses, niche picking, buying and selling small products | Moderate — with disclosure |
| r/SaaS | Pricing, churn, first customers, tool recommendations for small teams | Low — disclosure expected |
| r/EntrepreneurRideAlong | Ongoing build logs, week-by-week progress, operational detail | Moderate — narrative posts are welcome |
| r/webdev | Stack choices, hosting, deployment, and occasional showcase threads | Very low outside designated threads |
| r/SomebodyMakeThis | People describing products they wish existed, often in unmet-need detail | Low — but ideal for research |
| r/AlphaandBetaUsers | Builders recruiting early testers and trading feedback | High — that is the purpose |
Reading intent in an indie audience
The buying signals here look different from a corporate audience. Nobody writes "evaluating vendors". They write:
Build-versus-buy hesitation. "Is it worth building this myself or is there something off the shelf" is the highest-intent sentence in this entire audience. The person has a defined need, has already scoped the work, and is actively looking for a reason not to do it.
Free tier exhaustion. "I have outgrown the free plan on X and the next tier is a jump" appears constantly. It names the competitor, the constraint and the price ceiling in one sentence.
Stack posts. "Here is my stack for this project" threads attract long comment chains where people compare choices. These are not direct requests but they are where recommendations get absorbed.
Wish posts. r/SomebodyMakeThis and similar threads are pure unmet-need research. Nobody is buying today, but the language people use to describe a problem before a product exists for it is the best keyword source you will find.
What gets removed, and where
The most common mistake is treating r/SideProject rules as if they apply in r/startups. Launch posts are the expected content in the first and are removed on sight in the second.
Even in the permissive communities, low-effort launches get filtered. A title, a link and one sentence typically disappears or sinks without comment. The posts that do well include what you built it with, what it costs you to run, what is not working, and a specific question.
Cross-posting the same launch to six communities within an hour is the reliable way to get flagged site-wide. Space them out, rewrite each one for the community, and accept that some will be removed anyway.
Repeated launches of the same product also wear thin. Communities remember, and a builder who posts the same project every three weeks with a new screenshot loses the audience long before the moderators intervene.
Contributing in a way that compounds
The thing that works best here is transparency about the boring parts. Hosting costs, actual revenue, the marketing that failed, how long something took to build. This audience is starved of real numbers because most public writing about small software is aspirational, and a comment with real figures gets more attention than any launch post.
When answering a build-versus-buy question, answer it honestly. Sometimes the answer is that they should build it, because their use case is narrow and a weekend of work beats a subscription. Saying so is the fastest way to become someone whose recommendations are trusted.
Keep your product mention short and factual. A sentence describing what it does and what it costs, with a disclosure, outperforms a paragraph of positioning in every one of these communities.
FREQUENTLY ASKED QUESTIONS
Questions about indie hacker communities
Where can I post a launch without it being removed?
Communities built around showing work, such as r/SideProject and r/AlphaandBetaUsers, expect launch posts. General business and startup communities almost always remove them. Read the sidebar and check recent posts to see whether launches are actually surviving there this month.
Do indie hacker communities convert into paying customers?
They convert quickly and at low value. Decisions are made by one person, often the same day, but budgets are personal and churn is high. It is a good audience for low-priced self-serve products and a poor one for anything requiring a sales call.
How do I find people who want what I am building before it exists?
Monitor the wish and frustration language rather than the category name. Threads asking whether something exists, or describing a manual workaround, tell you there is demand and give you the exact words to use in your own copy.
Should I post my revenue numbers publicly?
In these communities it is the most effective thing you can share, provided the numbers are real. Vague growth percentages without a base read as evasive and get called out.
CATCH THE BUILD-VERSUS-BUY THREADS
Somebody is deciding whether to build what you already made.
MentionSpot monitors r/SideProject, r/indiehackers and the rest for the questions that precede a purchase, and ranks them by intent.
Get the 7-day pass