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.
False Agent Completion Claims
AI agents report tasks as successfully completed without any ground-truth verification, so silent failures and half-finished work go undetected.
In their words
a minion's word is a claim, never evidence. the test can't be "did it report done." it has to be "does the world agree."
agent says booked you for tuesday at 2. customer hangs up happy, nothing actually booked
what do you treat as authoritative when the tool response and downstream reality disagree?
The only thing that counts is evidence the other side produced: a request on the wire, an id in their response, a confirmation page
I found actions that were "completed" in the conversation but nowhere in the actual system.
If it claims the job is finished when it isn't, I have to re-audit the entire task from scratch.
I cannot handle a junior that fabricates status.
the agent has proven an endless source of surprises
when I come back, I can't quickly tell whether a run actually did the right thing, quietly broke/regressed something, or just claimed "done."
An agent saying "I verified X" is not verification. Verify X yourself.
I had to painstakingly retrieve the galleries and cover images of much of the content by just the slug (AV website, it was hell).
Built is not integrated. Work on an unmerged branch or an unwired asset is not done.
Verification has been the painful one... batch execution, a minutes-long feedback loop, and no way to poke at a failure interactively.
Claude opus 4.8 kept asserting that this was a performance ceiling in the card abstraction I was using
AI agent developers and operators
Where they talk
- r/AI_Agents
- r/ClaudeAI
- r/LLMDevs
- r/ClaudeCode
- r/LangChain
- r/aiagents
- r/mcp
- r/hermesagent
Tools they use today
- Claude Code
- Claude
- git
- Codex
- MCP
- ChatGPT
- LangGraph
- Qwen
Why those fall short
- no hard separation between model narrative and real tool trace
- agent claims jobs finished when large parts of spec untouched
- no path from human-readable specs to Lean signatures
- verifier can short-circuit; no permanent proof a check ran
- agent summaries read clean but tests can be weakened or regressions missed
Map of ideas
Drawing the map…