HTSaS · Chapter 01
Before the Startup
Should you actually do this — and if so, on what idea? The two questions to answer before you write any code.
After this lesson
- Pressure-test your own motivation and risk tolerance honestly
- Understand the four (then five) things that determine early outcomes
- Know where good ideas actually come from — and why brainstorming isn't it
Lecture 1 of the course arc
This track follows the Stanford CS183B sequence in order. Chapter 1 covers Lecture 1 (Sam Altman & Dustin Moskovitz, "Why to Start a Startup") and Lecture 3 (Paul Graham, "Before the Startup") — the two talks the original course puts before anyone is allowed to touch a product. Everything from Chapter 2 onward assumes you've actually answered the two questions below, not skimmed them.
“A startup is one of the most intellectually rigorous career paths — it requires you to solve unsolved problems, and you don't even know what questions to ask.”
The real risk calculus
For most people with options, a startup is less risky than it looks. If you're talented and it fails, you're extremely employable afterward. The bigger risk is spending a decade on something you weren't obsessed with. Startups compress ten years of career growth into a much shorter, much harder window — that trade only makes sense if you'd regret not trying.
Four things that matter (then a fifth)
- Idea — a real, specific problem worth solving, not a category
- Product — the thing you actually build to solve it
- Team — the people who build and sell it with you
- Execution — the daily discipline of shipping and learning faster than you're comfortable with
- Luck — real, but it disproportionately finds founders who nailed the first four
Read the original
Lecture 1 — Why to Start a Startup, and Ideas, Products, Teams, Execution (Part I) — Sam Altman & Dustin MoskovitzWatch or read the lecture, then note which of the four (idea/product/team/execution) you're personally weakest on — that's your real risk, not the market.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.
Read the original
Before the Startup — Paul GrahamRead for the single line worth stealing: what you need before you start is not a business plan, but to be the right kind of person for a problem.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.
Ideas come from noticing, not brainstorming
The best startup ideas usually look bad, or at least niche, on the surface — that's why they're not already being done by someone with more resources. Don't sit down and 'think of startup ideas.' Instead, live in a place where the future has unevenly arrived, notice problems (ideally ones you personally have), and ask what's missing.
Read the original
How to Get Startup Ideas — Paul GrahamExtract the 'live in the future' framing and the warning against deliberately brainstorming startup ideas — both are load-bearing for this chapter's decision below.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.
Read the original
Lecture 3 — Before the Startup — Paul GrahamPaul Graham delivers this live, with Q&A — extract his answer on why the idea matters less than founders think, and what predicts success instead.
This chapter is a working summary. When the idea matters, read the source once — then come back and do the practice.
Where real ideas hide
- Problems you have yourself, that you'd pay to fix today
- Things experts in a field complain about that outsiders don't see
- New technology that makes something newly possible or newly cheap
- Manual workarounds a specific group of people already does by hand
Market beats team, most of the time
A great team in a bad market usually loses to an average team in a great, fast-growing market. Before you fall in love with an idea, ask honestly: if this works exactly as planned, is the resulting company big? Rocket ships get pulled up by the market they're strapped to.
This week's version of 'before the startup'
- Write one paragraph naming the specific problem, the specific person who has it, and why you're the one to fix it
- Run the honest risk calculus below in writing, not in your head
- List three markets or wedges where this problem shows up, and rank them by how fast they could plausibly grow
- Decide explicitly whether you're starting now, hunting for an idea, or not ready — the decision tree below forces the call
Should you start now?
Be brutally honest about where you actually are.
Case
Airbnb: from air mattresses to a market
Brian Chesky and Joe Gebbia's first version was three air mattresses in their apartment during a sold-out conference. It looked like a weird, unscalable side hustle, not a company.
Takeaway: The idea that survived wasn't the pitch — it was the repeated, specific problem (no affordable place to stay during high-demand events) that kept showing up. Don't judge an idea by how big it sounds on day one.