Paul Graham's Leadership Lessons for Startups

Turn this article into takeaways for your work.

Each assistant summarizes the article only for you and suggests best practices for your work.

Key Facts: Paul Graham (born November 13, 1964) trained as a philosopher and a painter before a programmer, earning a 1986 philosophy degree from Cornell and a computer science PhD from Harvard in 1990, with detours studying painting at RISD and the Accademia di Belle Arti in Florence. In July 1995 he founded Viaweb with Robert Morris and Trevor Blackwell, a web based tool that let ordinary merchants build online stores, and Yahoo bought it in 1998 for 455,000 shares of Yahoo stock, worth roughly $49 million at the time, folding it into what became Yahoo Store. Rather than start a second company, Graham spent the years after writing: On Lisp (1994), ANSI Common Lisp (1996), and the essay collection Hackers and Painters (2004). In March 2005 he founded Y Combinator with Jessica Livingston, Robert Morris, and Trevor Blackwell, running it hands on until February 2014, when he stepped back and appointed Sam Altman president. He hasn't returned to a day to day role there since. He does still write, and his September 2024 essay "Founder Mode," prompted by a talk Brian Chesky gave about running Airbnb through its 2020 crisis, drew more than 20 million views on Twitter within days and reopened a leadership debate he had effectively started from nothing.

Paul Graham gets filed under startup gurus, the guy who wrote "Do Things That Don't Scale" and funded your favorite unicorn's seed round. That undersells what he actually built. Graham ran one company for three years, then spent two decades doing something structurally unusual: shaping how thousands of founders operate without personally managing more than a handful at a time, mostly through a program he designed once and essays he published for free. Y Combinator's real invention was not spotting better founders than other investors. It was standardizing the deal (an identical cash-for-equity offer to every company in a batch), standardizing the calendar around a fixed batch and demo day, and distributing the actual philosophy through essays a founder applying in 2005 and one applying in 2025 could read in the same afternoon. That is a genuinely different model of leadership than most business writing describes, and it is worth taking seriously precisely because it never looked like leadership in the conventional sense.

The contrast sharpens next to how other well known investors built their firms. Marc Andreessen and Ben Horowitz built Andreessen Horowitz on close to the opposite bet: write much larger checks into far fewer companies, and staff an in-house team to work each one closely. Eric Ries tried to turn startup building into a repeatable, almost scientific process, a formal build measure learn loop any team could run regardless of who was in the room. Graham's YC did neither. It ran hundreds of companies a year through a deliberately thin, identical structure and let a shared body of essays carry the philosophy, on the theory that manual, founder to founder advice mattered more than bigger checks or a formal process could replace.

The Written Institution Doctrine

The Written Institution Doctrine is Graham's operating premise that a leader can shape the behavior of people they will never personally manage by designing the structure those people operate inside and publishing, in plain language, the reasoning behind it. Most of what gets called "Paul Graham's leadership style" is really a description of Y Combinator's architecture: a standardized batch, an identical deal, a fixed demo day, and a library of essays that functions as onboarding material for founders he will meet only a few times, if at all. The essays were never a marketing layer bolted onto the accelerator. They were the mechanism through which his judgment reached the founders he could not personally coach, which was most of them. He explained his reason for writing them years before Y Combinator existed: "An essay is something you write to try to figure something out," he wrote in 2004, adding, "In a real essay you're writing for yourself." Leadership, for Graham, ran through the same habit: think in public, publish the result, and let the writing manage what a growing organization would otherwise require him to do in person.

Leadership Style Breakdown

Style Weight How it showed up
Institution Architect 45% Designed Y Combinator's structure rather than its individual deals: an identical, non-negotiated cash-for-equity offer for every company in a batch, a fixed cohort, and a single demo day replacing hundreds of one-off pitch meetings. The structure did the standardizing so Graham didn't have to repeat the same advice company by company.
Essayist at Scale 35% Used published essays, "Do Things That Don't Scale," "Maker's Schedule, Manager's Schedule," "How to Start a Startup," and later "Founder Mode," as the actual delivery mechanism for his philosophy. Founders who never got one-on-one time with Graham still absorbed his views because the essays were free, searchable, and widely shared.
Pattern-Matching Selector 20% YC's core recurring act was the interview: deciding, in roughly ten minutes, which founders to fund. Graham studied his own selection process on video to isolate what he called "negative predictors," and has been candid that it carries real, admitted bias, a point covered in its own section below.

