Winning The Web 2.0 Lottery: Picking The Right Numbers

About This Blog

This site is for  entrepreneurs.  A full RSS feed to the articles is available.  Please subscribe so we know you're out there.  If you need more convincing, learn more about the site.

Community

Google+

And, you can find me on Google+

Connect on Twitter

Get Articles By Email

Your email:

Google

Blog Navigator

Navigate By : 
[Article Index]

Questions about startups?

If you have questions about startups, you can find me and a bunch of other startup fanatics on the free Q&A website:

Answers.OnStartups.com

Subscribe to Updates

 

30,000+ subscribers can't all be wrong.  Subscribe to the OnStartups.com RSS feed.

Follow me on LinkedIn

OnStartups

Current Articles | RSS Feed RSS Feed

Winning The Web 2.0 Lottery: Picking The Right Numbers

 


If you are a regular reader of this blog, you probably know that I'm somewhat of a skeptic when it comes to the viability of many of the "Web 2.0" businesses out there (note:  I use double quotes around "Web 2.0" as I'm still unsure exactly what it means).


In this article, I'd like to approach this issue from a slightly different perspective.  Let's say you are determined to play this lottery.  What should you do to increase your chances of winning?  What are the best numbers to pick?


Important Note:  I consider myself to be relatively objective and have a basic understanding of statistics (I was thinking about being a professional blackjack player at one point in my life).  As such, I do understand that lotteries are random events and that there is really no way to have tips for picking winning numbers.  Web 2.0 on the other hand, has a non-random component to it -- which is what makes it interesting.  So, I'm taking a bit of poetic license here.  Work with me.  It’s Monday morning and I haven’t had my coffee yet.

Picking Winning Numbers For The Web 2.0 Lottery

These are the numbers you should be striving for (Note:  Many of these are contrived and arbitrary, but I'm just trying to make a point).

0: 
This is the ideal number of other players that have already launched a product that is near identical to yours. 

10: 
The number of other startups that you should assume are working on an identical product to yours, but they haven't launched yet.

1: 
The minimum number of co-consipirators (co-founders) you need to get stuff done.  You'll need at least one more passionate and immensely competent person to spread the work around.  Going it alone is a recipe for failure as you have as much a marketing problem to solve as you have an engineering one.  I don’t care how smart and motivated you are, you are still limited by the laws of space and time.

2: 
The maximum number of VC meetings you should have before you get back to work on your product.  With two meetings, you learn most of what you need to know (after that it’s repetitive).  This number can increase once the product has launched and you have some real numbers to show.  I would have cited the probability of your raising VC before actually launching a prototype or product, but I didn’t want to resort to scientific notation, so will let it go.

7: 
The number of days a week each of the founders should be working pre-launch to get a product out the door as quickly as possible.

3: 
The approximately number of times you’ll actually “launch” your product.  The first time, you’ll be caught by surprise (because TechCrunch will write you up, even though you’re not quite ready).  Your servers will crash and you’ll lose sleep.  The second time, you’ll be ready, but the market will be caught by surprise because they have no idea what you actually do.  The third time will be when things almost work and it is almost clear to people what it is you do.

8: 
The average number of actual, real, “customers” you should expect to get as a result of being TechCrunched.  (Note:  This is a constant and is not influenced at all by the actual traffic generated).

37: 
As in learning from 37signals.  One of the few Web 2.0 companies out there that is actually a practical business.  They have much of the upside of a cool company (like a cult-like following and almost limitless PR successes) and little of the downside.  Somehow, they've figured out how to be cool, viral and still charge (gasp!) real money.

What have I missed?  What are your favorite numbers in the Web 2.0 lottery?

Posted by Dharmesh Shah on Mon, Aug 07, 2006

COMMENTS

*0*: The number of glossy magazines and empty-calorie websites (onstartups.com - certainly not an empty-calorie site!) you should read pre-launch. Spend time getting the product done, not day dreaming over the sensationalized successes of others.

posted on Monday, August 07, 2006 at 11:48 AM by Scott Meade


4 The number of paying customers you should have *before* launching. If you can sell something before it exists you may succeed at selling it after it is launched.

posted on Monday, August 07, 2006 at 12:13 PM by stiennon


90: the maximum length of a productive meeting. Many meetings last longer than this, but they actually accomplish *less* than shorter ones.

posted on Monday, August 07, 2006 at 12:38 PM by Greg Wilson


3: The number of people involve before launch - 1) passionate angel investor who is also a customer, 2) developer/business type of person, 3) marketing/html /admin type of person.

1 is essential. 2 and 3 can vary in roles depending upon the project.

posted on Monday, August 07, 2006 at 2:24 PM by Stacy


50: The number of high quality, influencing bloggers you should know (personally/professionally) to get your producted tested and reviewed on the right time. (Note: Flickr's founder said they got the initial 80% of the traffic from blogs with absolutely no PR)

posted on Tuesday, August 08, 2006 at 9:28 AM by Mustafa


Back to the observation on the "Web 2.0". I really think Shah is right. Looking at the underlying idea, the core appears to be AJAX or its deriveratives. Well that is a method no different than say a language selection.

Ask yourself this. By using AJAX did anything fundamental change? Any W3C protocols or strictures disappear? Java gone tomorrow? Browser market disappear? Answer -- nope.

AJAX ends up being an enabler fo some keener platform rollouts. But like developers who seperated programming from content for web operations. A business loosely couples the operational rules it operates under from the technology that enables it. AJAX as I see it is proably a better lever for already established online prsence than the basis for a startup whose sole reason to be is AJAX. Seldom does a method make a business.

posted on Tuesday, August 08, 2006 at 10:30 AM by John McGinnis


7: The maximum number of pizzas you should be allowed to eat in a single week while work on your web app.

posted on Thursday, August 10, 2006 at 8:36 PM by Chris


whats up

posted on Monday, December 10, 2007 at 6:40 PM by barry


Comments have been closed for this article.