Since many of you are building SaaS apps, you know that building your core product is only a part of the challenge.
To actually run the business, your app needs a ton of generic stuff:
- user registration + email verification
- forgot-my-password emails
- add/edit credit card
- change plan
- payment invoice/receipt emails
- “your card failed, login and update so we don’t shut down your account” emails (aka “dunning”)
Frameworks like Rails have components to do pieces of this, but nothing comprehensive.
People using other languages like Go, Node.js, Clojure, or frontend-only stacks are mostly out of luck: They have to roll their own solutions.
As a bootstrapper, I don’t have the team, time, or resources to do the necessary frontend design and backend server juggling to build custom solutions all the time.
That is to say, I’ve had a lot of promising lil’ apps and side projects that I never launched because it was just too much work to put 'em online and start charging.
My friend and I have been working for the past several months to try and factor out all of this stuff and “solve it once and for all” = )
You can see more details on our landing page:
or this 9-minute zero-to-SaaS app YouTube overview:
The basic idea is that you can either spend $10k + 2 weeks to do this boring stuff custom, or you drop in some JS that solves 95% of what you need and get on with shippin’ your core product.
I’d love to hear what ya’ll think:
- Does this solve a problem you have?
- Could you ship something faster by using Denizen?
- Does Denizen let you ship a lil’ project that otherwise wouldn’t have been worth the effort?
Are there any features or use cases you’d like Denizen to support?