Hacker News new | ask | show | jobs
by OzzyB 5027 days ago
Yes, but the problem with Twitter is they took too much money.

You don't need to have $1Billion dollars in financing to offer a service like this -- this is what the likes of app.net are teaching us.

A $50million Twitter could have "easily" sustained it's vision/objective without having to cannibalise it's entire ecosystem.

However someone promised the moon to a bunch of financiers and now they have to deliver above and beyond of what Twitter could have been, or should have just been.

As far I'm concerned that is the story of Twitter, a company that took the money and ran.

3 comments

> "You don't need to have $1Billion dollars in financing to offer a service like this"

Sometimes you do. We've seen a dramatic amount of "overfunding" of social media startups, and I have a theory why.

When your business model doesn't involve well, actually making money at its core, you end up in a position where you have to staff up massively so you can pursue an enormously vast range of monetization strategies in the hopes of finding something that sticks.

How many people on Facebook do you think are working on the core product - as in the Facebook that end users interact with on a daily basis? How many instead are working on a enormously numerous systems that Facebook hopes would make them monetizable? Ad platforms, billing systems, support systems, analytics systems, etc etc.

So yeah, Twitter as defined as "that thing where you submit strings of 140 chars or less and follow others doing the same" probably didn't need $1bn to get off the ground. Twitter in the "this might actually make money" sense though, probably isn't THAT overfunded.

So in other words, they needed $1 Billion dollars in order to have enough money to make money from the $1 Billion dollars?
It's like a rocket. Most of the fuel in a rocket goes towards lifting the rest of the fuel. Likewise, Twitter needs that level of investment to scale to the point where it can make a return on that level of investment.
This is a good analogy. But with 800m raised in 2011, arguably when they were close "escape velocity" already, its also a fair point to wonder if destiny could have been any different with less $$$ weighing them down.
Yeah, it's pretty perverse. I sometimes wonder how many AirBnb's and Squares we could've gotten for the price of Twitter.
Sounds to me like the ultimate a posteriori argument.
What I always found curious about Twitter, despite its massive concurrency requirements, is how low quality and short-lived the content is. Outside of charting historical trends, there's very little value in mining historical Twitter data - it's only the real-time part that matters. Theoretically, they coould just delete all content older than x days - and I doubt that many would notice.

1bln is funding is unreasonable, both from a technology standpoint (Twitter does go down, btw) and from a "let's figure out a way to monetize this" standpoint.

1) How do you know how much money it takes or does not take for Twitter to offer it's service?

2) Don't you think it's a little early to compare app.net and twitter? App.net is in it's infancy and is nowhere near the product twitter is

3) What could Twitter have been exactly? How did closing a few API's off prevent it from getting there?

4) Have you ever imagined that perhaps your vision for Twitter and Twitter's vision for Twitter just do not mesh?

1) No, but I know that the difference between $50M and $500M+ would change my outlook in terms of who I need to satisfy dramatically.

2) Don't like App.net? Pick Reddit vs Digg, same case. One managed to "get by" with a core team, the other took a ton of money, hired a bunch of folks, made a bunch of promises, and tried to shoehorn their original vision, the one that got them established in the first place, into something completely different. Reddit, makes money and is sustainable -- it just didn't need to make that much money -- as a user that's fine by me, and the reason why Reddit "won". If only Digg was happy to "just" be a $50mill website...

3) Twitter is what it's users/supporters made it to be. Its service/value was understood from the get-go, and in turn, it's popularity grew for that same reason -- ppl understood it's vision and supported by building upon it -- hence cannibalizing your core base by knee-capping your API, probably isn't the best way to go.

4) My vision of Twitter is fine, like many others, I think it's got something to do with SMS-web-mobile-140-characters-distributed-micro-messaging-or-summin? Does it need to be more than that?

