Paul Graham Essays: The 6 Ideas Every Founder Should Know

In our reading, Paul Graham's essays for founders keep returning to six ideas: make something a small group of people badly want, do unscalable things to win your first users, know whether you are default alive, notice ideas instead of brainstorming them, become ramen profitable, and avoid a familiar list of fatal mistakes. All of them are free on paulgraham.com.

Below, each idea in plain English, the essay and date it comes from, and one practical way to apply it, so you know what to look for when you read the originals in full.

Plenty of founders have read Graham. Far fewer have done what the essays say.

Why Paul Graham's essays still matter in 2026

Graham started publishing essays on his website in 2001 and co-founded Y Combinator in 2005 with Jessica Livingston, Robert Morris and Trevor Blackwell. Most of the startup essays founders cite were written between 2005 and 2015, long before AI coding tools and remote-first teams.

The examples have aged. The ideas have held up better, in our view, because they are about behavior: what makes a customer care, why founders fool themselves, and how companies run out of money. His essay index now lists more than 200 pieces, so knowing the six recurring themes helps you read them as one body of thought rather than a pile of unrelated posts.

For aspiring and first-time founders, these ideas cover much of the curriculum of the earliest stage. 1752vc's Launchpad is a 12-week, self-paced, remote sprint that takes aspiring founders from -1 to 1, which is the same ground these essays cover: validating an idea, finding a first customer and building a path to traction.

The six ideas in Paul Graham's essays, explained

Idea 1: Make something people want

Where it comes from. Y Combinator's motto, "Make something people want," which Graham traces back to YC's first months in Be Good (April 2008). It is also the frame for The 18 Mistakes That Kill Startups (October 2006), where every mistake on the list is treated as one route to the same failure: building something users do not want.

The idea in plain English. At the start, the question that counts most is whether a specific group of people want what you are building enough to use it, tell others and eventually pay. Branding, fundraising, hiring and press all come later.

The common failure, as we see it, is breadth, not badness. A product that is mildly interesting to lots of people loses to one that is essential to a few. It's the same line we draw between a vitamin and a painkiller.

How to apply it. Define your "few" precisely: not "small businesses" but "solo accountants who file more than 200 returns a year." Then track whether that group comes back without reminders. Retention of your core users is, in our view, the most honest scoreboard you have.

Idea 2: Do things that don't scale

Where it comes from. Do Things that Don't Scale (July 2013). The phrase is Graham's.

The idea in plain English. Your first users will rarely find you. You usually have to go and get them, one at a time, and look after them in ways that would be absurd at a thousand customers. We wouldn't rush through that manual work. It is often how you learn what the product actually needs, and how you earn users loyal enough to recommend you.

The essay's best-known example is Stripe's founders installing the product for new users in person instead of sending a link. Our guide to doing things that don't scale collects more examples and when to stop.

How to apply it. Set a weekly quota for direct outreach and personal onboarding, and keep it for months, not days. 1752vc's GTM Accelerator, a 12-week remote program for founders with early traction, builds the same selling muscle, and our guide to sales for technical founders covers the tactics.

Idea 3: Default alive or default dead

Where it comes from. Default Alive or Default Dead? (October 2015). Graham coined the terms.

The idea in plain English. Hold expenses flat, assume revenue keeps growing at its recent rate, and ask one question: does the company reach profitability before the cash runs out? If yes, you are default alive. If not, you are default dead, and your survival depends on someone else agreeing to fund you.

The danger isn't the answer. It's not knowing it. Founders who haven't done the math tend to assume the next round will be easy. The essay argues that the most common way a funded startup makes itself default dead is hiring ahead of growth, often as a substitute for the harder fix, which is making the product more appealing.

How to apply it. A simple model with current cash, monthly net burn and monthly revenue growth, projected forward, shows whether revenue crosses expenses before cash hits zero. The essay links to a calculator by Trevor Blackwell for a quick check, and our default alive or default dead guide works the formula month by month.

If you run out before you get there and are counting on the next round, you are default dead. It may be worth acting like it: hold headcount flat and put the time into growth through unscalable effort and product work. Our guide on startup burn rate and runway covers the planning.

Idea 4: How to get startup ideas

Where it comes from. How to Get Startup Ideas (November 2012).

The idea in plain English. Graham's advice is to stop brainstorming and start noticing. The strongest ideas usually come from a problem you have hit yourself, ideally in a field where you work close enough to the frontier to see what is missing. Ideas produced on a whiteboard tend to sound plausible and solve problems nobody has.

We'd put it even more simply: find problems, not ideas. An idea that looks a little odd but removes real pain for a specific group is often the better bet.

How to apply it. Keep a running list of annoyances you have tried to fix with a workaround. Rank them by how many people share the problem and how costly the workaround is, and test the top one before building. Our validation guide gives a four week process.

Idea 5: Ramen profitable

Where it comes from. Ramen Profitable (July 2009), which named the milestone.

The idea in plain English. Ramen profitable means revenue that covers the founders' basic living costs, nothing more. The company is still small, but a failed fundraise can no longer kill it.

That changes a lot. You negotiate with investors from a position where walking away is possible, you have proof that someone will pay and that you run lean, and the team stops living under a deadline. You can still raise. You just no longer have to raise or shut down.

How to apply it. Calculate the monthly revenue that covers founder living costs and essential tools. As an illustrative example, two founders who each need $4,000 a month plus $1,000 in software need about $9,000 a month in revenue; your number depends on where you live. It makes a sensible first revenue target before any vanity milestone. Reaching it can also strengthen your case with investors and with programs such as 1752vc's Accelerate, the flagship program for early-stage startups ready to grow, which includes a $100K investment (at a valuation cap of up to $3.5M).

