3 ms·
I know you're reworking the pricing page as you said but you may want to consider doing what a lot of email service providers do and list the per-user price in
by pc86 14y ago
I know you're reworking the pricing page as you said but you may want to consider doing what a lot of email service providers do and list the per-user price in tiers.
Something like
* Users 1-2,500: $0.01/user
* Users 2,501-20,000: $0.0625/user
* Users 20,001-80,000: $0.0583/user
might be a tad more intuitive, especially if you listed the top-end price along with that.
- pbreit 14y agoI don't think per user is the way to go. Customers want more predictability. Plus, per user feels like it's penalizing growers. It seems a bit more appropriate to charge per/email since there's som atomicity there. For analytics, simple tiers (without pro rating) should work fine.
- matm 14y agoThis is interesting. Our naive thinking was "fewer numbers" implies "easier comprehensibility", but I don't think the pricing was quite as understandable as we would've hoped. I like your suggestion a lot.
- eddmc 14y agoKeep the pricing message simple. I'm not a fan of variable pricing - I like to know what the monthly cost is going to be beforehand. I appreciate tiers where I can see what I'm going to hit depending on growth over time. Someone below said that you should base your pricing on cost - I completely disagree. You should absolutely NOT look at cost when you put pricing together - rather, you need to ask your customers about the value of what it is you're providing. For example, Heap will be saving the time and hassle of deploying a generic solution on a server and the time of customising it. Plus Heap will be improving their product every day whereas the self-hosted version would need a developer to add new features. These sort of things all add up - you'll be surprised what you find out when you ask your customers. Pricing is hard. There are a lot of good articles and discussions on HN if you do a bit of searching. Good luck. Heap looks good