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.
Realistic Test Data Generation
Teams struggle to generate and manage realistic, constraint-respecting test data that mirrors production, causing slow, flaky, and unreliable testing.
In their words
this might solve a massive issue we have with our data warehouse where we have to hand roll a whole bunch of seeding code
teams who passed on load testing and then come to us with issues when they get load in production
I am spending more time qa-ing my code than writing code and was looking at a way to make it more efficient
I've broken prod quite a few times. Every time it happens I mention it could be avoided with a proper test environment that's iso-prod. Still waiting after 2 and a half years.
these accounts end up with hundreds or even thousands of orders attached to them
So often we have clashes when multiple people want to test their feature branch on a test environment.
Testing under these conditions is usually far more difficult, far more uncertain, far slower, far more expensive than in simpler environments.
We have a test environment with a copy of the production database, but of course it is impossible to simulate the same workload there.
writing pgTAP tests by hand for every single migration it generates is completely killing our velocity
If a feature branch or external branch preview is still connected to the same Lovable Cloud backend as production, then the code is isolated but the data isn't.
they give up and I'm back to hand writing seeding scripts again
Is there any way to get more test data without manually keying a lot of vendors, customers, transactions, etc?
Testing involving models is slow. It runs all your migration.
the business logic that inevitably ends up in SPs - how do you go about unit testing that in isolation, and particularly from a behavioral standpoint?
QA and backend developers
Where they talk
- r/QualityAssurance
- r/Playwright
- r/softwaretesting
- r/microsaas
- r/programming
- r/automation
- r/lovable
- r/SQLServer
Tools they use today
- Playwright
- GitHub
- Neon
- Bitbucket
- Lovable
- PostgreSQL
- SQL scripts
- Claude
Why those fall short
- applying all migrations takes minutes and is done many times
- sqlx::test generates lots of code, slowing recompilation
- manual copying always happens; framework is old and slow
- environments built by contractors, no proper data separation or governance
- truncate too slow with thousands of tests; nested transactions block per-test rollback
Map of ideas
Drawing the map…