ENTREPRENEURSHIPMonths to result

The Three Startup Essentials

Start with good people, make something customers want, and spend as little as possible

Problem it solves

focus on what actually matters

Best for

First-time founders who have never started a company, technical builders considering leaving their jobs to start something, anyone overwhelmed by startup advice and needing to focus on what actually matters

Not ideal for

Experienced founders who already understand the basics, people starting lifestyle businesses rather than high-growth startups, situations where significant capital is required before any product can be built

Overview

Why this framework exists

The Three Startup Essentials is Paul Graham's distillation of everything needed to start a successful startup into three things: good people (particularly cofounders who are not just smart but tough and capable of independent action), making something customers actually want (not what you think they should want, but what they demonstrate through their behavior that they need), and spending as little money as possible (because money buys time and the more frugally you operate the more runway you have to figure things out). Graham argues that most startup advice complicates what is fundamentally simple: if you have strong people building something real customers want while spending carefully, you will probably succeed. Everything else — legal structure, office space, branding, pitch decks — is secondary. The essay is notable for its bluntness about what matters versus what feels like it matters, particularly the warning that most startup problems are really people problems in disguise.

Core principles

5 total
  1. A startup needs three things: good people, something customers want, and minimal spending
  2. The most important choice a founder makes is their cofounder — most startup problems are people problems
  3. Make something customers actually want as demonstrated by their behavior not their words
  4. Spending less money buys more time and more time increases the probability of finding product-market fit
  5. Technology matters less than understanding users — build what they need not what you find technically interesting

Steps

4 steps
  1. Choose Your Cofounders Carefully
    Select cofounders who are not just technically talented but genuinely tough, capable of independent decision-making, and people you trust completely under pressure. Graham argues this is the most important decision a founder makes because most startup failures are really cofounder failures. He advises choosing people you know well from previous experience rather than strangers who seem impressive on paper.
  2. Build What Customers Actually Want
    Focus relentlessly on understanding what your customers need and building exactly that — nothing more and nothing less. Graham emphasizes behavior over words: customers will tell you they want many things but their actual usage reveals what they truly need. Launch quickly with a minimal product, watch how people use it, and iterate based on observed behavior rather than stated preferences.
  3. Spend as Little as Possible
    Operate with extreme frugality to maximize your runway. Graham argues that the number one cause of startup death is running out of money, and the most reliable way to avoid that is spending less rather than raising more. Every dollar saved is a dollar more of time to figure out product-market fit. Cheap offices, minimal staff, and founders willing to live cheaply buy the most valuable resource: time.
  4. Launch Early and Learn from Users
    Get a product in front of users as soon as it has minimum utility, then improve based on their feedback. Graham argues against building in isolation — your initial model of users is always wrong, and the only way to correct it is to observe real behavior. A year of building in silence will produce a product for imaginary users. A month of building followed by real-world testing will produce something people actually want.

Checklist

Saved in your browser

Examples

2 cases
Viaweb's User-Driven Development

Graham's own company Viaweb (which became Yahoo Store) was built by watching how merchants actually tried to create online stores and adapting the product in real time. Sometimes the feedback loop was near-instantaneous — while building a merchant's store, Graham would discover a missing feature, spend a couple hours implementing it, and then resume building the store.

OutcomeThis extremely tight feedback loop between user needs and product development produced one of the first successful web applications, acquired by Yahoo for $49 million. The product succeeded not because of technical sophistication but because it was shaped entirely by real user behavior.
Paul Graham / Viaweb
The Importance of Cofounder Selection

Graham observes that among the hundreds of startups YC has funded, the ones that fail most often do so because of cofounder conflict rather than market failure or technical problems. He compares choosing a cofounder to marriage — you need someone you know well, trust deeply, and can work with under extreme stress for years.

OutcomeThis observation led to one of YC's strongest pieces of advice: never start a company with someone you do not know well. The best cofounding teams come from years of shared experience — college roommates, long-time colleagues — not from cofounder matching events or networking.
Paul Graham / Y Combinator

Common mistakes

3 traps
Focusing on Startup Theater Instead of Essentials
First-time founders spend enormous energy on things that feel important but are not: incorporating, designing logos, writing business plans, perfecting pitch decks, choosing office space. Graham argues these activities are forms of procrastination — they feel productive but delay the three things that actually matter: assembling good people, building what customers want, and doing it cheaply.
Choosing Cofounders Based on Complementary Skills Alone
The common advice to find a technical cofounder if you are a business person (or vice versa) focuses on skills but ignores character. Graham argues that toughness, independence, and mutual trust matter far more than complementary skill sets. A cofounder with the right skills but wrong character will destroy the company faster than a skill gap ever could.
Building What You Find Technically Interesting
Technical founders often build what they find intellectually stimulating rather than what users need. Graham warns that the product should be shaped entirely by user needs, not by what is technically elegant or interesting to the founders. The greatest technical achievement means nothing if it solves a problem no one has.

Origin story

How this framework came to be

Graham wrote this essay in 2005 based on his experience co-founding Viaweb and the early years of Y Combinator. He noticed that founders consistently focused on the wrong things — perfecting their pitch deck, choosing the right legal structure, designing business cards — while neglecting the three things that actually determined success. The essay became one of the most influential startup texts ever written because it cut through the noise with a clarity that first-time founders desperately needed. Graham later noted that everything he learned at YC confirmed and refined these three essentials without fundamentally changing them.

Source

Traced to primary
Source · ESSAY
How to Start a Startup
Paul Graham · 2005
Open source →