Demo Video

The video’s one job

Demo clarity and documentation carry five Lock 3 points, but the video’s real weight is indirect: it is how evaluators experience your working functionality before touching the live link. One continuous take of the real product doing the real loop is worth more than any motion-graphics intro. No intros longer than fifteen seconds. No stock music drowned narration. Show the thing working.

A structure that works

• 0:00–0:30 · The problem, concretely: who, what situation, what cost
• 0:30–1:00 · Your solution in one sentence, then straight into the product
• 1:00–3:30 · The core loop, live: real input, real processing, real output — narrate what the AI is doing
• 3:30–4:15 · The evidence: your impact metric, your accuracy numbers, your pilot observation
• 4:15–5:00 · Limitations and what comes next

Honesty rules

• Screen-record the actual product — no mock-up passed off as software
• If a step is slow, cut the wait but say so ("trimmed 20 seconds of processing")
• Show at least one failure or low-confidence state handled well
• Every claim in the video should be verifiable in the repo or live link

Practical quality bar

A quiet room, a readable screen recording at 1080p, and narration by a team member who knows the build. Phone-recorded audio in a hostel corridor loses information, not points for glamour. Upload where evaluators can stream without permission requests, and test the link in an incognito window.