4 ms·
For sure this is interesting to think about. Is all the work I need to do for the unpaid people who may or may not ever pay me a penny worth it to get a few mor
by brianwawok 11y ago
For sure this is interesting to think about. Is all the work I need to do for the unpaid people who may or may not ever pay me a penny worth it to get a few more users?
if the "work" is just spinning up some new AWS nodes, the math is easy. If lifetime value of a free guy > cost of AWS node, do it. If < cost of AWS node, don't do it.
If the work is lots of staff related hand-holding - then it depends. If your staff is at 100% capacity and you need to hire more staff, it is closer to the AWS example above. If you have staff sitting around doing nothing anyway, then maybe it is "free" as in an already sunk cost.
In their case it seems like they had some engineering flaws in their system (who doesn't), that made the scaling up part harder. Good to think about how to scale up early so you don't hit a wall.
- jacquesm 11y agoIt's actually a bit more complex than that. If the only way you measure the lifetime value of a free guy in dollars and cents than that value will always be pegged at '0' so applying your formula literally would lead to 0 times the freemium model would be given a chance. But free users can be put to work in other ways, and that value may be very hard to peg down accurately. A good 'free' user that promotes your service to paying users, for instance, an employee that uses the product at home that advocates its use in the business where he/she works. Or maybe free users give you content that you can monetize in some other way. And that's the hard part, assigning a value to the contribution. The cost part is the easy bit, servers are cheap. But support is costly and even then it may still make sense to have a free tier, it's never going to be an easy decision.
- mcherm 11y agoAlthough the conversion rate to paying customers provides one simple-to-estimate portion of the value and at an astounding 11% conversion rate, that alone might pay for it if the support costs weren't so high.
- jacquesm 11y agoSupport is super hard to scale. The best way is to design your product so well that you rarely need to answer calls/emails.
- kolinko 11y agoIf you think about scaling too early, you'll have a plethora of other problems to deal with.
- Shpigford 11y agoThis. We could have spent an infinite amount of time making the system as robust as possible...and then burned to the ground b/c we ran out of money before we had customers. Or we could just ship something and adjust as quickly as possible. :)