Open Corp Dev: An Idea Too Bold For Facebook Or Dropbox
blog.kirigin.com
blog.kirigin.com
How many of those people at $1mm per head will make it through your technical interviews and fit in well enough with your culture? How long do they have to work for you before they split?
It seems like you'd have to put together some pretty draconian terms attached to a deal like this and I don't think that would be fair for anyone involved.
I mentioned Instagram: $1B for 13 people and a product that makes no money (yet). You don't think the most recent 1000 employees at Facebook are wishing they joined a small startup instead?
Dealing with this is non-trivial, I'm not trying to dismiss it. I'm just saying the idea and this problem aren't as causal as you're implying.
It might be easier to just "take a job" (debatable) but it is probably not as lucrative. As an engineer, your choice is:
1. Get aqua-hired for $1MM right away (well, maybe after a few years of working in the start-up) plus whatever your new salary will be vs.
2. Slowly earn that $1MM spread over the course of 10 years or so as a regular employee.
I know which one I'd rather do.
Why not just skip all pretenses of "doing the startup" and "developing the product" and go right for the aqui-hire. Get a well-gelled team together (demonstrate the well-gelled-ness with a demo of some sort) and then shop the whole team around to a big company looking to acquire talent. If they're willing to pay $1MM a head for a team working on a start-up and then shut the start-up's project down, why wouldn't they simply pay $1MM a head for the team?
Demonstrating skill through building a product is also hard, and also helps build value.
I think of the math like this: are the next 1000 engineers at Facebook worth 1% of their market cap? Yes, the math works.
In the kind of world where the government can't get the federal Obamacare exchange working, and people pretend that Waterfall is a competitor to Agile while really, the most common alternative is no process at all. Most companies are highly effective at demotivating software developers, and if you get hired through the usual process you'll start out on the bottom of the pyramid and behind the 8 ball.
If it costs them $1M+ to hire you there's just a chance they'll behave as if your time is worthwhile.
I like your last sentence.
There is another side here too: companies often overestimate their ability to manage acquisitions. A price floor means that those more likely to be poor integrations will be filtered out.
The only behaviours I can see it encouraging are perverse ones, like failing companies that have had enough introductory meetings to anticipate an aqui-hire offer hiring a couple of extra engineers to bump the minimum sale price.
Many people I talk to have no idea how to start that conversation.
Another layer of your consideration for upside of the acquirer: what happens if one company does this and another doesn't? It's a lot like the seed funding changes that happened over the last few years, forcing later stage VCs to change.
Also, more transparency isn't perverse. The basic action here is positive, and you're talking about theoretical side effects. If your theories are right, then pull back.
There is no transparency in this market, and advice is especially lacking for those that have no VCs.
Another side is that talking to a VC about selling is a serious conversation. It can affect things like likelihood of follow on funding, so opening one door can close another.
That VCs are thought of as a group of people who are well-connected, presumably to other well-connected people, does it make logical sense to think of them as a cartel?
I'm excited about Exitround!