Skip to main content

Startup Valuation: Meebo.com

... continued from "Milk Money for Meebo.com"

I’d put the percentage equity that the VCs took for their $3.5 million at Meebo at a lot closer to 20% pre-money given how hot Meebo was (again, based on all the buzz about them on Sand Hill Road).

Still, let’s assume 25% pre-money.

That makes the pre-money valuation of the company 3.5 * 4 = $14M.

In other words, Sequoia put in $3.5 million and got 25% of Meebo, putting the company’s value at $14M pre-money.

After the investment, Meebo’s post-money valuation is $17.5M (i.e. 14 + 3.5, the value of the company + the cash). That means, Sequoia now owns 20% of Meebo, post-money. Like I said, that’s about the minimum any self-respecting VC firm in the Valley would like to hold in a startup after Series-A financing. And Sequoia is right up there with Kleiner-Perkins at the top of the VC hierarchy in the Valley.
---
Note that at the other extreme of 40% post-money, Meebo’s post-money valuation $8.75M. That puts the pre-money valuation at $5.25M for an absurdly high 66.7% ownership stake. We can readily discard this scenario.

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...

Agile Entrepreneurs Manifesto

The  Agile Manifesto  defines the 4 core Values that define "Agile":  " Individuals and interactions",  " Working software",  " Customer collaboration", and  " Responding to change" As I applied Agile requirements (user stories), engineering (XP), and process & project management (Scrum & Kanban) to my startups  (RideStation, and Agile Entrepreneurs)  starting from 2005 to now in 2018, I learned numerous lessons and shared them with my fellow entrepreneurs for the next dozen years. These lessons I have incorporated by "extending" the Agile Manifesto with two additional values pertaining to  Product (5th) and Startup/Business (6th)  -  that the services consultants who wrote it in 2001 probably didn't have to contend with as most (all?) of them were not founders of product startups:  "User Validation, Customer Traction, and Business Milestones" Agile Entrepreneurs Manifesto Us...

User Stories for Product Managers

I've previously said that User Stories are the most powerful construct in Agile methods, more than TDD, in my view. The challenge in using User Stories though lies in the fact that they shift the responsibility of getting things right - and quite fairly I might add - from the Engineering team onto the Product Owner/Product Manager. And unless you have strong buy-in from management, it's difficult to make it to the end of the Product Management process and to a point where you're cranking out iterations one by one. The key lies in efficiency in creating and managing User Stories, and tying them effectively to an evolving User Interface even as the product starts coming alive. I'm planning to share some of my experiences and thoughts on this soon. Meanwhile, I found this interesting article while searching the net for splitting stories along CRUD capabilities. Ways to split user stories .