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.
Repeated Logins Across Systems
Users across many roles struggle with inconsistent, repeated, and manual authentication across numerous systems, wasting time and creating security gaps.
In their words
I'm looking at a major project to consolidate a fragmented Keycloak setup into a single, simplified solution (ideally managed like Auth0 or similar).
We need a migration path that doesn't break SSO for orgs still on Auth0 while a few orgs move to Keycloak.
Management doesn't want them signing in or out of Outlook just to access a shared mailbox for a few minutes if work.
We've had some people come and go already and it's sometimes a headache.
okta feels a bit much for where we are tbh
It took about 10-15 minutes to log in, load up and login to 7 different programs, all with different passwords.
everyone just used the same login credentials for the UniFi site manager... It wasn't even a limited user! It was the full site owner account
the password would authenticate and the Mac would just hang at the login screen
spent a whole quarter building an elegant permissions system with role-based access control and custom policies, only for our biggest customer to share one single admin login with fifteen people anyway
I shouldn't have to login to a completely separate portal, with separate credentials/ID/Auth to open a support ticket
as a small SaaS developer who just wants to focus on building my product and not spend weeks setting up auth
the general path forward is to have users complete the OOBE with the temp password, then change after they've logged into Windows - this feels very haphazard to me
My problem with the SSO providers is not the technical part, thats "easy". Its the coordinate with the 200+ external and internal vendors / support to redeploy the SSO part which is time consuming.
Many services have REST API’s to create, retrieve, update, and delete users. However, these may not have a SCIM connector available
IT admins and employees
Where they talk
- r/sysadmin
- r/IdentityManagement
- r/k12sysadmin
- r/okta
- r/salesforce
- r/SaaS
- r/selfhosted
- r/Intune
Tools they use today
- Microsoft Entra
- Okta
- Google Workspace
- Keycloak
- Microsoft Intune
- SAML
- Auth0
- Microsoft Authenticator
Why those fall short
- pretends logged in then demands login, wrong account costs 10 minutes
- Local IT lacks Azure AD access, so every lockout needs escalation
- SSO moved to Pro; migration loses owners, comments and task dependencies
- HRIS integration costs $4/user/month and management refused; job titles unreliable
- third-party portals are old and cannot do SSO
Map of ideas
Drawing the map…