Hackathon Pitch Guide: How to Present Your Project and Win Prizes
A hackathon pitch guide with one 3-minute structure: problem, live demo, how it works, and impact. Plus Q&A prep, and how to cut it down for a shorter slot.
A 3-Minute Pitch Structure
I've watched technically weaker projects win because their pitch was better. This is the structure I use. It runs about three minutes, and you can drop your project into it tonight.
Problem (30 seconds)
State the pain point before you say anything about your product.
Solution demo (90 seconds)
Show the product live and walk through it as a user would. Lead with your most impressive feature, not the login screen.
How it works (30 seconds)
High level only. 'We use Claude's API to analyze medical records in real time.' Stop there.
Impact and what's next (30 seconds)
Who it helps, and what you'd build with more time.
Fit the Structure to Your Slot
When I judged at LA Hacks, each team had five minutes, and about 3.5 of those were for questions, which is where a judge fills in the rubric. Some teams pitched for all five. Formats vary, so ask how long your slot is and how much of it is Q&A. If Q&A comes out of the same slot, shrink this structure to about 90 seconds and keep the same order.
9 Hackathon Pitch Mistakes I Saw at LA Hacks
What I saw from the judging table.
Open With the Problem
A winning team I watched opened with this: 240 million 911 calls are made in the US every year, and dispatchers prioritize them by hand while people are dying on the line. (That number is the National Emergency Number Association's estimate: nena.org/page/911statistics.)
Do This
- Lead with one statistic that shows the scale
- Open with a personal story
- Describe the problem so the judge can picture it
Avoid This
- ✕Opening with your team name
- ✕Starting with your tech stack
- ✕A long backstory before the point
- ✕Jumping straight to the solution
Demo Live, and Always Record a Backup
Demo live whenever you can. Slides are backup only.
Watch Out
Pre-load realistic data: believable numbers in the dashboard and a real example to process. Never 'test123' or 'lorem ipsum'.
The Wi-Fi at LA Hacks was spotty while I was judging, and some teams couldn't run their demo at all. Without a backup video, I couldn't see what those projects did. A recording also stays on your Devpost for deliberation.
Here's our TalkTuahBank demo from HackUTD 2024, where we took 1st Overall. The problem gets one statistic and five seconds, and the product is running by 0:14. At 1:20, a $200 transfer goes through on camera.
Demo video by the TalkTuahBank team.
Screen Studio is the recorder I use for hackathon demos
Auto-zoom, cursor smoothing, and a webcam overlay are baked in, so a 60-second demo needs almost no editing. Worth a look if you're on Mac.
Affiliate link: I may earn a commission.
More demo video examples
The TalkTuahBank and SoundSearch demos, broken down.
Win the Q&A by Naming Your Limits
Prepare answers for
Pro Tip
When a judge asks what's missing, answer honestly instead of overselling. Something like: 'In a production version we'd add X, but for this demo we focused on Y because it best shows our core value.'
Delivery: One Speaker, No Apologies
Have one person talk while another drives the demo, and don't switch speakers mid-pitch. Look at the judges instead of your screen, and keep a measured pace even when you're nervous. Run the whole thing out loud with a timer at least once before you walk up.
Don't apologize in the pitch
Don't bring up bugs or say 'we ran out of time.' Judges don't know your original plan, so they can only judge what you show them.
How to Win Hackathons: The Complete Guide
All seven phases, from team formation to follow-up.
Get the next guide
Want more hackathon breakdowns like this?
Join the newsletter for practical build, pitch, and judging strategy from 36+ hackathon wins.
Ready to put these strategies into action?
Explore the full 7-phase hackathon playbook with interactive tools and templates.
Open the Playbook →Recommended next