Live data from Hacker News

Per Seat Pricing Sucks

blog.flippercloud.io

11–12 of 12 posts

Re: Per Seat Pricing Sucks

#11
post #2

Tiers based on seats doesn't seem all that different. Flipper Cloud seems to be roughly $60/seat/yr but only buyable in fixed chunks, meaning some pay as much as $499/yr for 1 seat, others pay $50/seat for 10 seats, others pay $136/seat for 11 seats, etc. So now, as a business with 10 users, I still have to decide if my 11th new employee is worth $1000/yr for their seat, if I should kick someone else off and give it…

There has to be some sort of limit because "unlimited" can easily lead to customers using far more resources than they're paying for.

However, by moving away from per-seat pricing, customers who have switched to the new pricing have now added many more users who can benefit from having access to the Flipper Cloud UI but were not worth paying for individual seats before.

So based on customer behavior and reception to the new plans, it has made things much more flexible for them in practice.

Re: Per Seat Pricing Sucks

#12

Pricing is hard, no question about it. One solution to the “not all users are equal” problem is to create different types of users and price accordingly. That’s what we’re doing, and it’s working out well so far. It depends on the product and use case, of course.

It still creates non-trivial day-to-day overhead for customers where they now have to think about who to invite and what permissions to grant them in conjunction with costs.

We'd much rather that 90% of the cases, customers can just invite anyone on their team without fearing ballooning costs. Then they can think about permissions purely from a permissions/access perspective and not have to factor cost into that decision.

Post reply on HN