Skip to main content

Funding an Entrepreneur's Pedigree

I got sucked into this debate with a friend, who is a great person and definitely not the type of investor I'm arguing against. That's why, it would be nice to hear first hand from the type of entrepreneurs I'm talking about - those who know similar startups that got funded because of better pedigree of founders, while they bootstrapped for years without investor support.

My friend is trying to explain to someone w/ a Harvard MBA why the 90% net income margin in their financial model is not believable.

... and yet, in the end, most VCs still end up investing in people with degrees from Harvard and Stanford; coz it's takes talent to spot talent, and a lot of work to support and nurture it. If they fail, it's not the VC's fault; if they succeed, the VC made smart investment.
My Friend
Murali I think that statement might be a bit over the top. I know plenty of unemployed / unfundable ivy league grads. It's not a magic ticket.

Trivia Q: What fancy school did Ron Conway graduate from?

Ok, maybe it was a bit over the top (esp. given your original post wasn't about that). But my point remains that, notwithstanding the Ivy league grads you know who can't get funded, I know - and I'm sure you do too - a lot of Ivy-league grads who got funded with a napkin-business plan while similar or better non-IL startups with a product, customer and a much refined business plan struggle to get funded. Again, my point here is the relative ease in access to capital for the IL guys due to the disproportionate weight given by the VCs to the pedigree.

My Friend
No, I don't know of anyone who got funded because of their degree. The belief that the lack of an ivy league degree holds you back is more damaging than the lack of an ivy league degree.

Conway graduated from San Jose State University. I doubt he cares if someone went to Harvard or not.

Life is what you make it. Ask Ellison and Gates.

I do know a lot of investors who are lazy, choosing to back a startup primarily because one of the founders has a brand-name pedigree. If they practiced what they preach, they wouldn't lower the bar for the ivy-league entrepreneurs while raising it even more for non-IL startups. For the record, the entrepreneurs I'm talking about do not believe they're held back by lack of Ivy-league degrees- they take pride in their path to positive cash flow by bootstrapping for years. And they don't confuse raising Venture Capital with success- in fact, I also know quite a few who failed because they raised VC money too soon.


Popular posts from this blog

Splitting User Stories vs. Rally's "split" feature (that has nothing to do with it!)

Agile tool Rally has a "split" feature it recommends to handle "unfinished work" in a Scrum Sprint:

Manage Unfinished Work - Split user stories (new link)

Below are my observations on the "Split" feature in Rally (followed by a few excellent articles on Splitting User Stories):
This "split" feature in Rally has numerous problems: 1. Nothing to do with Splitting User Stories It has nothing to do with "Splitting a User Story" which is an advanced but fairly well-understood field in Agile, and a tool for Product Managers to use in one of the two scenarios: The Product Manager does it before an Iteration commences (i.e. during backlog creation or release planning) to create User Stories by business value that are right-sized, i.e. they can be comfortably implemented inside an iteration; The Product Manager does it in Iteration Planning or in the middle of an Iteration to reduce scope by removing/simplifying acceptance criteria, in response to t…

User Stories: you're not Agile without them

Failure to effectively transition to Agile development is often based on a fundamental failure to understand what a User Story is.

Allow me to explain.

The most important aspect of a User Story is that it's an independently *schedulable* unit of requirement (feature). The key to achieving the "independently schedulable" characteristic of a user story is that you express it in terms of how a "user" would use it. This leads you to a unit of functionality that's implemented end-to-end (UI to backend) that a user can actually interact with.

Not surprisingly, because of the focus on how a user would think about a feature, a user stories are highly readable - and could very well be written by the users themselves. However, the other important and less obvious aspect of a User Story is the emphasis on communication with the end-user and getting confirmation on the acceptance criteria.

Describing all the requirements as User Stories for a decent sized product is rigoro…

To dream or not to dream? How about keeping your mouth shut?

Here's a really nice quote from one of my dear friends in response to one of my dreams.
Between the bigger things you cannot do,and the smaller things you don't want to do,you may end up doing nothing The problem with quotes and analogies is that they are almost always approximately appropriate, but rarely if ever exactly applicable . A quote is by definition a generalization. Also, we are by nature biased with our prejudices, biased by our own very personal and unique experiences, and biased, by nature, against those who are near and dear to us. While we want them to succeed and would eventually be happy if they succeed big, our natural instinct is to "help" them "stay grounded".

I disagree with this helping nature, of course. I can - and will- expound on the virtue of dreaming big and having a big mouth. But that will be another day.

Today I'm going to present a few quotes on the flip-side of my friend's quote. Feel free to add yours to the list…