I think the problem with your business model is:
- People who have already built their company/website/product are not going to move the world to adopt your platform. It's just too much work.
- This leaves you with people who haven't built/shipped anything yet, who aren't really willing to pay $500-2000 for your software (there may be exceptions, but not thaaaat many).
I think a really successful business model would be something like:
- Free for the first $10k revenue
- 3% of revenue after that (auto calculated via Stripe)
This way, many more people will get started with your software, and those that are actually successful will end up paying you a lot more than $500. "We don't get paid till you do" is the headline on your pricing page.
I'd imagine your retention would be amazing because it'd be very difficult to move off (similar reasons as Stripe, AWS).
I own a consultancy and I might find this interesting as I don't have an internal SaaS framework yet.
The two problems I see are:
1. Lack of options... There may be some parts of the stack that I don't like or don't fit requirements
2. Unknown code quality... Cannot tell what the coding standards are. This is related to #1 in that I don't know how hard the code will be to modify unless I read it.
Otherwise it's an interesting proposition. React/Nextjs are my jam, and I prefer serverful (Django) to serverless but that might be negotiable. But even if I wanted to drop in my own server, if the front-end is well coded I could easily save 2x-3x the 1.8k sticker price in dev costs on a single project.
If I were to build a SaaS myself, I might also find this interesting with all the caveats above, but I would 200% certain not pay a revenue share unless the platform really required minimal tweaking and was about 90% adjusted to my use case, and provided continued platform value after that launch (like, say, Shopify).
If you can get all of that for free (to start), and that saves you months of building, that's pretty worthwhile. At $1m ARR you're only spending $30k/yr on the platform, which is roughly what your AWS/Stripe bill is anyway.
There can definitely be more features too like user permissions, A/B testing, CMS, analytics/tag manager integration, etc, etc that continue to deliver value / save you time/money/effort as you grow.
These all things we wanted to tackle at Clerk (https://www.clerk.dev) as a SaaS. The first thing we hit down that path is user authentication -- and that opened up an entire can of worms we're still working through. User authentication alone has been tough enough because you can't just build yet another Auth0 clone and brand it "passwordless"... you'll have a tough time competing against the incumbents. This has led us to session management, which proved tricky to get right across local development and production environments, and has led is to the disparate ways people authenticate, which is a massive API design challenge. However, we think it could be a game changer, especially with all the Next.js / React advancements as of late. Especially the component-ization of the frontend in conjunction managed backends, session management feels like something that ties it all together.
I'm certainly excited for the next decade of developer tools :). Things will get dramatically easier with all these commoditized verticals.
Here in terms of Nextless.js, as the customer will have access to the source code, the revenue sharing like 3% as you suggest is extremely hard to implement. It raises a lot of technical challenge...
Perhaps in the future, this concern can be addressed somehow and your proposed business model shall be implemented. Have you had such concerns/experiences for your projects? Pricing is not an easy subject though :)
All of them give access to:
- Dashboard UI
- Landing page
- Form management
- Infrastructure as code
- Serverless for scalability and pay-as-you-go pricing with no server to manage, no docker, no kubernetes
Thanks to cutting-edge tech, you can deploy your backend in one command and the same thing to provision your cloud infrastructure (also in one command). With Serverless, everything scale based on your traffic, you don't need to worry about over/under provision with little maintenance.
I was a web developer in 2010 and the developer experience wasn't the same. You need to rent a server, SSH to the server, install OS dependencies, install a firewall, install a webserver, install a database, log management, monitoring, etc. and still, I didn't talk about your application and business logic. Launching a SaaS in 2010 has been extremely painful.
It seems there are a lot of dependencies but every dependency is integrated into Nextless.js for a reason. It's just the bare minimum to build a high-quality SaaS product in 2021.
Nextless.js speeds up development for your SaaS with UI components, authentication, subscription, form management with developer experience in mind: type checking, linter, code formatter, editor configuration.
Not only Nextless.js will help you to build your SaaS, but it also takes care of your production environment by leveraging serverless.
On the contrary, using all these dependencies, remove a lot of burden from you and give you more time to focus on your business. No need to be an Ops engineer or UI/UX designer anymore for a small SaaS.
Still not convince? You aren't dealing with these dependencies directly, a lot of them work under the hood and Nextless.js are taking care of them. So, no need to worry about these dependencies yourself and Nextless will receive updates. You just need to focus on the things that make your SaaS unique and grow your business.
PS: Sorry for this long response ;) I started with one paragraph and make a short response. But, I end up with this huge text and I hope it responds to your questions.
- User dashboard
- Landing Page
- Stripe integration
- Type checking, linter, code formatter
Nextless.js provides everything out-of-the-box for you to build a SaaS business and focus on the things that makes your SaaS unique. You shouldn't lose time on boring UI, setup and configuration.
They have a free example on their page, covers most of what this is offering
What's keeping me from using serverless for more general purpose SaaS is that there is absolutely no good answer for background jobs. Sure, you can plug in some external CRON service, use GitHub Actions, or maybe use something like quirrel.dev. But none of that comes close to "rails g job example" (or your favourite frameworks equivalent).
Good luck with your project, though!
I've never tried it myself but there several option to build a background jobs in serverless mode: Amazon EventBridge and CloudWatch Events. You can check the documentation at https://docs.aws.amazon.com/AmazonCloudWatch/latest/events/S...
So, no need to plug any external service.
I'm totally bias but I love Serverless, you can do everything. Background jobs shouldn't stop you using Serverless ;)
What's the strategy here?
Node.js is a horrible programming language with a worse package system and anyone who thinks otherwise hasn't had the privilege to work with something else.
You also seem to have a vendetta against me. You okay?
Likewise I think someone starting up for themselves is more likely to be a React programmer than a PHP programmer.
I also think it's damned near impossible to find React developers who are capable of doing anything that isn't React flavored.
For those reasons alone, I'd choose PHP over React, especially if I want to scale.
As someone who ran a company for 5+ years on a Node.js stack, never again.
Before when I managed 5k+ servers running PHP, I actually slept at night knowing nothing was suddenly going to go wrong because of some stupid memory consumption bug or exploit in a popular and critical package.
Anything you can think of, chances are there is not only a PHP package for it, but probably an out-of-the-box Laravel package.
Whatever this is, it won't beat Laravel.
I'm do it more "on the side", the actual goal is an SaaS product.
Also, I'm looking more into non-AWS solutions right now. Cloudflare Workers, FaunaDB, Auth0, Paddle, etc.
Definitively, there are several ways to build a SaaS product and I also think Cloudflare Workers, FaunaDB, Auth0, Paddle, etc. is a good stack.
One good thing to use AWS, everything is centralized. Another good thing is you can use Infrastructure as code. As a developer, you can provision everything with code (TypeScript), no need to click and remember user interface.
AWS brings more out-of-the-box.
But stand alone solutions are usually more polished.
Currently, I'm using Pulumi, which is like the AWS CDK, but for more than AWS.
I built some resource providers for unsupported services, and it worked like a charm.
I'll seek the help from a native english speaker.
* Infrastucture -> Infrastructure
* Dasbhoard -> Dashboard
I do wish the project success and hope they're able to find their market.
Nextless.js is different compared to blitzjs, here is the feature which aren't available in blitzjs:
- Payment integration
- Deploy in Serverless environment
Nextless.js focus on SaaS application and help you build your SaaS product faster.
For the backend, it uses AWS lambda with API gateway and protected by AWS Cognito for private route.