Wow! What can I saw about the TechStars investor pitch/demo day except that it was fantastic. The teams were extremely well prepared and every single one of them really nailed it. We had about 50 private investors and venture capitalists in attendance to see the 10 TechStars teams go through what they’ve been up to this summer.

Those of you who follow me on Twitter know that I’ve been somewhat of a TechStars groupie this summer – I’ve spent many hours with the teams giving feedback, advice and lending a sympathetic ear. I’ve seen early ideas and kluge demos turn into the seeds of real business ideas, real prototypes and true products. The journey has been amazing to watch. For me this was the best part of yesterday – the progress that each of these companies has made this summer is truly remarkable.

TechStars was raw entrepreneurship at its finest. The program brought in teams who had ideas that ranged from pet projects to recently crafted plans to companies that the founders had been working on already for years. Over the course of the summer these ideas were refined, changed, thrown out completely and refined again. The result was a pretty amazing experience for the founders and ten pretty interesting potential businesses.

Don Doge had a nice summary of each on his blog if you’re interested. I’ve also linked to the companies below.

EventVue

IntenseDebate

SocialThing

StickyNotes

Search-to-Phone

Villij

MadKast

FiltrBox

KBLabs

BrightKite

As promised – a few thoughts on StartupWeekend now that I’ve had a chance to both get over my disappointment that we didn’t release anything on Monday morning and more importantly time to think about what worked and what didn’t work last weekend. There seems to be no lack of opinion on the subject (see the comments to the “Success and Failure” post on the StartupWeekend website and the mass of comments left on the TechCrunch article about the weekend or just do a Google search for StartupWeekend).

Overall, it was a great experience. We had an outstanding group of founders from a broad cross-section of Denver/Boulder technology companies. Andrew did a great job of facilitating the weekend without being too heavy handed (although see below for some ideas on where more structure might have benefitted the ultimate goal of the project). A lot of the people involved have posted on their blogs or elsewhere online that as a “Social Experiment” StartupWeekend was a success. I think what they mean is that we had a fun time, everyone contributed, and no-one wanted to kill anyone at the end of the weekend (which says something given that many people were operating on only a few hours sleep over the 50+ hours that the project was active). That said, if StartupWeekend is only a social experiment the concept will have pretty limited value (and a limited life – it’s fun to do once, but to make it a regular occurrence, there needs to be the realistic expectation that a ‘product’ will actually be released). Don’t get me wrong – I loved the ‘social experiment’ side of the weekend, but the goal of the project was to produce something in the period of time we were together (and capitalize on the buzz generated by the excitement around the process for the benefit of the company that was created). The journey was great, but we actually needed to get somewhere. I know Andrew wants to replicate the Boulder StartupWeekend elsewhere around the country – I’d love to see this happen and think what we learned last weekend will help make the effort in other cities more productive and ultimately more successful.

That said, VoSnap will launch – and soon. The project did live beyond the weekend and, after everyone got some sleep and returned to their Monday-Friday lives, there was a great deal of interest by the group in continuing with the project. Not just to the first launch, but beyond that (and potentially building a business around the project). When it’s up and working I’ll put up a note and link to the working site. It definitely says something both about the weekend and the group of people who participated that the project will live on beyond Monday. It’s emblematic of why the weekend was such a great experience.

Here are some summary thoughts on what worked, what didn’t work and what we might do differently when we do this again:

What worked:

• Picking the idea: We ended up with something that was realistic to do in a weekend and had the potential for legs beyond the two day project. Having a site where the founders could post ideas and doing an initial vote before we showed up on Friday night were keys to vetting the list before we even showed up (we spent around an hour picking the idea – that felt about right)
• Group dynamics: While there were plenty of type-a personalities in attendance, the group self organized really well and it was clear that people checked their egos at the door. It helped that this was a one weekend project (at least that was the thought going into it). A lot of work was done by these groups – much of it not visible to people following along on-line. PR, business development, marketing, etc. were all on their game and came up with plans/ideas that will serve the company well beyond Sunday night.
• Focusing on one project: When I looked around the room on Friday night I thought to myself “no way can this many people stay busy for the weekend”. Andrew held to his guns and insisted that we all work the same idea. He was right on – while a group of much more than this size probably wouldn’t work the weekend needs to be about ONE idea and the focus of the group needs to be singular in that respect.
• Quick meetings/quick decisions: Every hour we met for 7 minutes for an update. This is an incredibly effective way to communicate with a group w/o disrupting everyone for a long period of time. A few people have actually extended this idea beyond StartupWeekend to their day jobs. We were maniacal about keeping these short and as a result there was a lot of information conveyed at regular intervals in a very short period of time. Andrew also implemented a system of “quick votes” to make decisions (VoSnap would be perfect for this!) – the idea was to lay out the options, vote and move on. Quick votes allowed us to keep moving throughout the weekend.
• Buzz. StartupWeekend really took on a life of its own online last weekend. It started with David’s regular blog posts on www.startupweekend.com but also included the live video stream that was put up (which regularly had nearly 100 viewers), flickr photos and, of course, the TechCrunch posting. At the beginning of the weekend very few people outside of the Boulder tech community knew what StartupWeekend was and VoSnap didn’t even exist – by the end of the weekend there were hundreds of mentions online of both and tens of thousands of hits to the VoSnap site (there are more than a thousand people now on the VoSnap mailing list).

