How to Write a Y Combinator Application: The 13-Point Blueprint (With Examples)

by
Illustration of a startup founder throwing a paper airplane towards a Y Combinator sign, symbolizing the submission of a Y Combinator application.
Don’t Keep This to Yourself

The Y Combinator application is not a traditional pitch; it is a brutal test of clarity. Every batch, YC partners read tens of thousands of applications, and the vast majority are rejected for one simple reason: the founders cannot clearly explain what they actually do. They hide a good business behind layers of corporate jargon instead of explaining the actual mechanics of their startup.

If you want to get funded, you must abandon marketing speak and adopt the exact evaluation framework championed by leaders like Garry Tan. YC partners do not want a beautifully crafted story. They want undeniable facts, hard traction numbers, and extreme precision with zero fluff.

Here is the exhaustive, 13-point blueprint answering every critical section of the YC application. Follow this strict structure, study the exact examples, and adopt this level of detail to ensure your application survives the review process.

1. The One-Liner (The “What”)

The Rule: Explain your startup literally. Do not use marketing speak, acronyms, or buzzwords. The Reason: YC partners spend about five seconds on your one-liner. If a smart high schooler cannot understand exactly what you do immediately, they will stop reading.

  • Bad Example: “We are building an AI-powered B2B ecosystem for workflow optimization.”
  • Good Example: “We make software that helps local bakeries process their payroll in 10 minutes instead of 4 hours.”

2. Founder Details & Team Dynamics (The “Who”)

The Rule: Highlight execution speed, technical ability, and unique market insights. The Reason: YC funds relentless people, not just good ideas. They want concrete evidence that you can build fast and sell aggressively without waiting for permission.

  • Bad Example: “We are passionate, visionary leaders with extensive corporate management experience.”
  • Good Example: “John built the entire backend in 48 hours. Sarah cold-called 100 independent plumbers to secure our first 10 paying customers.”

3. Technical Capabilities (Who Writes the Code?)

The Rule: Prove that the founding team builds the core product entirely in-house without relying on outsourced agencies or non-founder contractors. The Reason: YC primarily funds technology companies. If you cannot write the code yourselves, you cannot iterate fast enough to survive. Outsourcing your core technology is a massive red flag.

  • Bad Example: “We hired an external development agency to build our initial MVP, and we are currently looking for a technical co-founder to take over.”
  • Good Example: “David wrote the entire backend in Python. Sarah built the iOS app natively in Swift. 100% of the codebase was written by the founding team.”

4. Co-Founder Bonding and Trust

The Rule: Demonstrate a deep, pre-existing relationship between co-founders with a history of building things together. The Reason: Co-founder disputes are the number one reason early-stage startups fail. Solo founders seeking partners are a risk; established, tight-knit teams are highly fundable.

  • Bad Example: “We met three weeks ago on a networking app and are still looking for a third co-founder to handle our enterprise sales.”
  • Good Example: “We were college roommates for four years and built two profitable side projects together before starting this company. We are not looking for additional co-founders.”

5. Equity Distribution (The Cap Table)

The Rule: Divide equity equally (or extremely close to equally) among the founding team. The Reason: YC partners view wildly unequal equity splits as a predictor of failure. It indicates that you do not value your co-founders as true peers, which almost always leads to a breakup.

  • Bad Example: “I came up with the idea, so I have 85%, and my technical co-founder who writes all the code has 15%.”
  • Good Example: “We have two co-founders and the equity is split exactly 50/50 with a standard 4-year vesting schedule.”

6. Domain Expertise (Why Did You Pick This Idea?)

The Rule: Prove you have an “earned secret” about this specific problem that outsiders do not have. The Reason: YC wants to know why your team is uniquely positioned to solve this. Real domain expertise prevents you from building a solution for a problem nobody actually has.

  • Bad Example: “We chose to build AI for healthcare because the total addressable market is $4 trillion and it is ripe for disruption.”
  • Good Example: “I worked as an ER nurse for 7 years. I personally spent 3 hours every shift dealing with manual coding errors, which is exactly why we built this.”