The 45/35/20 split matters because the second style is what let the first work at scale. A standardized batch deal only functions as a leadership tool if founders actually understand and buy into the philosophy behind it, and Graham supplied that understanding through writing rather than repeated persuasion. The selection function is smaller by weight but sits underneath both of the others, since an institution and a body of essays only matter if the right founders are in the room to receive them.

Key Leadership Traits

Trait Rating What it means in practice
Designing structure instead of managing people Very High Y Combinator's standardized deal and fixed batch calendar meant Graham never had to individually negotiate or mentor most founders who passed through it. The structure carried a large share of what a hands-on manager would otherwise do in person.
Writing as a leadership mechanism Exceptional Essays like Do Things That Don't Scale and Founder Mode reached far more founders than Graham could ever advise directly, with more precision than management telephone through intermediate staff would allow.
Willingness to hand off day-to-day control High He stepped back from running Y Combinator in February 2014 and appointed Sam Altman president, a genuine exit from daily operating authority, not a title change with the same responsibilities attached.
Founder pattern-matching intuition Uneven Unusually candid that his own snap judgments carry real bias, including a documented admission that he can be "tricked by anyone who looks like Mark Zuckerberg." The candor is a strength. The underlying bias is the weakness, examined below.
Generalizing personal experience into universal advice Double-Edged Nearly every widely quoted Graham essay draws on Viaweb and the first YC batches, a narrow slice of consumer and developer software startups. Genuinely useful advice for that slice, and advice critics say gets misapplied well outside it.

The 3 Decisions That Defined Paul Graham as a Leader

1. Writing Up Viaweb Instead of Chasing a Second Company (1995 to 2004)

Graham built one company, Viaweb, from July 1995 until Yahoo bought it in 1998 for 455,000 shares of Yahoo stock, worth roughly $49 million at the time. Plenty of founders with an exit that size go straight into a second startup while the operating muscle is still warm. Graham didn't. He spent the years afterward writing: essays on programming and startups, the technical books On Lisp (1994) and ANSI Common Lisp (1996), and eventually Hackers and Painters (2004), an essay collection arguing programming was closer to a craft like painting than to pure engineering.

That choice is easy to read as a founder cashing out and indulging a side interest. It reads differently once you see what it built. In March 2005, Graham gave the Harvard undergraduate computer club a talk that became the essay "How to Start a Startup." By his own account, walking home from dinner that same evening he decided to turn the angel investing he had meant to do for seven years into an actual fund, and within days he had recruited Robert Morris and Trevor Blackwell to put in money alongside his own, $200,000 in total. The essays weren't preparation for a second startup. They were the credibility that let a single talk turn into an institution days later.

For you: the years right after an exit are usually spent chasing the next operating win. Graham spent that time writing down what the first one taught him instead, in public, for anyone to read. That's a bet that ideas are worth more distributed widely than protected as a private edge, and it only pays off if the writing is good enough that people come looking for you because of it.

2. Standardizing the Batch: Founding Y Combinator on an Identical Deal for Every Startup (March 2005)

Graham, Jessica Livingston, Robert Morris, and Trevor Blackwell founded Y Combinator with the explicit intent to standardize seed funding, not just to pick good startups. Graham later wrote plainly what the goal was: "We were going to do seed funding with standardized terms," at a time when, in his words, "seed funding was very haphazard," with terms negotiated deal by deal and often botched by investors, founders, and lawyers alike. YC's first batch, funded that summer in Cambridge, Massachusetts, ran on that different premise: every company got the same structure and the same short runway, with none negotiating a bespoke arrangement. Reddit's founders were accepted into that first class after pitching Graham a different, unsuccessful idea first. Two years later, Drew Houston brought Dropbox through the same standardized structure in the Summer 2007 batch, proof the identical deal worked as well for a file-syncing tool as it had for a link-sharing site.

