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.
API Integration Testing Pain
Developers struggle to test and maintain integrations against real third-party APIs because mocks and docs drift, causing production failures.
In their words
O cara pedindo API e eles passaram 40 minutos tentando convencer ele que era melhor ele dropar do portal dele e usar mcp no claude code, pagando mais caro por isso.
Honestly yes if it actually catches these mismatches before deployment and saves me from debugging frontend and backend issues
sales telling a client we'd be able to automatically sync their data from a third party through the API that party had available. That party didn't offer an API.
the OOTB spokes were not sufficient for our needs, or consumed way too many transactions to make them sustainable
Instead of "took me 3 days to write," it's now "took me 3 days to verify it actually works in prod."
Has anyone successfully deployed a node.js service that can answer REST API requests and return JSON data from an RPGLE program or service program?
Between me performing the code change and me saying "yeah check now", there is a 5-8 minute delay.
we had over 40,000,000 API calls in a year from maybe 125 integrations
how do you guys handle this without wasting 2 hours setting up fake servers or messing up your codebase with temporary dummy data?
has anyone found an easier way to keep Stripe setup from turning into random frontend and backend glue, or is a dedicated backend still the only stable way?
Every few weeks, a minor API update would break it, and I'd spend half a day troubleshooting.
As our number of services has grown, our API workflow has become more complicated than we'd like.
I reverse engineered the internal API of a SAAS tool we use and it allowed me to gain programmatic access to data that was only available in their slow clunky UI.
We've seen integrations stall for weeks because of environment config differences and dependency conflicts on the customer side.
backend and frontend developers
Where they talk
- r/AI_Agents
- r/SaaS
- r/webdev
- r/QualityAssurance
- r/nextjs
- r/brdev
- r/n8n
- r/microservices
Tools they use today
- Postman
- Swagger
- Stoplight
- MSW
- n8n
- APIM
- OpenAPI
- Python
Why those fall short
- third party offered no API to sync data
- no rate-limit awareness or API governance
- Rate limits clobbered by thousands of test requests in seconds
- static review and local tests miss runtime behavior like idempotency and retries
- Vendor connectors poll frequently and cannot be throttled or configured
Map of ideas
Drawing the map…