Idea 6: The predictable mistakes

Where it comes from. The 18 Mistakes That Kill Startups (October 2006).

The idea in plain English. The mistakes that kill startups are ordinary, which is why they are worth a checklist. We group the essay's 18 into four kinds:

Team: going it alone, fighting between founders, hiring weak engineers, half-hearted effort.
Idea and product: copying an existing idea, retreating to a marginal niche to avoid competition, having no specific user in mind, obstinacy, choosing the wrong platform, sacrificing users for supposed profit.
Execution: launching too slowly or too early, choosing a bad location, not wanting to get your hands dirty.
Money: raising too little or too much, spending too much, managing investors poorly.

Most of them come back to Idea 1. The company didn't build something people want, usually because it didn't try hard enough to find out.

How to apply it. Use the list as a quarterly self-audit. For each item, write one sentence on whether you are making that mistake now. If your honest reply is "sort of," we'd count it as a yes.

A suggested reading order for Paul Graham's essays

Read one essay a week in this order and write a paragraph after each on what you will change. If you want longer reads alongside them, our list of books for startup founders suggests ten.

How to Get Startup Ideas (2012). Start here even if you already have an idea; it's a good test of whether the idea is real.
Do Things that Don't Scale (2013). Read before your first launch.
Startup = Growth (2012). Read before you set goals. Its benchmark for a good growth rate during YC is 5 to 7 percent a week, with 10 percent exceptional.
Default Alive or Default Dead? (2015). Read before you raise or the week after you close.
Ramen Profitable (2009). Read alongside your first financial model.
The 18 Mistakes That Kill Startups (2006). Read at the end of your first quarter and again after your first year.
Relentlessly Resourceful (2009) and What Startups Are Really Like (2009). Read when you are tired; they describe the psychological reality of founding.

All of these are on the essay index at paulgraham.com, and Y Combinator's free YC Startup Library adds related talks and guides.

"Graham's advice is gospel"

Some founders treat the essays as rules. That's understandable: they're clear, they're persuasive, and they come from someone who has watched thousands of startups up close.

But Several common readings go further than the essays do:

Unscalable work is not a ban on systems. Systems tend to pay off once you know what customers need, not before.
Building what people want is not the same as asking them. People are often poor at predicting their own behavior, so watching what they do tends to tell you more.
Startup = Growth describes venture-scale companies. Not every new company is a startup in that sense; a barbershop is not designed to grow fast, and the essay makes the same distinction. A profitable services business growing 3 percent a month is not failing; it is just not a venture investment. The investor-side seed funding guide explains why investors price for outsized growth.
The essays describe patterns, not laws. Solo founders do succeed, and late launches sometimes work. We find the patterns most useful as a checklist for your blind spots.

An example one month plan to apply the essays

Week 1: Write the problem you solve as a sentence about a specific person, and list the workarounds you have personally used.
Week 2: Hand-recruit five users. Onboard each one personally and note what confused them.
Week 3: Build the default-alive model. Decide whether you are cutting costs, pushing revenue, or both.
Week 4: Run the 18-mistakes audit with your co-founder and fix the one item you are most likely fooling yourselves about.

Investors read founders through a similar lens; the investor-side guide on how venture capitalists make investment decisions shows which signals they weigh most.

The bottom line

The essays are free, short and easy to agree with. The hard part is the month after you read them.

Reading Graham feels like progress.

Doing what he says is the progress.

Key takeaways

Paul Graham's startup essays keep returning to six ideas: want, unscalable effort, default alive or dead, noticed ideas, ramen profitability and predictable mistakes.
Defining your customer narrowly and measuring whether they come back is, in our view, the practical meaning of the YC motto.
Hand-recruiting and personally onboarding your first users, rather than waiting for organic growth, is often where you learn what the product needs.
The default-alive test from Graham's 2015 essay shows whether you reach profitability before cash runs out, and it is worth acting on the answer.
Founder living costs can make a sensible first revenue target, because ramen profitability tends to change your leverage with investors.

Frequently asked questions

What are Paul Graham's most important essays for founders?

For a first-time founder, we would start with How to Get Startup Ideas (2012), Do Things that Don't Scale (2013), Startup = Growth (2012), Default Alive or Default Dead? (2015), Ramen Profitable (2009) and The 18 Mistakes That Kill Startups (2006). Together they cover idea selection, first users, growth, financial survival and common failure modes.

What does doing things that don't scale mean for a founder?

In Graham's framing, it means founders win and serve early customers through manual, personal effort that would be impossible at scale: recruiting users one by one, setting them up by hand and fixing their problems personally. It is how startups get their first users and learn what the product needs to become, so it is usually a phase that lasts months.

What is the difference between default alive and default dead?

In Graham's 2015 essay, a startup is default alive if, with expenses held flat and revenue growing at its recent rate, it reaches profitability on the money it has left. It is default dead if it will need more outside money to survive. We think it helps founders to know which one they are, because it changes how they might act.

What does ramen profitable mean?

Graham's 2009 essay defines ramen profitable as a startup making just enough money to cover the founders' living expenses. It does not make the company a large business, but it removes the need to raise money to survive, which improves your negotiating position and your focus.

Is Paul Graham's advice still relevant for startups in 2026?

In our view, yes, because the core ideas concern customer behavior, founder psychology and cash, which have changed little. The examples are dated and the growth framing fits venture-backed companies best, so read the essays as patterns to check yourself against rather than rules.

Sources

Disclaimer: This guide is for general education only and is not legal, tax or investment advice. Laws, market data and program terms change, so it may not reflect the latest developments or fit your situation. Treat it as a starting point, not a source of truth, and talk to a qualified lawyer, accountant or financial adviser before you make decisions.