Chris Dixon

Ford Motors dominated the auto market in the early 20th century with a single car model, the Model T.  At the time, customers were seeking low-cost, functional cars, and were satisfied by an extremely standardized product (Ford famously quipped that “customers can choose it in any color, as long as it’s black”). But as technology improved and serious competitors emerged, customers began wanting cars that were tailored to their specific needs and desires. The basis of competition shifted from price and basic functionality to ”style, power, and prestige“. General Motors surpassed Ford by capitalizing on this desire for segmentation. They created Cadillacs for wealthy older folks, Pontiacs for hipsters, and so on.

Today, the venture financing industry is going through a similar segmentation process. Venture capital has only existed in its modern form for about 35 years.  In the early days there were relatively few VCs. Entrepreneurs were happy simply getting money and general business guidance.  Today, there is a surplus of venture capital and entrepreneurs have become increasingly savvy “shoppers.”  As a result, competition amongst venture financiers has increased and their “customers” (entrepreneurs) have flocked to more specialized “products.”

Some of this segmentation has been by industry (IT, cleantech, health care) and subindustry (iPhone apps, financial tech, etc). But more pronounced, especially lately, has been the segmentation by company stage.  Today at least four distinct types of venture financing “products” have become popular.

1) Mentorship programs like Y Combinator help startups ideate, form founding teams, and build initial products. I suspect many of the companies they hatch wouldn’t exist at all (and certainly wouldn’t be as savvy) if it weren’t for these programs.

2) So-called super angels provide capital and guidance to a) hire non-founder employees, b) further product development c) market the initial product (usually to early adopters), and d) raise follow on VC funding. Often current or former entrepreneurs themselves, super angels have gone through this stage many times as founders and angel investors.

3) Traditional VCs (Sequoia, Kleiner, etc) help companies scale and get to profitability. They often have broad networks to help with hiring, sales, bizdev and other scaling functions. They are also experts at selling companies and raising follow-on financing.

4) Accelerator funds (most prominent recently is DST) focus on providing partial liquidity and preparing the company for an IPO or big M&A exit.

In the past, traditional VC’s played all of of these roles (hence they called themselves “lifecycle” investors). They incubated companies, provided smalls seed financings, and in some cases provided later stage liquidity. But mostly the mentorship and angel investing roles were played by entrepreneurs who had expertise but shallow pockets and limited time and infrastructure.

What we are witnessing now is a the VC industry segmenting as it matures. Mentorship and angel funding are performed more effectively by specialized firms.  Entrepreneurs seem to realize this and prefer these specialized “products.”  There is a lot of angst and controversy on tech blogs that tends to focus on individual players and events. But this is just a (sometimes salacious) byproduct of the larger trends. The segmentation of the venture industry is healthy for startups and innovation at large, even if at the moment it might be uncomfortable and confusing for some of the people involved.

My most useful career experience was about eight years ago when I was trying to break into the world of VC-backed startups. I applied to hundreds of jobs:  low-level VC roles, startups jobs, even to big tech companies.  I got rejected from every single one.  Big companies rejected me outright or gave me a courtesy interview before rejecting me. VCs told me they wanted someone with VC experience.  Startups at the time were laying people off.  The economy was bad (particularly where I was looking – consumer internet) and I had a strange resume (computer programmer, small bootstrapped startups, undergrad and masters studying Philosophy/mathematical logic).

The reason this period was so useful was that it helped me develop a really thick skin.  I came to realize that employers weren’t really rejecting me as a person or on my potential – they were rejecting a resume.  As it became depersonalized, I became bolder in my tactics. I eventually landed a job at Bessemer (thanks to their willingness to take chances and look beyond resumes), which led to getting my first VC-backed startup funded, and things got better from there.