The wrinkle in #2 is that once you decide to take conventional venture funding (as opposed to bootstrapping, or fundraising through angels, incubators, etc.), you really don't have the option to just be a small, sustainable business anymore. VCs don't want to invest in small, sustainable businesses, they want to invest in aggressive plays that have the potential to blow up into something huge.

According to TechCrunch the only money Reddit ever raised was $100k of seed funding (http://www.crunchbase.com/company/reddit). That's a very different trajectory than Twitter, who (again according to TC: http://www.crunchbase.com/company/twitter) have raised $1.16 billion (with a B) in funding.

Taking in that sort of money raises the stakes dramatically. Nobody loans you a billion dollars to build a $50 million/year business.

> Taking in that sort of money raises the stakes dramatically. Nobody loans you a billion dollars to build a $50 million/year business.

That was OzzyB's original point: Twitter should not have taken big VC money. They took too much money. From his first post:

> someone promised the moon to a bunch of financiers and now they have to deliver above and beyond of what Twitter could have been, or should have just been.

Certainly fair questions. Here are some of the data:

1.16 billion of capital and 140 employees

6.0-7.0 billion valuation, estimated

In terms of profit per employee, you're looking at 50 to 100 million to 'break even' at that vauation

So, part of it is the $$ raised and part is the $$ valuation

Is it possible paint yourself into a box, strategically, if you take money at aggressive valuation?

Source: http://www.crunchbase.com/company/twitter

Edit: Headcount data look out of date at TechCrunch. See comment below, this now ~1,000 not 140.

Woa woa, 140 employees? You mean over 1000 now. Source: http://www.mediabistro.com/alltwitter/twitter-1000-employees...
Thanks, this is a good catch. I pulled the data from techcrunch (they were out of date, added reference above).

General direction of the comment is distilled, still as follows:

1) valuation is 7x invested capital

2) The invested capital is large, requires large exit

3) This is going to put pressure on the team ($10-15B exit?)

4) Thats a requires lot of $$/head for the team to bring in

Not to mention well over 100mil/yr in salaries alone (prob more like 150-170mil with benefits, taxes, and generally high salaries in SF, glassdoor shows avg salary 120-130k)
Re: "how do you know how much money it takes ..."

I don't know how much it takes Twitter (even though it should be relatively easy to find out), but I do have an idea how much it should take.

Twitter presentations suggest 70 million messages per day. 800 tweets per second:

http://www.slideshare.net/raffikrikorian/twitter-by-the-numb...

It's not that much, actually. Some of us have processed 50-70 million transactions per day on a much smaller infrastructure (25..40 AWS boxes) - quite often designed and deployed just days prior to the massive traffic spike, with fancy features like real-time fraud checking etc.

It's not that hard to do what Twitter does. At least, with the amount of financial backing that they have, I don't expect them to be failing in a spactacular fashion periodically.

The reason for the mismatch is that it's not 70 million transactions a day. It's potentially 70 million times the average number of people that access each tweet, which is probably more like 100+, plus all the polling that twitter applications do even when there are no new tweets, as well as all the ancillary stuff that's required to run something like this (spam filtering, API servers, etc).
> the average number of people that access each tweet, which is probably more like 100+

I'm sorry. I really am. I know this isn't Reddit. But...

HAHAHAHAHAHHAHAHAHAHAHAHAHAHAHAHHAHAHAHAHAHAHAHHAHAHA

Yes. Yes, on average, a given tweet reaches ONE HUNDRED PEOPLE. Do any of you folks even listen to yourself? Even if you change that to "users" instead of "people," since so many twitter accounts are robots - even then, 100 users on average for every tweet is ABSURD.

> the polling that twitter applications do even when there are no new tweets

Polling with no new tweets is far easier to optimize than polling when there are tweets. So just discount this almost entirely in your roughshod analysis.

> spam filtering

Have you been on twitter? We all get spam and see fake accounts trying to get at us regularly. Try mentioning you're on a diet on twitter and see how many followers you rack up. If they're filtering spam, they're not filtering it well, so I hope they aren't burning too much cash on it.

