FAW #2: Saber Bhatia of Hotmail
The enabling tool they built internally during development BECAME the actual product
Just like Paypal, the Hotmail founders (Sabeer Bhatia and Jack Smith) originally set out to build an entirely different product. They sought to make a simple plug-n-play database that anyone could use to store structured information and then expose it via the web. That product was called JavaSoft and sounds as if it would have been Google Base ten years before its time. Both founders held their corporate jobs while developing Javasoft. When their IT department implemented a firewall, it killed their ability to access their personal email (which they had been using to collaborate during development). They were forced to use paper and floppy’s to trade data and it crippled their development efforts. They were driven by necessity to find another way to access their personal emails remotely and it occurred to them that web sites could be accessed from anywhere. They immediately began developing a web-based email client.
The parallel here for us was that the original concept for the hardware version of JumpBox was born when Kimbro was working a consulting gig for a major hotel chain. He stepped into a situation of utter chaos with twenty consultants on the job using excel spreadsheets to track bugs and “free climbing” with no source control. He entered the situation and implemented a bug tracker, source control and a wiki for documentation to put some structure to the development effort and after the three days it took to setup this open source infrastructure, he thought “wouldn’t it be neat if a pristine instance of all this stuff could be cloned on small form factor machines and used every time you parachute into a gig and need development infrastructure?” This was of course before the concept of virtual appliances existed and he was thinking of a hardware-based appliance at the time. But he essentially arrived at the JumpBox concept in an effort to “scratch his own itch” - a common theme throughout the Founder’s At Work series.
Using the JavaSoft idea to test the waters with VC’s
Once they had the web-based email working they thought “other people probably have the same problem… we should share.” So they opened it up and began offering web email access for others and (just like Max posting his Palm Pilot security application) they had immediate visibility and rapid adoption. They gradually realized that the web-based email idea was bigger than the Javasoft product idea, but given the low barrier to entry they feared that telegraphing their intentions by distributing the business plan of the web email to VC circles could leak the concept to someone like Netscape and blow them out. They needed to tread carefully in how they approached potential investors so they used the JavaSoft story to gauge their reaction and broached the web email idea only after they had confidence in the VC.
Just-in-time scaling
The Hotmail story was very similar to the “Hot or Not” story in that they experienced such explosive growth early on that their growth nearly killed them. They managed to stay just one step ahead of being overwhelmed with traffic by relentlessly adding servers. This is a problem everyone wants to have - growing so fast that you can’t keep up with the new traffic - but at the same time server outages not only prevent new growth but destroy your credibility with existing users so it’s an all-or-nothing game. Services will typically throttle new signups in that situation to preserve the quality of the experience for existing users rather than risk blowing it but Hotmail managed to keep performance satisfactory while keeping open signups throughout.
We have the luxury now given the nature of our offering that scaling is much easier relatively than it was for other companies. First, our products currently run locally on user hardware so ours is not an SaaS offering in that we don’t do the hosting. Secondly, because we’re now beginning to move all production apps to a virtualized environment, it should be much easier to deploy to faster hardware as necessary. We do face issues of bandwidth in making these large files available for download from our servers but we’re mitigating that with spill-over hosting on Amazon’s S3 (and we’ve also moved our dedicated servers to a higher-bandwidth data center).
The viral component
Hotmail is probably the classic example of viral marketing. Every email that was sent via their system had a tagline appended to the end of the message that said “This message sent via Hotmail. Get free email on Hotmail.com.” The users of Hotmail were inadvertently advertising the product to each of their friends with each message they sent and given that the signup process was frictionless and free, it immediately went viral. Viral advertising is trait of most of the companies that experienced logarithmic growth in FAW. Our offering fortunately takes advantage of this aspect now as well and we’re seeing some immediate results.
An unassailable lead
With the same premise of the Mythical Man Month, even with Microsoft having 16,000 engineers and Hotmail only 60, they had an six-month head start on the product, it’s scalability and a loyal user base that was promoting it virally each day. Their lead proved to be insurmountable for MS and on New Year’s Eve 1997, Microsoft acquired Hotmail for $400MM. The story of how the negotiations went down reminded me of a negotiating gambit called “deference to higher authority” and how silence can be the strongest bargaining tactic you have.
The lead we have with the JumpBox technology is by far insurmountable at this point but with the viral component and our commitment to provide our customers massive value, we strive to build a loyal following before other competitors enter the virtual appliance space.

May 5th, 2007 at 12:13 pm
[…] We see this all the time in our world- there may be a better way of doing something but if the usablity prohibits the adoption of the more powerful technique, the potential user will flee to an inferior yet attainable solution. As I mentioned in a previous post regarding the original light bulb for JumpBox that Kimbro had while working a consulting gig for a major hotel chain, the twenty-some consultants that were already on the project prior to Kimbro’s entrance were using rudimentary methods for development. In essence there was no development infrastructure because the open source tools which were freely-available for use were too difficult to setup- their usability was prohibitively bad. Good thing for us though because this is at the heart of what makes JumpBox attractive- it eliminates that prohibitive barrier and brings those power tools that had previously been out of reach within the grasp of non-technical people. […]
May 8th, 2007 at 2:00 pm
[…] I’ve been following Evan Williams’ blog for about a year now and knew him as the founder of the podcasting portal Odeo and now the popular Twitter service. I had never put it together until reading Founders that he was also the original founder of Blogger.com. What’s interesting about Evan’s story is that like the Hotmail story, the internal tool that they built to help with development of their main product became the product they sold. […]
June 1st, 2007 at 9:06 am
[…] 37s followed the path of Blogger, Hotmail and Bloglines in that BaseCamp emerged as a product after having evolved as an internal tool for solving their own problem of project management. They carved out one third of their time from client work and devoted it to refining and abstracting the application they used themselves in-house to collaborate on projects and then sold it as a subscription-based service to other developers. “It was just a flow of the application coming together and the feedback we started to get from people we respected saying, ‘I want this too!’ We thought, ‘This is something that it would be selfish to keep to ourselves.” […]