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.
Hidden AI Agent Failures
AI agents fail, stall, loop, or falsely report success without surfacing errors, so problems go unnoticed for days or weeks.
In their words
we continue to have issues where the N1 agent just "dies". The service is scheduled to restart it twice and then do nothing.
She also keeps breaking in ways we do not find out about for days, by which point the lead is gone.
came back to my macbook fans screaming and the session had been stuck waiting for input for like 20 minutes while burning memory doing nothing useful
those 5 sub-agents spawned their own children and grandchildren and that happened recursively
I'd pay if it accurately highlighted real user frustration, not just model mistakes.
Our rule catalog only covers mistakes our agents already made, so every new integration starts naive, and that's exactly the gap you're closing.
not letting Hermes fill the disk so I can’t even chat it to fix it
Glance at a screen, know the state of my company. No log-tailing.
agents that look busy but aren't actually getting any closer to completing the task
the polling only happens while my own coding session is open. Close it and the agent goes deaf.
Our failure mode was never a bad plan, it was agents that silently stopped. An agent that died looks identical to an agent thinking hard.
I give you a data source and an endpoint. You poll on schedule, call me with what you found, I say fired or not and hand back state.
Running four or five Codex agents in parallel, what eats my time isn't reasoning level, it's noticing one went down a wrong path
an agent batch of mine fires on a schedule every morning with nobody watching it start, so "dead or thinking" is the normal state
AI agent developers and operators
Where they talk
- r/AI_Agents
- r/ClaudeAI
- r/hermesagent
- r/ClaudeCode
- r/LLMDevs
- r/aiagents
- r/LangChain
- r/n8n
Tools they use today
- Claude Code
- Claude
- Hermes
- cron
- Codex
- Braintrust
- Cursor
- git
Why those fall short
- no unified view of which agent is waiting; easy to miss questions
- Task-level monitoring records success while the action was semantically wrong
- no guardrails against self-update crashes or disk exhaustion
- no proper error tracking, failure alerts or health checks built in
- Tools assume worktree/project workflows; add complexity and no unified status view
Map of ideas
Drawing the map…