[scottybo]

Billing and the associated subscription models is a problem that has been largely solved, so there isn't much need to roll your own. Instead you can dive straight into the 'fun' parts of your project.

I used Laravel Spark + Stripe for my SaaS and it works great.

However.. The downside is that if major changes happen (e.g. The new SCA regulations) you could find the core modules used in a package such as the Laravel billing package need to be upgraded, so you have a domino effect where everything needs to be upgraded. We were left with a LOT of work as we had to upgrade Laravel core to a new version, which meant upgrading from Bootstrap 3 to 4 (a huge job).

I wouldn't change our initial approach as it allowed us to quickly get a product to market and see whether it was viable, but the reality is that we will be rebuilding the entire system from scratch in the future to get rid of the legacy inefficiencies.