I Collected 1,000+ Data Points on SaaS Competitors. Here's What Surprised Me.
I thought competitor research was about finding the best product.
Then I started collecting data.
1,000+ data points.
Pricing.
Features.
Traffic sources.
SEO.
Customer reviews.
Marketing channels.
And a few things surprised me.
- The biggest competitor isn't always the biggest threat
Some products have huge audiences.
Others have a tiny user base but dominate a very specific niche.
A product with 10,000 users isn't automatically a better competitor than one with 500.
Sometimes the smaller product understands its audience better.
-
Great products don't always have great distribution
You can build an amazing SaaS.
Beautiful UI.
Powerful features.
Perfect onboarding.
And still struggle to get users.
Meanwhile, a simpler product with a clear distribution strategy keeps growing.
Building something useful and getting people to discover it are two different problems. -
Customer complaints can be more valuable than feature lists
A competitor's landing page tells you what they want you to see.
Their reviews tell you what customers actually experience.
That's where interesting opportunities appear.
Not every complaint is a business opportunity.
But some reveal problems that competitors haven't solved well. -
More research doesn't automatically mean more clarity
This was probably the biggest surprise.
After collecting all this information, I realized that data alone doesn't tell you what to do next.
You can have 30 competitors in a spreadsheet.
Hundreds of notes.
Thousands of data points.
And still be stuck.
The real question is:
Which of these findings should actually change my product or marketing strategy?
That's the problem we're exploring with Fountrail.
We're building a platform to help founders research markets, analyze competitors, and turn scattered information into a more actionable startup strategy.
Still early.
Still learning.
But I'm curious:
What's the most surprising thing you've discovered while researching competitors?
Was it pricing?
Marketing?
Customer complaints?
Or something completely unexpected?
This is a great framework. Especially the owner, deadline, and metric part.
That’s exactly where we want Fountrail to go: turning competitor research into actionable experiments, not just another spreadsheet full of data.
The job-to-be-done and buyer segment clustering is also a strong point. Two competitors can solve the same problem for completely different audiences, and treating them as direct alternatives can lead to the wrong conclusions.
The goal is to help founders move from “Here’s what the market looks like” to “Here’s what I should test next, and why.”
Exactly. Data without a decision is just noise.
We’re still early, so I don’t want to claim founders have already changed major decisions because of Fountrail when we haven’t documented those cases yet.
That’s actually the behavior we want to measure: did a founder change their positioning, drop a feature, narrow their niche, or rethink their acquisition strategy after using Fountrail?
The real value isn’t surfacing 1,000 data points. It’s helping a founder avoid spending 3 months building the wrong thing.
That’s the outcome we’re working toward.
1,000 data points can still leave you stuck. Have any founders changed a product or marketing decision because of something Fountrail surfaced?
The distinction between collecting data and making decisions is the key insight here. One way to force the “so what” is to turn each finding into a hypothesis with an owner, deadline, and metric, such as “complaints about X → test a copy or onboarding change → measure activation and retention.” I’d also cluster competitor evidence by job-to-be-done and buyer segment, then keep a short table of evidence, confidence, and next experiment. That keeps the spreadsheet from becoming an end in itself.