ZumoDrive, YC Founder Story

Company: ZumoDrive (by Zecter, Inc.) Founders: David Zhao (CEO), Kevin West, Vijay Mani YC Batch: Summer 2007 Industry: Cloud Storage / Consumer Media Tech Founded: 2007 | Product Launch: January 2009 Status: Acquired by Motorola Mobility, December 2010 Team at Acquisition: ~15 people Notable Deal: Powered HP CloudDrive on all HP Mini netbooks (2010)

---

---

The One-Line Summary

Three engineers from Microsoft and Amazon saw the same broken problem every day at their desk jobs, carrying content between devices was painful, and instead of complaining about it, they quit, applied to YC, pivoted once, and built the technology that powered HP's entire netbook line before Dropbox was even a household name.

---

Lens 1, The Before State

Who Were They Before YC?

David Zhao, Kevin West, and Vijay Mani didn't come from glamorous startup backgrounds. They were University of Washington computer engineering graduates who had taken the traditional path that every ambitious engineer takes: get a degree, join a big tech company, and build someone else's product.

They were working at Microsoft and Amazon, two of the most technically demanding companies in the world, where they spent their days building cloud infrastructure, file systems, and storage solutions at scale. They understood deeply how files moved across networks, how storage was provisioned, and why accessing your own content from multiple devices was still a nightmare, even for people who built these systems for a living.

This is the detail most people miss: these were not outsiders looking at the storage problem from the outside. They were insiders who dealt with it daily. They knew exactly how the plumbing worked, which made it all the more maddening that the consumer experience was still so broken.

The Personal Pain They Were Living

The specific frustration was this: by 2007, most people owned multiple devices, a home computer, a work laptop, a nascent smartphone, and moving files between them required either physical USB transfers, emailing yourself attachments, or navigating complex network shares. Your music library lived on one machine. Your photos on another. Your documents somewhere else entirely.

For engineers who thought about distributed systems all day, this was an almost offensive problem. The technology to fix it existed. Amazon had S3. Cloud infrastructure was real. Yet the consumer experience of accessing your own files on a second device was still stuck in 2001.

The founding insight was precise: what if your cloud files felt local? Not synced. Not downloaded. Not copied. What if the computer was simply fooled into thinking the file was already there, and streamed it invisibly when you opened it?

Why They Almost Didn't Look Like "YC Founders"

The team had no prior startup experience, no exits, no famous connections in Silicon Valley, and no flashy consumer app ideas. They were ex-corporate engineers from Seattle with a technical thesis, not a consumer brand vision.

They also walked into YC S07 with a product called Versionate, an office wiki and document collaboration tool aimed at businesses. Not a consumer product. Not a media story. A B2B document tool in a market already getting crowded by early Google Docs and Confluence.

On the surface, they looked like enterprise developers trying to build office software. What made them worth betting on was not the initial product, it was the technical depth behind it, and the willingness to change.

Key Insight for Aspiring Founders

The problem you solve at work is often the startup hiding in plain sight. David, Kevin, and Vijay had the technical expertise from Microsoft and Amazon to build what they built. Your "boring" corporate job may be where your unfair advantage lives. Look at the broken things you touch every day, that frustration is your research.

---

Lens 2, The Idea Origin

How ZumoDrive Actually Started

ZumoDrive did not begin as ZumoDrive. The company that entered YC Summer 2007 was building Versionate, an office wiki product designed to help teams manage business documents. It was a reasonable B2B idea with a clear market, but it wasn't the idea that would define Zecter.

The pivot happened because of a deeper technical insight that the team had been sitting on. While building document sync infrastructure for Versionate, they kept coming back to a more fundamental question: why does accessing any file from a second device still require so much friction?

The idea crystallised around a specific technical trick: instead of syncing files (downloading full copies to every device), what if you could make the operating system believe the file was local, and then stream only the parts of the file you actually needed, on demand, from the cloud? No duplication. No waiting for a full sync. Just instant access, like a local drive that happened to be infinite.

This was the core invention: a virtual drive that tricked the filesystem into treating cloud-stored content as local, while silently streaming data in the background as you accessed it. Documents opened instantly. Music played without downloading. Videos streamed without buffering full files.

They initially called it /dev/payments… wait, wrong story. Zecter named this product ZumoDrive, launched it in January 2009, and specifically designed it for the devices that were exploding in popularity at the time: netbooks, those cheap, lightweight laptops with tiny hard drives that millions of people were buying but immediately outgrowing.

The First Ugly Version

The first version was a desktop application for Windows only, with 1 GB of free storage, barely enough for a music playlist. The UI was minimal. The infrastructure ran on Amazon EC2, which was still new enough that "running in the cloud" felt cutting-edge rather than obvious.

What it had was the technical trick working perfectly: you could store 50 GB of music in ZumoDrive and your Windows music player would see all of it as if it were a local folder. That single behaviour, locally browsable, cloud-stored, streamed on access, was the product's entire identity.

The Signal That Validated It

The validation came not from paying customers but from HP. When ZumoDrive landed a white-label deal with Hewlett-Packard to power HP CloudDrive on every HP Mini netbook starting in January 2010, it wasn't just a revenue event, it was proof that the world's largest PC maker believed the "virtual local cloud drive" concept was the right model for the emerging mobile-computing era.

HP was selling millions of netbooks with 16, 32 GB of storage to consumers who had hundreds of gigabytes of media. ZumoDrive solved that mismatch elegantly. The HP deal was the market saying: this insight is real.

The Pattern This Follows

ZumoDrive fits a less-discussed but powerful YC archetype: the infrastructure pivot. They entered with a B2B product (Versionate), discovered a deeper technical insight during the build process, and pivoted to a consumer product that expressed that insight more cleanly. The initial idea wasn't wrong, it just wasn't the right expression of their actual advantage, which was expertise in how files move across systems.

---

Lens 3, The Application Anatomy

What They Brought to YC

ZumoDrive entered YC S07 as Versionate, not ZumoDrive. This is crucial context: YC didn't fund ZumoDrive, it funded the team behind it. The product that eventually became ZumoDrive didn't exist yet when YC wrote the cheque.

What the application actually sold was:

• Three technical co-founders with deep Microsoft and Amazon infrastructure experience
• A clear understanding of a real problem (document/file access friction)
• A working prototype of the Versionate wiki product
• Complementary skills, engineering depth across all three co-founders

The lesson here is stark: YC invested in the founders' ability to find the right answer, not in their initial answer. Versionate was the foot in the door. ZumoDrive was the answer they found once they were inside.

What Made Their Pitch Credible