June 11, 2026 · 12 min read · by Iris Wei

Competitor Research for YC Founders (2026): what to skip, what to track weekly

In W7 of a recent YC batch, a founder I was advising came back from partner office hours rattled — their partner had asked one question they couldn't answer: "who specifically did your last 3 customers switch from?" They had a 40-tab competitor analysis doc; they didn't have that one fact. This post is the founder-stage workflow I send people now, tuned for batch pace.

What the YC application question is actually testing

The competitor question in the YC application is famously brief, and founders tend to over-engineer the answer. The partners are testing two things, and only two:

1. Self-awareness — do you know the landscape, or have you convinced yourself you're unique?
2. Specificity — can you name 2-3 specific products, not categories?

The shape that works: two sentences naming 2-3 specific competitors, plus one sentence on your wedge. Anything longer and you're padding. Anything that says "we have no competitors" gets you rejected — it's the strongest "this founder hasn't looked" signal in the application.

"X and Y both target [ICP] with [approach]. Z does [adjacent thing]. Our wedge is [specific structural advantage], which compounds because [reason]."

That's the entire answer. Save the depth for the interview.

The three questions partners actually ask

In partner office hours, the competitor conversation lands on three recurring questions, in roughly this order:

1. "Who's the most obvious competitor?" — testing whether you know they exist. Have a 90-second answer per named competitor.
2. "What about [adjacent / substitute they think you might miss]?" — testing how wide your peripheral vision is. The competitors you forgot to name are more damaging than the ones you named.
3. "Who specifically did your last 3 customers switch from?" — the highest-signal question. It forces concrete founder-level distribution data — not market research. This is the question to be ready for above all others.

Most founders prepare exhaustively for #1 and #2 and get sandbagged on #3. The fix: keep a running 2-column note. Customer name | what they used before us. Update it after every customer onboarding.

Pre-batch baseline (8-10 hours, do this before W1)

Use the structured template from our 10-step competitive analysis post. Specifically:

1. Strategic question: "where should we compete and where should we avoid?" — the answer drives positioning for the entire batch
2. 5-7 competitors: 2 direct, 2 adjacent, 1-2 substitutes
3. Strategic matrix: positioning, primary channel, pricing model, ICP, founder distribution
4. Wedge identification: one dimension you can dominate
5. Compete/avoid decision: per competitor
6. Wedge → 12-week sprint commitment: 2-3 actions that operationalize the wedge across the batch

Write the wedge sentence somewhere your batchmates will see it (Slack pin, doc header). It becomes the filter for every decision during batch.

In-batch weekly check (30 min/week)

The weekly version of the template — designed to fit a Friday slot before group office hours:

1. 5 min — open each competitor's pricing page in tabs, eyeball-diff against last week
2. 10 min — scroll each competitor founder's X account for new launches / threads / positioning shifts
3. 5 min — check Product Hunt's "Upcoming" page for any of your tracked competitors
4. 5 min — update the "who-did-your-last-3-customers-switch-from" note
5. 5 min — write 1 sentence: "the most relevant competitor signal this week is X" — share with batchmates if useful

If nothing changed, the answer is "nothing changed" — that's a valid output. The 30-min slot exists to make sure you're not missing changes, not to manufacture insights when there aren't any.

Demo Day prep (2-3 hours, W11-W12)

The competitor slide in your Demo Day deck — what works, in order of importance:

1. 2-3 named competitors, not categories. Logos help; words help more.
2. One sentence per competitor explaining their wedge — yes, theirs, not yours. Shows you understand why they exist.
3. Your wedge in one sentence, positioned against theirs.
4. One concrete customer-switching example (anonymized if needed). The most persuasive evidence in 30 seconds.

Skip: feature matrices (boring), TAM-with-pie-charts (suspect), "no real competitors" (instant skepticism), bullet-point lists of differentiators (sounds like marketing).

The 4 traps that waste batch-time

1. Researching competitors as customer-conversation avoidance. Competitor teardowns feel productive and require zero awkward emails. They are not a substitute for the only research that moves PMF — direct customer conversations. If you spent more hours on competitor analysis than user interviews in a week, the ratio is wrong. Hard rule: every hour on competitors earns you at least 2 hours on customer conversations that week.
2. Over-tracking small competitors. Tracking 12 competitors weekly is a tax that doesn't pay back. 5-7 is the right number. If a competitor isn't material enough to track at 30 min/week, they're not material enough to make your slide.
3. Paying for enterprise CI tools during batch. Crayon and Klue start at four-figure monthly contracts and assume dedicated CI headcount. Free Google Sheet + Wayback + SimilarWeb preview gets you to Demo Day. A multi-source aggregator like Analook at $29/mo is reasonable if the weekly check is taking >1 hour; anything more is buying tools for problems you don't have.
4. Treating the wedge as fixed. The wedge you picked W0 should be refined or replaced if customer evidence in W4-6 contradicts it. Founders who hold the wedge despite contradictory signal usually fail their W10 partner review. The wedge is a hypothesis, not a commitment.

The one data point that tells you you're winning

Across maybe 30 YC founders I've worked with, one signal predicts whether the competitor question goes well at Demo Day better than any other: can you name 3 customers, by name, who switched to you from a specific competitor?

If yes — confident, specific, with a one-sentence reason per switch — investors lean in. If no, the entire competitive narrative reads as theoretical, no matter how thorough the analysis.

This is also why the customer-switching note is the single most important artifact from any competitor research workflow. Everything else — matrices, Wayback diffs, traffic estimates — supports that note. Without it, the rest is decoration.

Tools I'd actually use during YC batch

You don't need anything else. If a tool isn't in this table, it's almost certainly the wrong tool for batch-stage founder use.

The one-page summary I keep on my desk

Weekly: 30 min Fri. Check pricing pages, founder X accounts, PH Upcoming. Update customer-switching note. Write one sentence on the most relevant competitor signal this week.

Wedge: One sentence. Pinned in Slack. The filter for every roadmap decision.

Demo Day: 3 logos. 1 sentence per competitor's wedge. 1 sentence on yours. 1 customer-switching example. Skip everything else.

Hard rule: Every hour on competitor research = 2 hours on customer conversations this week.

The question: "Who specifically did your last 3 customers switch from?" Be ready.