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.
Slow Incident Root Cause
On-call engineers waste hours manually correlating scattered logs, metrics, deploys, and code to find incident root cause.
In their words
ever since around Jan 2026 every single piece of software, app, os, *anything* is breaking 3x as often now
I have spent the last year begging for scope to actually start to fix the root cause of the issues.
The fix took 90 minutes. The report took 2 hours.
Is there a faster way by which we can identify or stich the malicious website the led to an incident?
it took us 14 hours of bouncing between grafana dashboards, grepping through logs, and cross referencing slack threads to piece together
It’s the “ok, something weird happened… now who actually moves first, and what do they do?” That part is usually hand wavy.
the handoff between teams... at 11pm on a Saturday that gap is where the incident actually gets worse
Usually Google Analytics tells you that something happened, but not what happened.
The docs exist but you don't trust it's current, so you ping the author anyway.
nobody could even agree what state the remediation was actually in
he has to send a bunch of emails to different people instead company explaining what happened and said that takes up too much time and he doesn't want to have to do that
We currently don’t have a way to capture “identified time”, and in practice that often does not match when the ticket is opened.
I'd happily authorize a 100x spend for when we have a prod outage on a mission critical service.
context is definitely spread across different tools — and that's the painful part... bouncing between the host's logs, the third-party service's own dashboard
On-call SREs
Where they talk
- r/sre
- r/devops
- r/Observability
- r/sysadmin
- r/SaaS
- r/analytics
- r/cybersecurity
- r/servicenow
Tools they use today
- Slack
- Grafana
- Datadog
- PagerDuty
- GitHub
- incident.io
- Claude
- Jira
Why those fall short
- monitoring tools exist but few help investigate unexpected changes
- Huntress dashboard shows little; Petra has better visibility but still requires manual investigation.
- vendor oncall helpers were slower; needed in-house build
- runbooks only help with familiar incident shapes
- alerting routes by symptom, not by code ownership
Map of ideas
Drawing the map…