September 13, 2026
4 min read
Competitor Research for Indie Hackers
Competitor research for indie hackers: read user complaints instead of landing pages, find the gaps that matter, and run a repeatable pass you can keep.
Competitive analysis
Reviews · Forums · Issues
Competitive analysis from what customers actually say
A feature grid tells you what a competitor claims to do. The reviews, forum threads and support complaints tell you what it fails to do for people who already paid. This page is about reading the second source and turning it into the gaps your product can win.
Why feature lists lie
Every product's own comparison page is written to win the comparison. It is the least trustworthy source about a competitor. The trustworthy source is the customer who tried it, paid for it and left a review about what they could not do.
That is why the useful competitive analysis starts from complaints, not from a matrix — the same reason competitor research for indie hackers begins with real customers.
What to extract
Repeated gaps
The missing capability that shows up across many independent reviewers, not once.
Workarounds
They export to a spreadsheet, bolt on a second app, or do it by hand. The workaround is your spec.
Switching reasons
"Left because…" names the incumbent's weakness and the opening you can take.
How to run it
- 1 List the alternatives your buyer really has, including the spreadsheet and doing nothing.
- 2 For each, read the one and two-star reviews, then the four-star reviews — the withheld star is a feature request.
- 3 Note every repeated gap with the exact quote and a link.
- 4 Look for the gap every alternative shares. That is a market opening, not one product's bug.
- 5 Write one sentence naming the opening a small product can win.
Run the reading for you
Reading reviews across several competitors by hand takes days. A research runs over Reddit, Hacker News, Stack Overflow and GitHub at once and returns clustered problems with the quotes behind them — including the counter evidence, so you also see where the market pushes back.
Field notes
September 23, 2026
3 min read
Market Analysis for Startups Without the Consulting Deck
A practical market analysis for startups: size demand bottom-up, map the alternatives, and find the gap a small product can win.
September 20, 2026
3 min read
App Store Review Mining for Product Ideas and Gaps
App store review mining turns one-star reviews into a feature brief. Learn to read reviews for the gaps competitors keep failing to close.
Questions
How do you do a competitive analysis for a SaaS product?
Read what paying customers of the alternatives already wrote: reviews, forum threads and support complaints. Note the repeated gaps, the workarounds and the reasons people switched, then look for the opening they leave.
Why not just compare feature lists?
Feature grids describe what a product claims to do. Reviews describe what it fails to do for people who already paid. The gaps that matter show up in the second source, not the first.
What should a competitive analysis produce?
A short list of unmet needs with quotes, the alternatives your buyer actually has (including the spreadsheet), and one sentence naming the gap a small product can win.
How often should it be refreshed?
Whenever a competitor ships, churns or changes price, and whenever your buyers start asking for something new. A one-page analysis is cheap to keep current.
Run your own
Name a problem you keep hearing about — or the market people are stuck in. The report comes back with the problems they described, the quotes behind them and what they already tried.