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.
Silent Automation Failures
Automation workflows report success while silently failing or producing no output, so breakages go unnoticed until clients complain.
In their words
The first weird invoice that came through did not crash anything, it just quietly passed the wrong number down the line, and I only found out because the client noticed.
A token expires or an API changes, the flow stops, and I only notice hours (or days) later when something downstream is already broken.
It keeps firing and everyone assumes it's working, because these tools only look for errors and no error was thrown. You find out eventually, usually from the client.
An automation failing silently is how you lose the account.
A workflow just stops. No crash, no error, it just quietly stops firing or "succeeds" while doing nothing.
alerts were always late and half the time it showed false positives, i ended up building my own monitoring
they've got a workflow that works... sometimes. On a good day. If the wind's blowing the right way.
a job that failed and a job with nothing to do look exactly the same from outside
tasks that were working fine suddenly become less reliable, and you end up spending more time troubleshooting than actually improving the project
A make scenario fails silently and I find out two days later when a user pings me.
I just don’t want maintaining the stack to become half my job
you find out weeks later when they ask why leads stopped getting follow-ups
The workflow executes. Every node is green. No errors thrown. And zero records actually landed.
failures never happen when I'm at the desk - it's always a webhook dying on a Saturday. Checking the failed execution from the phone instead of
Automation builders and agencies
Where they talk
- r/n8n
- r/automation
- r/nocode
- r/AiAutomations
- r/zapier
- r/AI_Agents
- r/SaaS
- r/microsaas
Tools they use today
- n8n
- Zapier
- Make
- Google Sheets
- healthchecks.io
- Slack
- cron
- Telegram
Why those fall short
- job running is not the same as job working; silent success worse than loud crash
- no error handling, no docs, no notes to debug from
- jobs report success when only queued; no proper alerts
- catches didn't-run, not ran-successfully-but-did-nothing; windows drift or desensitise
- green run status hides bad business outcome; error monitors miss volume, cost and silent stops
Map of ideas
Drawing the map…