The standardization was the actual leadership decision, not a footnote to it. A bespoke deal for every company means the person running the fund has to personally understand and manage each relationship individually, which caps how many companies any one person can meaningfully oversee. An identical deal removes that constraint, letting Graham build something that could run at population scale because the terms themselves never required his personal negotiation. Peter Thiel later joined YC as a visiting partner from 2015 to 2017, and Thiel's own investing philosophy in Zero to One, that defensible businesses come from finding a monopoly rather than out-competing on speed, sits in real tension with the volume-and-standardization model Graham had already built YC around a decade earlier. Both approaches have produced enormous outcomes. They rest on opposite theories of where value comes from.

What this shows: a leadership model built to reach many people at once usually has to give up the customization a leader would otherwise use to demonstrate personal attention. Graham traded bespoke deals for standardized ones and made up the difference in essays, correctly betting that consistency of structure would matter more than the appearance of individualized care.

3. Stepping Back From Y Combinator in 2014, Then Reshaping It Again a Decade Later With an Essay

In February 2014, Graham appointed Sam Altman president of Y Combinator and stepped back from its daily operations, a genuine handoff rather than a symbolic one. Altman ran YC through 2019, Geoff Ralston succeeded him, and Garry Tan has led it since January 2023. Graham did not stay on as a shadow decision-maker. He left the operating chair to others entirely and kept writing essays from the outside, eventually relocating to England.

That would be a tidy story of a founder handing off cleanly, except for what happened in September 2024. Brian Chesky gave a talk at a YC event about how he had reformed Airbnb's management approach during its 2020 crisis, moving away from the "hire good people and give them room to do their jobs" advice he'd been given toward a more hands-on, Steve Jobs style model. Graham was in the room, and about a week later he published "Founder Mode," an essay arguing conventional advice to delegate through a professional management layer often actively damages the companies that follow it. He wrote plainly: "You tell your direct reports what to do, and it's up to them to figure out how. But you don't get involved in the details of what they do. That would be micromanaging them, which is bad." The essay reopened, a decade after he had formally stepped back, the exact question of how deeply a leader should stay involved in the details of what they built. He was no longer YC's president. He was still shaping what a generation of founders believed leadership should look like.

For you: stepping back from an operating role is not the same as stepping back from influence, and pretending otherwise underrates how much a well timed piece of writing can still move an organization you no longer run day to day. Graham's clean 2014 handoff and his 2024 essay are not in conflict. They're the same doctrine applied twice, first to an institution, then to an idea.

What Paul Graham Would Do in Your Role

If you're a founder or a very small team, Graham's advice starts from the essay that made "Do Things That Don't Scale" a cliche for a reason: recruit your first users manually, one at a time, the way Stripe's Patrick Collison personally installed the product on early users' laptops rather than waiting for self-serve signups. As Graham put it: "You can't wait for users to come to you. You have to go out and get them." The unscalable work isn't a phase to rush past. It's how you learn what the product should become before you can afford to advertise your way past not knowing.

If you're a manager trying to scale advice across people you can't personally coach one on one, Graham's model is to write the reasoning down in public rather than repeat it in private meetings. A standardized process paired with a clearly explained rationale reaches more people, more consistently, than the same advice delivered informally each time. The essays weren't a nice-to-have alongside YC's structure. They were how the structure's logic traveled.

If you're an executive who just inherited someone else's operating playbook, sit with Graham's maker's schedule essay: "You can't write or program well in units of an hour," and "when you're operating on the maker's schedule, meetings are a disaster." Before adopting a predecessor's calendar wholesale, ask whether the people doing the work are on a manager's schedule or a maker's one. The two need genuinely incompatible structures, not just different levels of discipline.

Situation you're facing Graham's likely move
You have a handful of early users and no marketing budget Recruit the next hundred manually yourself, in person if you can, rather than waiting for inbound interest
You need the same advice to reach hundreds of people you can't individually coach Write the reasoning down once, publish it, and let the structure plus the writing do the repeating
You've just been handed a team that mixes makers and managers Split the calendar by schedule type before assuming everyone should run on the same one
You've built something that runs without your daily involvement Step back from the operating chair fully rather than staying as an informal shadow decision-maker
You still see the organization drifting from what you believe in, years after stepping back Publish your reasoning again. Influence through writing doesn't expire when your title does

Notable Quotes & Lessons Beyond the Boardroom

