YC Application Q&A Analysis
Date: 2026-07-24 Purpose: Analyze YC application questions and patterns in successful applicants’ answers
Key YC Application Questions (15)
Part 1: Basic Information
Q1. What is your company going to make?
- Describe the product in one sentence
- The more specific, the better
- “AI platform” → “AI that auto-fills customs forms for Korean exporters”
Q2. Why did you pick this idea to work on?
- Personal connection
- Market insight
- “Why now?” timing
Q3. What will you do first if we give you money?
- Plan for the first 3 months
- Concrete milestones
- MVP + securing first customers
Part 2: Team
Q4. Who are the founders?
- Names, roles, backgrounds
- Emphasize core strengths
Q5. How long have you known each other?
- Depth of the relationship
- Shared experiences
- Proof of trust
Q6. What are your roles?
- Clear division of responsibilities
- Complementary skills
- CEO/CTO distinction
Q7. Are you open to relocating to San Francisco?
- YC is SF-based
- “Yes” is the right answer
- If there are visa issues, explain them
Part 3: Market & Product
Q8. Who are your users?
- Concrete personas
- Market size
- Approach/channel
Q9. What’s new about what you’re making?
- Differentiation
- What’s different from existing solutions
- Technical edge
Q10. What are your competitors?
- Honestly acknowledge competitors
- Points of differentiation
- Avoid “we have no competitors”
Q11. How will you make money?
- Business model
- Pricing strategy
- Unit economics
Part 4: Traction & Progress
Q12. What have you built so far?
- MVP, prototype
- Demo link
- Technical achievements
Q13. Do you have revenue?
- Exact figures
- MRR/ARR
- Growth rate
Q14. How many users do you have?
- Active user count
- Growth trend
- User feedback
Q15. What’s the most impressive thing you’ve done?
- Side projects
- Technical challenges
- Founding experience
Patterns in Successful Applicants’ Answers
1. “What is your company going to make?”
Good answer:
"We're building AI that auto-generates customs
documentation for cross-border traders in Asia.
Currently, exporters spend 8+ hours per shipment
on paperwork. We cut it to 10 minutes."
Pattern:
- A concrete problem (customs documentation)
- A clear target (cross-border traders in Asia)
- The pain point quantified (8 hours → 10 minutes)
- Avoid being abstract (“AI platform for trade”)
2. “Why did you pick this idea?”
Good answer:
"I'm from Korea and served in military logistics.
I saw firsthand how painful cross-border paperwork
is. My co-founder studied accounting and
built fintech tools. We realized this is a $300B
problem with no good digital solution in Asia."
Pattern:
- Personal experience (military logistics)
- Team connection (co-founder’s accounting background)
- Market size ($300B)
- “Why us” (unfair advantage)
3. “What will you do first?”
Good answer:
"Month 1: Interview 50 Korean exporters, build
waitlist. Month 2: MVP for one document type
(commercial invoice). Month 3: Beta with 10
customers, iterate based on feedback."
Pattern:
- Concrete milestones (50 interviews, 10 beta customers)
- A staged approach (starting with one document type)
- Customer-centric (iterating on feedback)
- Avoid being vague (“build the platform”)
4. “Who are your users?”
Good answer:
"Primary: Korean SME exporters shipping to
Southeast Asia (50,000+ companies). Secondary:
Freight forwarders who handle documentation for
multiple clients. We'll reach them through KOTRA
(Korea Trade-Investment Promotion Agency)
partnerships and trade associations."
Pattern:
- A concrete segment (Korean SME exporters)
- Market size (50,000+ companies)
- Go-to-market (KOTRA partnerships)
- Secondary market (freight forwarders)
5. “What’s new about what you’re making?”
Good answer:
"Existing solutions like Descartes and Flexport
focus on US-Europe routes and cost $500+/month.
We're building for Asia-specific regulations
(Korean customs, ASEAN import rules) at $50/month.
Our AI is trained on 10,000+ Korean trade documents."
Pattern:
- Named competitors (Descartes, Flexport)
- Clear differentiation (Asia-specific, pricing)
- Technical edge (trained on 10,000+ documents)
- Pricing strategy ($50 vs $500)
6. “What’s the most impressive thing you’ve done?”
Good answer:
"I built a side project that auto-translates
Korean web novels into English using LLMs. It
gained 5,000 users in 3 months with zero marketing.
I also led a military logistics team of 20 people,
managing $2M in equipment across 5 bases."
Pattern:
- Concrete results (5,000 users, 3 months)
- Proof of technical skill (LLM side project)
- Leadership (military logistics team)
- Impact quantified ($2M in equipment)
Special Tips for Idea-Stage Teams
What to emphasize when you have no traction
1. Fast execution
"I built an MVP in 2 weeks using [tech stack].
It's not perfect, but it works. Here's the demo:
[link]"
2. Market research
"I interviewed 30 potential customers. 25 said
they'd pay $X for this solution. Here are their
names and companies."
3. Technical achievements
"I published a paper on [topic] at [conference].
I also have 3 patents pending in [area]."
4. Relevant experience
"I worked at [company] where I saw this problem
firsthand. I know the market because I lived it."
Tips for International (Korean) Founders
1. Be clear in English
- Avoid complex Korean-specific concepts
- Frame things in a context YC partners can understand
- “Military service” → “military service, led logistics team”
2. Sell the Korean market
- Korea is a perfect testbed
- Small but cutting-edge
- Potential for global expansion
3. Visa/relocation plan
- Be clear about your SF relocation plan
- Be upfront if there are visa issues
- “We’ll figure it out” → give a concrete plan instead
Common Mistakes
1. Too abstract
“We’re building an AI platform for businesses” “We’re building AI that cuts customs paperwork from 8 hours to 10 minutes for Korean exporters”
2. Exaggerating market size
“This is a $1 trillion market” “There are 50,000 Korean SME exporters spending $2B annually on documentation”
3. Dismissing competitors
“We have no competitors” “Flexport does this for US-Europe at $500/month. We’re Asia-specific at $50/month”
4. Unclear team roles
“We both do everything” “I’m CTO building the AI. My co-founder is CEO handling sales and partnerships”
5. Overstating traction
“We have tons of users” “We have 50 beta users, 10 paying $50/month”
Sample Tailored Answers for a Non-Traditional-Background Team
Q: “What is your company going to make?”
"We're building AI that automates cross-border
trade documentation for Asian exporters. Currently,
shipping from Korea to Southeast Asia requires
8+ hours of paperwork per shipment. We cut it
to 10 minutes with AI trained on Asian trade
regulations."
Q: “Why did you pick this idea?”
"I'm from Korea, served in military logistics,
and studied engineering. I saw how painful
cross-border paperwork is. My co-founder studied
accounting and built fintech tools. We realized
Asia's $7.9T trade market has no good digital
documentation solution."
Q: “What will you do first?”
"Month 1: Interview 50 Korean exporters through
KOTRA partnerships. Month 2: Build MVP for one
document type (commercial invoice). Month 3:
Beta with 10 customers, iterate. Target: $5K MRR
by month 4."
Q: “Who are your users?”
"Primary: Korean SME exporters to Southeast Asia
(50,000+ companies). Secondary: Freight forwarders.
We'll reach them through KOTRA, trade associations,
and Korean exporter communities."
Q: “What’s new about what you’re making?”
"Flexport and Descartes focus on US-Europe at
$500+/month. We're Asia-specific (Korean customs,
ASEAN regulations) at $50/month. Our AI is trained
on 10,000+ Korean trade documents. No one else
does this for Asia."
Q: “What’s the most impressive thing you’ve done?”
"I built [side project] that gained [X users]
in [timeframe]. I also led a military logistics
team of 20 people, managing $2M in equipment.
My co-founder built fintech tools processing $400K
in cards annually at a Fortune 500 bank."
Key Takeaways
- Specificity wins — numbers, names, links
- A personal connection — why this problem
- Fast execution — MVP, demo, waitlist
- Honesty — be upfront if you lack traction
- Team synergy — why you two
Next step: write the actual application, get feedback