14 resources from Y Combinator (YouTube) we point founders to, and the questions each answers.
▶️ Video
✓ Link checkedFreeBeginner
Why we picked it
The single most-cited practical talk on scoping a first product, from the person who ran YC's accelerator. It cuts through the theory and shows what an MVP actually looks like using Airbnb, Twitch, and Stripe.
Why we picked it
A concise, practical talk from a two-time founder (Justin.tv/Twitch, Socialcam) who now advises thousands of startups. It reframes the search as sales, which is exactly the mindset shift most non-technical founders need.
Why we picked it
Before you have any data to cluster into an ICP, your job is to find and watch a handful of real customers up close. Michael Seibel (YC, co-founder of Twitch) gives a short, concrete talk on where those first customers actually come from and how to spot the ones who genuinely have the problem. It pairs well with the interview technique in The Mom Test: this is where to point that technique first.
Why we picked it
Michael Seibel has watched thousands of early teams up close, and here he walks through the patterns that sink first-timers, including pouring months into building something before checking that anyone wants it. For a first-time founder it helps you hear the warning signs in a real voice rather than a checklist, so you recognize them live when your own build starts drifting. It is broad on purpose, which is useful when you are still learning what "wrong thing" even looks like.
Why we picked it
Michael Seibel names the exact trap directly: founders who act like an artist getting the thing in their head into the world, rather than a business owner serving what customers actually want. His blunt line, launch something bad quickly, is the counter-habit to endless building. It is a short, high-signal warning against over-building before you have proof anyone wants it.
Why we picked it
This is the canonical short talk on winning your first users when you have no audience and no sales team. Alstromer (YC partner, former head of growth at Airbnb) makes the case that early on you do things that do not scale: you go where your users already gather, reach out directly, and talk to them one at a time. For a solo technical founder that is a relief, because it is closer to helping people in a community than to cold-call selling.
Why we picked it
Michael Seibel runs YC and has read thousands of these, so this is the receiving end talking back: what actually makes an investor open, read, and reply. It is a short, direct talk that pairs well with the written pieces if you would rather hear the reasoning than read it. Useful precisely because it comes from the person you are trying not to annoy.
Why we picked it
Michael Seibel ran Y Combinator and has watched roughly 70 percent of companies that raise on demo day never find real product-market fit, so his list of what kills them is postmortem-grade and concrete. He names the quiet ones first: fake product-market fit and building the company (hiring, offices, process) before you have built a product people want. Treat it as a checklist to run against your own startup, not a set of rules.
Why we picked it
A YC talk on growth that spends real time on the metrics that lie about product/market fit, which is exactly what a swelling waitlist can be. Alstromer separates numbers that flatter you from numbers that predict a business. Watch it to build a healthier scorecard than signup count.
Why we picked it
Adora Cheung built Homejoy, a cleaning marketplace, and here she is blunt that you should run the marketplace by hand first: schedule manually, call the providers yourself, handle payments yourself until you have done it fifty times. That is your do things that do not scale advice applied to an operational, offline heavy marketplace. Watch it if your marketplace involves real world services, not just listings.
Why we picked it
A talk on making those first critical hires, with the repeated point that early hiring is mostly selling, not filtering. Watching it helps a founder who has only ever bought agency hours understand what it takes to attract a permanent builder. It pairs well with the written YC library pieces above.
Why we picked it
Hale lays out how to set up working relationships and explicit processes so a team collaborates well instead of relying on everyone being in the same place at the same time. The framing of agreeing up front on how you work together is exactly what keeps a distributed team accountable. Watch it to design the operating agreement your remote team runs on.
Why we picked it
Garry Tan was a designer before he was an investor, and here he tells founders exactly how much design to care about and when. He argues clarity and usability matter far more than beauty at the early stage. It is the most direct answer to how much design you really need from someone who has funded hundreds of startups.
Why we picked it
A tight reminder that the only two jobs early on are building and talking to users, which is how you learn fast whether a feature is landing or dying. Talking to users honestly is how you get the evidence to promote a feature fairly, then judge it. Short enough to watch before your next build-or-kill decision.