On why manual, unscalable effort matters more than most founders assume: "Actually startups take off because the founders make them take off," Graham wrote in 2013. His follow-on line is the one that separates good advice from generic advice: "It's not the product that should be insanely great, but the experience of being your user." That distinction usually decides whether a startup gets a second chance with its early customers.

On what a startup actually needs, from the 2005 talk that helped set Y Combinator in motion: "You need three things to create a successful startup: to start with good people, to make something customers actually want, and to spend as little money as possible," and, more bluntly, "Good people can fix bad ideas, but good ideas can't save bad people."

On founder mode, the line that made the September 2024 essay spread describes what professional managers are taught: "You tell your direct reports what to do, and it's up to them to figure out how," which Graham argued is exactly backward for founders. Worth reading closely is his own footnote to that essay, written the same month: "Founders who are unable to delegate even things they should will use founder mode as the excuse." He anticipated the criticism below before most of his critics wrote it.

Early in Airbnb's life, Graham advised Brian Chesky that it's better to have 100 people who love your product than a million who like it, advice Chesky has credited as shaping Airbnb's earliest growth. Same "Do Things That Don't Scale" logic, delivered founder to founder almost two decades before the essay that made it famous.

Where This Style Breaks

Founder Mode is the clearest place to see the doctrine strain, largely because Graham himself flagged the risk before the critics did. His own footnote warned: "Founders who are unable to delegate even things they should will use founder mode as the excuse," close to exactly what happened. According to Wikipedia's account of the essay's reception, critics called a one-size-fits-all leadership prescription a "futile task," and pointed to successful non-founder or delegation-heavy CEOs, Tim Cook at Apple and Satya Nadella at Microsoft among them, as evidence that manager mode works fine at enormous scale when it's done well. Writer Joe Procopio went further, calling founder mode "not new" and "not rocket science," and the binary framing "basically another misguided attempt to break down leadership into two binary personas." Chesky himself later acknowledged a gap in how the idea landed, stating publicly: "Women founders have been reaching out to me... about how they don't have permission to run their companies in Founder Mode the same way men can." He called for that to change. A Harvard Business Review study of successful founder and non-founder CEOs that followed the essay concluded that durable leaders end up needing both modes, a more careful claim than the essay's own framing tends to get credited with.

The selection process underneath the whole institution has its own, separately documented bias. In a 2013 New York Times Magazine profile, reported by Bloomberg, Graham reviewed his own interview footage looking for what he called negative predictors and admitted plainly: "I can be tricked by anyone who looks like Mark Zuckerberg. There was a guy once who we funded who was terrible. I said: 'How could he be bad? He looks like Zuckerberg!'" That's an unusual level of candor for an investor to put on the record. It's also a direct admission that the pattern-matching underneath a fund built to reach thousands of founders does not, in fact, treat all of them the same, which cuts against the fairness implied by an identical, standardized deal.

Graham's January 2016 essay on economic inequality drew a different kind of pushback, less about founder selection and more about how he frames outcomes. He wrote: "Eliminating great variations in wealth would mean eliminating startups." NFL lineman Russell Okung publicly challenged him, writing that "economic inequality isn't the symptom, it's the virus that attacks," and asking directly: "What happened to your first love?" Graham responded that he didn't think they actually disagreed about much and that Okung "just doesn't seem to have read what I wrote very carefully," a reply that illustrates a pattern worth naming: writing as a leadership mechanism works well on readers already inclined to follow the argument, and works far worse on people who start from a different premise about what the problem even is.

Underneath all three critiques sits the same structural issue. Nearly every widely quoted Graham essay draws its evidence from Viaweb and YC's own portfolio, venture-backed, consumer or developer facing software startups founded mostly by people who look a great deal like Graham did at 30. Advice tuned that tightly to one kind of company travels less well than its popularity suggests, and the fact that its author has been more candid about that limitation than most of his imitators is a point in his favor. It doesn't make the limitation disappear.

Learn More

About the author

Victor Hoang

Victor Hoang

Co-Founder, Rework.com

Victor Hoang is Co-Founder and CMO of Rework. He spent 12+ years scaling B2B SaaS growth, building a lead engine that generated over 1 million leads and $10M+ in annual recurring revenue. Today he builds AI agents and MCP servers into Rework's products to empower customers across growth and operations. He writes about what actually works.