> API servers

API servers are frontends that use dramatically fewer resources than the work the backends have to do. If Twitter's frontends are costing them much money, again, they're wasting money.

I don't see what's hilariously off about that? If you look at the average number of people that a given real person follows, 100 probably isn't that far off. I'm not saying those are actually read by a human, but associated with that many, sure.

My point was that the grandparent was probably an order of magnitude or more off counting 70 million new messages per day as 70 million transactions per day.

I'm not saying they're doing things well, but it's pretty naive to think that you could build Twitter's infrastructure with <50 AWS instances.

You think the API is a trivial matter of spinning up some front end machines? From that presentation linked to above, they were getting 6 Billion API calls per day, or 70k/sec.

Besides that, all of these numbers are 2 years old, and according to those slides, they were growing at about 10x per year. It has probably slowed, but those numbers may all be much bigger now.

I have no idea if Twitter is over-funded or not, but App.net has yet to have to service anywhere near the level of simultaneous traffic that Twitter deals with daily. App.net services 20,000 users (http://thenextweb.com/socialmedia/2012/09/07/off-slow-start-...); Twitter services 140 million (https://business.twitter.com/en/basics/what-is-twitter/). Twitter went through severe growing pains to reach the point where it could handle that much traffic; there's no reason to believe App.net won't have to go through similar issues if/as it grows.

Any centralized system that has to support tens or hundreds of millions of users in real time is going to be seriously expensive to operate. There may well be a point at which it's simply economically infeasible to do it without splitting the expense into tiny slices borne by lots of different parties, the way we do for email.

> Twitter went through severe growing pains to reach the point where it could handle that much traffic; there's no reason to believe App.net won't have to go through similar issues if/as it grows.

Actually, there is: app.net could just observe what twitter did.

And twitter didn't have to go through it either; There's discussions going on about that since 2008 when their uptime suffered outage after outage; here's something I wrote 2 years ago, for example: http://www.reddit.com/r/programming/comments/b2u6t/twitter_o... and I had given that same answer before several time in other forums.

> Any centralized system that has to support tens or hundreds of millions of users in real time is going to be seriously expensive to operate.

And yet, reddit which is much more complex, and of comparable reach (I don't have time to google the numbers right now, let's say it has 1/10 of the audience), costs much less than 1/10 of twitter's operational costs. And is profitable.

> There may well be a point at which it's simply economically infeasible to do it without splitting the expense into tiny slices borne by lots of different parties, the way we do for email.

Actually ... I suspect gmail can easily handle the entire world email infrastructure, cheaply and reliably. They already handle a two-digit percentage of the world email accounts.

For sure, facebook can do that - they already do it (although it is simplified email).

The reason email is sliced is not a problem of scale - it is a problem of control.

edit: removed half a sentence that was there, and which was written earlier.

If you think you could have replicated Twitter with 300K of hardware and software 2 years ago, surely it would be even cheaper now. Why wouldn't you go to Twitter and offer to do it for them? Even if they paid you three million dollars it would give them massive savings in headcount and operational costs.
I'm sure there's at least one technical person high enough there who is aware of how inefficient their implementation is, and how much better it can be. And I suspect that person is unable to do anything about it, despite being in a way better position than anyone on the outside.

But ... the real question, is even if I brought it in a turn-key and backward compatible setup for them (that is, they pay $3M, I install stuff, we flick a switch, and everything just works) - would it be worth $3M to them?

I suspect the answer is: Not worth any kind of risk or hassle to save $10M/year (or however much it would save them; if it is more than $10M/year, I'd be surprised).

I don't know how they spend their money, but I'm willing to bet that running the service is less than 10% of their expenses. (Of the money spent to get e.g. win95, or a new drug, to market, r&d costs are usually no more than 5-10%)

I think Twitter hasn't been a lean organization in years, and they took too much money to "reboot" themselves as a lean.

I think Twitter is already dead, it just won't acknowledge.