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.
AI Code Outpaces QA
AI-generated code ships faster than QA can verify, producing unreliable, bloated, or hallucinated tests that miss real defects and let regressions slip through.
In their words
it's quite expensive to have claude come up with the plan and run it every single time, especially when feature is evolving
unit tests which claude write and executes never faile
I have some thoughts on making a performance test tool with reporting but need some ideas on what sort of solutions are being done on other companies.
over 80% of our code is now written with AI and we're shipping more defects than features
Before a 40 questions test produced by either would require me to review all 40 and usually have to give changes to roughly 15 questions.
turning AI-assisted prototypes into something reliable enough for real use: regression control, performance, edge cases, architecture drift
QA doesn't have enough capacity to match our pace, hence we are being made to sit idle.
We decided to skip QA because of ownership. And while testing so many things broke
A sea of unit test generated by AI with no concerns about being DRY or readable by a human being.
I am a full-time test babysitter for an AI system that was supposed to eliminate my department
I'm the only QA left... I have been given two projects to test by myself.
Claude is telling them what to test and how to test it, they don't know what they're putting into tickets
They're running the code but not asserting anything. Or they're asserting test inputs instead of implementation outputs.
It happens and I hate it. What happens: the tests are green and all looks falsly good.
QA and dev teams
Where they talk
- r/QualityAssurance
- r/softwaretesting
- r/ClaudeCode
- r/ClaudeAI
- r/AI_Agents
- r/vibecoding
- r/Playwright
- r/Everything_QA
Tools they use today
- Claude
- Playwright
- Claude Code
- Codex
- Cursor
- Jira
- Selenium
- Copilot
Why those fall short
- manual testing non-negotiable; human-in-loop approval legally required
- barely get time to do dev testing
- expensive to re-plan and re-run the same e2e path every time
- tests written from the same code pass by construction, never go red
- tests assert implementation details and wrong business logic
Map of ideas
Drawing the map…