Posterous, YC Founder Story

Company: Posterous Founders: Sachin Agarwal (CEO), Garry Tan, Brett Gibson YC Batch: Summer 2008 (S08) Industry: Blogging / Consumer Internet / Content Publishing Founded: May 2008 | Acquired: March 2012 by Twitter Peak Users: 15 million monthly unique visitors (2011) Total Funding: $10.1 million (Redpoint Ventures, Trinity Ventures, Jafco Ventures) Exit: Acqui-hire by Twitter (undisclosed; estimated $20, 30M)

---

---

The One-Line Summary

Three Stanford engineers built the world's simplest blogging platform, post anything just by sending an email, grew it to 15 million users, then watched it unravel the moment they stopped trusting simplicity. One founder went on to run Y Combinator. The story of Posterous is equal parts inspiration and cautionary tale.

---

Lens 1, The Before State

Who Were They Before YC?

Sachin Agarwal had one of the most enviable engineering pedigrees a startup founder could have in 2008. He had spent six years at Apple as the lead engineer on Final Cut Pro, the professional video editing software used by filmmakers worldwide. He wasn't a junior developer learning the ropes. He had shipped software that professional Hollywood editors depended on. He knew what polish looked like. He knew what "it just works" meant as a product philosophy.

Garry Tan had a different flavour of impressive. A Stanford Computer Systems Engineering graduate, he had been employee number ten at Palantir Technologies, at a time when nobody outside intelligence circles had heard of the company. He'd designed the Palantir logo, built early product teams, and was operating at the intersection of design and engineering before that intersection had a name. Before Palantir, he'd been grinding as a program manager at Microsoft, the kind of job that feels stable but slowly suffocates anyone with startup ambitions.

Brett Gibson completed the trio, also with a technical background, bringing engineering depth to the founding team.

These were not garage-hackers. These were people with real corporate careers, real salaries, and the kind of resume that could get them any job in Silicon Valley. The question was: why leave?

The Personal Pain They Were Living

Garry Tan was obsessed with a specific friction: he wanted to share things online, photos, thoughts, links, moments, and every existing tool made it harder than it should be. Blogging platforms required logins, web interfaces, formatting decisions. Photo platforms were siloed. Twitter had just launched and was limited to 140 characters.

The specific insight came from a simple personal frustration. Garry and Sachin had been friends since their Stanford days in 2000, they'd been in the same fraternity, and Sachin had got Garry into photography. They were constantly sharing photos, links, and updates with each other. But the process of getting content onto the internet was still unnecessarily complicated.

The question they kept returning to: what if publishing online was as easy as sending an email? Everyone already knew how to send email. Everyone had it on their phone. No login required. No interface to learn. Just, send it, and it appears online, formatted beautifully, cross-posted to all your social networks automatically.

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

In 2008, the YC stereotype was young, often college-dropout, hyper-technical hackers solving technical infrastructure problems. Sachin and Garry were mid-career professionals with Apple and Palantir on their CVs. They were building a consumer product, a blogging tool, in a space already occupied by WordPress, Blogger, and a scrappy upstart called Tumblr.

The YC application system had just opened. Nobody knew if consumer blogging tools were what YC wanted. The founders couldn't even know if their polished, corporate backgrounds would help or hurt them in a program that prized raw, scrappy building instincts.

What they had, though, was something underrated: they had tasted great product design at Apple and Palantir, and they had a visceral allergy to bad UX. That taste was their edge.

Key Insight for Aspiring Founders

Corporate experience is not the enemy of startup thinking, bad corporate habits are. Sachin's six years at Apple gave him a precision for user experience that most first-time founders take years to develop. The key is extracting the craft from the corporate environment and leaving the bureaucracy behind.

---

Lens 2, The Idea Origin

How the Idea Was Actually Born

The kernel of Posterous came from a specific shared experience between Garry and Sachin. They were both photographers. They took photos constantly, on trips, at events, in daily life. And getting those photos onto a blog, with any kind of decent formatting, with cross-posting to social networks, required too many steps.

The insight was deceptively simple: the bottleneck to publishing online isn't lack of ideas or content, it's the interface. Every blogging platform assumed you would sit down at a computer, log in, navigate a CMS, write in a text editor, attach files, format everything, and hit publish. But what if you were on a train? What if you'd just taken a photo at a concert and wanted it online in 30 seconds?

Email was already on every phone. Email handled attachments natively. Email had no learning curve. The idea: make the email itself the publishing interface.

Send a photo to post@posterous.com. That's it. The platform handles everything else, formatting, hosting, cross-posting to Twitter, Flickr, Facebook, and any other service you'd connected. The blog post appears automatically, looking clean and professional.

The First Version and What Made It Work

The first version was built fast and kept minimal. It did one thing: turned an email into a blog post. No dashboard. No settings to configure. No themes to choose. You sent an email and a blog appeared.

What made this sing was the zero onboarding experience. Most blogging platforms required 10, 15 steps before you'd published anything. Posterous required one action, one email, and a blog existed. By the time you'd hit send, your content was already live.

The platform's early tagline captured it perfectly: "Dead simple blogs by email." No jargon. No features list. Just the clearest possible statement of what it did and why it was different.

The Signal That Validated It

Posterous launched in May 2008 and immediately got TechCrunched, covered by TechCrunch early in its life, which drove a wave of signups. But the more meaningful signal was organic: developers and early adopters were emailing the founders to say they'd set up their blog in under two minutes. That time-to-value metric was the proof that the idea worked.

Y Combinator itself started using Posterous for the official YC blog. When your investors and mentors use your product without being asked, that's a signal nothing else can replicate.

The Pattern This Follows

Posterous follows the "remove the interface" idea archetype, a category that consistently produces breakthrough consumer products. Rather than adding features to an existing tool, the founders asked: what if the tool itself disappeared, and the action was just a natural human behaviour (sending an email)?

This same pattern later appeared in countless successful products: Superhuman (email as a superpower), Notion (documents as a universal interface), and others. The insight, that the interface is the friction, not the task, is one of the most reliable product ideas in consumer tech.

---

Lens 3, The Application Anatomy

What Made Their Application Work

Posterous applied to YC Summer 2008 with a proposition so clear it was almost impossible to misunderstand. Their core pitch was:

"Dead simple blogs by email. Send an email, get a blog. No setup required."

Every word was doing real work:

• "Dead simple", immediately signals they understand the problem with existing tools
• "By email", concrete mechanism, not vague "easy to use" marketing language
• "No setup required", the specific pain point of every other blogging platform

The one-liner was memorable, specific, and immediately created a mental demo in the reader's head. You could picture exactly what it meant to use Posterous before ever seeing the product.

What They Had at Application Time