Skip to main content

Milk Money for Meebo.com

Here’s something that I highly recommend y’all read:

milk money…” - parts I, II, & III


It’s an amazingly detailed and honest account of the fund-raising process from someone who raised the money just over a month ago - in December 2005!

One thing that’s not mentioned in the story is the amount raised from Sequoia. I know it’s $3.5 million- straight from the horse’s mouth.

So let’s do the numbers.

$3.5M in Series ‘A’ means anywhere between 20% to 40 % stake was given away, based on how much leverage each party had.

Note that regardless of leverage, any experienced VC will typically want to own *not more than* 40% and *not less than* 20%, “post-money”. [VCs taking more than 40% drastically reduces the founders’ feeling of ownership and thus, their incentive to succeed. Taking less than 20% would mean the VCs will spend very little time or effort on this company- instead choosing to focus on the other companies in their portfolio where they have a greater “interest”.]

... continued in "Startup Valuation: Meebo.com"

Comments

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 accept

Venture Quotes for a softening economy

Guess who said the following? "There's a lot of hot air and arrogance in the (VC) business that we all would be better off without" "...useless pontificating in front of entrepreneurs working harder than (VCs)..." "...VCs who constantly speak of deals and projects , reveal their self-interest and slight the labor and dreams of the entrepreneurs" If you think it's some disgruntled entrepreneurs who don't "get it", think again. In the past, I've made some pretty strong but heartfelt things, and I could have said the above, but I didn't . Read on here to learn who uttered these pearls of wisdom.

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