Cited from real sources 6 min read Updated May 2026

A framework by Paul Graham

Paul Graham's Do Things That Don't Scale

Do Things That Don't Scale is Paul Graham's 2013 essay and the most-quoted piece of early-stage startup advice in Y Combinator's canon. The argument: startups do not take off by themselves. In the beginning you have to recruit users one by one, by hand, and do the unscalable, unglamorous work that delights them. The point is not the work itself. The point is what the manual work teaches you that an automated funnel never would.

What the essay actually solves

"The biggest problem that most startups have is they can't get users."

Not the architecture. Not the scalability. Founders optimize the thing that is not yet their problem.

YC partners on Paul Graham's essay Y Combinator Watch at 03:26

The framework

The startup that scaled itself never existed

A generation of founders absorbed the wrong lesson from Google. Google made scalability look like the whole game, technically and as a business model, and an industry of founders and investors started optimizing for it from day one. Graham's 2013 essay was the counter-argument. The thing that kills most early companies is not that they cannot scale. It is that nobody is using the product, and the founders are polishing architecture for a load that does not exist.

The reframe is to stop treating "it doesn't scale" as a disqualifier. In the beginning, the unscalable thing is usually the only thing that works. You recruit users one at a time. You do their setup for them. You go physically stand where they are. None of that survives contact with a million users, and that is fine, because you do not have a million users. You have ten, and ten is the problem to solve right now.

The canonical example is Airbnb. The founders had an idea, no users, and a flywheel that would not turn. So they went door to door in New York and took professional photos of hosts' apartments themselves. Photography is not a scalable feature of a marketplace. It was the unscalable act that made the early listings good enough that the marketplace started to move.

Do Things That Don't Scale is not a license to avoid building a real company. It is a sequencing claim: the manual, embarrassing work comes first because it is the fastest way to learn whether you are making something people want. Automation is a reward you earn after the learning, not a substitute for it.

How to apply it

How do you actually do things that don't scale?

Five moves, ordered. Each one is something a later-stage company would never let you do, which is exactly why it works now.

  1. 1

    Recruit your first users by hand.

    Startups do not take off on their own. Go find the first ten users individually: email them, message them, meet them. If you cannot name the next ten people who should use this, you do not have a distribution problem yet, you have a who-is-this-for problem.

  2. 2

    Do the unscalable work that delights them.

    Set the product up for them. Take the photos. Do the data entry. Airbnb's founders shot listing photography by hand because that was what made the listings good. Whatever the equivalent embarrassing manual task is for you, do it yourself before you automate it away.

  3. 3

    Take the work that feels beneath you.

    The manual outreach, the support tickets, the admin. Founders who delegate this early lose the one feed of raw signal that tells them what the product should become. The unglamorous work is where the insight is, not despite being unglamorous but because nobody else is paying that close attention.

  4. 4

    Optimize every interaction for learning.

    The point of doing it by hand is not heroics. It is that every manual setup, every support conversation, teaches you what to build next. Ask of each unscalable thing: what did this teach me that a dashboard would not have?

  5. 5

    Use the learnings to justify scaling, then stop.

    The unscalable phase ends. Once you understand the customer well enough to know what to automate, build the scalable version, and resist the trap of staying in lucrative manual work, like custom consulting, that quietly turns you into a service business instead of a startup.

The Airbnb guys would go out and do that, and that was clearly something that did not scale. That's what got them that flywheel turning early on.
YC partners on the Airbnb example Watch at 06:29

The photography did not survive into the scaled company. It did not need to. It existed to get the flywheel turning; once it was, the scaffold came down.

Boundary conditions

When it works, when it fails

Works best when

  • You are pre-traction with few or no users and need the flywheel to start turning
  • The product needs a human to make the early experience good enough
  • You can personally do the unscalable work and extract the learning from it
  • You treat the manual phase as temporary scaffolding, not the company

Fails when

  • You never exit the manual phase and ossify into a service business
  • The unscalable work drifts into custom consulting that cannot grow 10x
  • You delegate the manual work and lose the learning it was there to produce
  • You use it as an excuse to avoid building the real product at all
The biggest problem that most startups have is they can't get users and they're not making something people want.
YC partners on what Graham realized Watch at 03:26

The honest tension lives between the two columns. The same manual work that gets the flywheel turning becomes the thing that traps you if you never stop. YC pushes hard growth targets partly to force the question: can this grow 10x, or have you quietly built a consultancy that happens to have a login screen?

The receipts

Where YC breaks down Graham's essay

Useful? Pass it to a founder who is automating before anyone is using it.

Want the full playbook?

Get 329 execution & shipping frameworks.

49 frameworks 97 rules 175 heuristics & principles 7 operators

From Gretchen Rubin, Jake Knapp, BJ Fogg, and 4 more. Drop one .md into Claude, Cursor, or ChatGPT. Your AI cites practitioners, not guesses.

See the pack

Instant .md download · One-time purchase · No subscription

Related frameworks