15 resources from Y Combinator Startup School we point founders to, and the questions each answers.
▶️ Video
✓ Link checkedFreeBeginner
Why we picked it
Pete Koomen took Optimizely from zero to $100M+ ARR, and here he breaks the enterprise funnel down for exactly the person who finds it terrifying: the technical founder who has never sold. It is the clearest short primer we know on how a builder starts closing real deals.
Why we picked it
Kevin Hale is a YC partner and cofounder of Wufoo, so this is both the investor lens (what makes a bet worth backing) and the operator lens (someone who built and sold a company). His core move is treating an idea as a hypothesis about why the company will grow fast, which is exactly the question to ask before you sign up for years on it. Use it as a starting point to pressure test your own idea, not as a verdict.
An idea is a hypothesis for why the company will grow quickly, made of a problem, a solution, and an insight, so be honest about whether the growth story holds.
You need an unfair advantage, a concrete reason you will win and reach people faster than everyone else, before the years of commitment make sense.
Evaluate your own idea the way an investor would, since that is the same lens that tells you whether it is big enough to be worth your life.
Why we picked it
When you are new to a space, your instinct is to explain your idea and hope people nod, which teaches you nothing. This YC talk is a concrete guide to running discovery interviews the right way: extract data from the person instead of pitching, and use a small set of questions that work in any industry, including one you are still learning. It pairs well with The Mom Test as the applied version you can watch before your next call.
Why we picked it
Founders often keep validating because they secretly doubt the idea itself, so a structured way to judge the idea is half the readiness question. YC partner Jared Friedman gives an idea quality score across four criteria (how big, founder/market fit, how sure you are the problem is real, and whether you have a genuine insight) plus the bad filters that make founders quietly reject their best ideas. It is the honest bar to check your idea against before you commit to building. A starting framework, not a scorecard to obsess over.
Rate an idea on four criteria and average them, rather than trusting a gut yes or no.
Great companies usually started from a good enough idea plus strong execution, not a brilliant one, so waiting for the perfect idea is itself a mistake.
Watch for filters (seems hard, boring space, too ambitious, competitors exist) that make you reject strong ideas without realising it.
Why we picked it
Kevin Hale's YC talk is the founder-facing way to reason about a market when you cannot just look up a number. He treats the idea as a hypothesis about fast growth and pushes you to judge the market by the shape of the problem (is it growing, urgent, expensive, frequent, mandatory) rather than a tidy TAM slide. That is the honest starting point for a product whose category does not exist yet: you argue from the problem, not from off-the-shelf data.
Why we picked it
This is a founder-facing YC talk from someone who spent 18 months grinding before Weebly clicked, so it is honest about how long focusing your market actually takes. Rusenko is direct that you find fit by narrowing and iterating on who you serve, not by trying to be everything on day one. A good starting point if you want the shape of the problem before you sit down with a heavier positioning method.
Why we picked it
Kat Mañalac (YC) makes the case that most founders overthink the first launch, treating it as one perfect shot when it is really something you do again and again. That reframing is the direct answer to the fear behind the question: a low drama, repeatable launch is the norm, not a cop-out. She walks through concrete formats, from a friends and family launch to a full public one.
Why we picked it
Anu Hariharan walks through the two or three metrics that actually matter at the earliest stage depending on how you make money, which spares a first-time founder from drowning in a dashboard of numbers that do not decide anything. Her clearest warning is the one non-technical founders miss most: never report a metric without defining it, since a company once reported daily active users that really meant emails sent. It is a trusted, founder-facing primer, so use it to pick your three real numbers before you argue about the rest.
At the earliest stage only two or three metrics matter, and revenue (or, if you do not charge yet, a clear definition of the core user action) is usually the truest one.
Always define what active means and always show the absolute number alongside the percentage, because an undefined or relative metric quietly misleads you and everyone reading it.
Which metrics matter depends on your business model, so match your handful of numbers to how you actually charge rather than copying another startup's dashboard.
Why we picked it
Kevin Hale from Y Combinator lays out the acquisition-cost and lifetime-value math in plain language, framed around how much you can afford to spend to win a customer. It is aimed at first-time founders, so there is no jargon wall, just the reasoning you need to set a target CAC. He is also refreshingly blunt that leaning only on paid acquisition is a weak growth story, which is worth hearing early.
Why we picked it
Alstromer ran growth at Airbnb and now works with hundreds of YC startups, and his core message answers the question directly: working on growth, including paid ads, before you have product-market fit and real retention is a mistake. He is specific about the metrics that actually signal you are ready, versus the vanity numbers that lie. It reframes paid spend as an amplifier for something already working, not a way to create demand.
Why we picked it
YC's David Lieb walks through cohort retention: watching each week's new users and asking how many actually come back. For a very early founder that framing answers the real question, because it shows you can read retention off a handful of early cohorts long before you have scale. Treat it as a starting point for how to look at your first users, not a benchmark you must hit on day one.
Why we picked it
A YC group partner walks through unit economics the way you actually reason about them early on, per customer revenue minus the variable cost of serving that customer, before you have clean data to plug in. It is short and plain spoken, which is exactly what you want when you are estimating rather than reporting. Treat it as a way to sanity check your assumptions, not a promise about your real numbers.
Unit economics is revenue per customer minus the variable cost of serving that customer, and scaling while that number is negative is the dangerous move.
Separate organic growth from paid growth early, because leaning on paid channels hides whether people actually want the product.
Look for the moment a user gets real value, since that magic moment is what makes the rest of your acquisition math hold up.
Why we picked it
YC partner and Monzo co-founder Tom Blomfield built real side projects with these tools and turned the lessons into a practical playbook. You get concrete habits (use version control, write tests, get unstuck when the AI loops) that separate a founder who ships from one who ends up with an unmaintainable mess. Watch this before you start so your fast prototype does not become a trap.
Why we picked it
The audio companion to Harj Taggar's co-founder guidance, good for a walk or commute, covering why you want a co-founder, when to bring one on, where to find them, and how to keep the relationship healthy. It reinforces the pipeline mindset in a conversational format. A low-effort way to absorb the fundamentals before you start reaching out.
Why we picked it
The audio version goes deeper on the practical mistakes: unequal splits that breed resentment, forgetting vesting, and treating the split as a reward for past work rather than an incentive for the next four years. If you prefer listening on a commute, this covers the co-founder side thoroughly. It pairs well with reading a data driven guide on the early engineer side.
