5 ms·
I don't think that's true. They had a lot of people using their messenger client. More to do with mistakes and execution. Why did they take $70m in funding? Th
by mibbitier 14y ago
I don't think that's true. They had a lot of people using their messenger client.
More to do with mistakes and execution. Why did they take $70m in funding? That's a ridiculous amount of investment to take.
Why couldn't they monetize that amount of eyeballs?
- 1123581321 14y agoI know they had a lot of users, but I don't see how they were making money off the client and they had a lot of employees. Maybe the spam thing was working for them but I don't think they would have folded if so.
- mibbitier 14y agoSure. They had way too much investment, way too many employees, and didn't seem to have much of a handle on making money by the looks of things. It'll be spun as a success "Acquired by Google yay!", but seems a pretty resounding failure to me.
- danudey 14y agoOr go beyond monetizing eyeballs. Turn it into a live chat service, so visitors to your website can instantly communicate with you. Or do what Chatterous did and let people create custom IM group chats. Maybe they did these things and I didn't notice, but anything seems better than 'Let's put a toolbar at the bottom of other peoples' sites!'
- earl 14y agoit's very difficult to monetize eyeballs without intent. If you're going to do that, you'd better do what fb did, and generate a fuckton [1] of pageviews. [1] Definition: lots and lots -- 1T / month in summer 2011 [2] [2] http://mashable.com/2011/08/24/facebook-1-trillion-pageviews/ http://mashable.com/2011/08/24/facebook-1-trillion-pageviews...
- mibbitier 14y agoDepends. It's easy to make a comfortable amount of money even without intent, but the problem comes when you have massive outgoings (office, staff, etc), and tons of investment, where making a good amount of revenue isn't good enough.
- 1123581321 14y agoThey have now announced shutdown of the messenger. http://www.meebo.com/support/article/175/ http://www.meebo.com/support/article/175/