Your SaaS doesn't always need more traffic. It might need better discovery.
I've been noticing something interesting while looking at how early-stage products try to get their first users.
A founder launches.
Gets some traffic.
Maybe even gets people signing up.
Then the growth slows down.
The immediate reaction is usually:
“We need more marketing.”
But I'm starting to think that's often the wrong question.
If the people discovering your product aren't the people actively experiencing the problem you solve, increasing traffic only gives you more of the wrong visitors.
That's why I've become increasingly interested in community-driven discovery.
Not:
“Which platform has the biggest audience?”
But:
“Where are people already talking about the problem?”
That's a very different question.
And it changes how you approach content, communities, outreach, and even what you say about the product.
Reddit is a particularly interesting example.
The communities with the biggest member counts aren't necessarily the most valuable ones.
Sometimes a much smaller community contains exactly the people you need.
I've been studying this from the perspective of how products become part of conversations instead of interrupting them.
There's a lot more to it than dropping a link and hoping for clicks.
Curious about something:
When you're trying to get your first users, do you start with the platform you want to market on, or do you start by finding where your potential customers are already having conversations?
You make a solid point about focusing on quality rather than just traffic. From my experience, especially in the SaaS space, cultivating a niche community around your product can lead to more meaningful engagement and conversions than just chasing big traffic numbers.
When I launched my blog automation tool, I initially aimed to amplify traffic to our homepage through traditional SEO tactics and paid ads. However, I quickly realized that the content we were creating wasn't resonating with a specific audience. It wasn't until I turned my focus to niche communities like relevant subreddits and online forums where I found a more engaged audience.
Instead of trying to appeal to everyone, I tailored our content to the discussions happening within those groups. For instance, I offered insights and best practices specifically geared toward optimizing blog performance, taking into account the unique challenges those users faced. This approach not only improved our community connection but also led to higher conversion rates from those audiences.
Another tactic that worked was sharing case studies from our users who had success with our solutions. Demonstrating real-world impact in discussions can amplify trust and stimulate organic referrals. It's less about the volume of traffic and more about connecting with people who genuinely need your solution.
Building these relationships takes time, but once you're in, you can often leverage those connections into lifelong customers. It’s about quality interactions that drive advocacy more than just aiming for that raw traffic metric.
used to think bigger platform meant more reach, now i think it just means more noise. finding the smaller spaces where people are already venting about the exact problem you solve beats chasing traffic every time
This is something I'm thinking about a lot right now. I'm getting ready to soft launch a running-focused SaaS, and I've found myself thinking less about “where can I get the most traffic?” and more about “where are runners already talking about the problems I'm solving?”
The difficult part seems to be finding communities where the product is genuinely relevant without turning every interaction into promotion. How do you distinguish between a community that's actually worth investing time in and one that just happens to have a large audience?
I’ve been realizing this myself lately. It’s surprisingly easy to spend all your time looking for places with the biggest audience instead of asking whether those people would actually care about what you built. A community of 2,000 people with the exact problem probably beats 100k random visitors every time. The difficult part for me has been finding those smaller communities without coming across as someone who’s only there to promote something.
I think there’s a pretty thin line between genuinely joining the conversation and disguising marketing as a conversation.
This is the part I think most people underestimate.
Finding a community is relatively easy. Finding one where your potential users are actively discussing the problem is much harder.
And I agree on the second point too, there's a difference between contributing to a conversation and reverse-engineering a conversation just to sneak in a promotion.
I've found that the best signal usually isn't “Can I mention my product here?”
It's “Would this conversation still be worth participating in if I couldn't mention my product at all?”
If the answer is yes, you're probably looking in a much healthier place.
The distinction between more traffic and better discovery of value is an extremely helpful one. ~
I see too many founders getting confused between audience size versus people who actually have the problem.
Better discovery of value is where you get to have a conversation even with a smaller audience.
Asking the question about what platforms people are already discussing the problem in is likely to be a more important choice criteria than simply picking whichever one you want
It's also going to make your marketing feel less like marketing.
You're right, I've also realized that the hardest part of a business is promotion (without paid ads). It's much more important to have a few high-quality people than many who are useless to your business.
Worth separating two things that get called discovery. Being findable when someone is already looking, and being suggested to someone who is not. They need almost opposite work, and most posts about discovery only mean the first.
I think the distinction between traffic and discovery is important. More visitors won't help much if the people arriving don't have the problem you're solving.
I usually think about it as intent first, channel second. Once you understand where people are already expressing that problem, it becomes much easier to decide whether Reddit, search, outbound, or another channel actually makes sense.
The interesting part is figuring out whether the conversations you're finding represent real buying intent or just people discussing a problem.
to answer directly: I start with finding the conversation, not the platform, though I stumbled into that by accident rather than strategy at first. genuinely started on reddit because that's where a phone-automation problem seemed most likely discussed, only realized afterward that the smaller, specific subreddits mattered way more than the big general ones
the "keyword alerts for problem-specific phrases instead of brand names" tip above is smart and I wish I'd done that from day one instead of manually hunting fresh posts
one thing I'd add to the framing though: the value isn't just finding where people complain about the problem, it's that genuinely answering unrelated questions in that same space (not pitching, just being useful) is what makes people actually check your profile later. discovery through community isn't just about locating the right room, it's about having a reason to be trusted once you're in it
That's a really important distinction: finding the right room isn't the same as becoming relevant in that room. The keyword-alert approach is especially interesting because it changes the timing. Instead of looking for places to promote after deciding on a channel, you're finding conversations while the problem is already active.
And I think your point about answering unrelated questions is where the trust piece gets overlooked. People don't necessarily remember the person who dropped the best product link.
They remember the person who was consistently useful.
The interesting question then becomes: how do you know which conversations are actually worth investing time in?
honestly the filter I've landed on, mostly by trial and error, is whether I can add something specific, not just agree or encourage. if my genuine reaction to a post is "nice project" or "good luck," that's a sign it's not really worth commenting at all, those add nothing and don't build anything either
the posts worth investing in usually have a specific detail I can respond to directly, a number, a decision, a tradeoff they made, something concrete enough that my reply has to actually engage with their situation instead of being swappable into any thread. if I could copy-paste my comment onto five other posts unchanged, that's the tell I picked the wrong post
volume matters less than that filter honestly, I'd rather leave three genuinely specific comments a day than ten generic ones
This is a really good filter. I especially like the “could I copy-paste this comment into five other threads?” test.
Specificity is what turns a comment from noise into an actual contribution. And I agree that three thoughtful comments can be far more valuable than ten generic ones.
That's also how I approach Reddit growth strategy: it's not about maximizing comment volume; it's about finding the right conversations where you can add something genuinely relevant and become recognizable over time.
"becoming recognizable over time" is a good way to frame the end goal, that's really what the specificity filter is building toward, not the comment itself. glad it resonated
I completely agree with this framing—pouring traffic into a leaky bucket or targeting the wrong intent is one of the most common early-stage traps.
To answer your question directly: I always start with finding the active conversations rather than picking a platform upfront. When you track down where people are actively asking for workarounds, complaining about existing tools, or sharing manual workflows (whether that's a small subreddit, a specialized Discord server, or an industry forum), three key things happen:
One tactical approach that's worked well is setting up targeted keyword alerts for problem-specific phrases (e.g., "how to automate X", "alternative to Y") rather than brand names. That way, you're joining the conversation right at the exact moment the pain is freshest.
Seems to be an almost universal experience — the issue isn't "not enough traffic," it's mistaking discovery for validation. If someone lands on your page and bounces, that's not necessarily a marketing problem yet, it's a sign you haven't found the room where people are already describing your problem in their own words. The traffic solution comes after that, not instead of it. I've started treating "where are people complaining about this without naming a solution" as the actual research phase, and everything downstream — copy, positioning, even which features to lead with — gets easier once you start from that first.
The distinction between traffic and discovery is a useful one. You’re focusing on where the problem is already being discussed rather than simply where the largest audience is.
This is the exact insight that made me build ThumbRank. YouTube creators obsess over SEO and titles, but the real discovery happens in the first 0.5 seconds when someone sees the thumbnail. Better discovery > more content.
What's your #1 tactic for improving SaaS discovery beyond SEO?