YC application example: accepted vs rejected answers (2026)

The strongest YC application example answers replace vague claims with one verifiable fact per sentence. Vague one-liners get rejected. Concrete metrics, named customers, and shipped features get reads. This guide rewrites the four highest-stakes fields, the one-liner, what you're building, traction, and founders, from vague to partner-grade specific.

Most rejected YC applications fail in the same four fields, and almost always for the same reason: the founder wrote in adjectives where partners expect numbers. A good YC application example is not a longer answer. It is the shortest answer that names the customer, the job, the magnitude, and the mechanism in one sentence, then proves it with three more.

How to write a YC application example that gets in

The seven moves that separate a read from a skip:

1. Answer the literal question first, then add context. Partners read top-down and stop early.
2. Quantify everything you can. Replace "many users" with "47 paying users, $4,200 MRR as of last week."
3. Name customers by industry, not by adjective. "Two NYC dental practices" beats "early adopters in healthcare."
4. Strip every adjective from your one-liner. If a word does not change what you build, cut it.
5. State what you have shipped, not what you will ship. Future tense kills credibility.
6. Show founder-market fit in one sentence. Why you, specifically, are the right person to build this.
7. Be honest about competitors. Saying "no competitors" is a near-instant rejection signal per the YC Library.

YC one-liner examples: vague vs specific

The one-liner is the field partners read first. It decides whether they read the rest.

✅ Good: "We help dentists bill insurance claims 8x faster using AI that reads x-rays and auto-fills CDT codes." Names the customer, the job, the magnitude, and the mechanism.

❌ Bad: "We are reinventing healthcare billing with an AI-powered platform that streamlines workflows." Zero specifics. Could be any of fifty companies.

The pattern: customer + job + magnitude + mechanism, in one sentence. If you cannot name all four, you have not narrowed enough.

What you're building: from buzzwords to mechanism

This field rewards mechanism, not category. Partners want to know what the software actually does, not which buzzword it sits next to.

✅ Good: "A Chrome extension that scrapes Shopify checkout pages and writes 3 personalized upsell offers into the merchant's email tool within 30 seconds of cart abandonment."

❌ Bad: "An AI-driven personalization engine that helps Shopify merchants increase revenue through intelligent upsell automation."

The good answer tells a partner exactly what to look at if they install the product tomorrow. The bad answer could describe any of two hundred Shopify apps.

Traction: the YC application answers partners read first

Once the one-liner clears the bar, partners jump straight to traction. Numbers or counts only, no adjectives.

✅ Good: "Launched June 2025. 312 paying users, $11,400 MRR, 18% week-over-week growth for the last 6 weeks. 4 of our 312 users pay us over $500/mo each."

❌ Bad: "Strong early traction with a growing user base and significant interest from enterprise customers."

If you have no revenue, give counts: signups, weekly active users, paid pilots, LOIs with named companies. The YC Library is explicit that partners reward simple, testable statements. "Strong" and "significant" fail that test. If you have nothing yet, say so plainly and describe the test you are running this week.

The founder and "why us" question: a successful YC application signal

This is where most technical founders underrate themselves and most non-technical founders over-claim.

✅ Good: "I spent 4 years at Stripe building the dispute-handling pipeline. I have shipped 9 production payments systems. My co-founder ran ops at two dental SaaS companies and has lost personal money to the exact billing problem we are solving."

❌ Bad: "We are a passionate team of serial entrepreneurs with deep experience across fintech, healthcare, and AI."

The good version names the company, the role, the duration, and the receipt. The bad version is what a YC partner reads two hundred times a batch and stops parsing. Years matter. Shipped systems matter. Personal exposure to the problem matters more than either.

Common rejection patterns

Most YC application rejections cluster around four answers:

• The "Uber of X" one-liner. Analogy is the opposite of specificity. Describe what you do, not what you are like.
• The competition answer that says "no one." There is always a competitor, even if it is the spreadsheet your customers use today. "No competition" reads as "I have not talked to users."
• Traction described in adjectives. "Strong", "growing", "early but promising" all fail. Use numbers or counts.
• Founder section without receipts. "Passionate", "experienced", "domain expert" without naming the company, the role, and the years.

A clean YC application example clears all four. If a partner has to guess what you mean in any field, you have rewriting to do before the deadline.

FAQ

What does a good YC application look like? A good YC application answers each question with the fewest words that contain the most verifiable facts. Partners want customer names, dollar amounts, week-over-week growth rates, shipped features, and concrete founder receipts. Anything that could appear in another founder's application is a sign you have not narrowed enough.

How do you answer the YC one-line question? Use the pattern customer + job + magnitude + mechanism in one sentence. Name who you serve, what you do for them, how much better than the status quo, and the specific software mechanism. Strip every adjective. If a partner cannot picture the product after reading the one-liner, rewrite it.

What makes a YC application get rejected? Four patterns dominate rejections: a buzzword one-liner that hides what you actually do, a competition answer that claims you have none, traction described in adjectives instead of numbers, and a founder section without role, company, and year receipts. Most rejected applications combine at least two of these.

How specific should YC answers be? More specific than feels comfortable. Replace "many users" with the exact count and the date you measured it. Name customers by company and industry, not by adjective. The YC Library explicitly says partners reward simple, testable statements, which means anything a partner could verify in 30 seconds.

How do you describe traction on a YC application? Lead with the single number that best represents your progress, then the date you measured it, then the trend. For revenue companies, that is MRR plus week-over-week growth. For pre-revenue, use weekly active users, paid pilots, or named LOIs. If you have nothing yet, say so plainly and describe the test you are running this week.

Related on the hub

• How to apply to 500 Global in 2026 — Related accelerators guide.
• How to apply to Sequoia Arc in 2026 — Related accelerators guide.
• How to apply to South Park Commons in 2026 — Related accelerators guide.