How to run a demo day for student builders
· buildtolaunch
This guide is for student organizers who want to close a build day, a club semester or a program with a demo day, and for team leads who have to present at one. You get a run of show, timing rules, a stage setup that works with no budget and a checklist for the day. For the bigger picture, see the guide to build days and builder communities.
Short answer
A demo day is a short public session where each team shows what it built, live, in a few minutes. For a student event, give each team 3 minutes, show a working link, keep one presenter per team and end with a vote or a round of feedback. Plan about an hour for 12 to 15 teams, and send the recap within two days.
What a demo day is (and what it is not)
A demo day is the end-of-program moment when teams show finished work to an audience. Startup accelerators run them for investors. Student organizers run them for classmates, mentors and sponsors.
The two are different. Y Combinator's own advice for its investor demo days says the goal is to earn a follow-up meeting, and it advises against relying on live demos in that setting. A student build day is the opposite: the working app is the point. Borrow the discipline from investor events (hard time limits, a clear first sentence, one speaker) and keep the live demo.
| Investor demo day | Student demo day | |
|---|---|---|
| Audience | Investors | Peers, mentors, sponsors, family |
| Goal | A follow-up meeting | Show real work, get feedback, build momentum |
| Live demo | Often avoided | The main event |
| Typical pitch | 5 to 10 minutes plus Q&A | 3 minutes |
Pick the right length
Converve, an event-networking company, says the working standard for investor pitches is 5 to 10 minutes plus 3 to 5 minutes of Q&A, and that an audience absorbs about four strong pitches per hour. Student events can go much shorter. CodePath's student demo day protocol, for example, gives each group 3 minutes and asks teams to rehearse at least three times.
A simple plan for a 90-minute session (our suggestion):
| Time | What happens |
|---|---|
| 0:00 to 0:10 | Welcome, rules, how voting works |
| 0:10 to 1:10 | 15 demos at 3 minutes each plus 1 minute to change over |
| 1:10 to 1:20 | Voting or audience feedback |
| 1:20 to 1:30 | Results, thanks, date of the next event |
If you have more than 15 teams, run two rooms or two sessions. Attention drops after about an hour of back-to-back demos.
Run of show, step by step
- Set the order a week early. Collect each team's lead presenter, project name and link, in a shared sheet. CodePath's protocol asks groups for a repo link, a short description and a designated lead presenter before the day, which is a good model.
- Test the projector and Wi-Fi the day before. Open every link from the presenting laptop. A link that works on a phone but not on the venue Wi-Fi is the most common surprise.
- Brief the presenters 15 minutes before. Explain the timer, the order and where to stand. Ask the next team to wait at the side.
- Use a visible timer. A phone on a stand works. Give a 1-minute warning, as CodePath does with a chat message at the 1-minute mark.
- Introduce each team in one line. The host says the project name and who it is for. Then the team starts.
- Keep applause and changeover short. One host manages the transition so the next team is ready.
- Close with a vote, then the next date. Do not let the energy fade while you find the winner.
What each team does in 3 minutes
Ask every team to follow the same shape:
- One sentence: "[Project] helps [who] do [what]."
- The problem, in one example: a real person or situation, not a market-size slide.
- The live demo: open the link and complete the main task.
- What is next: one thing they will do this week.
YC's guidance adds useful rules for any pitch: say plainly what you do first, avoid jargon, avoid dense slides (more than about seven words per slide is too many, it suggests) and choose one person to present rather than switching speakers.
CodePath's protocol offers a good fallback for demos: use one slide plus the app itself, and start from the home screen, not the login screen. Ask every team to record a short backup video in case Wi-Fi fails. For help with recording, see Quay video demo app 60 giây (Vietnamese) and the 3-minute pitch and demo script (Vietnamese).
Voting and feedback
Choose one of these:
- Audience vote: every attendee picks their favorite project. Simple and fun, but it favors popular teams.
- Panel with a rubric: three judges score with a judging rubric template. Fairer, but you need to recruit the judges.
- Feedback only: no winner. Each attendee writes one useful comment per demo. Good for first-time events.
At Vibe-a-thon Saigon, buildtolaunch used a public vote on the Launch League board instead of judges. The full story is in the Vibe-a-thon Saigon recap.
Who to invite
A demo day with only the participants feels like a rehearsal. Invite people who will react to real work:
- classmates who did not take part (they become next semester's builders)
- mentors and lecturers who helped
- sponsors or tool partners, so they see what their support produced
- friends and family, who often become the first real users
Tell guests what to do: try the apps, ask one question, leave one comment.
After the demo day
Within 48 hours, send the recap: a list of every project with its link, a few photos if people agreed, a thank-you to partners and the date of the next session. Converve's own playbook for investor demo days uses a 48-hour window for follow-up introductions and a review at day 90; student events can borrow the rhythm with a recap in two days and a check-in a month later. A template is in event recap template, and after the event: measuring whether your build day worked shows what to count.
Checklist for the day
- Order and links collected in one sheet
- Projector, adapters and Wi-Fi tested with every link
- Timer visible to presenters
- Backup video for each team
- One host, one timekeeper, one person managing transitions
- Voting method explained at the start
- Recap and next date ready to post
Want the surrounding event too? The checklist and timeline for hosting a student hackathon or build day covers the six weeks before.
How buildtolaunch fits in
buildtolaunch is a free community for university students, open to any major, with no coding needed to start. Teams that built in project Spaces with an AI teammate can post their finished project to the weekly Launch League, which gives a demo day a public link to point to afterwards. You can also check the events page for student sessions and opportunities for student programs.
FAQ
What is a demo day?
A demo day is a short public session where teams show what they built, usually at the end of a program, hackathon or build day. Accelerators run them for investors, and student organizers run them for peers, mentors and sponsors. The best ones have strict time limits and a working demo.
How long should each team's demo be?
For student events, 3 minutes is a good default. CodePath's student demo day uses 3 minutes per group. Add about a minute for changeover, and leave questions for the end or for a networking break.
Should teams use slides or a live demo?
Use a live demo of a working link, with at most one slide for the one-sentence pitch. Investor demo days often avoid live demos, but at a build day the working app is the proof. Always keep a recorded backup in case Wi-Fi fails.
How many teams can present in one session?
About 12 to 15 at 3 minutes each fits in an hour. Converve estimates an audience can absorb roughly four strong investor pitches per hour, but those pitches are far longer. Beyond 15 teams, split into two rooms or two sessions.
Do we need judges and prizes?
No. You can run a demo day with an audience vote or with feedback only. Add judges and prizes when you have a clear rubric and enough fair judges. See the rubric template linked above.
What should we do right after the demo day?
Post a recap within two days with every project link, thank your partners and announce the next date. Invite teams to keep building and to post their project publicly. The longer you wait, the less likely people are to return.