SaaS ideas your next customers are already looking for
100 SaaS startup ideas for the people who said they'd pay, from agency owners to dentists. Micro SaaS ideas, AI SaaS ideas and B2B SaaS ideas: find yours, build it, sign them up.
Popular:
| # | Idea |
|---|
No idea matches this filter.
Pain points in business: what people struggle with
Search the problems to solve, as people described them on Reddit and other platforms, in their own words.
Popular:
| # | Pain point |
|---|
No pain point matches this filter.
Vague Requirements Rework
Teams across roles struggle with unclear, incomplete, or conflicting requirements that cause delays, rework, and misalignment.
In their words
He spends as much time talking with me to make sure he understands what I need as he spends coding.
I'd definitely pay for something that stops clients sending random messages like "change this thing on the homepage" with zero context
The biggest headache was always the stuff they assumed was "obvious" but never wrote down.
They send back something vague like "does not meet regulatory requirements" and I'm supposed to just figure out which part and why.
The part that takes the longest is figuring out what people actually want to see and making sure everyone means the same thing when they talk about a metric.
It's YOUR responsibility to tell ME what is/has been defined a requirement so that I can build those artifacts, not the other way around.
my org PMs are now expected to move from idea to requirements in a week, and complete hand off to engineering in 10 days
they all freak out when something goes wrong because a requirement was just ignored
Sometimes it takes a whole business day just to get a yes/no answer on simple questions
Nosso maior problema sempre foram os requisitos ambíguos ou pela metade.
All of our testing and product specs live in people's brains or are buried in random disorganized files on a network drive.
Not being involved in the discussions about what we are going to be making with The Business and we end up making The Wrong Thing too often
analysts who think writing software is rote factory work but somehow struggle to write a handful of coherent user stories
The thing is basically already done!
Software teams and stakeholders
Where they talk
- r/ProductManagement
- r/systems_engineering
- r/ExperiencedDevs
- r/embedded
- r/projectmanagement
- r/businessanalysis
- r/ClaudeAI
- r/QualityAssurance
Tools they use today
- Jira
- Excel
- Claude
- Confluence
- DOORS
- Word
- Claude Code
- Jama
Why those fall short
- POs don't write business-level AC or communicate them
- AI speeds writing but not judgement, synthesis or engineering capacity
- no shared metric definitions; requests don't reflect real needs
- key details and decisions are missed
- no structured brief or feedback process
Map of ideas
Drawing the map…