How to Write a Pitch Deck for a High School Competition
A good pitch deck for a high school competition is about 10 slides that tell one story: here’s a real problem, here’s who has it, here’s what we built, and here’s the proof it works. Each slide carries one idea. The order runs title, problem, solution, demo, market, business model, traction, team, and ask or vision. If a judge can read one slide, look up, and still follow your logic, you’re doing it right.
Most students get this backwards. They build a slide for every fact they know instead of every point the judge needs. The result is 25 slides, tiny text, and a story nobody can hold in their head. Your deck is not a document. It’s a set of cue cards for the story you tell out loud.
What is a pitch deck?
A pitch deck is a short slide presentation that walks a judge or investor through your startup’s problem, solution, and evidence, one idea per slide. It supports what you say; it does not replace it.
The deck and the talk are two different things. The deck is what’s on screen: a few words, one image, one number. The talk is you, filling in the rest. If your slides contain full sentences and you read them aloud, you’ve built a script, not a deck, and judges tune out fast.
For a high school competition, aim for 10 slides and a 3 to 5 minute talk. That’s the format most events use, and it’s the constraint that forces you to cut everything that isn’t load-bearing.
The 10-slide structure, slide by slide
Here’s the order that works, and what belongs on each slide. Follow it top to bottom.
| # | Slide | The one job of this slide | Common mistake |
|---|---|---|---|
| 1 | Title | Company name, one-line description of what you do, your name | A clever name with no hint of what you actually do |
| 2 | Problem | The specific pain, and who feels it | Listing five problems instead of one sharp one |
| 3 | Solution | What you built and how it removes that pain | Describing features before the judge understands the problem |
| 4 | Demo | A screenshot, short clip, or live walkthrough of the product | Talking about the product with nothing to show |
| 5 | Market | Who the customers are and roughly how many exist | A giant number with no explanation of how you got it |
| 6 | Business model | How you make money per customer | ”We’ll run ads later” with no real plan |
| 7 | Traction | Proof: users, interviews, signups, revenue, waitlist | Claiming interest with zero evidence behind it |
| 8 | Team | Who you are and why you’re the ones building this | A list of hobbies instead of relevant strengths |
| 9 | Ask / Vision | What you want (or where this goes next) | Ending flat with “thanks” and no clear close |
That’s nine content slides plus an optional appendix. You don’t need more. If you’re tempted to add a “competitors” slide or a “roadmap” slide, fold that content into the ones above or move it to backup slides you only show if a judge asks.
Slide 1: Title
State the company name and, right under it, one plain line about what it does. “MealMap, a free app that plans a week of dinners for one person on a budget” tells a judge more than any logo animation. Put your name on it so they know who’s talking.
Slide 2: Problem
Name one problem and the exact person who has it. Make it concrete: not “food waste is a huge issue,” but “students who live alone buy groceries for recipes, cook once, and throw out the rest.” If you did the work, this is where the pain you heard in real conversations shows up. Weak problem slides come from skipping that work, so read how to find a startup problem worth solving before you write this one.
Slide 3: Solution
Now, and only now, show what you built. Connect it straight to the problem on slide 2. One sentence: “So we built X, which does Y.” Don’t list ten features. Name the one thing that removes the pain.
Slide 4: Demo
Show the thing working. A clean screenshot, a 20-second screen recording, or a quick live click-through all beat a paragraph describing it. Judges trust what they can see. Even a rough, half-built product on screen lands harder than a polished promise.
Slide 5: Market
Explain who your customers are and give a rough sense of how many exist. You don’t need a fake billion-dollar number. Build it from the ground up: “there are about X of these people, and if we reach Y percent of them” is more believable than a headline you can’t defend. Honest and small beats huge and made up.
Slide 6: Business model
Say how you make money on each customer. “We charge $6 a month” or “we take a 5% fee per order” is enough. If you can show the money left over after your costs per sale, even better. You don’t need an accounting class for this, just the price minus what each sale costs you.
Slide 7: Traction
This is the slide that wins competitions. Traction is any real proof that people want this: signups, users, revenue, a waitlist, or even the number of customer interviews you ran and what you learned. Numbers are strongest, but a real quote from a real person you talked to beats a claim with nothing behind it. No traction yet? Show evidence of demand instead: what you heard when you actually talked to the people who have this problem.
Slide 8: Team
Judges bet on people. Say who you are and why you specifically can build this. Relevant beats impressive: “I’ve cooked every meal for myself for two years and got frustrated enough to build this” is stronger than a list of AP classes. Two sentences per person is plenty.
Slide 9: Ask or vision
Close with a clear ending. In a competition where you’re not raising money, this is usually your vision: where this goes in a year, what you’d build next, the bigger picture. If there’s a real ask (feedback, a pilot, mentorship), name it. Do not fade out on “um, that’s it.” The last slide should make the judge want to keep talking to you.
What judges actually look for
Judges aren’t grading you on how much you built. They’re checking a few things fast:
- Is the problem real? Did you talk to people, or did you guess from your desk?
- Does the solution fit the problem? A clever product aimed at a fake problem loses to a simple one aimed at a real one. This is problem-solution fit, and it’s the first thing sharp judges test.
- Is there any proof? Even small traction signals you’ll actually do the work, not just talk.
- Do you understand your own numbers? If you can’t defend your market size or price, judges assume you don’t get your business.
- Can you handle a hard question? The Q&A often matters more than the pitch. Prepare for it with how to answer hard questions in a pitch.
Notice what’s not on that list: animations, slide count, or how many features you crammed in. Substance and a clear story win.
Design rules that keep your deck clean
The design bar is low and easy to hit. Follow four rules:
- One idea per slide. If a slide makes two points, split it or cut one.
- Big text, few words. Six words or fewer per line where you can. If a judge in the back row can’t read it, it’s too small.
- One image or number as the hero. A single screenshot or one bold stat beats a wall of bullets.
- Consistent everything. Same font, same colors, same alignment on every slide. Sloppy formatting reads as sloppy thinking.
You don’t need a designer. Free tools with clean templates get you 90% of the way. Spend your time on the story, not the gradients.
What a pitch deck is not
- It’s not a business plan. Nobody reads 20 dense slides in a 4-minute slot. Cut ruthlessly.
- It’s not a script. Full sentences on screen mean you’re reading, and reading kills the room. Slides are cue cards.
- It’s not the pitch itself. You are the pitch. The deck just keeps everyone on the same page while you talk, which is why how to pitch a startup idea as a teenager matters as much as the file.
- It’s not proof you built more. A tight 9-slide deck about one real thing beats a 30-slide tour of everything you thought about.
How to build your deck, and what to do next
Write the story first, on paper or in a doc, before you open any slide software. One line per slide: what’s the single point here? If the story doesn’t hold as nine plain sentences, no template will save it. Once the outline works, build the slides in an afternoon, then practice out loud until you hit time without reading.
A first draft takes a few hours. A deck you can deliver cleanly takes a few rounds of practice in front of a real person who’ll tell you where they got lost. That loop, build then get honest feedback then cut, is the core of a program like batch0, which ends in a live demo day where you pitch the real thing.
The deck follows the story, and the story comes from what you actually found by talking to people. If your slides feel thin, the fix usually isn’t design. Go deeper on the underlying narrative in the story structure behind every good pitch, then come back and cut your deck to the bone.