Disqus, YC Founder Story

Company: Disqus Founders: Daniel Ha (CEO) & Jason Yan (CTO) YC Batch: Summer 2007 Industry: Developer Tools / Community Infrastructure / Audience Engagement Founded: October 30, 2007 Total Funding Raised: $11.5 Million Acquired: December 2017 by Zeta Global (~$90 Million) Scale at Acquisition: 4 million websites, 2 billion monthly unique users, 17 billion page views/month

---

---

The One-Line Summary

Two college friends, bored in computer science classes and building side projects for fun, accidentally created the internet's default comment system, not by chasing a big idea, but by following the one small feature that people actually showed up to use.

---

Lens 1, The Before State

Who Were They Before YC?

Daniel Ha was born in Anchorage, Alaska and grew up in the Bay Area. By the time he and his high school friend Jason Yan were undergraduates at the University of California, Davis, they were exactly the kind of students who were academically capable but creatively restless. Daniel studied computer engineering. Jason studied computer science. They were technically strong but institutionally under-stimulated.

In Daniel's own words: "We were really bored in school. A lot of the science classes were already done for us. So we did a lot of unrelated things before we finished school."

This is not a story of two brilliant visionaries with a master plan. It's a story of two friends who knew how to build things, had too much free time, and kept finding reasons to make something together. Over the years they hacked on a series of micro-projects, small experiments, throwaway tools, weekend builds, none of which turned into a business, but all of which sharpened their instincts for what people actually needed online.

Daniel and Jason had known each other since 7th grade. They'd lost touch through high school, then reconnected at UC Davis. There's something important in that: their co-founder relationship was built on nearly a decade of real friendship before it was ever a professional one. That trust would become the quiet structural advantage of everything they built.

The Personal Pain They Were Living

It was the end of 2006. The blogosphere was at its cultural peak, millions of people publishing daily, comment sections becoming genuine communities. But the tools powering those conversations were, in Daniel's words, "terrible."

Existing comment systems were clunky, isolated, and felt like leftovers from early 2000s forum software. Every blog had its own silo. Commenters couldn't carry identity, reputation, or history from one site to another. There was no network, just a million separate boxes, each disconnected from the next.

Daniel and Jason started working on discussion tools and community infrastructure, "forums, group discussion, and community building", not because they had a genius thesis about the future of the internet, but because discussion was the domain they lived in and thought about most. The blog comment feature was just one piece of a larger project. And then something unexpected happened: it was the only piece people cared about.

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

Daniel and Jason had no prior exit. No famous connections. No industry experience. They were undergraduates at UC Davis, not Stanford, not MIT. They weren't dropout geniuses with a contrarian thesis about payments or AI. They were two normal CS students who liked building things together and happened to spot a gap in a space nobody else was taking seriously: comment infrastructure.

In a YC batch full of bigger, bolder ideas, two guys who wanted to fix blog comments could have easily been overlooked. What saved them wasn't pedigree, it was a working product and the nerve to demo it live, on a real VC's blog, in front of a room full of investors.

Key Insight for Aspiring Founders

Sometimes the idea finds you inside a bigger project you're already building. Don't kill your side features, monitor them. The one people actually use is the one worth betting on.

---

Lens 2, The Idea Origin

How the Idea Actually Emerged

In late 2006, Daniel and Jason decided to spend their winter building something together. They wanted to work on online communities, forums, discussion platforms, tools for group conversations. It was a broad, loosely defined ambition.

The first version of the product was a forum that could be embedded into a blog. Not a commenting widget. A whole forum, the next-generation bulletin board, connected to social content. They believed deeply in the idea of communities forming around content.

Then something happened: the blog comment piece of that forum kept getting attention. Their earliest testers weren't using the forum features, they were using the comment thread. They were sharing it. Asking for more of it. The full forum idea was theoretically interesting. The comment embed was immediately useful.

This is a classic "follow the signal" story. The founders had a bigger vision, and the market told them which part of that vision it actually wanted. Disqus wasn't born as a product insight. It was born as an act of listening.

Daniel later described it: "Today's Disqus evolved from this as the blog feature of our project became popular amongst our earliest testers."

The First Ugly Version

The first iteration was simple to the point of being humble: a JavaScript widget that replaced the default comment box on a WordPress or Typepad blog. That was it. No analytics. No spam filtering. No network features. Just a cleaner, faster, more modern comment thread that a blogger could install in minutes.

There was no revenue model. No business plan. No moat. Just a small, working piece of infrastructure that solved an embarrassingly mundane problem: the comment box on most blogs was genuinely bad, and nobody had bothered to fix it properly.

The Signal That Validated Everything

The validation came from behavior, not surveys. People installed Disqus and didn't uninstall it. Bloggers who added it told other bloggers. The feedback wasn't lukewarm, early adopters were enthusiastic in the specific way that comes from relief, not just satisfaction.

Then came the moment that crystallised the real insight: a commenter on one blog realised they could use the same Disqus profile on a different blog. The same identity, the same history, the same reputation, portable across the internet. That wasn't just a feature. That was a network. And Daniel Ha hadn't fully understood it yet himself.

The Pattern This Follows

Disqus is a textbook example of infrastructure hidden inside a UX problem. The surface complaint was "comment systems are ugly." The real opportunity was "there is no social layer connecting readers across the open web." The founders solved the UX problem first, which was the right order. The infrastructure insight came later, and it became the entire thesis for the business.

---

Lens 3, The Application Anatomy

What Their Application Looked Like

Daniel and Jason applied to YC Summer 2007 as undergraduates at UC Davis, with a working prototype and no users beyond their earliest testers. They were first-time founders, no prior exits, no industry credentials, exactly the profile that most aspiring YC applicants think disqualifies them.

What they had was a clear, demonstrable answer to a real problem. The comment systems bundled with WordPress and Typepad were widely known to be bad. Anyone who ran a blog had experienced the frustration. The problem didn't need to be explained or justified. It was universally felt.

Their pitch was essentially: "Comment systems are broken. Here is a better one. You can install it in minutes."