Pitch prep

Stop building. I mean it, hands off the keyboard. Your pitch is due tomorrow, and rehearsal is what makes it land.

Fill in the Pitch Outline card

Three sections:

• Problem (2 sentences): What does your site address, and who does it affect?
• Demo flow (3–5 steps): What pages and features will you click through? Write the exact sequence.
• What we learned (one sentence per team member): something specific. "Structured output prompts saved us 10 minutes every time we generated a component" is a reflection. "We learned a lot" is not.

Every team member should have at least one thing to say in the reflection section.

Dry run

Run your full pitch timed at 7 minutes, presenting from your live Netlify URL on screen. Not localhost, not VS Code. Demo Day runs from the public URL, so rehearse exactly that. A dry run is the only way to find out whether the demo flows smoothly and whether you're hitting the time limit; guessing doesn't work, and I say that as someone who has watched many teams guess.

The ratio that works: 1 minute problem, 5 minutes demo, 1 minute reflection. The most common pitch mistake is the reverse, a long wind-up about the problem that eats the demo.

Common things to catch:

• Spending more than 1 minute on the problem before the demo starts
• A dead end in the demo click sequence
• One team member not speaking

After the dry run, adjust your outline and run it again if you need to.