Live data from Hacker News

Billing Engines Don't Solve Pricing Problems

tier.run

61–66 of 66 posts

Re: Billing Engines Don't Solve Pricing Problems

#61

I think they abstracted the problem so away that they have no idea what they are talking about. Having a single file that contains all your plans and make both your app, marketing pages, and Stripe work from it is trivial and is just good engineering. It's not a "Pricing Engine" or a "Pricing Stack".

There are definitely easier and harder ways to handle pricing, but especially when you have higher touch sales “just use Stripe” stops working in a lot of cases.

Ultimately bespoke sales deals show up, and you need to be diligent in your tooling and pricing design to make it work well (especially if you have any form of metering or dynamic pricing you want to take effect “immediately”)

It’s easy to have the handful of price points and fixed billing. But there’s a lot of ways for things to get more complicated.

Re: Billing Engines Don't Solve Pricing Problems

#62
post #30

Oh neat, I'm coincidentally trying to setup tier rn. Bit stuck in progress following Vercel template here https://vercel.com/templates/next.js/tier But I've already built out my own stripe usage-based billing app b4, and it sucks way more to debug that, so I get what you're trying to do here.

Would love to help. Let me know whats blocking you with the template? Also you can join our community at https://tier.run/slack

Re: Billing Engines Don't Solve Pricing Problems

#63

My company is building in the same space as Tier - in fact our offering looks close to identical. The problem we've faced so far is catching buyers who want to solve this problem, the deeper, underlying issue, rather than the problem that's in front of their face. For technical contributors, they're usually tasked to throw up a paywall, and you can do that quickly and easily using your billing engine and some lightwe…

Linking to your service https://www.heystage.com/ for reference.

Re: Billing Engines Don't Solve Pricing Problems

#64
Tier looks great. But unfortunately Tier's commit history on their main branch looks close to abandoned. I'd much rather pay money than risk picking unmaintained solo-dev OSS. If we're gonna end up having to manage the code ourselves I'd rather we write our own abstractions. Tough chicken and egg problem for them, I hope they solve it.

Re: Billing Engines Don't Solve Pricing Problems

#65

My company is building in the same space as Tier - in fact our offering looks close to identical. The problem we've faced so far is catching buyers who want to solve this problem, the deeper, underlying issue, rather than the problem that's in front of their face. For technical contributors, they're usually tasked to throw up a paywall, and you can do that quickly and easily using your billing engine and some lightwe…

100%. The main reason we created https://priceops.org is that there's a real mind-shift that has to happen for someone to realize that there's even a "there" there. Most people who've been through it understand all too well, but even there, it's tempting to think "Oh, if only we'd just committed ignorantly to a better pricing model..." not realizing that you'll always get it wrong and the context will always be chang…

https://priceops.org/ looks a lot like https://12factor.net/ I guess on purpose and by culture.
Post reply on HN