How to Apply to Y Combinator: A Founder'S Guide
You apply to Y Combinator by submitting the online application at ycombinator.com, a short written form plus a one-minute video and, for most founders, a live demo link. It takes a few hours to complete, and there is no fee. The application is your one shot to show founders who ship fast and evidence people want what you have built.
This guide walks through every part of the process: what YC weighs, how to answer the written questions, the demo, the video, the timeline, and how to show traction even if you are early. If you want the deep dive on the evaluation criteria first, read our breakdown of what YC looks for in startups.
What Does YC Actually Look For?
YC applies a short, high-weight rubric rather than a long checklist. The four things that matter, in rough order, are exceptional founders, real momentum or traction, a compelling and clearly-explained idea, and a unique insight about why now. The idea ranks lowest of the four, which surprises most first-time applicants.
The founders dominate the decision. YC invests at a stage where the product will almost certainly change, so partners underwrite the people who will navigate that change. They look for speed of building, clarity of thought, domain insight, resilience, and a co-founder relationship that can survive stress. After the team comes traction, which we cover in detail below. The application form, the demo, and the interview all exist to surface those same signals, so everything you submit should point at them.
How Do You Write the YC Application?
The written application is the highest-leverage document you will write as an early founder. It is short, but every field is read, and answers are scanned for evidence, not adjectives. The core principle: answer with specific facts and numbers, and delete anything that could apply to a hundred other startups.
Here is how to approach the main sections:
- What are you building? One plain sentence a stranger understands. No jargon, no category words like "platform" or "AI-powered" unless they are load-bearing. If you cannot say it in one sentence, you do not understand it well enough yet.
- Who needs it and why now? Name the specific person with the problem and explain what changed in the last couple of years that makes this the moment. The timing answer matters more than most founders expect.
- Progress so far. This is the evidence section. Give real numbers: users, weekly growth, revenue, retention, waitlist signups. If you have nothing shipped, describe the prototype and who has actually used it. "We built X in three weeks and have 40 weekly active users, up from 10 last month" beats "we have strong interest."
- Why you and your co-founders? Show domain insight and speed, not resumes. State the earned secret you have about this market that most people do not, ideally from living the problem yourself.
- The "what do you understand that others do not" question. Answer with a concrete, non-obvious insight. A generic market summary here is a red flag.
One mechanical tip: write in the first person and use the founders' actual names in the founders section. Applications that read like a press release lose clarity. Have a stranger read your draft out loud; wherever they stop to ask "what does this mean," you have found a sentence to fix.
What Makes a Strong Demo?
If you have a product, the demo is where reviewers verify that your "we build fast" claim is real. The bar is simple: show a working product with real usage, not a mockup, not a landing page, and not a narrated slide deck.
Reviewers poke at the same few things. Does the product actually work end to end, or does the demo carefully avoid the broken parts? Are the users real, or fabricated test accounts? Does the founder understand every screen deeply enough to explain the choices behind it? The fastest way to lose credibility is to show a demo that only works on a happy path you rehearsed. Instead, show the real product, including the rough edges, and talk plainly about what is working and what you are still fixing. Honesty about the state of the build reads as a founder who is not bluffing.
If you are pre-product, a working prototype with a few committed users beats a polished slide. Ship something small and real rather than waiting to make it perfect.
How Should You Film the Video?
The one-minute video is not a marketing asset. It is a fast way for reviewers to meet the founders and see the product. Keep it simple: point the camera at yourselves, introduce who you are, state what you are building in one sentence, and show the product on screen. Skip intros, music, and animated logos.
Common failures to avoid:
- Too long or too vague. One minute, three sentences max of setup. If the reviewer does not know what you do in the first fifteen seconds, you have lost them.
- Founders not shown. Reviewers want to see the people. A voiceover over stock footage defeats the purpose.
- Reading a script. Prepared is fine; wooden is not. Speak naturally and with energy about the problem you live with.
- No product. If the product exists, it should appear. Screen-record a real flow rather than describing it.
- Overproduction. Polish signals misplaced effort. A clean phone or laptop recording is enough.
When Should You Apply and What Is the Timeline?
YC runs two batches a year, one starting in winter and one in summer, with applications due a few months before each. The exact dates change each cycle and are posted on ycombinator.com. Apply when you have something real to show, not on a fixed date; YC's own advice is to apply even if you are early, because the application forces clarity and you can apply again later.
A typical timeline looks like this:
| Stage | What happens | What to do |
|---|---|---|
| Application window | Form opens weeks before the deadline | Draft answers, record the video, gather real numbers |
| Submit | Apply by the published deadline | Have a stranger proofread; check the demo link works |
| Review | Partners read applications for a few weeks | Keep shipping; do not wait idle for a reply |
| Interview | Ten minutes, fast, often adversarial | Know your numbers cold; practice rapid answers |
| Decision | Usually the same day or within days | Accepted or not, use the feedback to improve |
For the interview, prepare by knowing your metrics from memory and practicing one-sentence answers to "what do you do," "why you," and "what are your numbers." YC expects speed and directness over polish, and a founder who hesitates on their own numbers reads as unprepared. The full question bank is covered in our YC interview questions guide.
How Do You Show Traction If You Are Early?
This is where most founders stall. YC cares about momentum more than absolute size, and it accepts pre-launch companies, but you still need some evidence that people want the thing. The good news is that early traction can be manufactured with focused effort, and the quality of that effort is itself a founder signal.
Start with the cheapest real signals. Get a handful of users onto a working prototype and log what they do. Run a waitlist and measure signups per week. Collect letters of intent or design partners who have committed time, not just said "sounds cool." Report the growth rate, not the total: going from 5 to 30 users in a month is more compelling than being flat at 500.
A focused marketing, content, and SEO motion is one of the most reliable ways to manufacture that early pull. Publishing content that ranks for the exact problems your users search for brings you warm, compounding traffic; a simple lead or signup path turns that into a measurable growth number you can put in the application. It is not about vanity metrics - it is about creating a credible growth narrative before the product is large enough to grow on its own. For a step-by-step on building that signal, see how to show traction to investors and marketing for accelerator startups. If you need help running that motion, Stackmatix helps venture-backed startups build marketing traction - and a stronger application along the way.
What Mistakes Sink YC Applications?
Most rejections trace back to a small set of avoidable errors. Fix these and you are ahead of most of the field:
- Vague answers. "Disrupting the X industry" with no numbers, no users, no specifics. Replace every adjective with a fact.
- No evidence. Claims of demand with nothing to back them. Screenshots, numbers, and user quotes are your currency.
- Copying other applications. The format is public, and reviewers read thousands. A template answer reads as a template founder.
- Applying too early without a real build. An idea with zero prototype and zero users is a hard pass unless you have an exceptional founder story. Ship something small first.
- Hiding the rough edges. Overclaiming traction or a demo that only survives a happy path. Reviewers have a sharp filter for spin, and a small real number beats a big invented one.
- Fumbling the one-sentence description. If you cannot say what you do in a single clear sentence, that is the first and last impression reviewers get.
Frequently Asked Questions
Can You Apply to YC More Than Once?
Yes, and you should. Many founders apply in one batch, get rejected, keep building, and are accepted in a later batch. Rejections are common even for strong startups, and YC explicitly encourages re-applying after you have made real progress. Each application also forces you to clarify what you are building and what the numbers actually say, which is valuable regardless of the outcome. The key is to re-apply with meaningful new evidence, not the same application resubmitted.
Do You Need Traction to Get into YC?
No, but you need momentum or a very strong founder story. YC accepts pre-launch companies and has funded many teams with zero revenue. What matters is evidence that people want what you are building, which can be a working prototype with a handful of users, a growing waitlist, or letters of intent. A steep growth rate on small numbers beats a large flat number. If you have nothing at all to show, a genuinely exceptional founding team with a sharp insight can still get in, but the bar is much higher.
How Long Is the YC Application?
The written form is short - roughly 40 questions, most answerable in one or two sentences, plus a one-minute video. Plan to spend a few focused hours drafting, then revise over a couple of days. The questions are designed to be quick to read and quick to answer, but the quality of your answers is what matters, so do not rush the substance. Many founders find the act of writing it clarifies their own thinking even before submission.
What Happens After You Submit the YC Application?
Partners review every application over a few weeks. A small fraction of applicants are invited to a ten-minute interview, often remote or in person. The interview is fast and direct, and decisions typically follow within hours to days of it. If you are not invited, you will generally get a short, polite note, and you are welcome to apply again in a future batch. In the meantime, keep shipping - the best thing you can do while waiting is improve your numbers.