> Can somebody explain to me why every startup company(or at least every one that articles are written about) feels the need to raise as much VC as possible ASAP?
1. It pays the bills.
2. Raising money is a strong signal of success both from a personal entrepreneur perspective and for the success of the team (whether you disagree with that notion or not, it's simply true). Whether that translate to success is a different story.
3. Raising money means your business exists. Many people (especially B2B) don't want to do business with vendors who aren't going to be around in 6 months.
4. The speed at which tech startups are created, also exists in reverse. Startups close down all of the time.
> Neither of them had to resort to advertising before their companies got big.
> I don't believe its a stretch at all to think that me and a buddy could build something like Snapchat or Instagram in a couple of weeks and throw it up on App Engine.
Heh, if it's that easy then, ummm, go build it? Chucking millions of dollars at these startups isn't necessarily about building the product, it's about supporting their growth to get network effects ASAP. Achieving "the network effect" means you've got a nice big moat around your business, which VCs and entrepreneurs love. You're right, they didn't have to do advertising, but they did have to pay for shit-hot SRE people to make sure 1bil tweets could be sent every week (or whatever).
I did not mean to say that I could build a product like these to demean or belittle them in any way. The vision, ideas and UX execution behind them were clearly thought up by inspired and talented people. What I mean to say is that from a purely technical standpoint, they would be trivially easy to build, so I don't see why you would need to raise millions to pay for "software engineers" to build and maintain your initial product. They are just simple CRUD apps, a class of system of which there are a deluge of accessible and easy to pick up resources and frameworks available to learn how to work with, and a huge pool of cheap developers available. The technical problems that they solve are not novel in any way. While some of the Silicon Valley brogrammer types like to paint themselves as these renegade code wizards hacking on these super hard to solve problems(probably because it helps them get a paycheck), the truth is the problems imposed by CRUD apps are some of the most already solved around. I don't mean to say that there aren't plenty of code wizards hacking on hard to solve problems, but I bet they sure aren't CRUD related. Hell, I don't think its unreasonable at all that 1 or 2 completely non-technical cofounders could team up and learn Ruby on Rails or Django in a couple of months and put a viable product together. If you use an IaaS/PaaS system, Google or Amazon or whoever handles scalability problems for you - its literally as easy as moving a slider and paying more money. Why pay $230k a year for a "scalability/reliability engineer", when I could pay exponentially less to Google or AWS and not have to worry about anything? Even if those didn't exist, have you ever heard of a user facing web company failing because their tech stack wasn't efficient, because it was built by someone just average at coding who chose an easy to work with system with a fast dev cycle and not a "Full stack Javascript distributed scalability Guru"? No, because by the point where the efficiency of their tech stack became a problem, they would have enough capital to hire 10 engineers to rewrite the whole system in Scala or whatever flavor of the month stack tech bloggers happened to be writing about if they so chose.
If your company required some kind of technology that only someone with specialized skills could work with, I would understand. Robotics software? Sure. Biotech? Sure. Life-critical systems? Sure. But I won't be told that photo sharing and social media apps in this day and age require that much capital to build.
And networking? It seems to be that tech, is one of the fields in which this matters less than others to build a successful company, which is why it attracts so many of the engineer types who hate dealing with bullshit. They don't want to deal with bureaucracies and market analysis, they just want to build awesome stuff. I'm certainly not saying it doesn't matter at all, but I find it hard to believe that people would sell away stakes in their companies just for "networking opportunities".
Google was unlike these companies, in that the product was unique in both idea and technical implementation. The idea was original - organizing search results by relevancy, and the algorithm behind the PageRank implementation required a bit of high level math. The actual engine was implemented in C++, not exactly the easiest language to work with. But like I said, Google was pretty much bootstrapped until they really did need the money. They didn't immediately raise millions prelaunch and headhunt the best engineers in the valley. The founders were bright CS people who built their thing, ran out of a garage, and solved problems on their own for as long as they could. When they received their first investment they hadn't even incorporated yet - they had to go file the papers and wait a week before depositing the money in an account. It would seem that the average founder has gone from being the type who is a tinkerer primarily interested in tech and doing stuff that hasn't been done before(think Sergey and Larry, Bill Gates, Wozniak, Paul Graham, Zuckerberg)- but with a side interest in business, now to the type who is primarily interested in business and sees tech only as a means to an end, and raising as much capital as possible and throwing it at developers and marketing people as a means to achieve that end.
I don't mean this to sound condescending or whatever, I'm just trying to come up with reasons here.
> Why pay $230k a year for a "scalability/reliability engineer", when I could pay exponentially less to Google or AWS and not have to worry about anything?
I think you're massively undervaluing the complexity of systems at scale. Let me give you a more concrete example. In Facebook and LinkedIn there is a feature that says "You may know this person". It's a small box in the upper right corner and looks like the smallest feature ever. But the underlying complexity of building such a feature is easily millions of dollars worth of man hours. Just that small feature has probably single-handedly grown those companies by > 1x factor. You don't get that simply by "throwing it at AWS".
I appreciate your enthusiasm for this topic, but I think the lens at which you see the startup world is being blurred by media and survivor bias. There is so much under the tip of the iceberg that 99% of the people here will never see.
I have to disagree with you here. Elasticsearch has a "more like this" feature built into it, which would give you pretty much the desired functionality you're describing that Facebook and LinkedIn have. It's a free and open source technology that I've installed and maintained on my servers. All you have to do is feed it some JSON, which you can modify as you choose to bias it to your exact specifications. Google and AWS offer cloud search and database features which already have this type of functionality implemented for you - all you have to do is wire it to your app. I'm not saying that these problems were trivial to solve in the first place, but THEY HAVE ALREADY BEEN SOLVED BY GOOGLE AND AMAZON AND FACEBOOK AND A MILLION OTHER COMPANIES' ENGINEERS, and made available to you in a nice and easy to use package with a bow on top.
So, I think it's very reasonable that 1 or 2 completely non-technical cofounders can team up and learn RoR or Django and put a product together on Heroku or AppEngine.
The problem is that they're competing with all the other completely non-technical cofounders who can do the same thing.
Most of the viable large-scale CRUD apps have already been picked clean. Much of what remains is niche software (eg. lifestyle SaaS businesses) or very non-obvious (eg. Facebook - it was technically trivial when it started, but it also wasn't obvious that there was a viable business in social networking until Zuckerburg went and built it). My prediction is that a lot of the startups that succeed over the next few years will involve some key technology that requires technical skill and domain knowledge to produce.
1. It pays the bills.
2. Raising money is a strong signal of success both from a personal entrepreneur perspective and for the success of the team (whether you disagree with that notion or not, it's simply true). Whether that translate to success is a different story.
3. Raising money means your business exists. Many people (especially B2B) don't want to do business with vendors who aren't going to be around in 6 months.
4. The speed at which tech startups are created, also exists in reverse. Startups close down all of the time.
> Neither of them had to resort to advertising before their companies got big.
> I don't believe its a stretch at all to think that me and a buddy could build something like Snapchat or Instagram in a couple of weeks and throw it up on App Engine.
Heh, if it's that easy then, ummm, go build it? Chucking millions of dollars at these startups isn't necessarily about building the product, it's about supporting their growth to get network effects ASAP. Achieving "the network effect" means you've got a nice big moat around your business, which VCs and entrepreneurs love. You're right, they didn't have to do advertising, but they did have to pay for shit-hot SRE people to make sure 1bil tweets could be sent every week (or whatever).