The best code in the room loses if the demo crashes or the pitch rambles. Judges have seen 30+ presentations by the time they see yours. You have 3 minutes to be memorable. Here’s how.
The 3-Minute Pitch Structure
0:00-0:20 – The Hook (Problem)
“X million people face Y problem. Today it takes Z to solve it.”
One sentence. One statistic. Make the judge feel the pain.
0:20-0:40 – The Solution (What You Built)
“We built [name] – it does [one sentence description].”
Don’t explain HOW yet. Just WHAT it does. The demo shows the how.
0:40-2:30 – Live Demo (Show It Working)
This is THE most important part. Show:
- User opens the app (first impression)
- User performs the core action (the ONE thing it does)
- Result/output that proves it works
Talk while demoing: “As you can see, the user simply [action] and gets [result].”
2:30-2:50 – Tech + Impact
“Built with [stack]. Uses [AI model/notable tech]. This can help [X people] save [Y hours/money].”
2:50-3:00 – Close
“Thank you. We’re [team name] and this is [product name].”
Stop talking. Don’t say “yeah, that’s it” or “so… any questions?”
Demo Do’s and Don’ts
DO:
- Use realistic test data (Indian names, real addresses, actual content)
- Demo on the actual device (phone if mobile, projected laptop if web)
- Have someone else operate while you narrate
- Show error handling (“and if the user enters wrong data, we show this helpful message”)
- Record a backup video before presenting
DON’T:
- Open code editor (judges don’t care about code during demo)
- Show the terminal/console (that’s debugging, not presenting)
- Say “it’s not working right now but normally it does…”
- Demo features that are half-built (show what WORKS perfectly)
- Go over time (judges literally stop listening)
When the Demo Crashes (It Happens)
- Don’t panic visibly – stay calm, judges respect composure
- Switch to backup video – “Let me show you a recorded demo while we fix this”
- Explain what SHOULD happen – walk through with screenshots
- Resume live if it comes back – shows resilience
What Judges Actually Write Down
- Does it work? (yes/no – most important)
- Would real people use this? (practical value)
- Is the UX intuitive? (first impression)
- Is the tech interesting? (innovation)
- Can this scale? (impact potential)
Notice: code quality, algorithm complexity, lines of code are NOT on this list. Judges care about the PRODUCT, not the code.