
We're the best online calendar solution to ever exist. Period.
Turn this teardown into a decision-ready prompt for ChatGPT, Claude, or your agent.
If you only have a few minutes to spare, here’s what investors, operators, and founders should know about Kiko (S05).
Kiko was the first company Y Combinator ever funded, and its failure taught the accelerator one of its foundational lessons. Built in YC's inaugural Summer 2005 batch by Yale friends Justin Kan and Emmett Shear, Kiko was one of the earliest Ajax web applications: a slick, drag-and-drop online calendar at a moment when almost nothing on the web felt that responsive.[4][2]
Then Google launched Google Calendar in 2006, and a free calendar bundled into Gmail's enormous user base left a standalone calendar startup with no reason to exist.[1] Rather than grind on, Kan and Shear did something now legendary: they auctioned Kiko on eBay for $258,000, returned money to investors, and used the episode as a springboard. Their next idea, hatched with Paul Graham, became Justin.tv and eventually Twitch.[3] Kiko died, but it produced the clearest early statement of a rule YC still preaches: don't build a feature a platform can absorb.
Justin Kan and Emmett Shear met as students and shared a programmer's instinct for building fast. When Paul Graham and his partners ran the first Y Combinator batch in the summer of 2005, Kan and Shear were in it with Kiko, making them charter members of what would become the most influential startup accelerator in the world.[4][8]
Their insight was timing-based and correct as far as it went. The web was shifting from static pages to interactive "Web 2.0" applications powered by Ajax, and a calendar — something people used daily and hated doing in clunky desktop software — was a natural showcase. Kiko let users drag events around a browser calendar with a fluidity that felt novel in 2005.[2]
The problem was that "a good web calendar" is a feature, not a defensible business, and the founders would learn this in the most direct way possible. After Kiko unwound, the pair sat down with Paul Graham to figure out what to do next. When they floated a modest idea — a service that printed web content into a physical book — Graham's reply was pointed: "What else do you guys have?" They then pitched broadcasting Kan's life 24/7 over the internet, and Graham said, "That sounds crazy enough that I'd fund it."[1] That exchange, born directly from Kiko's death, launched Justin.tv.
Kiko was a browser-based calendar built with then-cutting-edge Ajax techniques. Instead of reloading a page for every action, it updated in place, letting users click and drag to create and move appointments, set reminders, and view their schedule from any computer without installing software.[2] In 2005 this was genuinely ahead of the pack; most calendaring still lived in desktop Outlook or basic web forms.
The product's strength was also its ceiling. It did one thing — calendaring — and did it in the browser. There was no email, no social graph, no proprietary data, and no switching cost beyond the events a user had entered. A calendar is most useful right next to email, where invitations arrive and events are born, and Kiko had no email. That structural gap meant the natural home for a web calendar was inside a mail provider — exactly where Google was headed.[5]
Read the complete post-mortem, the rebuild playbook, and the exact reasons Kiko is still worth studying now.