5 ms·
Heroku runs on top of EC2, and they get charged the same amount of money by Amazon whether your instances are idle or on fire. That doesn't matter, though, bec
by patio11 16y ago
Heroku runs on top of EC2, and they get charged the same amount of money by Amazon whether your instances are idle or on fire. That doesn't matter, though, because businesses do not do cost-based pricing.
There comes a time in a young man's life when "haha, whoopsie, I'm a kid who is not responsible for his own decisions" is no longer sufficient for a do-over. I am not sure when that is, but if you're running a business, well, welcome to being an adult.
- jacquesm 16y agoThere comes a time in a business owners life when he realizes that he may be able to take the money from this particular customer but that the PR damage done by that customer may be larger than being reasonable and understanding that mistakes happen. And if there is some egg on the face of the business owner for not alerting the user to their sudden suspicious consumption pattern then there are valuable lessons to be learned for all parties. So, the adult business owner would likely split the bill with the customer to cover his costs, fore go his profits on this particular occasion, have a very happy customer (who might even write about that!) and would apply the lessons learned to their business.
- ErrantX 16y agoHow do you judge the PR damage of a customer? Unless they bring up who they are elsewhere on the net (assuming it is not obvious) you simply can't judge such things. So what do you do; lose money each time this happens? Or take a hard line "we're nice guys and all but, sorry, it's costing us too". And the happy customer might write about you; but the risk is it sets a precedent. So the next month when another customer screws up they think to try the same tactic - and if you refuse them it's even worse press ("oh, apparently I'm not good enough to be treated that way", "2 tier customer service" etc.). It's a minefield all round.
- patio11 16y agoAs an empirical question, I think you are likely right that charging off some money owed might buy Heroku disproportionate amounts of goodwill. (I do it all the time.) That is, properly, their call. As a normative question, though, for-profit businesses do not have a generalized right to make their mistakes into others' obligations. More broadly, one of my periodic crusades is trying to get HN people to understand that norms in the business world are very unlike the norms of cash-strapped twenty-somethings regarding things like a) the appropriateness of charging money (charge more) b) how much money $1,000 really is (a lot to you, a lot to me, rat spit to businesses with an HR department) and c) expectations for professional behavior (you're doing taxes like a boss, reading contracts like a boss, capacity planning like a boss, paying your invoices like a boss, etc).
- jacquesm 16y agoBusinesses that work on 'metered' entities (phone companies, banks and so on) as a rule have velocity checks in place. This limits the amount of damage a customer can do to himself and to the company between billing periods. I think Heroku is the party here that stands to benefit the most from the encounter, and by simply charging the customer they've lost an opportunity for good PR and have made half of HN more wary of dealing with them. I understand what you're getting at, but just like there is a maturity to being 'in business' there is a maturity in dealing with your customers, and in this case both parties carry part of the blame, so the reasonable thing to do is to find a solution that lies in the middle. Even the pros mess up occasionally, and in this case it was pretty clear that it was a mistake. The real lesson here is that Heroku should implement a notification system when a customer has excess unused capacity or a min/max setting for their dynos with automatic increase and decrease depending on the amount of traffic a customer is currently receiving. As you say, you 'do this all the time', so that means that you know exactly what is in your interest as a business person, and if that means that you occasionally eat a charge that must mean that you know exactly what the value of goodwill is. Heroku, apparently has not yet learned that lesson, and 'heroku' and 'unexpected large bill due to mistake' are now two concepts that have become strongly linked. It did not need to be that way.
- pts101 16y agofor-profit businesses do not have a generalized right to make their mistakes into others' obligations. The OP never argued that he has the right to force the cost of his mistake onto Heroku. He's polling a community of business owners to see how they feel it should've been handled. If I were Heroku management, I would've written the OP something like this: (Valued Customer)- I'm so sorry your accident created a nasty end of the month surprise. We understand, but we cannot forgive the whole amount because while they were not servicing requests, we incurred real costs keeping the dynos ready, willing, and able for you. Since it's your first mistake of this sort, and you've been such a great customer, we're willing to reduce your total amount owed to $x. We hope this helps, Heroku ---- so yes, I think it's his own damned fault. But I also think it's a missed opportunity to create a happier customer.
- nwmcsween 16y agoHow is heroku any different from your or my business? Because they are mildly successful suddenly they are the bad guys and everyone is is good until proven on hn? Double standards really piss me off. The OP needs to take responsibility.
- davidedicillo 16y agoI understand Heroku's decision, but I must say, when the opposite happened to me with SendGrid a couple of days ago (I didn't even asked for the refund, they did it on their own initiative), I was extremely positively surprised.
- carbocation 16y agoRight... But I've heard nothing about your experience. Likewise, there is a nonzero likelihood that Heroku could give this HNer a $1000 break and get no publicity...
- jacquesm 16y agoFor $1,000 and no publicity that would still be a valuable lesson learned. What's more interesting is if this happened before and how they dealt with that. What's the cut-off point at which you want to stop your customers from doing serious monetary damage? $1000? Apparently not. $10,000 ? $100,000? There comes a point where the continued existence of Heroku would be at stake, so it is in their own interest to guard against this, especially when you take in to account the number of users they've got. They need some guardrails for this, and sooner probably better than later. Terms of service will not protect you if your customer can't pay your insanely large bill. In that case you'll end up eating the charges anyway, so guardrails are to mutual benefit.
- carbocation 16y agoIn my opinion, your point is totally orthogonal to the point I was responding to. I agree with your reasoning about Heroku's self-preservation completely.
- jacquesm 16y agoHe already wrote about his positive experience, right here in this thread.
- davidedicillo 16y ago
- staunch 16y agoHow horribly condescending and wrong. Any company that lets their customers go from huge fan to hater in a week has a major bug. The important question is why did their product turn a fan into a hater, and how can they prevent it? Heroku should almost certainly have user defined cut off points. They should require every new user to set a maximum monthly bill to something they can afford (or "unlimited"). I did exactly that for a similar type of service I worked on. One of the biggest anxieties customers had was that they'd get a massive unexpected bill, just like this guy did. Heroku's best move would be to cut his bill in half and institute a cut-off feature. Every service like it should follow suit.
- timinman 16y agoThey may have every right to hold the hard line, but a little compassion would probably pay off better in the long run. Some business' bottom line is profit alone, other's are in it to solve problems, and, keeping an eye on money, and can make enough profit to keep living the dream.
- patio11 16y agoThis is the Ruby versus Java debate: should we treat professional programmers like they know what they're doing, or should we straightjacket them? To which I answer: Yes. It is reasonable to run a Enterprise-oriented cloud scaling company which second-guesses your customers' decisions at every point. It is also reasonable to run an Enterprise-oriented cloud scaling company where a professional engineer engaged in capacity planning clicking OK to an estimate presented in 60 pt Arial is assumed to know what they're doing.
- staunch 16y agoI hardly think a single global setting (set one time) counts as something that "second-guesses your customers' decisions at every point". Less like a straightjacket and more like an (optional) seatbelt.
- docgnome 16y agoI don't agree. It's not an issue of straight jacketing programmers. It's an issue of reminding a user they are incurring an enormous bill for no reason. A simple "Hi, we see you're using X widgets but your traffic would allow you to reduce this to Y widgets. If you'd like to do that, here's a link. If not just ignore this email." That would solve the problem with very little effort. It would keep people forgetting and having a heart attack, getting pissed and leaving. It really doesn't matter if it is the customer's fault if it causes them to leave with a bad taste in their mouth.
- petercooper 16y agoHeroku runs on top of EC2, and they get charged the same amount of money by Amazon whether your instances are idle or on fire. Is the latter part of that true? (I'm not playing Devil's Advocate, honest!) I'd assumed the lion share of Heroku's profits were coming from clever arbitrage of EC2 instances rather than markup alone. For example, if they have 1000 users paying $108 per month for 4 dynos, they don't keep 4000 "dynos worth" of EC2 instances running constantly. Instead they can see the overall load and maintain that lower level of EC2 instances plus some "slack." When traffic increases among apps, the slack can be rapidly configured to pick it up. Heroku would then make not only a markup on EC2 but also profit from the difference between the maximum load and actual load. (Isn't this how cloud scaling systems work anyway, right? Heroku could/might be doing that over thousands of apps for collective benefit.) Perhaps I'm over-thinking how I'd be trying to squeeze profits out of a Heroku-type system though ;-)
- jacquesm 16y agoIf they're not doing it that way already then they should definitely hire you at 10% of what you would save them every year ;)
- petercooper 16y agoI know a few of the guys at Heroku and I'd be gobsmacked if they weren't doing stuff 100x smarter than I mentioned. With that said.. I hope I'm not wrong and making them feel bad in the process ;-)
- tlrobinson 16y agoI was under the same impression. If your app has been idle for a long time it takes a few seconds for the first request to complete, which leads me to believe they shut down dynos for idle apps. But it's possible that's only for the free apps.
- tlrobinson 16y agoI'm pretty sure that's not true, but I don't know exactly how Heroku works. The way I understand it is if no one is making requests to your app they will shut down the dynos, and when you start getting requests they'll spin them back up, up to the number of dynos you're paying for. That's why if your app has been idle for a long time it takes a few seconds for the first request to complete. This lowers their costs, and presumably the prices for their customers. I could be wrong though, and perhaps they only turn off dynos for non-paying customers.
- davidw 16y agoRefunding a portion of their profits on the 1K could be seen as money spent on advertising. It sounds like the guy realizes he made a mistake, so he'd probably be happy if he got something back, and think it perfectly fair not to seek to get everything back, so in the end it wouldn't be a great deal of cash, that, long term, they'll probably recoup in the course of a year anyway. Since he's a good customer, they could even give it to him in the form of credit for their service, which gives him an incentive not to leave.