Tim's Wiki

YC Startup School

Properties2
descriptionY Combinator's free startup course covering why to start, idea generation, co-founders, MVP, user interviews, launching, and growth.
tagsentrepreneurship, startup, learning, mature

5 min read

YC Startup School

Overview

YC Startup School is Y Combinator’s free online course distilling decades of startup advice into structured lessons. It covers the full early-stage journey from deciding whether to start, through finding ideas and co-founders, building and launching an MVP, talking to users, and growing/monetizing.

1. Should You Start a Startup?

  • Enduring motivation comes from interest in the problem and love for the people you work with
  • Worst-case analysis: probably costs ~1 year to find out
  • Don’t need a perfect idea or co-founder before starting — find smart people to talk ideas with
  • Turn ideas into side projects and launch them
  • If you enjoy the process, make the jump
  • Curiosity is a sufficient starting motivation

2. Generating and Evaluating Ideas

Common Mistakes

  • Thinking you need an amazing idea to start
  • Jumping into the first idea without critical evaluation
  • Starting with a solution instead of a problem
  • Believing good ideas are hard to find

Evaluating Ideas

  • How big? Look for existing large companies doing something similar
  • Founder/market fit — are you an expert in this area?
  • Problem confidence — how sure are you it’s a real, big problem?
  • New insight — do you see something others don’t? (Airbnb: strangers staying in your apartment)

Four Dangerous Filters (Cause You to Reject Best Ideas)

  1. Rejecting ideas that seem hard to get started (Stripe)
  2. Rejecting ideas in boring spaces (Gusto — payroll software)
  3. Rejecting ideas that seem too ambitious
  4. Shying away from spaces with existing competitors

7 Recipes for Generating Ideas

  1. Start with what your team is especially good at — unfair advantage
  2. Things you wish someone else would build for you (DoorDash)
  3. What would you work on for 10 years even if it didn’t succeed?
  4. What changed in the world recently that enables new solutions?
  5. Find successful companies and look for new variants
  6. Talk to people — ask them for problems they want solved
  7. Look for industries that seem broken (LendUp → payday lending)

3. Co-Founders

Why Co-Founders Matter

  • All tech giants had co-founders
  • Should you wait? Generally yes — unless you’re certain about the idea

What to Look For

  • How they handle stress (and help you handle yours)
  • Alignment on objectives and goals (sell in 2 years? build forever?)
  • Complementary skills

Practical Decisions

  • Equity: try for equal split
  • CEO: usually the one who talks more; be honest with yourself
  • Formalize: incorporate, set up vesting agreement
  • De-risk by working together on an MVP for a set period

Working Together (Kevin Hale)

  • Treat co-founder relationship like a marriage
  • Practice crucial conversations
  • Address conflict early and directly

4. MVP and Talking to Users

Talk to Users — Even Before Having a Product

Find users:

  • Your connections (easy but may not be objective)
  • Facebook groups, LinkedIn, Slack, Reddit

How to interview:

  • Video/phone calls or in person
  • Build rapport, don’t introduce your product
  • Listen, don’t talk
  • Ask open-ended questions
  • Never ask: “Will you use this?” / “Which feature should we add?” / Yes/No questions

After interviews: Synthesize learnings into patterns

Product Development Cycle (Michael Seibel / Socialcam)

Define cycle length by product type (2 weeks for mobile, shorter for web)

Product meeting structure:

  1. Choose ONE goal: increase content creation, new users, or retention
  2. Brainstorm: new features, maintenance, A/B tests — no debates, no judgment
  3. Grade difficulty: easy (several/day), medium (half day), hard (most of cycle)
  4. Build consensus starting with hard items
  5. Spec clearly with measurements of success
  6. Separate need-to-haves from nice-to-haves

Key principles:

  • Never release a feature without releasing its analytics
  • No product roadmap beyond current cycle — start fresh each meeting
  • Everyone tests; last 3 days of each cycle = testing only
  • Monthly in-person user testing sessions

5. Launching

“1st launch is not important, so launch early” — Kat Manalac

When: Right Now, ASAP

  • Worst case of launching early: no one sees it, users think it’s ugly
  • Solution: launch again and again (Airbnb did 3 times)

One-Line Description

  • Lead with what, not why
  • Don’t ramble
  • “X for Y” format: X should be a household name, Y should be a huge market
  • Example: “Payze is Stripe for Russia”

Launch Cadence

  • Launch → interact → launch → interact (continuous cycle)

6. Growing and Monetizing

Move Your KPIs

  • Write down ideas, rank them, choose a few
  • If KPI doesn’t move: honest retro → do something different
  • If working: double down

What Should Be on Your List

  • Talking to users / responding to support
  • Building features you know customers will pay for
  • Getting users to pay for what you’ve built

What Should NOT Be on Your List

  • Investor coffee
  • Conferences
  • Arbitrary technical milestones (e.g., “build Android version”)
  • Mitigating downsides (feels falsely urgent vs. chasing upside)
  • Working on secondary problems (150 users asking for a feature → the problem is only 150 users)

Key Mindset

Fast decisions are good decisions. If wrong, learn and change.

Source References

  • YC Startup School Online Course
  • 1 Why
  • 2 Ideas
  • 3 Founders
  • 4 MVP and Users
  • 4.3 Product Development Cycle Fundamentals
  • 5 Launching
  • 6 Growing and Monetizing

Graph View

Backlinks