Let's assume you are CTO of a growing SaaS company, and you are tasked to rebuild the hand-cranked billing solution that is beyond the end of its life. You want to replace it with a state-of-the-art self-service billing solution without spending much effort on your product resources. I'm going to ask you three questions, answer each in your mind before continuing reading. Here we go:
Will you build an in-house payment gateway solution to handle credit card payments?
Of course not. Stripe is the way to go. There is absolutely no reason for any business to be developing a payment gateway solution unless that is their core product.
Will you build your in-house subscription billing solution to automate recurring revenue?
Again, of course not. If you're already using Stripe, the obvious choice is Stripe Billing. If not, there are hundreds of subscription billing tools out there.
Will you build the UI/UX of your billing inside your SaaS platform so your users can see plans, pay, and manage billing info?
Yes, maybe? Your answer is most likely because you have a very custom flow and want it to be scalable and fit the brand. After all, the point was to upgrade the billing to scale with the current growth rate.
If I ask you the last question two years from now, your answer will be an obvious no, similar to the first two answers. Why? Because embeddable customer-facing solutions like Billflow will be no-brainers, just like how payment gateways and subscription billing solutions are currently.