What didn’t work/what to do differently:

• The product. I guess I have to start here. On Monday we had a lot of things working, but the product wasn’t one of them (still isn’t – at least not publically). I think we should have put up whatever we had on Monday morning. On the one hand, this would have been fodder for those online who were down on the idea of creating a product over the weekend. On the other hand, it would have been true to the idea of the weekend (to create something in 2 days).
• The development process. We had a lot of great developers, but we made a bad choice of dev environments (at least in the context of putting something out in a weekend) and as a result we ended up scrapping a lot of the initial work that was done on Saturday on the product. In retrospect, we should have appointed a dev lead ahead of time, probably had the development team meet before the weekend to review the likely top candidates (based on the pre-weekend voting) and make the choice of development platforms ahead of time. The decision wouldn’t have been rushed and it would have been more well thought out. In the end, we made some choices that might have been right for the long term success of the product, but made it difficult for us to complete the first rev in time to launch on Monday. There were also a few among us that recognized this early (David, Andrew and I had this conversation on Saturday) but we (wrongly) decided to let it go.
• More developers. Out of 70 people we had probably 7 hard core developers. This ratio was too light. Many of our early stage companies are between 30% and 50% development staff. While on top of the 7 dev types, we had a handful of other people that would probably count as “engineering” in the numbers I just quoted, this imbalance set us up for some challenges (not the least of which was that development of the business plan, pr, marketing, etc pretty quickly got very far ahead of what we could do in a short period of time and probably contributed at least some to feature creep).
• Communication after the fact. During the weekend we did a great job of communicating with the outside world. Through emails, blogs, streaming video, flickr, etc, we were very open about what we were up to. A surprising amount of work has taken place since Monday, but we’ve been totally mum about it beyond the founder group (to give you a sense of the volume of email traffic, I’ve created a separate inbox just for VoSnap related email so I can see it all in one place).

I’ll end with a few pictures to give you a sense of the environment we were working in (two views of the main room and one of a stand-up product meeting).

Just over 48 hours ago 72 people came together in Boulder Colorado to see if they could come up with a business idea and launch by midnight Sunday.  We started Friday night with a handful of ideas . . . winnowed the list down to the top 3 favorites . . . and picked one to run with.  Here’s the result:

The process of working on a business with 70 people in such a short period of time was amazing.  I’ll put up some of the notes I took throughout the weekend in a post tomorrow but you can see a running tally of the experience at www.startupweekend.com.  This was entrepreneurship on steroids and was as much about the social experiment of starting a business as it was about the idea itself (something lost on many of the comment authors on our TechCrunch posting, but not lost on anyone who actually participated). 

Check out what we accomplished, but know that this is just the tip of the iceberg…

I have to admit that when I set up my Twitter account I thought I’d be turning it off after a few days for lack of interest. Instead I was calling up T-Mobile ordering a higher volume sms package.

I have to say there’s something addicting about it – I like the short message format; I like hearing what my friends are up to; I like the record of my day that it creates for me and for people that are following me; in short – it’s just fun. My Twitter ID is Sether (www.twitter.com/sether) if you want to see what I’m doing.

A few quick comments, in case this post finds its way to the Obvious gang (creators of the Twitter app):

• it’s too hard to find users and even harder to add them to your network. seems like this should be much much easier. and while we’re talking about it, what’s the difference between friends and followers?
• i’d like to be able to reply to the individual sender – replying to a twitter message sends a note back to twitter (meaning it gets broadcast as a twitter message to your friends and followers) rather than sending a message back to the poster. at a minimum a reply should trigger a ‘comment’ like feature (that would keep it w/in the twitter ‘system’ if that’s what the issue is), but ideally, you could reply directly to the message originator.
• it would be great to be able to twitter pictures.

If you really get into the service, check out TinyTwitter (www.tinytwitter.com) – an app written by my friend Kevin Crawley which will save you the hassle (if you think of it that way) of constant IM pings. Very slick and in typical Kevin fashion both simple and extremely useful at the same time.

Check out socialmeter. It gives you the link count for any site (any specific URL actually) from Bloglines, Del.icio.us, Digg, Google, Rojo, Shadows, Technorati and Yahoo. It’s a bit blunt and it would be useful as a widget (rather than taking you off the page you’re visiting and to the socialmeter page) – not to mention if it had a way to actually parse the link sources – but it’s both fun an interesting.

Thanks to Paul at Blau Exchange for the pointer.