Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The problem is that you wouldn't need a dozen but rather 100+. Support doesn't scale well.


As many as it takes or is permissible, then.

The notion that customer support, just like security, is just a sunken cost needs to stop.


Why would hiring 100+ customer support reps be a problem for Microsoft?


1. They would need to be somewhat technical, so they would not be cheap. Let's say $70,000 a piece.

2. It is a free product. Would you spend 7 million a year supporting a free product?

3. 99% of complaints would be of the nature "GitHub is broken. HELP!" and really be some person who did not set the origin before pushing.


1. They would need to be somewhat technical, so they would not be cheap. Let's say $70,000 a piece.

That is roughly the fully-loaded cost to employ a senior software developer in much of the world. A decent but first-line tech support agent would cost a fraction of that amount almost anywhere outside the US.

2. It is a free product. Would you spend 7 million a year supporting a free product?

Presumably for the same reasons you spent far more than that to buy and continue to operate the service at all.

3. 99% of complaints would be of the nature "GitHub is broken. HELP!" and really be some person who did not set the origin before pushing.

Then 99% of the complaints will be dealt with quickly using standard replies and references to FAQs. These aren't going to be the ones attracting hundreds of comments and presumably thousands more readers on prominent online forums for software developers.


They paid $7.5 billion for it so they're already spending much more than that if they keep it running for any less than the next thousand years.


It isn't a free product. It's a paid product with a free "introduction tier" that helps them capture the open-source ecosystem, so that when your company needs paid services, they are the obvious choice because everyone is using it already.

Basically the same deal as "educational licenses" for expensive software suites. It isn't a freebie at all; it's an investment into future customer acquisition through lock-in. That's how you're paying for it.


> It is a free product.

I for one pay for GitHub. I've never had a ticket that wasn't answered in under a day, but I'd be almightily annoyed with them if I submitted a ticked like this and didn't have a response within hours.


Mostly support is a person getting a hold of someone that can escalate. No technical requirements needed.


No. Support is a pyramid where each node should try to solve the problems they can before an escalation.


It should at worst scale linearly with user-count and hence, at least in the asymptotic limit, revenue.


> It should at worst scale linearly with user-count

No, front-line support staff might scale that way, but organizational costs scale superlinearly with the size of the bottom of the pyramid, so even if it did, total cost would be super linear with userbase.


Users can be free or paid. When I open up support tickets backed by a paid account they're always very quickly resolved. I'm not sure how much GitHub needs to support people who won't even pay for the product...


I'm not convinced revenue on services with free plans scales linearly with users.

It's unclear if the poster had a paid for account.


Regardless, a dozen is a good starting point.


I am not sure that would be better simply because they would either need to throw away a lot of tickets randomly or the wait times would be horrendous.


They already have more than a dozen




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: