A hackathon pitch is the short talk or recorded demo in which a team shows judges what it built, which problem it solves and why it matters. Strong ones are clear, demonstrate a working project and stay inside the time limit.
Pitching is a core skill at every event, including the online events of the covid-19 hackathon era, and this guide draws on organiser and platform advice to explain how the best presentations are put together.
What a hackathon pitch has to accomplish
A pitch has one job: help a judge who is seeing many projects understand yours quickly. Devpost, the platform behind a large share of online hackathons, notes that it is sad to stay up for three days building something awesome only to bomb the demo presentation. Its advice for avoiding that outcome is to focus on clearly explaining the project, because exhaustion and a lack of time to plan the words are the usual causes of a weak presentation.
Because the audience is usually judges moving from one team to the next, the pitch needs to work for people with no background on the project. Devpost’s participant guide on video demos adds that judges will likely review multiple projects back to back, so the opening should be a quick overview rather than a slow build-up. A team that assumes the judge already knows the problem tends to lose the first, most valuable part of its time.
In practice the pitch has to answer three questions in order. What problem does the project address? What does the working prototype do about it? What could it become after the event? Every other choice, from slide design to speaking order, supports those three answers.
A simple structure that fits a short slot
Devpost’s presentation advice breaks a live demo into three beats. The first is to quickly set the scene: explain in a few sentences the problem being solved or the status quo being improved, and keep it short and to the point. The more clearly the audience grasps the problem, the more the later demo means.
The second beat is the demonstration itself. The same guide says to decide what is important to show within the time allotted, to mention key technologies or impressive technical challenges briefly, and to skip mundane flows such as creating user credentials. It also stresses showing a resolution to the problem identified at the start, so that the audience can see what the project does and that the key components are finished.
The third beat is the close. Devpost suggests spending a sentence or two on the project’s potential and the team’s ambitions, so the audience understands its long-term impact. Together the three beats make a pitch that opens on a problem, proves a solution and ends on a future, which is a shape judges can follow even when they are tired.
- Set the scene: state the problem or the weakness of the current approach in a few plain sentences.
- Demonstrate: show the prototype working on the main path and name the technology only briefly.
- Look ahead: close on potential impact and what the team would build next.

