How to Answer "Why Are You the Right Team for This?" at YC

The question has two layers:

Layer 1: Do you have an unfair insight into this problem? Can you see something about this problem — its real cause, its actual user, its overlooked solution path — that someone without your specific background would not see? Your insight should be a direct function of your specific life experience, not something anyone could derive from market research.

Layer 2: Can you execute on that insight? Do you have the specific skills, relationships, or access needed to build and sell this product to this user? Your execution ability should also be a direct function of your specific background — domain relationships, technical depth, distribution access — not generic startup competency.

Both layers must be answered. An answer that covers insight without execution ability leaves a critical question open. An answer that covers execution without insight leaves partners wondering if you truly understand the problem you are solving.

Structure every "why are you the right team?" answer in four sentences:

Sentence 1 — Your personal origin with the problem Name the specific experience that gave you insight into this problem before you decided to build a company around it. The more specific and personal, the more credible.

Sentence 2 — What that experience revealed that others cannot see Name the specific non-obvious thing you learned from that experience. This is your insight. It should be something that could only be known by someone with your specific background.

Sentence 3 — The specific execution advantage you have from that background Name a concrete asset your background gives you: a relationship network, domain knowledge that reduces your sales cycle, regulatory access others do not have, or technical depth that lets you build something competitors cannot.

Sentence 4 — The evidence that you have already used this advantage Name a specific outcome that could only have happened because of your specific background. A customer acquired in 48 hours through a relationship. A distributor partnership that took 2 weeks instead of 6 months. A regulatory approval that took 4 months instead of 18.

Full example: "My cofounder spent 6 years managing inventory operations for Apollo Pharmacy's Maharashtra network — he saw firsthand that 80% of stock losses happen because the person managing inventory is not the pharmacist but a family member using WhatsApp who never touches the desktop software. That insight is why we built entirely on WhatsApp — no app, no login, no training required. His relationships with 14 of Maharashtra's 20 largest pharmaceutical distributors mean we get onboarding meetings in 48 hours that a competitor starting today would spend 18 months trying to get. Six weeks after launch, all 14 of those distributors have agreed to pilot our returns integration — something that has not happened for any other pharmacy software company in the state."

That answer is 110 words, under 45 seconds, and covers all four components with specific, verifiable evidence.

THE DOMAIN EXPERT FOUNDER

You spent years working inside the industry you are now disrupting. Your evidence:

• Specific years in the specific role

• Specific relationships that give you distribution access

• Specific internal knowledge that shapes your product decisions in ways competitors cannot replicate

• Observable outcome that proves the advantage is real (time to first customer, time to regulatory approval, time to distribution partnership)

"I ran pharmacy operations at Apollo for 6 years. I know every distributor relationship manager in Maharashtra personally. Our first 8 customers came from one WhatsApp message to my personal pharmacy owner network."

THE PERSONAL EXPERIENCE FOUNDER

You experienced the problem yourself — as a user, a patient, a customer, a student. Your evidence:

• The specific moment you experienced the problem

• The specific cost or consequence you personally incurred

• The specific research you did after that moment that revealed the problem was systemic

• The specific insight you have that no one without your experience would have

"My father has run a pharmacy in Nashik for 22 years. I watched him lose ₹1.8 lakh last year to expired medicines he did not know were about to expire. That experience is why I can describe the exact emotional moment — late Sunday night, finding boxes of expired stock — that every pharmacy owner in our user base has lived. No product we evaluated was built for that specific moment."

THE RESEARCH-DRIVEN FOUNDER

You came to this problem through systematic research — not prior domain experience, but extraordinary user research that produced a genuine insight. Your evidence:

• Number of user interviews (must be high — 60+ for this profile to be credible)

• The specific non-obvious insight you discovered that could only come from those interviews

• At least one piece of behavior-based pre-commitment evidence (someone who asked to pay, who took an action without being prompted)

• Evidence that your insight has been embedded into specific product decisions

"Neither of us has a pharmacy background. We compensated by doing 80 user interviews over 6 weeks across 3 cities. Interview 34 was when it clicked — a pharmacy owner in Aurangabad showed me his notebook and said 'I only find out about expired stock when I'm throwing it away.' That statement appears in 43 of 80 interviews, almost word for word. No software we evaluated is built for that specific moment of discovery. Ours is."

THE SERIAL DOMAIN FOUNDER

You built a company in this space before — it may have succeeded, may have failed, but you have deep domain credibility from having operated in this market. Your evidence:

• What you built before, what it achieved, why it ended

• The specific thing you learned from that company that shapes how you are building this one

• The domain network and customer relationships you carry from the previous company

• Evidence that those lessons are embedded in your current approach in a specific and observable way

"We built Karyalay HR for Indian SMEs from 2020 to 2023 — reached ₹1.2Cr ARR before shutting down when we failed to convert SMB customers to enterprise. The core lesson: SMBs in India do not have an IT person to manage software. Every product decision in this company is filtered through that constraint. Our WhatsApp-native approach is a direct result of 3 years of watching Indian SMB owners struggle with software that assumed desktop literacy they did not have."

The reason "why are you the right team?" is hard is the same reason most applications are weak on founder-problem fit: many founders chose their problem through market research or opportunity identification rather than through direct personal experience. There is nothing wrong with that — it is a valid way to find a problem. But it makes the "why you" question structurally harder to answer compellingly.

If you came to this problem through research rather than experience, your answer must do more work. The research depth must be exceptional (60+ interviews). The insight must be genuinely non-obvious (something that contradicts the conventional understanding of the problem). The pre-commitment evidence must be strong (not just people who liked the idea, but people who took an action). And the execution advantage must be something you have actually built — not something you plan to build.

The founders who answer this question best, regardless of their background, share one characteristic: they can describe a specific moment when they understood something about the problem that changed how they thought about it. That moment is the foundation of the answer. Find yours. Name it specifically. Build the rest of the answer around it.

Partners ask this question in several different forms. Prepare for all of them:

• "Why are you the right people to build this?"

• "What is your unfair advantage?"

• "Why will you succeed where others have failed?"

• "What do you know about this problem that a competitor starting today wouldn't know?"

• "Why haven't well-funded teams already solved this?"

• "What about your background specifically makes you the right founder for this?"

Each variation probes the same underlying question from a different angle. Your answer should be consistent across all of them — the same core insight, the same execution advantage, the same specific evidence. What changes is the framing. Practice responding to all six variations until your answer is consistent, concise, and natural regardless of which version you receive.