Billing Engines Don't Solve Pricing Problems
1–10 of 66 posts
Re: Billing Engines Don't Solve Pricing Problems
#2A pricing SASS company without a pricing page? Umm?
Re: Billing Engines Don't Solve Pricing Problems
#3Tier seems to be solving a real problem that every company beyond MVP stage will face.
What I would love to see is a tool that would make it easy to run multi-variant pricing experiments and give me the optimal pricing down to geo, platform etc. "Optimal" being the maximum cash collected.
Re: Billing Engines Don't Solve Pricing Problems
#4Concerned about the number of lightweight marketing blog posts making it to the front page of HN. It’s like it’s part of the “marketing to devs” playbook at this point.
Re: Billing Engines Don't Solve Pricing Problems
#5A pricing SASS company without a pricing page? Umm?
Guess they need a pricing engine.
Re: Billing Engines Don't Solve Pricing Problems
#6A pricing SASS company without a pricing page? Umm?
"Don't worry about pricing ever again, we'll take our money without you ever knowing ;)"
/s in case it isn't obvious
Re: Billing Engines Don't Solve Pricing Problems
#7Is this product extensible beyond SaaS style tiered subscription models?
I love the pricing space, but at first glance, the limitation in your company's scope seems depressingly limited and is essentially hard-coded into the name of your company (Tier).
I have grandiose ideas, hopes and dreams of what the pricing space will look like in the future, and it doesn't involve immutable JSON files.
But I can see why this would be really useful right now. Looks great.
Re: Billing Engines Don't Solve Pricing Problems
#8My 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 lightweight hard-coded logic.
For the business stakeholders, they're usually paralyzed by an inability to decide what the pricing should be, and implementation is an engineering problem. I spoke to one buyer recently who was doing a re-pricing exercise (which Tier and Stage both promise to make easier going forward), but even he believed that this re-pricing would be the last, and that further adjustments would be minimal.
It's nice to see other, credible people enter the space - I think it actually is a problem worth solving, and it's neat to see how their approach rhymes with ours. Of course I don't wish them too much success, since I'd like to have some customers too.
Re: Billing Engines Don't Solve Pricing Problems
#9The idea of splitting off payment plans into its own abstraction is super interesting. Personally I would really like if the abstraction layer also was independent of the payments processor, currently it seems heavily dependent on Stripe. Even though I currently use Stripe I find them to be untrustworthy and don't want anything that ties me to them even further. And more generally, using a platform built on top of a SaaS is a recipe for future headaches.
Re: Billing Engines Don't Solve Pricing Problems
#10Concerned about the number of lightweight marketing blog posts making it to the front page of HN. It’s like it’s part of the “marketing to devs” playbook at this point.
Devs tend to know less about marketing than might be optimal for them. And the startup / side project crowd certainly needs some marketing knowledge.
No wonder sometimes such posts get upvoted as useful or even insightful.