Building the demo around what judges score
A pitch is easier to write once the scoring categories are known. Devpost’s guide to submissions says that hackathon judges score submissions against criteria set by each hackathon’s organizers, and that the usual list includes technological implementation, ease of use, demonstration, potential impact, quality of the idea and design. Because each event publishes its own list on its hackathon page, a team should read it before planning the talk.
The criteria map neatly onto the three beats. The problem statement serves quality of the idea. The live demonstration serves implementation, design and ease of use. The closing serves potential impact. Devpost’s participant advice also tells presenters to address how the project meets the judging criteria, which means asking whether it covers what the event actually requested. A pitch that is brilliant but off-theme loses ground to a plainer one that fits the brief.
The same Devpost article offers a test for ease of use: if you cannot explain how to use your project in a sentence or two, it might be too complicated. That makes a handy rehearsal check. If the one-sentence explanation does not come easily, the team likely has too many features competing in the demo. Matching each beat of the talk to a scored category is the quickest way to keep it focused.
Timing, scripts and the recorded demo video
Many events now ask for a recorded video in place of, or as well as, a live talk. Devpost’s video guide says the video is one of the first things judges look at and gives teams around three minutes to show what the project can do. It adds that most hackathons require demo videos to be less than three minutes, but that the limit varies, so the submission requirements should be checked for the exact length allowed.
Major League Hacking (MLH), which runs a student hackathon league, takes a similar line in its organiser guide. It recommends that hackers submit 2 minute videos on your submission platform for the judges to review, and it says the video should be a demo of the hack, not a presentation. The two sources agree on the principle: short, visual and focused on the project working.
A script keeps a short slot under control. The Devpost video guide quotes one competitor who plans the video by deciding how many seconds go to the introduction, the idea, the components, the demo and the closing. It also quotes a participant who advises writing the script personally, since generic text rarely describes a project better than the team can. Having decided the time split in advance, a team can cut material early instead of discovering at the end that the demo overran.
The guide also gives a scheduling warning. One participant advises teams to leave at least two or three hours before the end of the hackathon to polish, record, and upload the demo video and submission. Uploads, retakes and exports always take longer than expected, so recording is best treated as a fixed part of the schedule rather than a final scramble.
Live judging and the time per project
When judging is live, the slot is often shorter than teams expect. The MLH judging plan recommends science-fair style judging, where teams stand at their tables and judges visit one by one. In its planning formula, MLH allows 4 mins per project, which the guide splits between 2 minutes for presentation + demo and the rest for questions, scoring and judge travel. That is an organiser’s planning figure rather than a rule for every event, but it shows how little time a pitch may get.
For events that pick finalists to present at a closing ceremony, the same MLH page says to allow roughly 7 minutes per team, with a few minutes for the presentation and the remainder to set up the next group. A finalist talk therefore has more room than a table visit, but it is still brief.
| Setting | Time the organiser guide allows | What fits |
|---|---|---|
| Recorded demo video | Around three minutes (Devpost) or a two-minute demo (MLH) | Problem, working demo, one line on the future |
| Table visit by a judge | Two minutes of presentation and demo in the planning formula | One core scenario and a sentence on impact |
| Finalist stage talk | Roughly seven minutes per team including changeover | Fuller story with a short, rehearsed demo |
Figures in the table come from the MLH judging plan and the Devpost demo video guide, as of the dates those pages were read.
Making the demo reliable and memorable
Judges remember a project that worked in front of them. Devpost’s presentation guide advises skipping mundane flows and having needed text copied to the clipboard, which in practice means preparing the data and accounts before the talk starts. Running the demo locally, as one quoted participant suggests, also removes dependence on conference Wi-Fi, though a recorded fallback is wise for anything that relies on a network.
Memorable pitches also tell a short story. The Devpost video guide quotes a participant who says to tie everything back to the story, meaning what problem was solved and who the project positively affects, and to keep the video short, interesting and visually engaging. The same participant suggests avoiding slide shows, so screens should show the product rather than bullet points. Credit for teammates and the technologies used belongs in the written submission, where Devpost says the best presentations include screenshots and a video demo.
Good pitches rely on real project material, which comes from choosing a worthwhile problem in the first place. Teams still searching for a topic can browse these hackathon ideas for starting points, and projects tied to public services often suit a civic setting, as in the examples collected under civic hackathon events.
Common mistakes to avoid
The Devpost etiquette guide lists several habits that hurt a presentation. It warns against taking on too many features, saying that teams should focus on quality over quantity and prioritise the core functionality of the project. A pitch built around one dependable feature beats one that tries to show everything and stumbles.
The same guide recommends submitting early, which helps avoid technical issues and allows baseline eligibility checks. A team that submits early also has time to review its own entry as a judge would see it: whether the video plays, whether links work and whether the description matches the demo.
The video guide adds two more cautions. One participant says not to pack in too much information or speed up the audio to fit a time limit. Another reminds teams to check the submission requirements for how long demo videos can be. Both come down to respecting the format the event has set.
- Do not open with team introductions or technology lists before the problem is clear.
- Do not demonstrate sign-up screens or other routine steps.
- Do not exceed the time limit; trim material instead of talking faster.
- Do not claim features that the prototype cannot show.
Frequently asked questions
How long should a hackathon pitch be?
It depends on the event. Devpost’s video guide says most hackathons require demo videos of under three minutes, while live slots can be shorter, so the rules page of the specific event is the final word.
Should a pitch use slides?
Slides can help set the scene, but advice from Devpost participants favours showing the working project. One quoted competitor recommends keeping the video visually engaging and avoiding slide shows.
What should come first in the talk?
The problem. Devpost’s presentation advice starts with setting the scene in a few sentences, then moves to the demo and closes on potential and ambition.
When should a team start preparing the pitch?
Early. Participants quoted by Devpost suggest planning the video from the ideation phase and leaving time at the end for recording and uploading.
