Haven't quit the day job, but am making decent money.
I've found a sort of sweet-spot where working a couple of hours before work, and sometimes on weekends forces me to really focus on what I'm building. So I don't see myself quitting my day job until the support workload becomes unmanageable.
I started with the Next.js TypeScript Blog Template, and built things gradually, as I needed them.
By the time I realised I'd need a Stripe integration, I had already built enough functionality that it didn't make sense to replace everything with Divjoy.
If I were to start completely from scratch, sure, I'd use Divjoy from the start.
Comments
Haven't quit the day job, but am making decent money.
I've found a sort of sweet-spot where working a couple of hours before work, and sometimes on weekends forces me to really focus on what I'm building. So I don't see myself quitting my day job until the support workload becomes unmanageable.
For validating, I built a quick version in 7 days (https://onlineornot.com/building-saas-in-one-week-how-built-...), told the internet how I did it, kept building features, and customers kept coming back.
I'm curious why you used Divjoy for only billing. If you were to start again from scratch, would you use Divjoy at the start?
I started with the Next.js TypeScript Blog Template, and built things gradually, as I needed them.
By the time I realised I'd need a Stripe integration, I had already built enough functionality that it didn't make sense to replace everything with Divjoy.
If I were to start completely from scratch, sure, I'd use Divjoy from the start.