Applications · 14 min read
YC Application Mistakes That Get You Rejected Immediately
Short answer
Most YC rejections are not close calls. Partners reading 50,000 applications per batch develop pattern recognition fast. Certain mistakes signal "not ready" within the first two fields and the rest of the application rarely recovers. This page documents the 18 most common mistakes — drawn from patterns across public founder accounts, YC partner commentary, and analysis of rejected vs accepted applications.
The Core Principle Behind Every Mistake
Every mistake on this list comes from the same root cause: the founder is thinking about what sounds impressive instead of what is true and specific.
YC partners are not looking for the most ambitious application. They are looking for the most credible one. Credibility comes from specificity. Vagueness — even well-written, confident vagueness — reads as a signal that the founder does not yet have a real grasp on what they are building.
Keep that principle in mind as you read each mistake.
Mistakes That Kill Applications in the First Two Fields
MISTAKE 1: WRITING A VISION STATEMENT INSTEAD OF A COMPANY DESCRIPTION
The 50-character field asks what your company does. Most founders write what they want to become.
Version that gets rejected: "Transforming the future of healthcare in emerging markets" Version that gets an interview: "Teleconsultation platform for rural Indian patients"
The second version is citable. A partner reading it knows immediately what the product is, who uses it, and roughly what problem it solves. The first version says nothing a partner can use.
MISTAKE 2: LEADING WITH MARKET SIZE
The most common opening mistake in the full application: "The global [X] market is worth $[Y] billion and growing at [Z]% CAGR."
YC partners know market sizes. They do not need you to quote a Gartner report. What they need is evidence that you understand your specific user, your specific problem, and your specific solution. Market size context can come later in your answer. It should never be your opening sentence.
MISTAKE 3: USING THE WORD "PLATFORM"
"Platform" is the single most overused word in YC applications. It is almost always used to avoid describing what the product specifically does.
Replace every instance of "platform" with what the product actually does:
- "HR platform" → "payroll and benefits software"
- "Healthcare platform" → "online doctor consultation booking"
- "Fintech platform" → "credit scoring for gig workers"
If you cannot replace "platform" with something specific, that is a signal you need to think harder about your product description.
Mistakes in the Traction and Validation Fields
MISTAKE 4: DESCRIBING TRACTION VAGUELY
"We have several customers who are very excited about the product" is a sentence that has appeared in thousands of rejected applications.
Every traction claim needs a number. Every number needs a unit.
- "Several customers" → "11 paying customers"
- "Growing quickly" → "47% MoM growth over the last 3 months"
- "Strong retention" → "Month 2 retention of 91%"
- "Early interest" → "340 waitlist signups from a single Reddit post"
If you have no traction yet, say so directly and substitute interview data: "We have no revenue yet. We've conducted 63 user interviews across Pune and Nashik in the past 8 weeks."
MISTAKE 5: CITING MARKET RESEARCH INSTEAD OF USER EVIDENCE
"According to a 2024 McKinsey report, 78% of SMBs in India face significant challenges with [X]..." is not evidence that people want your product. It is evidence that a consultant thinks the market is big.
YC wants founder-generated evidence: conversations you had, things users told you, behavior you observed, money someone paid you. Third-party market research signals that you haven't done the work yourself.
MISTAKE 6: CLAIMING "NO COMPETITION"
Every application that claims no competition raises a flag. If there is truly no competition, either the market doesn't exist or no one has noticed the opportunity yet — both are concerning signals.
The right answer acknowledges competition specifically and explains your differentiation specifically.
"The main alternatives are Rx30 and PharmaTrack. Both are built for large pharmacy chains with dedicated IT staff. Neither works on a phone. 90% of our users tell us they tried one of these and gave up within a week. We are built mobile-first, WhatsApp-native, and require zero training."
This answer tells partners you know the landscape and you have a real reason to exist.
MISTAKE 7: CONFUSING INTEREST WITH DEMAND
"We showed 50 people our product and they all said they loved it" is not traction. People say they love things they will never pay for.
YC looks for demand signals: money exchanged, repeated usage, referrals, people asking when they can have access. "Loved it" is not one of these.
If you have actual demand signals, lead with the strongest one. If you only have interest signals, label them as such and be honest: "We have 200 waitlist signups but no paying customers yet. Our first sales conversations start next week."
Mistakes in the Founder and Team Fields
MISTAKE 8: DESCRIBING YOUR BACKGROUND WITHOUT TYING IT TO THIS PROBLEM
"10 years at McKinsey + 5 years at Goldman Sachs" is an impressive background. Without context, it is also irrelevant to a pharmacy software company.
Every background detail you include should connect to why it makes you specifically well-suited to build this specific product.
"I ran operations at a 240-bed hospital in Pune for 4 years and watched pharmacists manually reconcile stock every night. That direct observation is why I know exactly which features matter and which ones pharmacy owners will never use."
The credential plus the connection to the problem is what makes the background section work.
MISTAKE 9: NOT EXPLAINING COFOUNDER EQUITY IMBALANCES
A 70/30 or 80/20 equity split is not automatically a red flag. An unexplained 70/30 split is.
If your equity is not equal, explain it in one sentence: "Priya has 60% because she conceived the idea 18 months before I joined and spent a year doing market research full-time before I came on board."
Partners are not asking you to justify the number. They are asking you to demonstrate that you've had the conversation and that both founders are aligned.
MISTAKE 10: DESCRIBING A COFOUNDER RELATIONSHIP THAT STARTED RECENTLY
"We met 3 months ago at a startup meetup and decided to start a company together" is one of the riskiest cofounder stories you can tell YC.
YC invests in teams, and cofounder conflict is one of the top reasons YC companies fail. A short cofounder relationship history puts the burden on you to show exceptional complementarity and alignment.
If your cofounder relationship is short, compensate by showing you have already worked through hard decisions together: "We've been working together for 4 months, but in that time we've already navigated a major product pivot and fired our first hire. We know how we handle conflict."
MISTAKE 11: HAVING NO COFOUNDER AND NOT ADDRESSING IT
Solo founders do get into YC. But solo founders who don't address the question in their application miss an opportunity.
If you are a solo founder, acknowledge it and show you've thought about it: "I'm building this alone currently. I've made this decision deliberately — I want to reach $50K MRR before bringing on a technical cofounder so that I have leverage in the equity conversation. I am actively looking through YC's cofounder matching program."
That answer is more credible than silence on the topic.
Mistakes in the Vision and Insight Fields
MISTAKE 12: COPYING YC'S OWN LANGUAGE BACK TO THEM
Applications that include phrases like "we want to make something people want" or "we do things that don't scale" signal that the founder has read Paul Graham essays but hasn't yet developed their own thinking.
YC partners wrote those phrases. They know them. Using them back signals surface-level engagement with YC's philosophy rather than deep thinking about your own startup.
MISTAKE 13: AN INSIGHT THAT IS ACTUALLY A MARKET OBSERVATION
The "what do you understand about this business that others don't" field is the field most commonly filled with market observations masquerading as insights.
Market observation (not an insight): "The Indian pharmacy software market is fragmented and dominated by legacy players with outdated UI."
Real insight: "Every pharmacy software company builds for the pharmacist-in-charge who has a desktop computer. The actual person who manages stock in 80% of independent pharmacies is a family member — often a spouse or adult child — who uses a smartphone and communicates via WhatsApp. No software is built for that person. We are."
The real insight identifies a specific mistake in how competitors have framed the user and explains exactly how you've framed it differently.
MISTAKE 14: FUTURE TENSE ANSWERS TO PRESENT TENSE QUESTIONS
"How do you know people want this?" is a present tense question. Answering it in future tense — "we plan to conduct user interviews" or "we will validate through a pilot program" — signals that you haven't done this work yet.
YC funds founders who have already started. If you haven't validated demand yet, you are not ready to apply.
Process and Submission Mistakes
MISTAKE 15: SUBMITTING WITHOUT HAVING SOMEONE EXTERNAL READ IT
The single cheapest improvement you can make to your application is having someone unfamiliar with your startup read every answer and tell you what questions each answer raises.
Founders know their own context. They write assuming the reader shares that context. Every assumption the reader doesn't share is a confusion that weakens your application.
MISTAKE 16: APPLYING TOO EARLY
The best time to apply to YC is when you have something to show. That is not necessarily revenue — it can be prototypes, user research, interviews, pilot agreements. But it is not an idea in a slide deck.
Applying with just an idea is a statistical waste of your application unless your founder-problem fit story is exceptionally compelling. Most ideas-only applications do not have that level of story.
MISTAKE 17: INCONSISTENCY BETWEEN THE WRITTEN APPLICATION AND THE VIDEO
If your written application describes one business and your video describes a slightly different one — different user, different problem, different metric — partners notice. It reads as a team that has not aligned on what they are building.
Before submitting, watch your video and read your application in the same sitting. Make sure they tell the same story.
MISTAKE 18: NO CLEAR ASK
The final field of the YC application asks why you are applying to YC. Most founders write a generic answer about mentorship and network.
A specific answer signals strategic thinking: "We're applying to YC because we need two things in the next 6 months: introductions to hospital and pharma distributor networks that would otherwise take us 2 years to build, and pressure-testing from partners who have seen supply chain startup failures we haven't."
Partners have seen thousands of startups that needed exactly what you need. The more specifically you can name it, the more confidently they can picture how they'd help.
How to Audit Your Application Against This List
Go through your application field by field. For each one, check:
- Is there at least one specific number?
- Is there no instance of "platform," "solution," or "ecosystem"?
- Is every traction claim in past tense with a concrete unit?
- Is every background claim connected to this specific problem?
If you clear all four checks on every field, your application is in the top 20% of what YC receives.
Keep reading
More on Applications
How to Write a YC Application That Gets an Interview in 2025
10 min read
YC Application Word Limits — What to Write in Each Field
11 min read
How to Answer "What Is Your Company?" on the YC Application
10 min read
YC Video Essay Tips — What YC Partners Actually Want to See
11 min read
Founder Stories
Want the real version of these answers? Read long-form, source-linked stories from actual YC founders — how they got in, what broke, what scaled.
Read Founder Stories →Go deeper
Want the full data behind this answer?
Our YC database tracks 5,000+ companies, every batch, with application patterns, founder backgrounds, and pivot stories — the raw material we built this answer on.
FAQ
Frequently asked questions
What is the single most common reason YC rejects applications?
Does YC reject applications because the idea is bad?
Is it a red flag to have failed at a previous startup on a YC application?
How does YC feel about applications from very early-stage startups with no code written yet?
Do YC partners check whether the metrics founders report are accurate?
What words and phrases should I completely avoid in my YC application?
Can I apply to YC if I already have significant revenue — say $50K MRR?
Is using AI to help write a YC application a mistake?
What is the biggest mistake founders make when describing their competition?
Should I mention my startup's valuation or previous funding in the application?
Why do so many YC applications fail at the insight field specifically?
Does the order in which you answer the YC application fields matter?
An independent resource · Not affiliated with Y Combinator · Last updated 2026-02-01