Free resource
The YC Startup Launch Checklist
A tactical checklist to gain clarity, validate faster, and ship sooner. Work through the steps below to validate your idea, learn from users, and decide what to build next. Also included: a curated guide to the YC application with tips and example answers.
What you'll learn quickly
- How to validate your idea in the next 48 hours
- What to focus on during early validation
- What to ask users to uncover real pain
- How to build the smallest MVP that proves value
- How to generate early momentum fast
- Mindsets that help you move fast without chaos
Part 1
YC Startup Launch Checklist
Ensure you're solving a real, painful problem. Work through each section in order.
1
Problem foundation
Ensure you're solving a real, painful problem.
YC principle: Great startups are built on real problems, not ideas.
- Define the user problem in one clear sentence: Write the core pain point from the user's perspective. Keep it concrete, specific, and emotion-linked rather than abstract.
- Identify your primary user segment (be specific): Narrow it down. Instead of "founders," say "solo SaaS founders with no technical cofounder who struggle with validation."
- Confirm it's a "hair-on-fire" problem, not a nice-to-have: Evaluate urgency. Would they try imperfect hacks today? Would they pay or spend time to solve it immediately?
- List 3 ways users solve this today (their current workaround): Identify real alternative behaviors. Workarounds show how painful the problem is and reveal opportunities to outperform them.
- Write a simple "Why now?" explanation: Strong startups have timing advantages. Describe what changed: technology, habits, regulations, costs - that makes your solution timely.
2
Founder clarity (10-minute exercise)
Align your thinking before building anything.
YC principle: Clarity reduces wasted months.
- Write your startup hypothesis (Problem → User → Value → Channel): Form a simple, testable statement about what you believe. Think of this as your temporary "north star"; it guides your first 2 weeks of decisions.
- Identify your riskiest assumption: This is the one assumption that, if wrong, collapses the idea. Calling it out early helps you design faster tests around it.
- Define your "One Metric That Matters" for the next 30 days: Pick only one metric (not 3). It should measure real progress, like engagement, repeat use, or user conversations, not vanity numbers.
- Write your temporary unfair advantage (even if small): Identify something that gives you early leverage: domain knowledge, access to users, speed, or insights others don't have.
3
Fast validation experiments
Replace guesses with real data within 48 hours.
- Talk to 3–5 potential users (no surveys; real conversations): Aim for real stories. Conversations reveal motivations and frustrations you'll never see in survey checkboxes.
- Collect problem stories instead of feature requests: Users describe problems better than they describe solutions. Look for patterns in what frustrates them today.
- Ask: "How do you solve this today?": Workarounds are gold. They show willingness to act and highlight gaps your MVP can fill immediately.
- Check willingness to pay (even if hypothetical): Frame this gently; you want to see if the pain has monetary value, not to pressure them into committing.
- Extract 3 insights from each conversation: Summarize what you learned. The strongest insights are emotional, behavioral, or repeated across users.
Insight log (fill this after each conversation)
- Key patterns:
- Motivations:
- Pain points:
- Decision triggers:
4
Build the simplest MVP
Create the smallest version that proves value.
YC principle: If you're not embarrassed by your MVP, you launched too late.
- Remove 90% of your original feature ideas: Strip the product down to its proof-of-value core. Every extra feature slows you down without increasing validation.
- Define one core action the user must complete: This is the backbone of your MVP. Everything should guide the user toward completing this action.
- Build a version that takes < 48 hours (manual/no-code acceptable): Speed matters. Use no-code, docs, or even manual operations - the goal is learning, not engineering.
- Define "MVP success criteria" before shipping: Make this measurable. e.g., "3 users complete the core action twice in a week." It prevents emotional decision-making.
- Plan one experiment to get the first 10 users: Keep it simple - DM people, post in niche communities, reach out directly. Early acquisition must be scrappy.
5
Create early momentum
Move users from interest → engagement → learning.
YC principle: Momentum is a strategy. Startups win by learning faster than everyone else.
- Set up a simple waitlist (email only): One field is enough. Lower friction increases sign-ups and keeps the loop fast.
- Share a small teaser with your audience (friends, communities): Don't overthink this. Share your problem statement or mockup. Early interest validates your direction.
- Start capturing insights from every sign-up: Every user tells you something; track patterns, motivations, and expectations.
- Document 10 insights + 3 decisions made: Insights are useless until they influence what you build. Write decisions clearly and commit to them.
- Celebrate a small win (keeps momentum high): Momentum prevents founder burnout. Acknowledge progress to stay motivated and consistent.
6
Founder mindsets (daily reminders)
Essential habits that help you move fast and learn. Learn by doing.
- Move fast, talk to users faster
- Ship before you feel ready
- Focus on one thing that moves the metric
- Prioritize learning over perfection
- Kill ideas that don't drive progress
Part 2
YC Application Guide
A curated guide to the YC application: what to emphasize, how to answer each section, and what strong answers look like. Answer directly, use facts and numbers, and tell a cohesive story.
High-level recommendations
- Answer questions directly, clearly, and concisely: Base your responses on facts and numbers. Use simple language and avoid marketing buzz. Most answers should be 1–5 sentences long.
- YC invests in people, so focus on your team and what makes each of you exceptional.
- Share insights and obstacles that you discovered while working on the idea.
- Good application should be a cohesive, compelling story.
- Last, but not least: be honest.
This guide curates lessons from publicly available YC content and from insights shared by YC-backed founders. Needle is not affiliated with Y Combinator.
Learn more
Validate with real conversations
See what potential customers are already asking for - across Reddit, HN, GitHub and more.
Cancel anytime