First Customers Before YC: A 3-Month Demand Plan

The odds favor a small proof

You are deciding whether to apply to Y Combinator (YC) now or spend the next three months building demand. The Summer 2026 YC cycle drew 47,000 applications, compared with 32,000 two years earlier. YC's admit rate for that batch was under half a percent. The small proof is the first move: show that someone would use what you are building.

Each YC batch draws over 10,000 applicants, while the company issues only 150 to 200 offers. After late 2024, YC shifted from two batches per year to four. More batches make the calendar matter.

You do not need a polished product to improve your odds; you need a signal a stranger would recognize: small enough to build quickly, clear enough to explain in a short answer.

Build the proof in the order you will use it

Apply now if you already have a demand signal you can show; otherwise, use this three-month checklist to build one. The rule is simple: one demand signal, a reapplication date three months out, and the interview-stage offer rate as your target.

• Pick the one demand signal you can show. Say a number out loud: a waitlist count, a paid pilot, a scheduled call, or a refund rate. Start with the user who already feels the problem. Ask what they do today, what it costs them in time or money, and what would make them switch. Write the answer in their words; that becomes the sentence you will use in the application. A larger waitlist with no follow-up is weaker than a small group that can explain why they care.
• Set the reapplication date before you start. Put a calendar entry in place for the next batch you can target after a no. A rejection now delays reapplication by roughly three months rather than six. Use that date as a deadline, not a hope. Work backward from it. Decide what you will have learned by the end of each week, and what you will stop doing if the signal does not improve.
• Make the interview-stage offer rate your target. Check the target against your own numbers. At the interview stage, YC admits 200 to 250 companies from an estimated 800 to 1,200 interview invites per batch, a 20% to 30% conversion. That target changes how you prepare: show a pattern where someone has a problem, you have a response, and the response is being used.
• Run the smallest committed test. Get a small group of users to say they would keep using it, or get them to pay. Name the users, or keep the test open. Offer the smallest version of the help you can deliver by hand: a spreadsheet, a shared document, a scheduled review, or a manual service. See whether the user returns when the novelty fades. When they ask for it again, you have a signal. When they go quiet, you have a lesson. Either way, write it down before you move to the next step.
• Write the demand proof as a short note. The note should hold the signal, the users, the next step, and the date you will reapply. Keep it short enough to read in a hurry. Put the signal first, then the users who created it, then the next action you will take. Stop editing when a reader can repeat the proof after a quick pass.

Let the proof set your next application date

Applicants who can show real user demand are three to five times more likely to convert at YC than applicants who have not built a product. The proof comes before the application because it gives you a short interview answer you can defend.

Use the note to shape the application. Lead with the signal, not the market size. Show who the users are, what they did, and what you learned. Then show the next step you are ready to take.

A weak proof still leaves the next batch ahead. Put the date in your calendar, then run the next test.