One of the great things about looking for a job is that your “payoff” is almost always a max function (the best of all attempts), not an average. This is also generally true for raising VC financing, doing bizdev partnerships, hiring programmers, finding good advisors/mentors, even blogging and marketing.  I probably got rejected by someone once a day last week alone. In one case a friend who tried to help called me to console me. He seemed surprised when I told him: “no worries – this is a daily occurrence – we’ll just keep trying.”  If you aren’t getting rejected on a daily basis, your goals aren’t ambitious enough.

One of the most important developments of the web 2.0 era is the proliferation of full featured, bidirectional APIs.  APIs provide a way to “federate” web services from a single website to a distributed network of 3rd party sites. Another important web 2.0 development is the proliferation of web Apps (e.g. Facebook Apps). Apps provide a way to make websites “extensible.”

The next step in this evolution is to create web services that are both federated (APIs) and extensible (Apps).

In my ideal world, the social graph would not be controlled by a private company. That said, Facebook, to its credit, has aggressively promoted a fairly open API through Facebook Connect. Facebook has also been a leader in promoting Apps. For Facebook, creating extensible, federated services would mean providing a framework for Facebook Connect Apps – apps that extend Facebook functionality but reside on non-Facebook.com websites.

Consider the following scenario.  Imagine that in the future a geolocation data/algorithm provider like SimpleGeo takes Facebook Places check-in data and, using algorithms and non-Facebook data, produces new data sets, for example: map directions, venue recommendations, and location-based coupons. The combination of Facebook’s data (social graph and check-ins) and SimpleGeo data/algorithms would create much more advanced feature possibilities than either service acting alone.

With today’s APIs, if, say, Gowalla wanted to integrate Facebook plus SimpleGeo into their app*, they would basically have 3 choices:

1) Embed Facebook widgets in Gowalla.  These are simple iframes (effectively separate little websites) that don’t interact with SimpleGeo.  Gowalla would just have to sit and wait and hope that Facebook decided to bake in SimpleGeo-like functionality.

2) Pre-import SimpleGeo data. This significantly limits the size and dynamism of the SimpleGeo data sets and doesn’t incorporate SimpleGeo algorithms, thus severely limiting functionality.

3) Host an instance of SimpleGeo’s servers internally.  This requires heavy technical integration, undermining the main benefit of APIs.

In a world of extensible APIs (or “API Apps”), Gowalla could instead send Facebook data back to SimpleGeo.  The data flow would look something like this:

(Note how there are three parties involved – @peretti calls this a “data threesome”). This configuration is much simpler to integrate – and potentially much more powerful and dynamic – than the other configurations listed above.  You could implement this today, but it would create user experience challenges.  For example, Gowalla would be sending Facebook data to a 3rd party (step 3), which might (depending on the data sent) require explicit user opt-in. Things become more onerous if SimpleGeo wanted to share its own user data with Gowalla. That would require an additional oAuth to SimpleGeo (authorizing step 4).

Allowing websites to be federated and extensible will open up a whole new wave of innovation.  Ideally some spec like oAuth could include the multiple authorizations in a single authorization screen.  Facebook could also do this by allowing 3rd parties to be part of the Facebook Connect authorization process.  Inasmuch as Facebook’s seems to be trying to embed their social graph as deeply as possible into the core experiences of other websites, allowing extensible APIs would seem to be a smart move.

* I have no connection to any of these companies (Facebook, Gowalla, SimpleGeo) and have no knowledge of their product plans beyond their public websites.  I am imagining functionality that Gowalla and SimpleGeo might include someday but for all I know they have no interest in these features – I just picked them somewhat arbitrarily as examples.

Howard’s Stocktwits interviews are always really fun.  Some people don’t get his subtly self-deprecating sense of humor but I love it. Besides discussing the usual suspects (Facebook, Twitter, Apple), we spend some time trashing Wall Street and chatting about some early-stage startups including Founder Collective investments Bnter, Giiv, Ze Frank Games, and Canvas (founder of 4chan Moot’s new startup).  Of course I also shamelessly promote Hunch.

Also, Fred Wilson’s interview with Howard is a must watch.