Thinkature, YC Founder Story

Company: Thinkature Founder: Drew Harry YC Batch: Summer 2006 (S06), One of YC's earliest batches ever Industry: Collaboration SaaS / Online Whiteboard Founded: 2005, 2006 | Closed: December 19, 2010 Outcome: Shut Down (Permanently Closed) Founder's next chapter: PhD at MIT Media Lab → Research Scientist & VP of Data Science at Twitch

---

⚠️ Why a Failed Company Belongs in This Collection

Not every YC story ends at a billion-dollar valuation. Thinkature got accepted into one of YC's earliest ever batches, Summer 2006, when the program was only a year old and acceptance was arguably harder than it is today. The product was technically ahead of its time. The idea was directionally correct. And yet the company closed four years after launching. Understanding why is one of the most valuable things an aspiring founder can take into their YC application.

---

---

The One-Line Summary

Drew Harry built a real-time online whiteboard in 2006 that worked, got into YC, got press, got users, and still shut down four years later. The lesson isn't about the product. It's about building something people admire vs. building something people pay for.

---

Lens 1, The Before State

Who Was Drew Harry Before YC?

Drew Harry was a recent graduate of Olin College of Engineering, one of the most unconventional engineering schools in the United States. Olin, located in Needham, Massachusetts, was only a few years old when Drew attended. It had been founded with a single radical idea: that engineering education should be project-based, hands-on, and entrepreneurially oriented from day one. No traditional lecture-heavy curriculum. No departmental silos. Just builders, learning by building.

That environment shaped Drew directly. Olin students didn't just study computer science, they built things, tested them, broke them, and shipped them. By the time Drew finished his undergraduate degree, he'd already done research internships at IBM, Sun Microsystems, and Motorola. He was technically sharp, curious about human-computer interaction, and deeply interested in what it meant for people to collaborate online.

He was not a business person. He was a researcher who wanted to build something real.

The Personal Pain He Was Living

In the mid-2000s, remote collaboration was genuinely broken. If you wanted to brainstorm with a colleague in another city, your options were: email attachments back and forth, a phone call with no shared visual, or expensive enterprise video conferencing software that nobody outside a Fortune 500 company could afford.

Drew was living this frustration directly, both as an Olin student working on distributed projects and as someone fascinated by online community and communication research. The question he kept returning to was simple: why can't two people just think together on a shared surface, the way they would at a physical whiteboard?

In 2005, while the rest of the tech world was still figuring out Web 2.0, Drew started building the answer.

Why He Almost Didn't "Look Like" a YC Founder

By 2006, the YC stereotype was already forming: technical co-founder teams, usually from MIT or Stanford, building consumer internet products with obvious viral potential. Drew was a solo founder from a school most people in Silicon Valley hadn't heard of, building a free tool with no clear business model, targeting a use case (remote visual collaboration) that most people in 2006 didn't think they needed yet.

He wasn't polished. He wasn't fundraising-ready. He was a builder who genuinely believed in the problem, and that combination, in YC's earliest days, was exactly what Paul Graham was looking for.

Key Insight for Aspiring Founders

YC in its early years bet on people, not pitches. Drew Harry got into the S06 batch, one of the smallest and most selective in YC's history, not because he had a deck or a revenue model, but because he was clearly a strong technical founder who had identified a real problem and started building. In the absence of traction, conviction and capability are your application.

---

Lens 2, The Idea Origin

How the Idea Was Actually Born

The idea for Thinkature emerged from a combination of Drew's research background and a very direct observation: the tools people used to collaborate online in 2005 were designed for file transfer and messaging, not for thinking together.

Email was asynchronous. IM was too linear. Shared documents were clunky and didn't support visual thinking. And the whiteboard, the single most-used collaboration tool in any real office, had no credible online equivalent that normal people could access.

Drew's instinct was grounded in something real: people think differently when they can draw ideas, connect concepts visually, and move things around a shared space in real time. Text doesn't capture that. He wanted to build the digital equivalent of two people standing at a whiteboard with markers.

The First Version, Technically Impressive, Conceptually Ahead of Its Time

What Drew shipped was, for 2006, remarkable. Thinkature was built entirely in HTML and JavaScript, no Flash, no plugins, no downloads, and used a persistent HTTP connection for real-time synchronisation. This was before WebSockets were a standard. Before Google Docs had real-time co-editing. Before Figma, before Miro, before any of the collaboration tools that today's founders take for granted.

Users could:

• Place images and text in shared workspaces
• Connect boxes visually with lines
• Chat in real time alongside the canvas
• Invite anyone to a shared board with a link

The product launched formally in October 2006. TechCrunch covered it. The comparison was to ConceptShare, a well-funded competitor, and Thinkature, despite taking a fraction of the funding, held its own in the review.

The Signal That It Was Working, Sort Of

Users liked it. They genuinely liked it. The product worked, it was free, it was simple, and it did something that nothing else at the time did quite so cleanly. Word spread within design and tech communities. The waitlist grew.

But here is the problem with that signal: people liking a free product tells you almost nothing about whether they'll pay for it. Thinkature had enthusiastic users. It did not have a path to revenue.

The Pattern This Follows, And Why It's a Warning

Thinkature fits a painful but common YC archetype: the correct idea at the wrong moment, with the wrong monetisation strategy. The problem Drew identified in 2006, that remote collaboration needed a visual, real-time shared canvas, was 100% correct. Miro (founded 2011, valued at $17.5B by 2022) and Figma (founded 2012, acquired by Adobe for $20B) both proved that. Drew was just five years too early, and he launched as free when he should have been testing willingness to pay from day one.

---

Lens 3, The Application Anatomy

What Made Their Application Work

Thinkature applied to YC Summer 2006, the second batch in YC's history. At that point, YC had funded fewer than 20 companies total. The bar was different. Paul Graham was looking for smart, technical hackers who had identified real problems and started building, not polished fundraisers with five-year projections.

Drew's application worked because:

1. The demo was real. Thinkature was already working when Drew applied. In YC's earliest days, having a live, functional product was itself exceptional.