Re:The 14 pains of building your own billing system
by Rafsark on Monday February 26, 2024 @11:16AM
(#39513026)
(Lago co-founder here.)
I guess it depends on how complex your pricing and monetization process are (is it the same pricing for everyone or custom ; is it a simple subscription: or a is there revenue share, transactional pricing, usage-based, tiers ; is it self-serve or sales-led with a quoting system, do you have grandfathered plans, do you need to use other payment processors than Stripe - "Stripe Billing" is only usable with "Stripe Payments").
In some cases, it's "brain dead simple", in a lot of cases it ends up "being much more complex than it seemed".
Related threads: - "Why Stripe doesn't use Stripe Billing": https://news.ycombinator.com/item?id=33191307 - "Stripe's real pricing: a primer" : https://news.ycombinator.com/item?id=33920019
Re:The 14 pains of building your own billing system
by atonse on Tuesday February 27, 2024 @10:43PM
(#39533711)
I wouldn’t actually expect stripe to use stripe billing. Just like I don’t expect AWS to be built on top of AWS.
The point is that I’d happily pay someone else to sweat the details than my own team. Our volume is so small that it is a no brainer, especially if you want to sell in multiple countries.
But in all seriousness, we looked at Stripe, thought about "aw man is it worth spending the .5% extra" and then spent about 30 seconds thinking about how much time it would take to roll our own, and it was an absolute no brainer.
(replace Stripe with any of the other similar competitors, not trying to be too biased, but stripe is kind of the mind-share default for SaaS startups, aren't they?)