Re:The Google black hole: What happens to startups when they...
by fleaflicker on Thursday August 14, 2008 @01:08PM
(#276274)
That's somewhat true--I've noticed that AOL is very aware of their uncool image and they don't overtly brand their properties with the AOL name (e.g., TMZ, MapQuest, Moviefone, ...).
Re:The Google black hole: What happens to startups when they...
by kajecounterhack on Saturday August 16, 2008 @06:35PM
(#278020)
Wow I had no idea Mapquest was owned by AOL. I'm sure there are alternatives but usually thats the service I use...I don't think I'm so shallow as to switch services just because its AOL though. A good service is a good service.
Re:The Google black hole: What happens to startups when they...
by josefresco on Thursday August 14, 2008 @04:15PM
(#276443)
Hearing your story brings back painful memories of when AOL bought Winamp and drove that wonderful software into obscurity (and forced guy like Justin Franke to skedaddle)
Re:The Google black hole: What happens to startups when they...
by micah63 on Thursday August 14, 2008 @09:48AM
(#276062)
I think the google + youtube worked out because they let the community continue unhampered. Even today you can get a youtube account without a google account. That is smart.... We can't pretend to know google's intentions with some aquisitions though, ie measure map getting blended into google analytics.
Re:The Google black hole: What happens to startups when they...
by goodkarma on Thursday August 14, 2008 @11:30AM
(#276184)
When Google hands over six or seven or eight figures for something, they obviously have a plan for how the technology and team fits into their "master plan".
Why is it surprising that, at least some of the time, they aren't actually interested in the original web site?
Re:The Google black hole: What happens to startups when they...
by neilk on Thursday August 14, 2008 @04:09PM
(#276435)
they obviously have a plan
That's not actually true. The thing about giants that acquire startups, is that a) they had the resources to build this thing themselves; b) they didn't.
So ask yourself why didn't they build this thing. It wasn't lack of resources. It wasn't lack of intelligence; they keep tabs on everyone and they go to SXSW too. There were forces that stopped the giant from innovating in this direction. Some of them are technological, but the real issues are usually cultural and political.
Once acquired, the startup is now exposed to all these forces -- with double intensity, since it is an outsider and has few friends in the organization. Unless it's already profitable, has a large userbase, or has big fans among the top execs, it has very little power.
I think these recent articles about how giants "ruin" acquisitions do not take culture and politics into account. The technical issues are not the problem.
Re:The Google black hole: What happens to startups when they...
by goodkarma on Saturday August 16, 2008 @12:39AM
(#277583)
The depth/extent of the plan is surely debatable, but folks like Larry and Sergey and Eric Schmidt would not make the decision to pull the trigger for an acquisition unless they knew what they wanted out of it. They are smarter than that .
In the case of MeasureMap, for instance, they knew they wanted that technology integrated into Google Analytics. They may not have been able to answer the "how" part of "who, what, when, where, why, and how", but surely they knew the "who", "what", and "why".
I understand that the startup built the technology and the acquirer didn't. That's the beauty of how this system is set up - a company like Google with piles of cash and stock can has so much money it can buy anything it wants.
Well then how do they decide which startups to buy (MeasureMap, Feedburner, etc.) and which startups to pass on (Digg)? That's the "master plan"..
Re:The Google black hole: What happens to startups when they...
by ojbyrne on Saturday August 16, 2008 @12:19AM
(#277580)
And the thing about startups is that there's no reason to think that they would continue running the way they were indefinitely without charging membership fees, or plastering ads all over them, or somehow ruining the experience that their supporters value so much.
They sell for a reason, usually that their funding is running out, founders facing a down round, increasing pressure to become profitable. The fallacy is that the sweetness and light will continue indefinitely.
Re:The Google black hole: What happens to startups when they...
by webwright on Thursday August 14, 2008 @04:02PM
(#276431)
"When Google hands over six or seven or eight figures for something, they obviously have a plan for how the technology and team fits into their "master plan"."
I have heard that Google will pay $1m+ per engineer if they like the team and what they've pulled off, even if they are going to dump the technology (or want it rebuilt from the ground up).
I think once you get into eight figures, though-- you're probably right.
I don't see the problem, if you start a startup to make a shitload of money and you do make a shitload of money, then, mission accomplished right? (or, as DHH would say: Profit!)
There will always be companies that get screwed up in the acquisition process, just like there will always be companies that don't. But, let's fuel the rumor that Google kills all that it consumes, why not?
Re:The Google black hole: What happens to startups when they...
by josefresco on Thursday August 14, 2008 @04:10PM
(#276438)
I think the article states that it isn't always a shitload of money. Sure it beats your part-time gig at Starbucks but why sell your app for 5-6 figures when it could be worth 7-8?
If Google is interested in your application now, why wouldn't someone else snatch it up 6 months later when you have more users for a higher price?
Sometimes winning the buyout lottery is selling yourself short.
Re:The Google black hole: What happens to startups when they...
by mickt on Friday August 15, 2008 @11:44AM
(#277060)
> if you start a startup to make a shitload of money and you do make a shitload of money, then, mission accomplished right
What about the user-base? Don't we have a responsibility to them also? Without them we can't be successful, and we should own them some responsibility to ensure that the tools/product/web-site they've been using remains useful for them.
Re:The Google black hole: What happens to startups when they...
by rams on Friday August 15, 2008 @12:34AM
(#276762)
Actually Blogger met with pretty much the same fate as other companies. Check out Evan's blog post about freeing blogger from Google at evhead.com - it must be in the archives.
Re:The Google black hole: What happens to startups when they...
by ashleyw on Thursday August 14, 2008 @06:09PM
(#276523)
The problem with Google is it has very, very little focus as a whole. This is a good thing internally, they seem to develop and release so much stuff without much bother, but in my opinion, joining Google would FEEL like a black hole. Your working on your own project but also have to concern Google about everything, as well as moving your app to Google technologies (in most cases). How can you continue to innovate in that situation?
The same goes for Delicious too I think, they were doing fine, brought by Yahoo, and then went back to being a stealth app while they rewrote everything in C++/PHP. Would they have done that without Yahoo input? Nope, I dont think so...
Re:The Google black hole: What happens to startups when they...
by ajross on Thursday August 14, 2008 @10:31AM
(#276117)
Indeed. From the perspective of a developer, I can see not wanting your baby to be ignored in a corporate bureaucracy. But investors don't normally think that way. I don't know what founders are "supposed" to think here, but if it were me I'd take the money and find a new baby if I had to.
Re:The Google black hole: What happens to startups when they...
by jlogic77 on Thursday August 14, 2008 @11:25AM
(#276182)
I wonder what types of questions the founders are asking of Google pre-aquisition? As a founder, I would think you are concerned with what is Google's "vision" for your product/company. I could also see just the shiny things being enough to make me not worry about the vision.
Also, there are successes. Writely - > Google Docs seemed to be a pretty big success. I'm sure there are others.
Re:The Google black hole: What happens to startups when they...
by Timothee on Thursday August 14, 2008 @01:31PM
(#276292)
Keyhole -> Google Earth was a big success too.
The thing is that we tend to forget the successes a little bit because they got to merge so well with Google.
Looking at the list of acquisitions on Wikipedia (http://en.wikipedia.org/wiki/List_of_Google_acquisitions), I can only think about Blogger but I have no experience on if it changed for the best. As far as I can tell, it looks like it's still working fine.
Re:The Google black hole: What happens to startups when they...
by neilk on Thursday August 14, 2008 @07:45PM
(#276591)
Yeah, Writely is a great counterexample. Their vision and Google's vision were really close, so they integrated well into Docs.
And just to show you that technical issues are not the primary problem, they were using Windows/C# but managed to port to Google's Linux/Java-based infrastructure and login system very quickly. (Granted, C# is way closer to Java than PHP).
Re:The Google black hole: What happens to startups when they...
by andreyf on Thursday August 14, 2008 @10:41AM
(#276135)
to rot away under mountains of management and infrastructure/policy hell.
I missed where exactly the article said this. I imagine if you're looking at a Google acquisition and you care about your service, nobody is stopping you from asking "how will this integrate into Google's MapReduce/BigTable? Where will I be in the Google corp. structure? Will I get engineers working with me on my product, or will I be farmed off to other products?" Weigh the answers to this as part of yoru consideration about whether this acquisition is good or not.
I think the founders are more to blame for not understanding what an acquisition by Google involved, not whoever@Google they were dealing with for not spoon-feeding them.
Re:The Google black hole: What happens to startups when they...
by josefresco on Thursday August 14, 2008 @04:07PM
(#276434)
I'm sure Google promised these founders all sorts of things once their application was assimilated into the borg that is Google. And with lots of money on the table I'm sure the founders grinned and asked where to sign.
Closing your doors to new signups is practically like suicide. As a founder I would never agree to that if I was taking a smaller buyout in exchange for continuing to work on my application as an employee of Goog.
Now if they backed up the money dump truck and sent me on my way I wouldn't care so much (although I'd probably have thousands of users who'd hate me but probably also wouldn't blame me)
Speaking of cool places to work, there is of course Google. But I notice something slightly frightening about Google: zero startups come out of there. In that respect it's a black hole. People seem to like working at Google too much to leave. So if you hope to start a startup one day, the evidence so far suggests you shouldn't work there.
Re:The Google black hole: What happens to startups when they...
by neilk on Thursday August 14, 2008 @07:52PM
(#276595)
No, what you are seeing is that individually creditable work occurs in the pre- and post-corporate employment stage. Which is practically a tautology.
There are plenty of epic technical achievements within Google. In fact, it's practically expected. The rest of the world just hears about these innovations, on average, three years after they happen. If they ever hear about them.
Re:The Google black hole: What happens to startups when they...
by snprbob86 on Thursday August 14, 2008 @09:06PM
(#276640)
"shut down to new users" just means "taking their sweet time porting to a google backend"
When things are Google products, there is a certain level of reliability, security, and performance that is expect. Google tries harder than anyone to avoid the Fail Whale.
It takes a long time for large software systems to be ported, security reviewed, integrated, and tested with Google's custom stuff.
From what I have seen, being acquired by Google means that you go dark for 18 months and then emerge as a Google product.
Re:The Google black hole: What happens to startups when they...
by vaksel on Thursday August 14, 2008 @01:27PM
(#276289)
not really, its just another case of Google getting into an industry because they see someone else have success in it. If it works? Good. If it doesn't? No biggie, they only lost 2 days of revenue in the investment.
Re:The Google black hole: What happens to startups when they...
by prospero on Thursday August 14, 2008 @02:13PM
(#276322)
But if someone is wildly successful with an AppEngine site, it's a much simpler acquisition because it already sits on top of the Google infrastructure. Conversely, it's much less appealing to any competitors for the same reason.
Re:The Google black hole: What happens to startups when they...
by cstejerean on Thursday August 14, 2008 @02:13PM
(#276323)
I hope it's not "getting into an industry because they see someone else have success in it" because that reminds me of Microsoft and I don't think it's worked out well for them.
Re:The Google black hole: What happens to startups when they...
by jm4 on Thursday August 14, 2008 @05:49PM
(#276514)
Are you crazy? How has it not worked out for Microsoft? As of 2000 it was estimated that Microsoft had produced 10,000 millionaires. Sure, they've produced tons of crappy software too, but as long as we're measuring success in terms of money then I'd say the strategy has worked perfectly. They've been by far the most successful software company to date. They could care less about the quality of software as long as it's the best selling software. Google is no different. They see a revenue opportunity and they grab it.
Re:The Google black hole: What happens to startups when they...
by ewanmcteagle on Friday August 15, 2008 @03:43PM
(#277266)
Visual Studio is not profitable for Microsoft (from what I've heard from MS employees) but that is also not its purpose. It's there to guarantee the success of the Windows desktop and server platforms. Microsoft knows development and ease of development has been a large contributor to the success of Windows.
Re:The Google black hole: What happens to startups when they...
by cstejerean on Friday August 15, 2008 @11:50AM
(#277068)
I don't think the revenue from Visual Studio and SQL Server come anywhere close to Office and Windows. Keep in mind that pretty much every computer sold for the past decade has had Windows pre-installed and that everyone in a business or university environment is forced to have a copy of Office.
Re:The Google black hole: What happens to startups when they...
by andreyf on Thursday August 14, 2008 @10:45AM
(#276139)
I'm not sure if it's fair to pick out specific cases with the number of acquisitions Google does ... sure, some aren't going to be perfect - some founders won't understand Google infrastructure, others will lose interest in their products, etc.
Re:The Google black hole: What happens to startups when they...
by trickjarrett on Thursday August 14, 2008 @10:18AM
(#276105)
I remember reading about the infrastructure hell with both Google and Yahoo. I think I've read stories from founders of companies acquired by each. It seems to me Ev (of Blogger.com and now twitter) wrote or spoke about these same issues.
But so far my experience has been very positive. I still have near-absolute control over the development and creative direction of the site.
Why is it surprising that, at least some of the time, they aren't actually interested in the original web site?
That's not actually true. The thing about giants that acquire startups, is that a) they had the resources to build this thing themselves; b) they didn't.
So ask yourself why didn't they build this thing. It wasn't lack of resources. It wasn't lack of intelligence; they keep tabs on everyone and they go to SXSW too. There were forces that stopped the giant from innovating in this direction. Some of them are technological, but the real issues are usually cultural and political.
Once acquired, the startup is now exposed to all these forces -- with double intensity, since it is an outsider and has few friends in the organization. Unless it's already profitable, has a large userbase, or has big fans among the top execs, it has very little power.
I think these recent articles about how giants "ruin" acquisitions do not take culture and politics into account. The technical issues are not the problem.
In the case of MeasureMap, for instance, they knew they wanted that technology integrated into Google Analytics. They may not have been able to answer the "how" part of "who, what, when, where, why, and how", but surely they knew the "who", "what", and "why".
I understand that the startup built the technology and the acquirer didn't. That's the beauty of how this system is set up - a company like Google with piles of cash and stock can has so much money it can buy anything it wants.
Well then how do they decide which startups to buy (MeasureMap, Feedburner, etc.) and which startups to pass on (Digg)? That's the "master plan"..
They sell for a reason, usually that their funding is running out, founders facing a down round, increasing pressure to become profitable. The fallacy is that the sweetness and light will continue indefinitely.
I have heard that Google will pay $1m+ per engineer if they like the team and what they've pulled off, even if they are going to dump the technology (or want it rebuilt from the ground up).
I think once you get into eight figures, though-- you're probably right.
1 the technology
2 the product/userbase
3 the employees
4 kill competition
1 & 2 could be 'masterplan' motivations. 3 has a maximum dollar value. 4 is rarely admitted.
It's hard to judge if they messed up without knowing which one it is.
http://siteanalytics.compete.com/blogger.com+livejournal.com...
I don't see the problem, if you start a startup to make a shitload of money and you do make a shitload of money, then, mission accomplished right? (or, as DHH would say: Profit!)
There will always be companies that get screwed up in the acquisition process, just like there will always be companies that don't. But, let's fuel the rumor that Google kills all that it consumes, why not?
If Google is interested in your application now, why wouldn't someone else snatch it up 6 months later when you have more users for a higher price?
Sometimes winning the buyout lottery is selling yourself short.
This is what managing risk is all about isn't it? You just plain don't know!
What about the user-base? Don't we have a responsibility to them also? Without them we can't be successful, and we should own them some responsibility to ensure that the tools/product/web-site they've been using remains useful for them.
But it is a problem for acquirers & by extension a problem for future founders. If acquisitions fail to meet goals, they'll dry up.
The same goes for Delicious too I think, they were doing fine, brought by Yahoo, and then went back to being a stealth app while they rewrote everything in C++/PHP. Would they have done that without Yahoo input? Nope, I dont think so...
If you have any chance of making it on your own, I'd turn down Google money in an instant after reading this.
Personally, I would evaluate "Google" money based on the numbers.
Founders are supposed to take into consideration their product's role after acquisition when they're talking about getting bought out?
This isn't rocket science - once you sell your company to Google (or whomever), you don't own it anymore. That's why you get all those shiny coins.
Also, there are successes. Writely - > Google Docs seemed to be a pretty big success. I'm sure there are others.
The thing is that we tend to forget the successes a little bit because they got to merge so well with Google. Looking at the list of acquisitions on Wikipedia (http://en.wikipedia.org/wiki/List_of_Google_acquisitions), I can only think about Blogger but I have no experience on if it changed for the best. As far as I can tell, it looks like it's still working fine.
And just to show you that technical issues are not the primary problem, they were using Windows/C# but managed to port to Google's Linux/Java-based infrastructure and login system very quickly. (Granted, C# is way closer to Java than PHP).
I missed where exactly the article said this. I imagine if you're looking at a Google acquisition and you care about your service, nobody is stopping you from asking "how will this integrate into Google's MapReduce/BigTable? Where will I be in the Google corp. structure? Will I get engineers working with me on my product, or will I be farmed off to other products?" Weigh the answers to this as part of yoru consideration about whether this acquisition is good or not.
I think the founders are more to blame for not understanding what an acquisition by Google involved, not whoever@Google they were dealing with for not spoon-feeding them.
Closing your doors to new signups is practically like suicide. As a founder I would never agree to that if I was taking a smaller buyout in exchange for continuing to work on my application as an employee of Goog.
Now if they backed up the money dump truck and sent me on my way I wouldn't care so much (although I'd probably have thousands of users who'd hate me but probably also wouldn't blame me)
I have to ask though, given that most M&A's don't end up working out is google's failure rate really any worse than anyone else's?
Speaking of cool places to work, there is of course Google. But I notice something slightly frightening about Google: zero startups come out of there. In that respect it's a black hole. People seem to like working at Google too much to leave. So if you hope to start a startup one day, the evidence so far suggests you shouldn't work there.
http://www.google.com/search?q=ex-googlers
I think two founders in our YC class were Googlers.
Is Google just a giant Y Combinator?
There are plenty of epic technical achievements within Google. In fact, it's practically expected. The rest of the world just hears about these innovations, on average, three years after they happen. If they ever hear about them.
When things are Google products, there is a certain level of reliability, security, and performance that is expect. Google tries harder than anyone to avoid the Fail Whale.
It takes a long time for large software systems to be ported, security reviewed, integrated, and tested with Google's custom stuff.
From what I have seen, being acquired by Google means that you go dark for 18 months and then emerge as a Google product.
For any other company, habitual 9-10 figure losses would have heads rolling on the floor.