Kiko, YC Founder Story

Company: Kiko (Kiko Software) Founders: Justin Kan & Emmett Shear YC Batch: Summer 2005, YC's Very First Batch Ever Industry: Productivity / Web Calendar (AJAX) Founded: 2005 | Acquired (eBay auction): 2006 Exit Price: $258,100, sold on eBay to Tucows CEO Elliot Noss What came after: Justin.tv → Twitch → $970M acquisition by Amazon (2014)

---

---

The One-Line Summary

Kiko failed in 12 months, got killed by Google, and was sold on eBay for $258,100, and it's one of the most important startup stories in YC's entire history, because the two founders who built it went on to create Twitch, which sold to Amazon for $970 million. This is the story of what a "failed" startup actually looks like, and why failure is often just a slow-burning launchpad.

---

Why This Story Belongs in Your Library

Most YC story collections only celebrate winners. Kiko is essential because it shows the other path, the one that most aspiring founders will actually experience first. A real product, real users, a real exit, and a catastrophic competitor, all before turning 23. Justin Kan and Emmett Shear didn't become legends despite Kiko. They became legends because of what Kiko taught them.

---

Lens 1, The Before State

Who Were They Before YC?

Justin Kan and Emmett Shear had been friends since second grade in Seattle. They grew up walking around a nearby lake for hours, just talking through ideas. This childhood habit, comfortable sitting with uncertainty, endlessly brainstorming without pressure, turned out to be the most valuable skill they ever built.

By the time they arrived at Yale, they were already a unit. Emmett was the quieter, more analytical one. Justin was extroverted, restless, and constitutionally unable to stay still. They were studying physics and psychology respectively, degrees that, by their own admission, had nothing to do with what they actually cared about.

In their senior year at Yale, they faced the choice almost every Ivy League graduate faces: take the safe, high-paying consulting or finance job that their degree had been pointed at for four years, or try something else entirely.

The Personal Pain They Were Living

The idea for Kiko came from a frustration Justin had been sitting with: digital calendars were terrible. Paper calendars were still dominant in 2005. Google hadn't yet built Google Calendar. The web was finally capable of rich interactive applications, AJAX technology was just emerging, and nobody had used it to solve something as basic as scheduling.

Justin had actually started a charity calendar project earlier that year, a quasi-humorous calendar featuring Yale students (including himself), which had gotten him thinking about digital calendars more seriously. It was a low-fi signal, but it planted the seed.

The idea wasn't born from a dramatic insight. It was born from the simple observation that the obvious thing didn't exist yet.

Why They Almost Didn't Fit the "YC Founder" Mould

Justin and Emmett were not technical founders in the traditional Silicon Valley sense. They were Yale physics and psychology students with no industry experience, no prior exits, no startup networks, and no particular reason to believe that two twenty-two-year-olds could build something that mattered.

They heard about Y Combinator almost by accident, a mutual friend introduced Justin to Paul Graham just before the application deadline. There was no months-long strategy. They applied on instinct, essentially on a whim, and got in.

What they turned down to do it: lucrative post-graduation consulting jobs. That decision, choosing uncertainty over a guaranteed income at 22, is the most underrated thing about this story.

Key Insight for Aspiring Founders

You don't need a dramatic origin story. You need to notice the obvious thing that doesn't exist yet, and then be willing to choose it over comfort. Kiko started because calendars were bad and Yale seniors turned down consulting jobs. That's the whole story of how it began.

---

Lens 2, The Idea Origin

How the Idea Was Born

The idea for Kiko emerged during Justin and Emmett's senior year, when they were deep in the emerging world of Web 2.0. AJAX, the technology that allowed web pages to update dynamically without reloading, was just becoming viable. Google Maps had just used it spectacularly. The question on every developer's mind was: what else could AJAX unlock?

For Justin and Emmett, the answer was clear: a calendar that worked like a desktop app, but in the browser. Accessible from any computer, shareable with anyone, integrated with the newly launched Gmail. The idea was technically ambitious for 2005, and that's precisely what made it interesting to YC.

Their tagline, "We're the best online calendar solution to ever exist. Period.", tells you everything about the confidence (and perhaps the overconfidence) of the early Kiko mindset.

The First Version, Bold and Technically Sharp

Kiko launched in August 2005, just weeks after getting into YC's inaugural batch. For a consumer web app in 2005, the product was genuinely impressive. It offered:

• Universal access across any computer
• Calendar sharing with non-Kiko users via a simple link
• Mobile phone integration
• AIM (instant messaging) sync
• Natural language input: type "Pay gas bill every month" and it would parse it correctly

The team were strong engineers. They weren't faking it. The product worked. It was well-designed. Early users liked it.

Within a year, they had enough momentum to raise an additional $50,000 from outside investors beyond YC's initial $12,000. That's not a product people hated. That's a product that had genuine early signal.

The Signal That Validated It, And the Signal That Killed It

The validation was real user growth and investor interest. The death signal arrived on April 13, 2006: Google launched Google Calendar.

Free. Deeply integrated with Gmail, which was already the email product of choice for exactly the users Kiko was targeting. Backed by Google's brand, infrastructure, and distribution. Immediately, Kiko's growth stalled. Users who had been enthusiastic went quiet. The product that had felt ahead of its time suddenly felt redundant.

The Pattern This Follows

Kiko is the canonical example of a "right idea, wrong timing, wrong competitor" startup. The idea was sound. The execution was competent. The problem was that they were building in a space that a search giant had decided to enter, and against Google's distribution and brand, a two-person team had no structural advantage.

This pattern repeats throughout startup history. The lesson is not "don't build if Google might enter." The lesson is: know where your moat is before a bigger competitor shows up. If your only advantage is being first, that advantage has an expiry date.

---

Lens 3, The Application Anatomy

Getting Into YC's Very First Batch, What That Actually Meant

When Justin and Emmett applied to Y Combinator in 2005, YC did not exist as a known quantity. Paul Graham, Jessica Livingston, Robert Morris, and Trevor Blackwell had just started the accelerator as an experiment, a bet that young technical founders could use a small amount of money and mentorship to build real companies faster than the traditional VC model allowed.

There was no prestige attached to the YC brand yet. There was no guarantee that being accepted would mean anything. It was a gamble on both sides.

Justin and Emmett got in through a warm introduction, a mutual friend connected Justin to Paul Graham shortly before the application deadline. The connection was serendipitous, not strategic.