(this is page 118 of 121)





Latest

Paul Graham is at it again with one of his lucid and thought provoking essays, "The Venture Captial Squeeze", on why he thinks venture capitalists are hosed. His argument basically that capital is less important due to a few factors which make things cheaper to start companies and that Sarbanes-Oxley compliance makes it harder for startups to exit through the public markets (which implies they must sell for less to bigger companies in order to ensure a VC return).

I don't think that anyone can dispute the fact that post-bubble we are in a much different IPO market and I would not argue with the fact that it is cheaper to start companies these days but Graham misses a couple of important things that bear mentioning [Full disclosure: I have tried both the bootstrapped approach in the past (didn't work) and am currently at the beginning of a VC-funded go at-bat].

First, he forgets to mention that even having fewer people can get expensive quickly. Unless you are going to fund college students that can live in dorms and eat Ramen for dinner (something that I think he is having some success at, most people have real expenses and thus can't afford to work for no pay, or even minimum wage. If you factor in basic benefits and other people-related overhead, it is not out of the norm to think that you'll spend about $700K for a small team to come together to develop something worthwhile over the course of a year (see "runway" below before you quibble with this timeframe). And that amount is just above the reach of most angel or friends-and-family investors, or at least it is if you want to keep the signal-to-noise ratio of dealing with investors manageable (someone once told me that having angels do more than $200K was like trying to herd a litter of kittens due to their number and how fragile they can be).

Second, and this is something that he overlooks altogether (as do all of the drum-pounding Web2.0ers), when you are a bootstrapped startup that fails you can run the risk of being the tree in the woods that no one hears fall. When we did Memora we got a bunch of press at launch, great product reviews, and loads of interest. And yet, after we failed the only thing that people wanted to know when I would talk about it is: "who funded you?" as if this was more important than anything we actually built. This is lame I realize, but a fact of life you need to consider when you just look at the low odds of success in the average startup. Here the "venture filter" is your friend for two reasons: first it means you've made it past a set of guys who specialize is weeding out potential failures (which more than picking successes is what is at the heart of a top-tier VC fund), and second it means that if timing, the market, or a hurricane causes you to fail, you won't be that tree that no one hears falling.

Overall though, I think that Paul is right on to point to the fact that the VC model needs to change, at least in the web space. I think the best guys get this and like to think that our current venture is an experiment in this new direction.

The important thing that good VCs already realize is that the way to deliver value to entrepreneurs is shifting. Entrepreneurs no longer need access to big amounts of capital to grow; we don't even need access to expertise about how to grow or who to hire (because teams are smaller and the Internet is a wonderful way to identify, vet, and attract the right set of folks).

What we need is runway and support.

The first comes directly from a judicious amount of capital. Assume for a moment most startups do not get their first product right. Having enough capital to refine the product, the messaging, and even the team composition if necessary really helps to overcome the mosquito effect that affects most bootstrapped startups (you get one sting and then blam, you're dead). Ergo the number cited above for keeping a team running for a year in tight but manageable conditions.

The second comes from rolling up the sleeves and getting down and dirty. Now, every VC will tell you that this is something that comes with their money but it is just not true. First off, most VCs don't come from operating backgrounds which means that when it comes to helping you position your product and important "business" things like that most of what they can provide can be gleaned from the pages of The Portable MBA. This doesn't mean that VCs can't be valuable thought-partners though-- after all a VC that has been in the business for a couple of decades has seen plenty of good operating guys go through several technology phases.

The real killer is that most VCs spend the largest share of their time either hunting down new deals (something that becomes more important when you've got a billion dollar fund and are making ever smaller investments) or dealing with their existing companies that are on fire. Therefore time for thinking and really engaging at the point where they can be most valuable to small companies falls by the wayside. And unfortunately the dynamic that underlies Paul's essay (falling costs of starting companies) is going to make this worse before it makes it better.

So the big take-away is this: if you're still thinking about starting something and think that the reasons I've laid out above make it worth your while to at least explore the VC route, make sure that you pay close attention to whether you'll be getting the runway and support you'll need to get it right. And, of course, go out and read Graham's essay because it's written with the little guys in mind.

Comments Permalink

Here's a news-inspired thought about one of my favorite concepts from the social sciences-- path dependence:

A decade ago when smart top-tier venture guys were funding the likes of Yahoo and Excite we all witnessed what I believe to have been the beginning of path dependence towards ad-backed software over the web effect that ends with Microsoft making a feeble attempt to come to the party.

When the web was new and it came time for the VCs to find the adult supervision for the kids in the startups, they faced two choices:

  1. since the web was technology, they could have recruited technology executives to run companies that were fundamentally software makers at their core
  2. since the web was media, they could have recruited media executives to run the drive to eyeballs

I believe that the first major stake in the ground was Sequoia's when they put Tim Koogle (a magazine guy) in charge of Yahoo. KP quickly followed by putting George Bell (a documentary film maker) in charge of Excite. The rest is history.

I'm not arguing here that the web and webapps should not be seen as something that can be used to build huge advertising businesses (interestingly enough, Google, who picked a geek for its adult supervision proved that) but that it's really sort of boring that now advertising is all that people seem think of when they think of web businesses. The metaphors, analogies, and models are all lifted from more traditional media businesses. Even the executives have been recruited from the media companies, sometimes with mixed success.

I guess I was sort of waiting for someone big to stand up and say: "wait a minute here, we're gonna play on the web and our business is about XXX" where XXX could be subscriptions, novel e-commerce schemes, or just about anything beside advertising. And of all the big companies to be able to do this, I guess I would have thought that Microsoft would have both the confidence and resources to do so. Where is it's iTunes Music Store? (Though that is media, it's not advertising backed media).

I'm sure they'll do a fine Microsoft-style job on this whole ad-sponsored search and online tools thing. I just want to see something a little less me-too and a little more encouraging for those of us who don't think that the future all belongs to adwords.

Comments Permalink

I've been following the debate in the blogoshere that was ignited by the less-is-more movement spearheaded by 37signals for some time trying to think of how to write the first of many blog posts about it. On one side are all the folks who (like me) felt that a lot of heavy-weight development techniques were being applied to web development (functional specs, loads of QA, explicit design vs. development phases, a bunch of efforts to reinvent most of the LAMP infrastructure with every app, to name a few) and that despite being "professional" these things were actually hurting rather helping the cause (building useful and popular webapps). On the other side are folks who claim that software development is software development and "real" products will always require these "formal" support structures.

Today I had a work-related email conversation which made me think of this again, and then tonight while catching up on my feeds I came across a presentation which helped me get over a mental hiccup brought on by the email.

Let me start at the beginning though. This morning while writing on our corporate wiki about our current project status I wrote an offhand comment:

In web speak, with a small and agile team as talented as this one, 12 weeks ought to be enough time to build almost any product.

This landed an email from a co-worker who basically called me out for making such a crazy generalization. At first, I felt like maybe I had drunk a little too much of the 37signals kool-aid with respect to speed of development (It should be noted that while I like what they have to say in principle, in practice I think it should be taken with a grain of salt given that most of what they put out there are very thin web frontends to database-driven workflow apps). Of course, I wrote back right away with the reasons why I felt that a generalization like this one can hold, namely that in the webapp-as-service world:

  1. You don't ship the bits to the customer which means you can piece it together in the back end and rely on real-time patching to fix things.
  2. Browser apps are better for doing incrementally interface-wise so you can draw the big blocks up there and then refine in a way that you just can't when you are running a fat client app.
  3. The general shape of web apps (stateless protocol that hits and app server which uses a DB and a filesystem) is relatively straight forward (hence low overall complexity). The real challenge comes (in my opinion) in User Experience and scalability.

I feel pretty good about why these three things cut down on the time to build web applications but still felt a little weird about making a generalization in the first place. But then I heard this Salesforce.com conference by Adam Bosworth (see sidebar) about the development model at Google and something clicked for me. It's not that every web app can necessarily be built in three months (though I still hold that most can for the reasons listed above), it's that all of them should be. Because unlike the era of productivity applications when once the bits shipped the app was complete until the next release (except for bugfixes), most interesting web applications are community applications which necessarily means that when they "ship" they are only half done at best. The other half comes from looking at the logs, reading the customer email, finding what works and what doesn't and managing this iteration cycle to be as tight as is humanly possible (I can't remember when I heard that at Flickr this could be as short as 1 hour.

So, go listen to Bosworth (it's short). We're in a new world and I for one am thankful we have the right tools to meet the ever tightening development schedules.

Comments Permalink

An thought-provoking post from Peter Rip, author of a new VC blog I just stumbled upon, argues that Web 2.0 is about us entrepreneurs also being in a bubble. This is my favorite kind of grizzled-and-experienced post because it ends with an historical reference:

Today's three person startup on LAMP is 1981's Pascal developer. The few that got rich did well. The many that didn't quit their day jobs did OK. And those who quit their day jobs and didn't get rich.... learned something. (more)

Now this is a sobering thought, even for us funded LAMP/Web2.0/post-bubble startups-- reading it this evening almost gave me indigestion. However, after a little thought it occurred to me that the big difference between all of us today and the hobbyists of the early PC era is that we have now have both a bigger and better playing field to be on. For starters, PCs are ubiquitous and the network is all-pervasive. The universe of things that you can do, in photos, music, video, and communications for starters have much more appeal to the general public than writing yet another version of UCSD Pascal. Ergo a much bigger market with a whole set of new challenges around usability, scalability, and usefulness that few get right in the best of circumstances. Much more "economic energy" to capitalize upon.

Back in the day that Rip describes you might have sold 2k licenses of your Apple II Pascal compiler and been considered a wild success-- today a Web 2 company like Flickr can make a difference in half a million people's lives before "exiting" to then make a difference in millions of people's lives. And like Flickr there are others-- what were the equivalents back in 1981?

It's not to say that he doesn't make a good point in observing that the LAMP stack and the cost of commodity servers + bandwidth does allow a whole bunch of folks into the game that would have been locked out by cost before. But this should make everything that much better-- because we can all build from a cheaper, more robust, and more pliable infrastructure than even in the days of early web. It's a great time to be alive if you are into starting small and want a shot at making a difference in loads of people's lives. It's even a great time to be an investor if you're willing to think for yourself and take a few bets in this brave new world of ours.

Comments Permalink

The Weather in the East

So Joel (from Joel on Software), who just barely missed the cut for my sidebar, asks a very similar question to one I often ponder when I think of the east coast and the west coast in terms of good startup activity in the online space. He is griping about NYC-versus-Boston when he writes:

Is New York just lame compared to Boston? Or does it just seem that way? Why is that... is it because of MIT? or all the other high tech stuff going on there?

It's good to see this, because it makes me feel a little silly to often ask the question in the context of Boston-versus-Silicon Valley. Having just worked in New York for two years, and having just recently raised money in Boston, I feel qualified in saying that it really is no worse in New York than in Boston, and that in fact when it comes to media-related businesses it's actually better.

That said, it is still tough to find folks in Boston on the investment side of things that will take the big swings with that same level of nonchalance that you get from your typical west coast VC. In general I don't find this to be a huge impediment, but sometimes you see start-ups which try to squeeze themselves into a certain unnatural shapes for the sake of potential investors. The cost of this is an inability to stay loose and playful, two elements which seem to be so critical to the experimentation that allowed the west coast to take the torch from the east as soon as the PC wave hit.

However, the bigger problem is not with the investors or sources of talent per se, but rather with the fact that we are lacking a cabal of folks who can get together to bat ideas around without an explicit agenda. This was one of my favorite things about the culture out at Stanford when I lived there and it seems to be sorely missing here. Most of the events that I have been too are either tediously forced (where people with nothing more than raw ambition bump into each other, much like amoebas trying to recombine into higher lifeforms) or totally out of touch with the real cool and interesting stuff.

This is why, as Joel points out, Y Combinator may be such a special place-- if indeed Paul Graham's experiment can be made to take off.

In the meanwhile, I may take some airtime here to try to puzzle this out. And given that we've had 10 straight days of rain I might start with the climatological argument-- that is, maybe our shitty weather keeps us all locked away inside instead of out of doors bumping into each other between the rollerblading, biking, and tofu burrito munching.

Comments Permalink