How do you find the right communities before posting about your product?
I’m trying to get better at finding the right communities before posting about a small SaaS project.
The part I’m struggling with is not really the product, but knowing where the pain is actually strong enough that people would care.
I don’t want to just drop links or show up only when I need feedback. I’d rather first understand where the right people already talk about this kind of problem.
For those of you who found early users through communities, how did you find the right places?
Was it Reddit, IndieHackers, Slack/Discord groups, Hacker News, niche forums, search, or something else?
And how did you start participating without making it feel like you were only there to promote your own thing?
Trending on Indie Hackers
The "how to find communities" framing is usually backwards. Communities aren't found through research — they're built backwards from your customers. Take your top 5-10 paying users, ask each: "where do you learn about tools in this space, where do you ask questions about [problem]." 80% of discovery happens through customer interviews, not cold search.
"Where is pain strongest" isn't the right filter either. Buyer concentration density beats pain density. r/Entrepreneur has massive pain expression and terrible buyer concentration. A niche Discord of 200 members in one job title can outperform it 10x.
The "how to participate without seeming promotional" question solves itself if you're genuinely in the community 6-8 weeks before mentioning your product. Founders fail this because they're impatient, not because the rule is complex.
I happen to know a couple of users who experience issues with silently failing background processes, and they would probably be willing to answer any questions you have.
That would be really useful, thanks.
I’m mostly trying to understand the real situations where this happens, not pitch something immediately. If they’d be open to answering a few questions about what failed and how they noticed it, I’d appreciate an intro.
Finding the right community is like conducting a UX audit; you have to spot the broken flows where people are already vocalizing their frustration. Searching for phrases like "I hate when..." or "Does anyone else..." on Reddit or niche Slacks reveals exactly where the friction is most painful. Entering these spaces as a fellow problem-solver builds trust mileage, so your eventual project mention feels like a helpful suggestion rather than an ad. Listening to how people describe their current "workarounds" is usually a much better signal than any formal feature request list.
What specific "pain phrase" or workaround have you noticed popping up most frequently in your research so far?
That’s a really useful framing. So far I’ve been looking at phrases like “cron job failed silently”, “backup didn’t run”, “script stopped running”, and “we didn’t notice until later”.
The interesting pattern is that people don’t always describe it as “cron monitoring”. They describe the damage after the fact — missing data, failed imports, broken syncs, or customers noticing before the team does.
I’m still trying to figure out which phrase is strongest, but “failed silently” and “didn’t notice until later” seem closest so far.
Thanks for the reply! My team has also been hearing the same consistent feedback from the communities where our real users hang out: the barrier to entry is a bit high. It’s exactly as you said people walk in expecting a 'light' experience, but soon realize that what we're offering is actually quite heavy. That’s why we’re constantly obsessing over how to save our users' time and figure out how to deliver the maximum amount of insight with the absolute minimum amount of effort on their part.
This comment was deleted 5 days ago.