Introduction

Some of the most difficult questions about a startup have to do with making predictions about the future. Estimates are just part of the game if you’re trying to manage the precious few resources you have at various points in the beginnings of your company. The problem is we’re all pretty terrible about extrapolations because if you’re an entrepreneur, by definition, all your estimates will be wildly optimistic.

Making mistakes about your skills and speed can lead you to hold off on a billing system until the last minute or estimate that you have 1 month to launch when you really have 4. And if you’re not careful, hubris might kick in and have you predicting a $1 million in revenue within 8 months of launch.

HTML Form Builder

In this feature, we’d like to help you minimize those mistakes by dissecting 4 very different web application companies that are at varying stages of their life cycle. In addition to age and size, these companies vary in their business models, programming languages and views on approaching the web as a platform. Specifically, we’ll be sharing code line counts, business processes, conversion rates, support requests revenues per customer. It’s good stuff and we’re hoping it’ll help you identify some trends that’ll make your predictions a bit more accurate.

The Participants

Here is a quick overview of the companies featured in this article:

  • Wufoo is our web application. It’s an online HTML form builder that helps anybody collect information over the Internet. When you design a form with Wufoo, it automatically builds the database, backend and scripts needed to make collecting and understanding your data easy, fast and fun.

  • Blinksale is used to invoice clients for services or products sold. Blinksale is used by attorneys, accountants, designers, IT professionals, software developers, journalists, contractors, engineers, architects, videographers, and more. Basically, if you need to send invoices, Blinksale can work for you.

  • FeedBurner is the leading provider of media distribution and audience engagement services for blogs and RSS feeds. Their web-based tools help bloggers, podcasters and commercial publishers promote, deliver and profit from their content on the Web.

  • RegOnline is one of the largest online registration systems on the web having processed over 3,537,094 registrations for more than 49,133 events worldwide. Over the past eight years they’ve invested over 20,000 development hours into the system and is considered one of the most mature and robust event registration systems available today.

The Basics

Looking over the basics, everything is fairly standard. The longer a startup has been around, the more employees it has, and programming language alone will not make or break a company.

LanguageTime to LaunchLaunch DateCurrent Employees
WufooPHP6 monthsJuly 20063
BlinksaleRuby on Rails3 monthsJuly 20056
FeedBurnerJava5 monthsFebruary 2004~30
RegOnline.NET3 years199650

The largest discrepancy is with time to launch. All companies were started with 3 or less people working on the code, but RegOnline in particular took the tough route: bootstrapping. The original founder worked a full time job, and wrote the code in his off time. This approach is definitely more demanding and requires much more dedication than receiving funding or backing by your freelance firm, but it can be done. All participants agreed that language had little to do with time to launch.

Code Line Counts

Not surprisingly, the longer a company has been around the more code it has. Experience also shows that once you are past your base set of code, the percentage dedicated to server side code starts to increase. This is primarily due to added complexity of features and other enhancements (spam protection, security, error handling, etc.) that do not necessarily have an interface element attached to them.

Download a PDF of the Slides.

As far as the original interface is concerned, it’s interesting to see how Wufoo, the youngest company, has 29% of it’s code invested in JavaScript with the second highest line count for that language among all 4 companies. Arguably, this trend will probably continue with other young “Web 2.0” apps as they adopt more Ajax intensive programming techniques.

As far as choice of language goes, all 4 companies are satisfied with their choices. There are a few minor complaints — FeedBurner wishes to some extent that the lighter, simple web interface tasks were in a different language (but they’re just fine with the heavy processing in Java), while RegOnline is aware of the fees that need to be paid in order to use a Microsoft based development platform — but overall, everyone is happy. In the end, it seems that choosing a language that you’re comfortable with can result in less lines of code and a quicker development time.

Line Counts per Business Process

The goal of this section was to uncover any task that might be overlooked. When writing a software product, the tendency is to focus 100% on the application. Items like support, marketing, and especially billing never cross your mind — in addition to the rest of the underbelly.

Download a PDF of the Slides.

While these business processes seem to only contribute towards 10% of the code base for the two most established companies, it is important to recognize that the core for the business code has to be in place during launch, if not shortly after.

Support Requests

Before even looking at the numbers, it is worth noting that support is more demanding than most would anticipate. While multiple things can lead to support requests (poor code, bad interface, complexity, lack of documentation, etc.) what seems to matter the most to customers is how quickly, friendly, and accurately you handle it.

