What YC Partners Look for in a 2-Minute Demo Video

YC asks applicants to optionally include a product demo link in addition to the founder video essay. The purpose is simple: show the product working. Partners reading your written application have a mental model of what your product does. The demo video confirms or complicates that mental model.

A demo video that shows a real user doing a real thing and achieving a real outcome in under 2 minutes is more credible than any written description of the same product.

A demo video that shows polished UI screens with no real usage, or that walks through features without showing a user accomplishing a specific goal, adds little value and sometimes raises concerns about whether the product is as functional as the written application implies.

Partners watching a demo video are asking four questions in the first 60 seconds:

Is this product real? Does it work? Can a user actually accomplish something with it, or is this a prototype that only works in ideal conditions?

Is the user workflow intuitive? Does the product solve the problem in a way that makes sense, or does using it require training and explanation?

Does it do what the written application says it does? Consistency between written claims and demo reality is a trust signal. Inconsistency — product does something different from what was described — is a major concern.

What does product quality reveal about the team? A clean, functional product that solves a specific problem well signals engineering judgment. A cluttered, buggy, or confusing product signals execution risk regardless of how impressive the written application is.

0:00 – 0:15 — State the problem and the user in one sentence Do not assume the viewer remembers your written application. Open the demo with context: "This is MedStock. A pharmacy owner in Pune is about to check their expiry report for the week." One sentence. Then go directly to the product.

0:15 – 1:15 — Show one complete user workflow end-to-end Pick the single most important workflow your product enables. Not the most impressive feature — the most important one. The workflow that, if it stopped working, your users would immediately notice.

Show a real user — or simulate one credibly — completing that workflow from start to finish. Do not skip steps. Do not say "and then you'd do X" and cut away. Show X happening. The completeness of the workflow demonstration is what makes the demo credible.

"Sanjay opens WhatsApp, sends our bot his daily stock count in 3 minutes. Our system flags 4 medicines that expire within 10 days. He taps to auto-generate a return request to the distributor. Done. That workflow used to take him 45 minutes with a notebook."

1:15 – 1:45 — Show the outcome data If your product produces a measurable output — a report, a saved amount, a time comparison, a retention metric — show it in the demo. This is where the product's value proposition becomes concrete and visual rather than abstract and written.

"This is Sanjay's dashboard from the last 30 days. He has flagged ₹34,000 of near-expiry stock. His expiry loss this month: ₹1,200 — down from ₹18,000 the month before he started using us."

Numbers on a screen are more credible than numbers in a written field. Show them.

1:45 – 2:00 — One sentence on what comes next Close briefly with the one feature or improvement in your immediate roadmap. This signals that the product is actively developing and gives partners a forward-looking hook. Keep it to one sentence and keep it specific.

Real data, not dummy data. Placeholder text ("Customer Name," "Product ABC," "₹0.00") signals a product that has not been used by real users. Real data — even anonymized — signals live usage and real customers.

Showing the product under realistic conditions. A demo where everything goes perfectly and loads instantly in a quiet test environment is less credible than a demo that shows a real interaction, even with minor imperfections. Partners know products are not perfect. A slightly imperfect but real demo is more trustworthy than a flawless scripted walkthrough.

No voiceover reading from a script. Narrate the demo naturally, the way you would explain the product to a potential customer in a live call. Scripted voiceover sounds like a product marketing video. Natural narration sounds like a founder who uses their own product daily.

Mobile-first demos for mobile-first products. If your product runs on mobile, film the demo on mobile. Recording a mobile app on a desktop browser simulator is a signal that you built for a use case that does not match how users actually experience the product.

Showing a complete workflow, not features. Features are what the product has. Workflows are what users do. Partners care about the latter. A feature tour ("here is our dashboard, here is our settings, here is our report") tells partners nothing about how a user solves a problem. A workflow demo ("here is how a user goes from problem to resolution in 4 steps") tells them everything.

Starting with the login screen. The login process is not part of the product experience. Start logged in. Begin immediately at the point where the user's problem is about to be solved.

Spending more than 20% of the demo on navigation menus or settings. Navigation is infrastructure. Settings are infrastructure. Value is what happens when the user does the core thing the product exists to help them do. Get to the core thing immediately.

Showing a product that contradicts the written application. If your application says your product is WhatsApp-native and your demo shows a desktop SaaS interface, partners notice. If your application says users can complete the workflow in 3 minutes and the demo takes 8 minutes, that inconsistency undermines the written claims. Align your demo with your written application exactly.

Recording in low light or poor audio. Video quality matters less than audio quality. If the narrator is hard to understand — poor microphone, background noise, fast speech — partners lose the thread of what is being shown. Reshoot with better audio before a better-looking video.

Ending without showing an outcome. A demo that shows process but not outcome leaves partners without the most important data point: did the product actually solve the problem? Always end with a visible result — a number, a completed task, a before-and-after comparison.

SaaS / web apps: Record directly from the screen using Loom or similar. Show the core workflow from the user's perspective, not the admin perspective.

Mobile apps: Film from the phone screen using a screen recording. Use a real device, not a simulator.

WhatsApp / messaging-based products: Show an actual WhatsApp conversation thread. The conversational UX is the product — show it in its native environment.

Hardware products: Show the device being used in its real context. Bench tests are less credible than field use. If your pharmacy device is used at a pharmacy counter, film it at a pharmacy counter.

Marketplace products: Show both sides of the market completing a transaction. A marketplace demo that only shows the buyer side leaves the supply-side credibility entirely to the imagination.

AI / ML products: Show the input, the processing, and the output. Do not just show impressive outputs — show the process of getting there and how a user interprets and acts on the output.