7. The “Hacked” Question

The Rule: Describe a time you showed extreme resourcefulness outside of writing code. The Reason: Startups require finding loopholes when the default answer is no. YC wants to see your “hacker spirit” and ability to solve problems creatively.

  • Bad Example: “I guessed my neighbor’s wifi password and used their internet.”
  • Good Example: “I found a legal loophole in my university’s policy to get $5,000 worth of free server hosting for my side project.”

8. Traction and Progress (The Evidence)

The Rule: Use the inverted pyramid structure. Put your hard metrics in the very first sentence. The Reason: Numbers prove real demand. Adjectives prove absolutely nothing. YC partners are looking for builders who talk to users, not presenters who make slide decks.

  • Bad Example: “We have significant interest from the market and are growing very fast.”
  • Good Example: “We launched 14 days ago. We currently have 400 active users, and 12 of them have paid a $50 deposit.”

9. Distribution Strategy (How Will You Get Users?)

The Rule: Explain your exact, manual, unscalable strategy to get your first 100 or 1,000 users. The Reason: Claiming that your product will “go viral” or relying on paid ads on day one shows you do not know how to hustle. YC wants founders who will do things that do not scale.

  • Bad Example: “We will run targeted Facebook ads and rely on word-of-mouth marketing for viral organic growth.”
  • Good Example: “We are physically walking into 50 local dental offices in our city this week to pitch the software directly to the receptionists.”

10. The Business Model (How Will You Make Money?)

The Rule: State the simplest possible mechanism for charging users right now. The Reason: YC hates convoluted, theoretical business models. They want to know you have the courage to ask users for money immediately, rather than giving it away for free forever.

  • Bad Example: “We will offer it for free, gather big data, and eventually monetize through targeted enterprise advertising partnerships.”
  • Good Example: “We charge a simple $50/month SaaS subscription per user.”

11. Competition and Substitutes

The Rule: Name your massive competitors directly. Explain exactly why your specific users hate them. The Reason: Claiming you have “no competition” is a massive red flag. It shows you have not researched the market or you are solving a problem that does not exist.

  • Bad Example: “We have no competitors because our proprietary AI algorithm is completely unique.”
  • Good Example: “Salesforce exists, but our users (independent plumbers) find it far too expensive and complex. We win purely on simplicity.”

12. Alternative Ideas (The Pivot Test)

The Rule: List actual, viable alternative ideas you would genuinely work on if this startup fails. The Reason: Being overly romantic about one specific idea is dangerous. YC wants to fund formidable founders who will pivot and survive, not founders who will quit if their first idea dies.

  • Bad Example: “We have no other ideas because we are 100% committed to making this specific product work no matter what.”
  • Good Example: “If this fails, we would build a vertical SaaS for landscaping companies, or an API tool for cross-border payroll.”

13. The Unwritten Rules of the Founder Video

The Rule: Keep it under one minute, use zero scripts, and do zero editing. The Reason: YC wants to see how you communicate naturally as a team. A highly produced video feels like a corporate commercial, not a startup pitch.

  • Bad Example: A highly edited 3-minute commercial with background music and B-roll footage.
  • Good Example: A raw, 45-second smartphone video where the founders plainly state who they are and exactly what they are building.

Essential Resources: Successful YC Application Examples

Do not just take our word for it. The best way to understand the extreme precision YC demands is to study the applications of founders who actually got funded. Here is a curated list of real, accepted YC applications and official video examples to benchmark your own against:

Accepted Written Applications:

Official Founder Video Examples:

Top YouTube Masterclasses to Help Your Application:

The Application Ends Here. Your Startup Doesn’t.

Before you submit the application, review every single sentence. Ask yourself: “Does this sentence prove that we are executing fast?”Getting rejected is part of the process. The application itself is designed to force you to think clearly about your business mechanics. Keep building your product, keep talking to your users, and re-apply for the next batch with better metrics.


Don’t Keep This to Yourself