Pitching
What is a Pitch?
Pitching is telling the story of your project in a clear, engaging, and memorable way. A good pitch helps people understand what you built, why it matters, and why they should care.
At a hackathon, your pitch should answer a few important questions:
- What problem are you solving?
- Why does this problem matter?
- How does your solution work?
- Why should people care about it?
Great projects do not always win. Great presentations can make the difference.
Why Pitching Matters
Judges do not see every late-night debugging session, design decision, or 24 hours of prompt engineering that went into your project. They only have a few minutes to understand what you made and decide whether it is valuable in the real world.
A strong pitch highlights the effort, impact, and technical choices behind your project. It helps judges see why your project is worth remembering.
How Does Pitching Work?
At HackUTD, plan for a short pitch window:
- 3 minutes to pitch
- 2 minutes for judge questions
A simple pitch flow looks like this:
- Problem: What issue are you solving?
- Solution: What did you build?
- Demo: Show the project working.
- Impact: Why is it useful, interesting, or important?
- Questions: Be ready to explain your decisions.
Do not treat the pitch like a status update. Treat it like a sales pitch. You are helping judges understand why your project deserves attention.
Pitching Starts Before the Judges Meet You
Your first impression often happens before your live pitch. Judges may see your Devpost, thumbnail, name, description, or demo video before they talk to you.
Before judging starts:
- Choose a visually compelling Devpost thumbnail
- Keep your demo video under 2 minutes
- Give your project a clear, memorable name
- Make sure your project description explains the problem and solution quickly
Your Slides Do Most of the Talking
Slides should support your story instead of competing with it. Start from a clean template, then redesign it around your app's color palette and visual style.
Be intentional with every slide. A helpful slide flow is:
| Slide | Goal |
|---|---|
| What you built | Introduce the project and the core idea |
| Why it matters | Explain the problem, audience, and impact |
| How it works | Show the technical approach or product flow |
| What's next | Explain future improvements or where the project can go |
If your project has a strong visual interface, walk through the product. Judges remember demos more easily when they can see the user experience.
Own the Room
Pitching is not just about having the right slides. Delivery matters too.
Talk to judges like you are trying to convince someone to invest in your idea. Avoid reading off a checklist. Make eye contact, pass between teammates smoothly, and show that your team understands both the product and the problem.
Practice at least once before the real pitch. Even a quick run-through helps catch awkward transitions, broken demos, and sections that run too long.
Team Roles
If you are pitching with a team, delegate roles before judging starts.
| Role | Responsibility |
|---|---|
| Storyteller | Opens the pitch and explains the problem |
| Demo driver | Controls the live demo or video |
| Tech lead | Explains important technical decisions |
| Closer | Ends with impact, future work, and final takeaway |
Knowing which track each judge is judging for can help you tailor your pitch. Emphasize the parts of your project that match the track or sponsor challenge.
Demo Time
Let's practice pitching with something low-stakes first: a hot take.
Setup
Partner up with one other person. Each person should think of their biggest hot take. It can be about food, tech, school, movies, or anything else that is easy to argue for in a fun way.
You will need:
- A partner
- A timer
- One hot take
- A willingness to sound a little dramatic
Step 1: Pitch Your Hot Take
Take 2 minutes to pitch your hot take to your partner. Try to make it clear, memorable, and convincing.
Use this structure:
- State the hot take
- Explain why it matters
- Give your strongest evidence
- End with a confident final takeaway
Step 2: Answer Questions
Your partner gets 1 minute to ask questions. Stay curious, not argumentative. The goal is to practice thinking on your feet.
Step 3: Switch Roles
Now switch. Your partner pitches their hot take for 2 minutes, and you ask questions for 1 minute.
Step 4: Team Up
Pair up with another duo. Choose the best hot take from your group and turn it into a team pitch.
Take 3 minutes to decide:
- Who opens the pitch?
- Who gives the evidence?
- Who handles the counterargument?
- Who closes?
Then pitch to the room.
Turning This Into a Hackathon Pitch
When you are ready to pitch an actual project, use this template:
We built [project name], a [type of product] for [target audience].
The problem is [problem], which matters because [impact].
Our solution lets users [main user action or benefit].
Here is the demo: [walk through the most important user flow].
We built it using [tech stack], and the most interesting technical part was [technical highlight].
With more time, we would [future improvement]. For now, our project shows that [main takeaway].
Next Steps
Before judging, rehearse your pitch with a timer and make sure your demo is ready. Keep your story simple, make your slides visually consistent with your app, and prepare answers for common judge questions.