·Business & Strategy
Section 1
The Core Idea
Paul Graham published "Do Things That Don't
Scale" in July 2013, and it became the most cited essay in Y Combinator's history. The thesis is deceptively simple: the best startups are built through deliberate, labour-intensive, unscalable acts of founder effort — recruiting users one at a time, providing concierge-level service, doing things by hand that will eventually need automation. The activities that create great companies are precisely the ones that cannot sustain great companies. That paradox is the entire point.
The essay opens with a line that reframes how most people think about startup growth: "Actually startups take off because the founders make them take off." Not because the market was ready. Not because the product went viral. Because the founders, personally and manually, forced the first growth to happen.
Airbnb is Graham's centrepiece example. In early 2009, the company was generating roughly $200 per week. The product existed. Nobody cared. Graham told founders Brian Chesky and Joe Gebbia to fly to New York — their densest market — and meet every host in person. They went door to door. They photographed apartments with a rented DSLR because the listing photos were terrible. They rewrote listing descriptions by hand. They sat in hosts' kitchens asking what would make the experience perfect and then built those things, one feature at a time. Revenue went from $200 per week to $400, then to $4,000. The growth curve changed shape entirely — not because of a product launch or a press hit, but because two founders did the most unscalable thing possible: they made each individual user feel like the only customer in the world.
Stripe ran an equally unscalable playbook from a different angle. Patrick and John Collison didn't wait for developers to sign up. They went to YC Demo Days and startup meetups, found developers complaining about payment integration, and said "give me your laptop." They installed Stripe's API on the spot — seven lines of code, working payments in minutes. What became known as "the Collison installation" was absurd from an efficiency standpoint. Two cofounders of a payment company doing individual technical integrations, one developer at a time. But each installation created a convert. Those first developers didn't just use Stripe. They evangelised it on Hacker News, on Twitter, in every conversation where another developer mentioned payment friction. By the time competitors improved their developer experience, Stripe had thousands of companies embedded — locked in not by contracts but by genuine devotion.
DoorDash took the principle to its literal extreme. Tony Xu, Stanley Tang, Andy Fang, and Evan Moore — Stanford MBA students — launched their food delivery service in January 2013 with a simple landing page called PaloAltoDelivery.com. For the first six months, the founders personally delivered every order. They drove to restaurants, picked up the food, and brought it to customers' doors. The operational absurdity was the point. By delivering food themselves, they learned which restaurants were slow, which packaging leaked, which neighbourhoods tipped well, and which delivery routes were fastest. That granular understanding — impossible to acquire from a dashboard — became the foundation for the logistics algorithms that eventually powered a $70 billion company.
Wufoo, the online form builder acquired by SurveyMonkey in 2011 for a reported $35 million, sent handwritten thank-you notes to every new user. Not automated emails styled to look personal. Actual handwritten notes, on physical stationery, mailed through the postal service. Co-founder Kevin Hale described the practice as deliberately unscalable — the team could only write so many per day. But the effect on user loyalty was disproportionate. In a world of automated onboarding flows, a handwritten note signalled something automated systems never can: that a human being noticed you and cared.
The underlying paradox cuts against every instinct of efficient management. Founders are told to build systems, automate processes, create leverage. Graham's essay says the opposite: at the earliest stage, systems are the enemy. Systems abstract away the very contact with users that generates the insights you need. When you personally photograph an apartment, you notice the lighting is bad and the description undersells the space. When you personally install your API, you learn which error messages confuse people. When you personally deliver the food, you discover the restaurant takes 45 minutes to prepare a 15-minute order. No analytics dashboard captures that texture. No user survey generates that depth.
The "don't scale" principle is really a sequencing argument. It doesn't say never scale. It says earn the right to scale by first doing things that give you unfair knowledge of your customers, your product gaps, and your market reality. Scale from understanding, not from assumption.
The essay's influence extends well beyond Silicon Valley. Y Combinator has funded over 4,000 companies since 2005, and "do things that don't scale" is the single most-referenced piece of advice in partner office hours. Jessica Livingston, YC co-founder, once estimated that the majority of YC's biggest successes — Airbnb, Stripe, DoorDash, Coinbase — had a distinct phase where the founders did something manually that seemed irrational from an efficiency standpoint but proved essential for product development. The irrationality is the feature. Rational operators optimise for throughput. Founders doing unscalable things optimise for understanding.
