How to Write the YC Application as a Solo Founder

YC does not ban solo founder applications. They have funded solo founders across multiple batches. Their concern is specific and practical: startups fail at a higher rate when there is no cofounder to provide the second perspective, absorb emotional pressure, and cover the skill gaps that every single person has.

Paul Graham has written that a solo founder is a signal that the idea was "not compelling enough to convince anyone else to join." That framing is worth engaging with directly in your application rather than ignoring it. The founders who get in as solos either have an exceptionally strong reason for being solo or are actively working to change it.

What YC is looking for in a solo application is evidence that you have thought carefully about this and have a plan — not that you are defensively insisting you don't need a cofounder.

If you are a solo founder applying to YC, the first thing partners will look for is how you handle the cofounder question. Answer it proactively and confidently, either in the cofounder section or in a brief note in a relevant field. The worst version is silence — hoping partners won't notice you are solo. They will notice, and unanswered questions create doubt.

A strong solo founder statement:

"I am currently building this alone. This is a deliberate choice — I want to reach $25K MRR before bringing on a cofounder so I have leverage in the equity conversation and can find someone whose skills are truly complementary rather than desperate for anyone willing to join. I am actively looking through YC's cofounder matching program and have been in conversations with two potential technical cofounders over the past month."

This statement does four things: acknowledges the solo status, explains the reasoning, shows it is temporary and intentional, and demonstrates active effort to solve it.

Solo founder applications live or die on traction. Because partners cannot evaluate team dynamics, complementary skill sets, or cofounder relationship history, they weight individual evidence signals more heavily. Your traction numbers need to carry the weight that a strong team story would carry in a two-founder application.

Specifically, solo founder applications are strongest when they include:

Clear revenue with growth trajectory. Even $3K MRR growing at 20% MoM is compelling for a solo founder. It demonstrates that one person has been able to acquire and retain paying customers — a strong signal of individual capability.

Retention data. Retention is a product quality signal that does not require a team to achieve. If users are coming back week after week, that says something specific about the product regardless of how many people built it.

Quantified user research. Solo founders who have done 60-80 user interviews have demonstrated the kind of systematic customer development that YC values. Cite the number and name one or two specific things you learned that shaped your product.

Evidence of exceptional output rate. Shipping a working product alone — especially a technical one — is itself a signal. If you have built something functional and live as a solo founder, note when you started and what you have shipped. The speed-to-product ratio matters.

The right framing is not "I'm solo but it's fine." The right framing is "being solo has given me specific advantages in this situation."

For founder-problem fit stories: a solo founder who built the product because they personally experienced the problem and could not find a solution is a compelling narrative. The absence of a cofounder is consistent with the founding story — you built it yourself because you needed it yourself.

For speed and iteration: solo founders make decisions faster and ship faster in the early stages. If your traction story involves rapid iteration — "I launched, got feedback, rebuilt the core workflow in 2 weeks, and retention jumped from 30% to 71%" — that timeline is more credible when you are working alone than when you credit a team of two for the same speed.

For resource efficiency: many solo YC founders have built to meaningful revenue milestones with lower burn than comparable two-founder teams. If your revenue-to-cost structure is efficient, make that explicit — it signals that you are capital-efficient and can stretch YC funding further.

The YC application has fields specifically about cofounders: how long you have known each other, what each person brings, and the equity split. As a solo founder, these fields require direct, honest answers rather than workarounds.

"How many founders are there?" Answer: one. State it clearly.

"Tell us the most impressive thing about each founder." Write about yourself only. Do not inflate this field with advisory board members or key employees who are not cofounders. Write two specific, outcome-based sentences about yourself: what you have built or shipped, and the specific domain knowledge that makes you the right person to solve this problem.

"Are you looking for a cofounder?" If yes, say so and describe exactly what you are looking for — technical vs business, specific domain expertise, experience level. A specific answer signals that you have thought about this seriously. "I am looking for a technical cofounder with backend infrastructure experience who has worked in regulated industries" is more credible than "I am open to cofounders."

Every solo founder has skill gaps. YC partners know this and will probe for it in the interview. Before you apply, identify your 2-3 biggest skill gaps relative to what the company needs in the next 12 months and have a clear plan for each.

The most common skill gaps for solo founders:

Non-technical founder, no product built yet. This is the highest-risk profile for a solo application. Without a cofounder and without a product, the application has no evidence of execution ability. If you are in this situation, the minimum bar before applying is: a working prototype (even a no-code one), evidence of 40+ user interviews, and a specific technical cofounder you are in active conversations with.

Technical founder, no sales or customer development yet. A working product with no customers is a red flag regardless of how technically impressive it is. If you are a technical solo founder, compensate with customer evidence: interviews, paying customers, letters of intent.

Founder with domain depth but no startup experience. This is addressable through other signals — the quality of your insight, the depth of your user research, the specificity of your go-to-market plan. YC has funded domain experts who had never worked at a startup before. The key is demonstrating that your domain expertise gives you an advantage that a more experienced but less knowledgeable founder would not have.

Based on public accounts and analysis of solo YC founders, the consistent pattern is: exceptional traction relative to stage, a founder-problem fit story that is deeply personal and provable, and a clear plan to address the cofounder gap. None of the successful solo applications were passive about the solo status — they all addressed it directly and framed it deliberately.