Talkito, YC Founder Story

Company: Talkito Founder: Hovig Bayandorian YC Batch: Summer 2006 (YC's 2nd year, one of the earliest batches ever) Industry: Social Web / Co-browsing / Real-time Communication Founded: 2006 | Status: Inactive Outcome: Did not scale, founder later transitioned to biotech research at Pacific Biosciences Why This Story Matters: Not every YC company becomes Stripe. This is the story of an early, ahead-of-its-time idea, and the lessons are just as valuable as any billion-dollar exit.

---

---

⚠️ A Note Before You Read

Most YC story collections only cover the winners. This one doesn't.

Talkito never became a household name. It went inactive. The founder moved on to a completely different career in biotech science. And yet, this story is one of the most instructive in this entire collection. Because the question it forces every aspiring founder to ask is not "how do I build the next Stripe?" but "how do I know if my idea is early, wrong, or just underfunded?" That question is worth $49 on its own.

---

The One-Line Summary

In 2006, one founder built a tool that let strangers chat when they landed on the same website, a concept so ahead of its time that the infrastructure, smartphones, and social norms to support it wouldn't exist for another decade. Talkito didn't fail because the idea was bad. It may have failed because the world wasn't ready yet.

---

Lens 1, The Before State

Who Was Hovig Bayandorian Before YC?

Talkito was founded in YC's Summer 2006 batch, only the second year of Y Combinator's existence. Paul Graham had just started the programme the year before with eight companies. The entire YC alumni network was a handful of people. There was no Demo Day mythology, no $500k standard cheque, no "YC effect" on valuations. Getting into YC in 2006 meant something raw and real: you were one of maybe 20, 30 people in the world being bet on by a small group of hackers who believed software startups could be built cheap and fast.

Hovig Bayandorian was a technical founder, the kind of person who thought about the web not as a consumer but as a builder. He was operating in the height of the Web 2.0 era: the period between 2005 and 2008 when the internet was being completely reimagined as something participatory, social, and real-time. Flickr had launched. Del.icio.us was growing. MySpace was at its peak. The question everyone was asking was: what if the web could be social in ways we haven't imagined yet?

The Personal Pain That Drove the Idea

The observation behind Talkito was genuine and elegant: the web in 2006 was a deeply solitary experience. You visited a website alone. You read an article alone. You browsed a forum alone. You had no idea if 10,000 other people were reading the same thing at the same time as you, and even if you did, you couldn't talk to them.

Hovig's insight was: physical spaces have always been social by default. You walk into a bookshop and you can see other people reading. You're at a café and you can strike up a conversation. Why did visiting a website feel like entering an empty room?

Talkito's answer: make websites social in real time. If you and another person are both on the same website at the same moment, you should be able to see each other and chat, without either of you doing anything to set it up.

Why This Founder Didn't "Look Like" a Typical Startup Founder

In 2006, the archetype of a startup founder was already starting to calcify: young, dropout from a top university, building in a garage in the Valley. Hovig was technical and capable, but the sheer structural difficulty of his problem, building real-time synchronised web presence detection across arbitrary third-party websites, with no smartphone ecosystem, limited browser APIs, and no WebSocket standard, meant the gap between the idea and the infrastructure to support it was enormous.

This was not a founder problem. It was a timing and infrastructure problem that no amount of determination could fully solve in 2006.

Key Insight for Aspiring Founders

The hardest type of startup to evaluate is one where the idea is right but the timing is wrong. Talkito's core concept, real-time social presence on websites, is now standard in customer support tools, collaborative browsers, and live shopping platforms. In 2006, the infrastructure simply didn't exist to make it work at scale. Knowing the difference between "bad idea" and "right idea, wrong decade" is one of the most underrated skills a founder can develop.

---

Lens 2, The Idea Origin

Where the Idea Came From

Talkito's idea came from a very pure place: the observation that the web had a social loneliness problem. The physical world naturally surfaced shared interests, you could tell who else was in a bookshop, a cinema, a park. The web could theoretically do the same thing at planetary scale, yet every user experience was designed as if each visitor was the only person on earth.

The product description from TechCrunch's 2006 coverage was crystalline: "A service that enables its users to meet and chat when they visit the same websites."

That's it. No jargon. No enterprise pitch. Just: you're here, they're here, so talk.

What the First Version Looked Like

The early web in 2006 was technically brutal for this kind of idea. There was no:

• WebSockets (standardised only in 2011)
• Real-time database infrastructure (Firebase launched in 2012)
• Browser push notifications
• Reliable cross-site JavaScript injection (most sites would block it)

What Talkito likely had was a browser toolbar or plugin, the dominant mechanism for adding cross-site functionality in that era. You'd install the Talkito toolbar, it would detect which URL you were on, check a server for other active users on the same URL, and surface a chat interface.

This architecture was clunky by necessity. It required users to install something, a massive friction point compared to what's possible today with a simple piece of embedded JavaScript.

The Signal That Seemed to Validate It

The fact that Talkito got into YC at all, in 2006, with Paul Graham personally selecting companies, is itself validation. Graham was famously good at identifying ideas that were technically interesting and socially novel. Talkito was both. The concept was clear enough, the founder technical enough, and the vision bold enough to earn a spot in one of the most selective cohorts of that era.

The problem was not validation. The problem was the distance between "compelling idea" and "technically executable at scale in 2006."

The Pattern This Follows

Talkito fits a classic YC idea archetype that rarely gets discussed: the infrastructure-dependent idea. These are ideas that are clearly right but require platform capabilities (browser APIs, mobile hardware, real-time infrastructure, social graphs) that simply don't exist yet at the time of founding.

Other famous examples: General Magic (smartphones in 1990), Kozmo.com (instant delivery in 1999), Google Wave (real-time collaborative documents in 2009). All right ideas. All wrong timing. The difference between these and Talkito is that the later ones had more capital to survive long enough for the world to catch up, and some still didn't make it.

---

Lens 3, The Application Anatomy

What Getting Into YC in 2006 Actually Meant

The Summer 2006 YC batch was one of the earliest in the programme's history. The landscape was radically different from what applicants face today:

Getting in during this period was both harder (fewer spots, no playbook) and differently evaluated. Paul Graham was making highly personal bets on founders who impressed him technically and intellectually, not founders who had optimised their applications for YC's current evaluation criteria.

What Made Talkito's Application Work