Support Requests
Wufoo12/day
Blinksale8/day
FeedBurner45/day
RegOnline234/day

A few successful approaches to reducing the number of requests that have worked for the above companies are the introduction of the following:

  • Forums
  • Knowledge Base
  • Documentation (with videos & screenshots)
  • Useful, custom tools for support staff

The amount of time dedicated towards improving support can speak volumes. A majority of the panel agreed that support requests tend to lean towards “How do I …” and “It would be cool if …”, which is why when RegOnline established their knowledge base they saw a huge decline in tickets of that nature. Personally, I am in agreement that this type of support reigns supreme, but be aware that heavy use of JavaScript (with JSON) and foreign characters will also keep you up for quite a few nights.

Conversion Rates

Getting users is one of the more stressful aspects of a startup. Without users, you have nothing. And contrary to grand expectations pre-launch, those users are tougher to convert than anticipated. In fact, 1% is a fairly standard number to expect. So of 100 people visit your homepage, 1 person will become a paying customer.

FreePaid
Conversion per 100 Visits
Wufoo7%1%
Blinksale11%1%
FeedBurner8%N/A
RegOnline1.52%1.14%

Free accounts can also generate revenue through ads, awareness, and link backs, but the amount of free accounts you have does not necessarily increase the conversion rate that leads to getting paid. Blinksale has the highest conversion to free ratio (even though their signup form has 20 fields!), but they still come in at 1% paid. On the other hand, RegOnline has a very limited free plan, which shows a significant drop in free signups along with a much higher free to paid conversion.

To place more emphasis on the difficulty to convert, we can look at the conversion of beta testers and free advertisements for Wufoo. After a few months of limited beta testing, everyone who provided active feedback was given a free account. Of 7000 other testers, less than 1% became paying customers even though they were given a 50% off lifetime discount. Similar to that, ads that we place on both Particletree and on free forms result in approximately a 1% conversion to paid.

Average Revenue per Customer

The three companies listed all rely on monthly and/or usage fees in order to make money. Obviously, RegOnline is in an enviable position here. A few things that may result in their revenue is the maturity of their product (and the number of features they have available) along with their 10 year reputation. Not to mention, their customers are all making money (event registration), so they are willing to spend money in order to make money.

Avg Revenue/Customer
Wufoo$13.03/month
Blinksale$12.25/month
RegOnline$131/month

Wufoo and Blinksale have a similar approach in that they are trying to get a swarm of users paying less money. The goal is to reach some of the smaller businesses that are more reluctant to jump into a big purchase, and also to increase word of mouth through the volume of customers. Finding the target price to charge for your product or service is no easy feat. When Blinksale first launched, they realized they underpriced their product, and had to make the appropriate adjustments later down the road. The grandfather adjustments worked out for them, but time and programing effort had to be provided to solve the problem.

Equally challenging is how to raise the average price per customer. There are a couple of ways to attempt this:

  • Keep adding features, and create truly worthwhile features that are only available to higher paid plans.
  • Improve the marketing/site direction of new users, so that they are more compelled to sign up for a higher paying plan.
  • Make it obvious in the application that certain features are missing from their lower paying account, without being blunt and obnoxious about it.
  • Make upgrading, downgrading, and canceling as painless as possible.
  • Varying levels of support.

Speaking for Wufoo, we’ve been working on these ideas for a year now, and noticed varying levels of success. The worst payoff has been premium support, but we haven’t tried throwing phone support into that package. One noted benefit of phone support is the ability to resolve an issue immediately. Adding features is definitely a plus, but nothing drastic. Actually, slow and steady seems to be the way things are, so there may be no home run solution that increases this number by 20% in one go.

Seasonal Trends

Perhaps the most demoralizing thing that can happen to a first year startup is the change in sales from month to month. The only way to get through it is to go through a year and see what happens, but try to prepare yourself for the fluctuations, and to predict what months will and will not work for you.

BestWorst
WufooFebDec
BlinksaleJanDec
FeedBurnerJan/FebDec
RegOnlineSeptDec

For most web services it will be a given that December is a horrible month comparatively. To put it into perspective, RegOnline has noticed an 18% decrease of registrations compared to the annual average, and Wufoo saw a 50% decrease. And even though the 50% figure is distorted by growth, December was still 25% lower than the prior October. A best guess prediction for the drop in sales is the trifecta of budgets running low towards the end of the year, the holiday season, and money being spent elsewhere (bonuses, travel, consumer goods).

