4 ms·
> the part or building a SaaS business that everyone needs to do. A few critical ones off the top of my head - payments (subscriptions, cancellations, invoice
by zild3d 5y ago
> the part or building a SaaS business that everyone needs to do.
A few critical ones off the top of my head
- payments (subscriptions, cancellations, invoices, etc)
- authentication (signup, login, invite, forgot password)
- transactional emails (confirmations, etc)
for enterprise:
- permissions, access controls
- audit logs
- gdpr
- reporting, monitoring
- single sign on
other common saas-y needs
- notifications
- error monitoring
- performance monitoring
- admin tools (impersonate, deletions)
- feature flagging
I'm surprised a "SaaS in a box" hasn't really gotten traction. I think part of it is the tech stack dependencies - frontend frameworks, backend languages & frameworks, infra, databases, 3rd party tools
- ozim 5y agoFrameworks like RoR, Laravel, .NET framework provide most of it which are mostly SaaS in a box from technical perspective. Then you have headless CMS-es on top of which you also can build stuff. So you can plugin your email provider, payment provider, single sign on. It does not take much code but you still have to understand how to integrate stuff. Then you have wordpress where people basically install all kind of plugins and you can have all what was listed in CMS, but then you get "wordpress developers" to hire so I don't see much difference.
- joshmanders 5y agoYou gotta understand that a lot of people who go into bootstrapping a SaaS are technical people, mostly developers. We're highly opinionated and naive af on stack stuff. We could find the ideal "SaaS in a box" framework/boilerplate, but one small feature just doesn't sit right, so now we're building it all ourselves.