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.
Unversioned Prompt Changes
Teams lack version control, review, and rollback for prompts and configs, so changes silently break production and debugging takes days.
In their words
We could see the regression but not the answer whether it came from the prompt, the model, the tool instructions or the environment promotion step.
we just didnt have one place that answered the question "what prompt is actually live right now?"
every Sunday there are at least a few changes that come in after we've already started building everything
Our "system" for managing this is a Notion doc with prompt versions and dates, Slack messages saying "hey did you change anything"
I'm fine with them editing prompts, I just need the changes to leave a trail.
a prompt change quietly changed behavior for one customer and nobody could answer who changed it or when
Two people editing the same nginx.conf in one week wiped out three days of one guy's changes, and nobody noticed until a client site went down.
stoert mich die Praxis mein Angebot incl Logo zu kopieren und ungetrackte (!) Aenderungen vorzunehmen enorm
We spend way too much time arguing over a single freaking sentence which inevitably turns into a bit of a shouting match
We had no prompt lineage tying an immutable version to region, cache state, model metadata, and request time.
Was a nightmare to keep track of which site was on which protocol version.
Oh by the way, we updated the UI.
I run daily check-in voice calls for older adults, so prompt drift across agent variants is a real operational problem on my side.
Since saving overwrites the previous version, I’ve never found a clean way to see what changed in a workflow week-to-week.
AI and engineering teams
Where they talk
- r/AI_Agents
- r/ClaudeAI
- r/PromptEngineering
- r/SaaS
- r/LangChain
- r/LLMDevs
- r/devops
- r/SideProject
Tools they use today
- git
- Braintrust
- Notion
- Claude
- Slack
- Claude Code
- Langfuse
- Excel
Why those fall short
- New model ignores existing crafted MDs; fixes take long and break older models
- control panels banned as attack surface; no versioning or audit
- very hard to catch when we test
- PDF is not meant for editing, so changes arrive untracked
- UI and measurement behavior differ between versions.
Map of ideas
Drawing the map…