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.
Stale Docs After Shipping
Teams ship code fast but changelogs, help docs, and AI-generated markdown files go stale because updating them is manual and skipped.
In their words
The information exists, but finding it is the problem... a lot of the useful context was basically in one person's head.
a folder full of markdown files spanning months of planning, half of them stale, and no single place that answers the basic question — where does this project actually stand right now
We're looking for something that gives us easy collaboration + version control while keeping the files in Markdown.
What are you using to manage frequently changing Markdown files that serve as context for AI agents?
The agent quotes the old article with total confidence and closes the ticket.
it’s pretty common for an endpoint or parameter to change without someone remembering every guide that references it
We're looking for something that gives us easy collaboration + version control while keeping the files in Markdown.
my job is now also doing this enmasse with documentation
it makes up screen/portal names and can’t write a release note if the ticket lacks content
How are you actually keeping these docs updated without it becoming a manual nightmare?
I lost like 1 or 2 hours on every single feature release step.
Cursor ships frequently enough that keeping runbooks and onboarding docs accurate basically becomes its own maintenance job that nobody owns.
I'm getting less and less knowledgeable about the details of my own code, so it's hard to fact-check everything all the time.
If the docs are stale, the agent context is stale too. We’re working on our own help center and llms.txt setup
Small SaaS and dev teams
Where they talk
- r/ClaudeCode
- r/ClaudeAI
- r/codex
- r/devops
- r/microsaas
- r/vibecoding
- r/AI_Agents
- r/SaaS
Tools they use today
- Claude Code
- git
- GitHub
- Claude
- Jira
- Google Docs
- Confluence
- Notion
Why those fall short
- engineers don't know which pages a change affects
- No single source of truth; nothing flags docs that fall behind code changes.
- makes up screen/portal names, can't write when ticket lacks content
- AI capability chosen over usability; every other writer task slower and harder
- entries reference internal names, include irrelevant refactors, unsorted by category
Map of ideas
Drawing the map…