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.
Unverified Production Changes
Teams lack reliable automated verification and context to prevent risky, drifted, or unreviewed changes from silently reaching production.
In their words
i would pay if it actually catches real breaks not just false alarms all night long
We've had so many test environment outages that our boss temporarily approved Codex licenses
everyone was thinking how did this even ship
critical features stopped working and the team had to scramble under massive time pressure to fix issues that were essentially self-inflicted
Do teams usually have a way to automatically check whether a PR still follows the project’s architecture decisions and conventions?
We want our release branch to only have our changes, otherwise we risk pushing someone else's not ready work into QA or PROD.
A gate everyone routes around is not really a gate, it just looks like one in the audit.
He's basically been a 1 man PM, Dev, QA working at the speed of light with AI coding.
we don't build anything that relies on anything being in 'preview' because we're not certain when it will actually be GA
we were requiring PRs to be up to date with main before merge, but at our scale the PRs were constantly getting stale which was leaving us blocked for long stretches
Both versions look identical on launch day. The cost only appears eight months later
Their servers would just throw us random 500s when we try to pull a repo. Inconsistently. Again, this would break our deployments
I've worked at a large enterprise that have a "Change Advisory Board", that you need to convince when you want to bump the major version on your linter.
Migrating sucks but so does having 500 engineers who can’t do any coding work for a day every {month,week}
software and platform teams
Where they talk
- r/devops
- r/SaaS
- r/ExperiencedDevs
- r/AI_Agents
- r/SideProject
- r/ClaudeAI
- r/git
- r/PowerBI
Tools they use today
- GitHub
- git
- Claude
- GitHub Actions
- Azure DevOps
- Linear
- Power BI
- Jira
Why those fall short
- deploys were a black box unless you were the deployer
- rubber-stamped PRs, no verification, no shared mental model of breakage
- no PR workflow, lead only replies it's okay without reading code
- No staging, beta track or kill switch for bad releases.
- Security blocks third-party automated code quality checkers
Map of ideas
Drawing the map…