r/YCInsights

Based on public analysis, solo founders have acceptance odds that are roughly five times lower than founding teams.

But after looking through founders who beat those odds, I noticed they share a few characteristics that make the "solo founder" label much less relevant.

1. They had already built products people actually used.

Not just startup experience or the ideas. They had a track record of shipping products into the hands of real users. MagicBell's Hana Mohan had spent nine years building products before YC. Mattan Griffel had already launched multiple products before creating One Month Rails.

2. Their traction was unusually strong for one person.

Not "I have a few hundred users."

More like:

• MagicBell was delivering 1M+ notifications every month before YC.
• One Month Rails already had 2,000+ students.
• Anja Health already had paying customers, despite being built with contractors.

The common pattern was traction that looked difficult for a single founder to achieve.

3. They knew their customers inside out.

Because they were doing every demo, every support conversation, and every sales call themselves, they could explain customer problems with a level of detail that's hard to fake. Being solo had become an advantage because it forced them closer to the customer.

4. They answered the "team" question with a plan, not an argument.

None of them tried to convince YC that solo founders are better. Instead, they had a clear idea of who they'd hire next, what skills they were missing, and how the company would grow beyond one person.

My takeaway isn't that YC doesn't fund solo founders. The average solo founder is competing against teams.The solo founders who get accepted often look like they've already accomplished what an early team would normally accomplish together.

If you're building solo, where do you think your evidence is strongest? Is it your product, your traction, your customer knowledge, or something else? & what is that..

YC sends three types of rejection emails. Most founders think there is only one type. Here is how to distinguish them and what each one means.

Type 1: "Thank you for applying to Y Combinator. After careful consideration, we have decided not to fund your company at this time."

This is the screening rejection. You did not make it past the initial read. The application was not strong enough to warrant deeper evaluation. This is not a judgment on your idea or your capability. It means your application did not pass the 90-second screen.

Type 2: "Thank you for applying to Y Combinator. We won't be moving forward at this time, but we encourage you to apply again in a future batch."

This is the most misread rejection in startup history. The phrase "encourage you to apply again" is not a consolation phrase. It is a specific signal that means: we saw something worth seeing and we want to see more of it. A partner voted yes on at least one dimension. Come back with more evidence on the dimension that was not yet there.

Type 3: A rejection that contains specific language about your company. Any rejection email that mentions your specific product category, your specific market, or a specific concern is a rejection that was written by a human who engaged with your application specifically. These rejections are rare and extremely valuable. They tell you exactly what the concern was.

The action for each type:

• Type 1: improve the application structure and surface evidence.
• Type 2: identify what was missing, go build it, reapply in three to six months.
• Type 3: address the specific concern directly, reapply with the answer to the specific question.

Most founders treat all three the same way. That is why most founders who reapply make the same mistakes.

Which type of rejection have you received and have you taken the specific action that type requires?

The answers that did not work

"I work better alone." This is an answer about preference, not about execution capability.

"I haven't found the right co-founder yet." This sounds like you are working on finding one, which is fine, but gives no evidence about your solo execution capability.

"I have strong advisors who fill the co-founder role." Advisors are not a founding team. Partners know this.

Long defensive explanations about why the solo path is actually better. Defensiveness signals that you know this is a weakness and are trying to hide it.

The answers that worked, from documented cases:

"I am building this solo. Here is what I have built in eight months (show specific revenue or specific customers). My plan is to hire a [state this specifically] when I reach (Share your milestone here). I have two conversations ongoing with people I have worked with previously. Here is one of them: [first name, what they did at what company, why I am talking to them].

This answer does four things. It is direct. It provides evidence of solo execution capability. It demonstrates a specific plan for the team question. It names a real person with real context.

The formula: direct + evidence + specific plan + named person.

Not one of these alone. All four together.

Its really been fun to group this YC solofounder case studies together, happy to share those case studies.... if anybody need it...

Not what YC says in their FAQ. What founders describe when they are honest about why they think they did not get in.

Reason one: the application described aspiration rather than reality. Future tense everywhere. "We plan to," "we will," "we believe that." The founders had not yet built the thing they were applying to build.

Reason two: the traction section had vanity metrics. Signups, waitlist size, app downloads, press mentions. None of these are evidence that someone paid money for something real.

Reason three: the "why now" was a trend, not an event. "AI is transforming every industry" is not a why now. The specific API release that dropped costs by 80% six months ago is a why now.

Reason four: the team section read like LinkedIn profiles. Credentials without domain observations. Experience without specific insight.

Reason five: the market size was from a Gartner report. "$50 billion total addressable market." Not calculated from a specific customer count times a specific willingness to pay. Borrowed from a report about an entire industry.

Reason six: solo founder with no answer to the team question. Not "solo founder" as the problem. Solo founder who had not thought through the co-founder conversation, the hiring plan, or what compensating evidence existed for the execution risk.

Reason seven: the idea was good but the evidence was not there. Good idea plus zero customer conversations equals a vision pitch. YC is funding companies, not visions.

The uncommon rejection reason that appears in the most honest post-mortems: the founders had not talked to enough customers to know whether their product was solving a real problem.

Which of these seven reasons is most likely to be in your current application and what would change if you fixed it?