The “traffic problem” is often a positioning problem
I keep noticing a pattern in a lot of early-stage SaaS discussions.
Someone launches, gets some traffic, and the immediate conclusion is: we just need more traffic.
But when you look closer, people often don’t really understand what the product actually does or who it’s for.
If 1,000 visitors land on the page and nobody moves, sending 10,000 more usually just amplifies the same issue.
A lot of founders try to solve a positioning problem with a distribution tactic.
More ads, more posts, more channels.
But sometimes the real constraint is simply that the product hasn’t found a clear place in the workflow yet.
Curious if others here noticed the same when launching something new.
Trending on Indie Hackers
Going through this right now with ReviseFlow. For a long time I described it as a "visual bug reporting tool", which is accurate but means nothing to most people. Nobody wakes up thinking they need a bug reporting tool.
When I started framing it around the actual alternative situation - your client sends a blurry phone screenshot in Slack saying "something looks broken" and you spend 20 minutes on a call trying to reproduce it - the pitch clicked immediately. The competition isn't other bug trackers. It's a chaotic back-and-forth that wastes everyone's time.
Still working on getting that framing into the actual landing page copy. The awkward part is the "right" positioning isn't always SEO-friendly, so there's a real tension between what resonates with humans and what search engines reward.
Often the issue isn’t traffic, it’s how the product is positioned.
Exactly. And the moment you frame it that way, the copy almost writes itself. You're no longer describing a tool — you're describing a situation the founder immediately recognizes. The product just becomes the obvious resolution to that moment.
exactly. 'competing with what people are doing right now' is the right frame — and for most early tools the answer is something embarrassingly manual. that realization changes how you write every line of copy.
for RecoverKit it's been valuable because the alternative isn't Churnbuster or Baremetrics — it's a founder staring at a failed payment notification in their Stripe dashboard and deciding not to do anything about it today.
ran into this exact thing with RecoverKit, a payment recovery tool for SaaS businesses.
First version of the landing page described what it was: 'automated dunning email tool.' Visitors landed, looked around, left. The traffic wasn't the problem — the framing was. Most founders don't think they need a dunning tool. They think their payment problem is rare or fixable by hand.
The positioning shift that helped: stop describing the product, describe the moment it solves. 'Your customer's card failed yesterday. They don't know. Neither did you until just now.' Suddenly the same traffic converts differently because visitors recognize their own situation.
The test that crystallized it for me: what is the visitor doing right now instead of using your product? If the answer isn't obvious from the landing page, more traffic won't help.
That’s a great example. The moment you describe the situation instead of the product category, the comparison changes completely. Instead of competing with other tools, you're competing with what people are doing right now — which is usually nothing or some manual workaround.