Learn startups from Paul Graham
A free 6-month course built only from what Paul Graham and Y Combinator have actually written and said: his essays, talks and interviews, and how a YC batch works.
Unofficial. Not affiliated with or endorsed by Paul Graham or Y Combinator. Every teaching links to the original essay or talk.
- Lessons
- 17
- 5 tracks, ideas to Demo Day
- PG essays cited
- 51
- Each linked to paulgraham.com
- Plan
- 6 months
- 30 weekly actions to tick off
- Cost
- Free
- No login, progress saved here
If Paul Graham mentored you for 6 months
What his essays and YC’s advice tell a founder to do, month by month. Read the lessons, do the actions, and check yourself against the tests Paul Graham and YC describe. Tick things off as you go; it is saved on this device.
- Month 1 of 60 of 5 actions done
Find the idea
By the end of the month: You have one idea that came from a real problem, and you can name at least ten people who have that problem and what they do about it today.
Show the 5 actionsHide the actionsKeep a problems log for two weeks: every time something is annoying, slow or missing in your work or life, write one line.
Graham says the way to get startup ideas is to look for problems, preferably your own, and that the right verb is "notice", not "think up".
Source: Paul Graham, How to Get Startup Ideas (2012) ↗Pick the three most promising problems and talk to ten people who have them. Ask how they deal with it now and what it costs them.
Michael Seibel lists "not knowing where your first users will come from" as a top first-time founder mistake. In the video he says it is odd to pick a problem when you don’t know anyone who has it, including yourself.
Source: Michael Seibel, The Biggest Mistakes First-Time Founders Make (YC, 2019) ↗For each idea, write who wants it urgently. Prefer a small group who need it badly over a big group who would find it nice.
Graham says good ideas are usually narrow and deep, "like a well": intense demand from a small group first.
Source: Paul Graham, How to Get Startup Ideas (2012) ↗Ask of every idea: would I use this myself if I hadn’t built it?
When user growth is slow, Graham says the product is often the real problem, and asks founders: "Would you use this yourself, if you hadn’t built it?"
Source: Paul Graham, What I’ve Learned from Users (2022) ↗Read the 18 mistakes and cross out any idea that is a marginal niche or a copy of something that exists.
"Marginal Niche" and "Derivative Idea" are on Graham’s list of mistakes that kill startups, along with having no specific user in mind.
Source: Paul Graham, The 18 Mistakes That Kill Startups (2006) ↗
CheckpointCan you name a specific group of people who want this badly now, and have you heard it from them, not just imagined it? That is the "well-shaped" test from How to Get Startup Ideas (2012).
- Month 2 of 60 of 5 actions done
Build a first version and launch
By the end of the month: A first version is in the hands of real users outside your friends, and you are measuring what they do.
Show the 5 actionsHide the actionsWrite a one-page spec for a version you can build in weeks, then cut every feature your first ten users won’t miss.
Seibel’s MVP advice: time-box the spec, write it down, cut features hard, and aim for weeks, not months.
Source: Michael Seibel, How to Plan an MVP (YC, 2019) ↗Set a launch date three to six weeks out and launch on it, even if it embarrasses you.
"Release early" is the first of Graham’s hardest lessons, and "Launch now" is the first line of YC’s pocket guide.
Source: Paul Graham, The Hardest Lessons for Startups to Learn (2006) ↗Install basic analytics before launch: signups, weekly active users and the one action that shows a user got value.
Seibel names "not using analytics" as a first-time founder mistake: you need to know what is being used and what is not.
Source: Michael Seibel, The Biggest Mistakes First-Time Founders Make (YC, 2019) ↗Sit with three users while they use the product. Say nothing; write down every place they hesitate.
Sam Altman: "Literally watch them use your product. Sit in their office if you can."
Source: Sam Altman, Startup Playbook (2015) ↗Ship a small improvement every day or two after launch.
Graham: "You should make your system better at least in some small way every day or two."
Source: Paul Graham, The Hardest Lessons for Startups to Learn (2006) ↗
CheckpointCan you write three things you learned from users that changed what you built? Graham calls "Explain what you’ve learned from users" the best per-word advice for getting into YC (What I’ve Learned from Users, 2022).
- Month 3 of 60 of 5 actions done
Do things that don’t scale, and grow every week
By the end of the month: You recruit users by hand, you track one growth number every week, and a small group of users would be upset if you shut down.
Show the 5 actionsHide the actionsRecruit users one at a time: write to 30 named people who have the problem and offer to set them up personally.
Graham calls recruiting users manually "the most common unscalable thing founders have to do at the start".
Source: Paul Graham, Do Things that Don’t Scale (2013) ↗When someone agrees to try it, set them up on the spot: on a call, on their laptop, right then.
This is the "Collison installation" Stripe’s founders used inside YC.
Source: Paul Graham, Do Things that Don’t Scale (2013) ↗Send every new user a personal thank-you, and reply to every message the same day.
Graham says to take extraordinary measures to make early users happy; Wufoo sent each new user a hand-written thank-you note.
Source: Paul Graham, Do Things that Don’t Scale (2013) ↗Choose one growth number (revenue, or active users if you don’t charge) and a weekly target. Check it every Monday.
YC measures growth per week during the batch. Graham says to pick a rate you think you can hit and try to hit it every week.
Source: Paul Graham, Startup = Growth (2012) ↗Each week, rank your three most important problems, try a fix within the week, and check the result the next week.
Graham says founders should try things "at a resolution of a week or less" and report results at the next office hours.
Source: Paul Graham, What I’ve Learned from Users (2022) ↗
CheckpointWeekly growth of 5–7% is good, 10% is exceptional, and 1% means you haven’t figured out what you are doing yet (Startup = Growth, 2012). YC’s pocket guide adds the second test: 10–100 customers who love you.
- Month 4 of 60 of 5 actions done
Founder habits
By the end of the month: You protect long blocks of build time, you have a cofounder (or a serious search for one), and you keep shipping through setbacks.
Show the 5 actionsHide the actionsStudyBlock at least two half-days a week with no meetings, and push calls to the end of the day.
Makers work in units of half a day, and "a single meeting can blow a whole afternoon". Graham held office hours at the end of his working day.
Source: Paul Graham, Maker’s Schedule, Manager’s Schedule (2009) ↗If you are alone, look for a cofounder: create a profile on YC’s free co-founder matching and meet three people this month.
"Single Founder" is the first of Graham’s 18 mistakes: "Starting a startup is too hard for one person." YC’s matching is free.
Source: Y Combinator: Co-founder matching ↗Hold a weekly 30-minute cofounder check-in, and write down roles and equity while things are going well.
Seibel lists not having transparent conversations with your cofounder as a top mistake; YC’s pocket guide says founder relationships matter more than you think.
Source: Michael Seibel, The Biggest Mistakes First-Time Founders Make (YC, 2019) ↗Keep a setbacks log: each time something goes wrong, write what you did next. Review it monthly.
Graham: "The most important quality in a startup founder is determination. Not intelligence-- determination."
Source: Paul Graham, The Hardest Lessons for Startups to Learn (2006) ↗Protect sleep and exercise. Put them in your calendar like customer meetings.
The last line of YC’s pocket guide: "Get sleep and exercise – take care of yourself".
Source: Geoff Ralston, YC’s Essential Startup Advice (2017) ↗
CheckpointRate yourself, and ask your cofounder to rate you, on the five qualities in What We Look for in Founders (2010): determination, flexibility, imagination, naughtiness and friendship. Any score you can’t back with a real example is the one to work on.
- Month 5 of 60 of 5 actions done
Default alive and ready to raise
By the end of the month: You know in numbers whether you will reach profitability on the money you have, and you could raise money if you chose to.
Show the 5 actionsHide the actionsWork out if you are default alive: with expenses flat and revenue growing at its recent rate, do you reach profitability before the money runs out?
Graham says founders should know this early, and that asking too early is far less dangerous than asking too late.
Source: Paul Graham, Default Alive or Default Dead? (2015) ↗Cut costs until revenue could cover the founders’ basic living expenses. Aim for ramen profitable.
Ramen profitable means you are "no longer at the mercy of investors", so you can raise on better terms or not at all.
Source: Paul Graham, Ramen Profitable (2009) ↗Freeze hiring until growth is real. Do the work yourselves for now.
Graham: "Hiring too fast is by far the biggest killer of startups that raise money."
Source: Paul Graham, Default Alive or Default Dead? (2015) ↗If you raise, list investors and talk to them in parallel, not one by one, and ask at every meeting what happens next.
Graham’s rules: breadth-first search weighted by expected value, and "never leave a meeting with an investor without asking what happens next".
Source: Paul Graham, How to Raise Money (2013) ↗Learn how a SAFE and the YC deal work, so you know what 7% plus an MFN SAFE would cost you.
YC’s standard deal is $500,000: $125,000 for a fixed 7% plus $375,000 on an uncapped MFN SAFE (as of November 2026).
Source: Y Combinator: The YC Deal ↗
CheckpointCan you answer "default alive or default dead?" in one sentence, with your burn, revenue growth and months of runway? Graham says the rest of the conversation depends on the answer (Default Alive or Default Dead?, 2015).
- Month 6 of 60 of 5 actions done
Apply to YC and write your Demo Day update
By the end of the month: Your YC application is submitted, you can handle a 10-minute interview, and you have a one-page update any investor could read.
Show the 5 actionsHide the actionsStudyWrite the application. Make the first sentence of every answer say the point plainly, and cut every word that adds no fact.
Graham: "Whatever you have to say, give it to us right in the first sentence, in the simplest possible terms."
Source: Paul Graham, How to Apply to Y Combinator ↗Record the founder video with all founders. Don’t skip it.
Graham says YC is much more likely to interview people who submit a video.
Source: Paul Graham, How to Apply to Y Combinator ↗Do three 10-minute mock interviews. Know your users, growth, revenue, burn and retention without looking.
In this 2019 video Garry Tan, now YC’s president, says "The YC interview is only ten minutes" and lists the numbers to know: revenue, growth, burn, retention.
Source: Garry Tan, 3 Tips to Nail the Y Combinator Interview ↗Write a one-page Demo-Day-style update: what you make, who uses it, weekly growth, what you learned, what you need.
Demo Day is where each YC startup presents to investors and press; writing it now shows whether your story and numbers hold up.
Source: Y Combinator: What Happens at YC ↗Submit before the on-time deadline on ycombinator.com/apply. If the answer is no, keep building and apply again next batch.
YC’s FAQ says that in a typical batch about half the companies applied multiple times before being accepted.
Source: Y Combinator: FAQ ↗
CheckpointCould a stranger repeat what you make after one sentence, and can you say what you have learned from users and your weekly growth rate? Those are the first things YC reads (How to Apply to Y Combinator; What I’ve Learned from Users, 2022).
Find an idea worth building
Notice startup ideas the way Paul Graham says the best founders do, and avoid the mistakes that kill startups.
- 1How to get startup ideas12 minPaul Graham’s answer is that you don’t think up startup ideas, you notice them. The best ones are things the founders themselves want, can build, and few others see as worth doing. Get to the leading edge of something that is changing fast, look for what is missing, start with a small group who want it badly, and switch off the filters (schleps, unsexy problems, competitors) that hide good ideas from you.
- 2Make something people want11 min“Make something people want” is Y Combinator’s motto, and Paul Graham says it came from his own failure: six months building software nobody wanted. In practice it means getting a rough version in front of real users fast, watching them use it, making a few people love it before trying to please many, and not letting tricks, investors or early revenue pull you away from what users actually need.
- 3The mistakes that kill startups13 minIn ‘The 18 Mistakes That Kill Startups’ (2006), Paul Graham lists the causes of failure that founders control, and says that in a sense there is only one: not making something users want. The 18 fall into six groups: the idea, the team, launching, money, users and sales, and effort. His follow-up, ‘How Not to Die’ (2007), adds the most important point: if you just avoid dying, you get rich, and startups usually die because the founders get demoralised and give up.
Make something people want
Launch early, do things that do not scale, talk to users and grow every week.
- 4Do things that don’t scale12 minStartups rarely take off on their own. In his 2013 essay, Paul Graham says founders have to push them into motion by hand: recruit users one at a time, make each early user extremely happy, and do manually what you will automate later. It feels small and slow, but it is how Stripe, Airbnb and DoorDash started, and it teaches you what to build.
- 5Launch early and talk to users13 minPaul Graham wrote in 2006 that launching too slowly has killed far more startups than launching too fast, because you only understand your idea once real users touch it. YC’s version is short: the most important early tasks are to write code and talk to users. Launch something small within weeks, win a few users who love it, and keep learning from them.
- 6Startup = growth12 minPaul Graham defines a startup as a company designed to grow fast. At YC, growth is measured weekly: 5–7% a week is good, 10% is exceptional, and 1% means you have not yet figured out what you are doing. Pick one number, usually revenue, set a weekly target, and let it decide what you work on. Getting ramen profitable buys you the time to keep going.
Become the founder YC looks for
Build the determination, judgment and habits of thought PG looks for in founders.
- 7What makes a great founder14 minPaul Graham’s answer has stayed the same for over fifteen years: past a basic level of intelligence, determination matters most. Add flexibility, imagination, a little naughtiness, earnestness and a cofounder you are close to, and you get the founder he calls "relentlessly resourceful". Most of it can be trained, and YC judges it from stories of what you actually did, not from how confident you sound.
- 8Cofounders13 minPaul Graham calls going solo the first of the 18 mistakes that kill startups: the work is too much for one person. Pick someone you already know well, ideally from building something together, who shares your values. Raise doubts before you start, split equity close to equally with vesting, and fix fights fast: by 2006, about one in five of the startups YC had funded had lost a founder.
- 9Founder mode11 minFounder mode is Paul Graham’s name, from a September 2024 essay, for how founders run companies differently from hired managers: staying close to the work and reaching past the org chart, instead of only steering through direct reports. It came from a Brian Chesky talk at a YC event. PG is clear that founders still have to delegate, and that almost nothing is known about it yet.
- 10How to do great work14 minPaul Graham’s 2023 essay boils down to four steps: choose a field, learn enough to get to the frontier, notice gaps, explore the promising ones. Around those steps sit the habits that make them work: your own projects, steady work that compounds, and protected morale. Curiosity is the guide throughout, and because returns are superlinear, small differences in effort and learning grow into very large ones.
- 11Think and write clearly13 minFor Paul Graham, writing is how you find out what you think, not just how you share it: half the ideas in an essay come while writing it. Write the way you would say it to a friend, keep your identity small so you can change your mind, disagree with the central point instead of the tone, and protect long blocks of time and the idea you think about in the shower.
Survive and raise money
Know if you are default alive, and raise money the way PG and YC advise.
- 12Default alive or default dead12 minYou are default alive if, with expenses flat and revenue growing at its recent rate, you reach profitability before the money runs out. If not, you are default dead and your survival depends on investors. Paul Graham says half the founders he asks don’t know which they are. Work it out now, because the most common way funded startups die is hiring too fast, and by the time you notice, it can be too late to raise.
- 13How to raise money15 minPaul Graham’s advice is to raise only if you need it and investors want in, to treat every investor as a no until money is committed, and to talk to many in parallel, ranked by expected value. The first commitment is the hardest; after that, investors follow each other. Raise less than you hope, take good offers fast, close the money, and get back to work.
Inside Y Combinator
What YC actually does in a batch, how to get in, and what its founders did right.
- 14What happens inside a YC batch14 minAs of November 2026, YC invests $500,000 in every company it accepts: $125,000 for a fixed 7% plus $375,000 on an uncapped SAFE with a most favored nation (MFN) clause. Then it runs a three-month, in-person program in San Francisco, four times a year. You get partner office hours, a group of batchmates, weekly talks and a weekly growth number to chase, and the program ends with Demo Day. Most of your time still goes on building and talking to users. After the batch, you keep partner access, Bookface and the alumni network.
- 15How to get into YC15 minYC reads your answer to "what are you making?" first, then looks hard at the founders. Paul Graham’s own advice is to say what you do in the first sentence, in plain words, and be specific about what each founder has built. The best short tip he knows: explain what you have learned from users. If you get an interview, it is a short video call, about 10 minutes, so know your numbers and answer plainly. About half of each batch applied more than once, per YC’s FAQ.
- 16What the first YC founders did15 minThe famous YC companies did not start with great ideas or great timing. Reddit changed its idea before the first batch began. Kiko failed and its founders went on to build Justin.tv, then Twitch. Airbnb sold cereal boxes to pay its debts and grew only after the founders went door to door in New York. Dropbox showed a 3-minute demo video instead of describing the product. Stripe set users up on the spot. Each story below links the source and says when the source is the founder’s own retelling.
- 17YC’s essential startup advice14 minIn 2017 YC partner Geoff Ralston published "YC’s Essential Startup Advice", a pocket guide of 22 short rules YC considers its most important advice. Most of it reduces to this: launch now, talk to users, make a small group love you, grow from the product, spend money as if it isn’t yours, ignore distractions and competitors, and look after your cofounders and yourself. Michael Seibel’s talks on launching and Sam Altman’s Startup Playbook say the same things from other angles.
Read the originals
The essays this course is built on, most used first. Each opens on paulgraham.com.
- Used in Make something people want, Launch early and talk to users and 3 more
- Used in Make something people want, The mistakes that kill startups and 3 more
- Used in Do things that don’t scale, Launch early and talk to users and 3 more
- Used in Make something people want, Startup = growth and 2 more
- Used in Launch early and talk to users, What happens inside a YC batch and 2 more
- Used in Startup = growth, Default alive or default dead and 2 more
- Used in How to get startup ideas, Make something people want and 1 more
- Used in What makes a great founder, Cofounders and 1 more
- Used in Make something people want, Cofounders
- Used in What makes a great founder, Cofounders
- Used in Cofounders, How to get into YC
Watch the talks
Paul Graham and YC partners in their own words. Each talk sits inside the lesson it belongs to.
Paul Graham and YC: questions people ask
Who is Paul Graham?
Paul Graham is a programmer, writer and investor. In 1995 he and Robert Morris started Viaweb, which he calls the first software-as-a-service company; Yahoo bought it in 1998. In 2005 he started Y Combinator with Jessica Livingston, Robert Morris and Trevor Blackwell (source: his bio on paulgraham.com). His essays, free on paulgraham.com, cover startups, programming, writing and how to do good work.
What does Y Combinator teach founders?
Mostly a few ideas, repeated until they stick: make something people want, launch early, talk to users, do things that don’t scale, grow every week, stay default alive, and raise money only when it helps. YC’s motto is “Make something people want.” During the three-month batch, partners advise each company in one-on-one and group office hours, an invited founder or investor speaks every week, and it ends with Demo Day, where founders present to investors (source: ycombinator.com/about). This course covers each idea in a lesson, sourced to the essay or talk it comes from.
Can I learn YC’s methods without getting into YC?
Much of it, yes. Paul Graham’s essays, YC’s Startup School and the YC Library are free and public, and most of the advice is about how you work, not about access. What you cannot copy is the network, the partners’ time and the peer pressure of a batch. The 6-month plan on this page turns the public advice into weekly actions so you can apply it on your own.
Which Paul Graham essays should I read first?
Start with How to Get Startup Ideas, Do Things that Don’t Scale and Startup = Growth. Then read Default Alive or Default Dead, How to Raise Money and Founder Mode. The “Most cited essays” list on this page ranks the essays by how often the lessons rely on them, each with a link to the original.
How long does this course take?
The lessons take about 4 hours to read, plus optional talks. The plan is built for six months because the advice only works when you do it: talk to users, ship, measure growth each week. Read one lesson a week and do that week’s actions.
Working at a startup instead of founding one?
Pitching investors or a founder? Practise out loud.
Answer hard questions out loud with an AI interviewer and get feedback on every answer.