Thank You Participants!

This article is based on the panel we presented at SXSW 2007. Many thanks goes out to hours of data collection put in by all the members: John Zeratsky (of FeedBurner), Josh Williams (of Blinksale) and William Flagg (of RegOnline). We asked a lot from them and they were generous enough to help us out and share their company’s information. You can download a copy of the graphs from the presentation’s slides here.

HTML Form Builder
Ryan Campbell

Web App Autopsy by Ryan Campbell

This entry was posted 4 days ago and was filed under Features.
You can follow comments on this entry by subscribing to the RSS feed.

· 25 Comments! ·

  1. David Smit · 4 days ago

    I really liked this post Ryan. Its well written and you give some good information. I was surprised by the conversion rates for Wufoo.

  2. sole · 4 days ago

    Hey! I know it’s being picky but the title is slightly misleading. At the beginning I thought you were going to analyse bankrupt companies, and then I saw feedburner in the list - couldn’t believe it was bankrupt.

    See first meaning of http://dictionary.reference.com/browse/autopsy - that’s what the title looks like: “inspection and dissection of a body after death, as for determination of the cause of death; postmortem examination.”

    I know it should be understood as (2) an analysis of something after it has been done or made, but you know what I mean… :)

    It was an interesting article anyway. Companies do not disclose those data everyday!

  3. Chad Crowell · 4 days ago

    Excellent article- some really interesting information going on behind the scenes of these popular apps. I really appreciate the insight, as an app developer its nice to see how much code goes into the apps, how they are built and managed. Thanks Ryan.

  4. Dr J · 4 days ago

    Nice writeup. Its good to see some of this “comparative” data with real production products. Makes it easier to judge the projects I’m working on both professionally and personally.

  5. Aditya Mukherjee · 4 days ago

    Great article Ryan. Perfect for anyone beginning a web-app / startup. It was heartening to see that a very small idea, like a form generator, can be successful (depending on your definition of successful ofcourse).

    Thanks for the info :)

  6. Mélissa Ducharme · 4 days ago

    Wow ! Everything I really wanted to know… but never asked!

    Thanks :)

  7. Peter Cooper · 4 days ago

    I’m just having a chuckle that my (profitable!) Web app has less lines in its entirety than any of these four apps have in just CSS ;-) Not sure if that’s a bad thing or a good thing, but funny nonetheless!

  8. Chris Campbell · 4 days ago

    Peter, I’d have to say that’s a good thing.

  9. Burag · 4 days ago

    One thing I don’t understand is what’s the point of comparing an app written in 1996 to 3 others written after 2004? I mean come on, then we show the code line count and make .NET look like crap. After 1996 three versions of .NET have come out with numerous libraries, same project would’ve finished in about 6 months with 1/6 of the line count today… We’re basically comparing apples to oranges…Was Rails even around in 1996?

  10. Ryan Campbell · 3 days ago

    I wouldn’t look at it quite like that. Just looking at features and configuration alone, RegOnline has quite a lot going on. In fact, nothing substantial can be gathered from the code line counts in relation to the language chosen. As far as time to develop goes, I’d wager that a one man team working nights and weekends only would still take around 2 years to finish even with modern languages and libraries.

    The better ideas to consider with that graph are the breakdowns between sever, client, designers, etc. Also, it gives people an idea just how much code they will have to manage, which leads to thoughts on source control, flexibility, and so on. And most importantly, having a company that is 10 years old lends a good amount of consistency to the statistics — especially the business related ones.

  11. Sean · 3 days ago

    Great article, but the ratio I care about is how many people register vs how many end up paying, as the people who create accounts are the ones who are at least somewhat interested in the product. Who cares about how many people see your homepage - your page gets on digg, you’ll get 20,000 visitors and none of them will be worth anything.

  12. Trek Glowacki · 3 days ago

    I think the “Code Line Counts” section could use some clarification. Is this lines of code written by the company only or does this include line counts of any languages they are using? And, where is the cutoff? 26,000 lines of handwritten backend code for even a large Rails project seems absolutely massive…. so, does this number separate code written and code used? And where does that statistic end? (classes like Array and String have code in them as well!)

  13. snorkel · 3 days ago

    Ah, how could they be using .net in 1996? It was still in the MS Labs(probably still with the company MS bought it from) in 96, not even a public beta existed at that time. You should probably change the wording to language used now for that particular entry.

  14. rumblestrut · 3 days ago

    Biopsy, not autopsy.

    None of these sites are dead.

  15. Yuval · 3 days ago

    I don’t get these comparisons.

    I mean, does it really surprise you that it took 2.5 years longer to build “the most robust online event registration system on the internet” than it did to build a form generator? Does it really surprise you that they have 50 employess (85% of which probably do support)?

    You need to pick applications that are in the same problem domain. Especially if you’re going to compare conversion rates, marketing expenditures, etc.

    Nice pie charts though.

  16. Darrell Pringle · 3 days ago

    One of the best articles I’ve read in a long time!
    Great insight into Web development and very useful for startups. :)
    Cheers.

  17. Steven Holloway · 3 days ago

    Having worked on several large web projects over several years using asp php and rails.
    The recent projects i worked on would still not be complete if we had used php java or asp.
    our team members have worked with all the above technologies and and in our collective experience
    we rails as being so far in front as far as time to launch, ease of bug fixing,
    and maintenance. Java app (how many XML config files did you write)
    I agree that language alone makes little difference, however, the framework is very important.
    since i now boycott all MS technology i cannot comment on .NET (its been years) but why pay M$ when Rails is free and makes web app development a joy. so .NET is a framework, java has a framework. Whats does PHP have? in my experince it has way too many different way to skin the same cat. There is no true centralized PHP community rallying around one framework, plus that language is flawed in many ways. No one would set out to write PHP today, its been a series of hacks from day one, when rasmus put up some perl scripts to count views of his resume.

    Ruby is a most eloquent language and Rails is a framework thats so smart its turning heads worldwide and brought into the international spotlight. One the best thing about Rails is Ruby.
    Yes its true I am now a rails zealot. Don’t get me wrong I loved PHP for years, but ruby on rails
    has helped me move to a new level. My intention is not to start technology dribbling contest but assert my view that Rails is the new future of web development. We watch the rest of you on the sidelines as we whiz by to launch our next app in 3rd 4th 5th maybe even 8th of the time.

    Great article but i really believe, framework of choice makes a difference to you time to launch.
    (Mufoo doesn’t look like a framework to me sousing it in this comparison is somewhat misleading)

  18. conmulligan · 3 days ago

    Great article, and a fascinating insight into how these companies work. What I’d really love too see is how a startup would approach designing a large application, from a software engineering perspective.

  19. gordon · 3 days ago

    I’m so glad you knew I needed a hug. As someone starting a web2.0 business it is really fascinating to know what makes all those other websites tick. i’m working with drupal with is php but I would much prefer ruby on rails.
    http://www.buythatlocally.com

  20. Nick · 3 days ago

    This would be even more useful with ballparks for the number of total users (or even total visits, which would match the way you currently present the data) of each app. Revenue from a 1% paid conversion rate of 1000 users is much different than for 10,000 users. It also gives a good view of the market size for each app, which I think is pretty valuable.

    But good work nonetheless.

  21. Dave Medlock · 2 days ago

    Very nice article, Ryan. I’m involved in a few different “web 2.0” projects so it’s good to see time-to-launch numbers that low. (At least, I consider 3-6 months low for launching a new product from scratch.)

    What I would be very interested in is marketing tactics for all companies. As a programmer, this is the most difficult piece of the puzzle for me.

    Thanks again for the write up.

  22. keith Watson · 2 days ago

    This is an interesting article. these kinds of stats are always interesting to read so you can build an overall picture of whats going on.

  23. Naren · 2 days ago

    A new perspective. I like that. What I feel is missing is which technology scaled better and hardware infrastructure requirements. Also a project with python could have been included in the list.

  24. Matt · 2 days ago

    Very cool article. Makes me feel a lot better about the ups and downs in the new site I am co-running/starting. We took 14 months to launch (like Reg, I am still working during the day, and the only coder atm), but have been getting very good results with users, just nothing in the way of real revenue yet, but its nice to be reassured that this will come as well.

  25. Marla Erwin · Yesterday

    Great article. But I use Blinksale — depend on it, actually — and the word “autopsy” gave me a scare, as it did other commenters. Don’t DO that to me, man!!

    Also … your layout & color choices make the comments really difficult to read. A little less creativity is sometimes a good thing.

Comments for this post will be closed on 26 November 2007.

For spam detection purposes, please copy the number 7759 to the field below: