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.
Boilerplate Project Setup
Developers repeatedly lose time to boilerplate setup, toolchain drift, and fragile tooling before they can build actual features.
In their words
Stop making me wait a million years for your indexing.
i switch between 30-40 board types and its crazy how bad it is. i spend more time troubleshooting ports that are locked by the IDE
she has to build every kit manually which takes hours and hours to do for every size and every colour for each pattern
The issue my company has is Kotlin tooling is not as diverse as Java tooling is.
It's genuinely absurd the amount of memory that this IDE needs.
full builds are running around 25-30 minutes on a cold runner, which matches roughly what CI sees since we’re mostly doing clean builds on PRs. that’s the sore spot.
Every time I've said that on previous projects, "later" eventually turned into a weekend of refactoring.
Someone's always on a slightly different version and it surfaces in the strangest ways, usually right before a release.
Burned myself twice already with vue component librarys dying in development.
I can easily lose a complete day just patching configuration scripts to search the correct directories before a single line of code is actually compiled.
Having to set this up manually for each new microservice would take us about 4 hours and very time.
rebuilding all the underlying bundle logic every time feels increasingly hard to justify
Every time a test suite takes five minutes to run ... is an off-ramp to that flow state, and that's where I lose a whole hour to procrastination.
an LLM can propose a change and immediately begin running unit tests while type errors that might affect some other module are found in parallel
software developers and engineers
Where they talk
- r/cpp
- r/rust
- r/embedded
- r/FlutterDev
- r/godot
- r/vuejs
- r/Unity3D
- r/cpp_questions
Tools they use today
- CMake
- VS Code
- Claude
- Python
- GitHub
- dotnet
- Flutter
- GCC High
Why those fall short
- CMake documentation is pathetic and hard to understand
- workarounds still leave huge build times and 200GB target folders
- tutorials only cover small examples, not complex project structure
- no native Rust project type, no automatic DLL copy, no debugger support
- no incremental cleanup of old build artifacts
Map of ideas
Drawing the map…