Lesson 8: Preparing Your Demo & Telling Your Story 🎤

🎯 Learning objectives

  • Understand how to structure a compelling project demo.
  • Learn how to tell the story of your project: the problem, the solution, and what you learned.
  • Practice your presentation skills and get comfortable talking about your work.

1. What makes a great demo? 🌟

A great demo isn’t just a list of features. It’s a story. It should have a beginning, a middle, and an end.
  • The Beginning (The “Why”): Who is your Community Hub for? What problem does it solve for them?
  • The Middle (The “How”): Show, don’t just tell. Walk through the key features of your application. How does it solve the problem you identified?
  • The End (The “What’s Next”): What did you learn? What are you proud of? What would you build next if you had more time?

The 5-minute demo structure

Here’s a simple structure you can follow for your 5-minute live presentation:
  • Intro (30 seconds): Introduce your team and the community your hub is for.
  • The Problem (30 seconds): Briefly explain the problem your community faces.
  • Live Demo (3 minutes): Walk through 2-3 key features of your application. This should be the bulk of your presentation.
  • What We Learned (30 seconds): Share one key takeaway from your experience.
  • Q&A (30 seconds): Thank the audience and open it up for questions.

2. Telling your story 🗣️

Every team member should have a speaking role in the presentation. Here’s a sample division of labor:
  • Person 1: The Storyteller. Sets the stage, introduces the community and the problem.
  • Person 2: The Live Demo Driver. Shares their screen and walks through the application.
  • Person 3: The Closer. Wraps up with what the team learned and what they’re proud of.

✅ Exercise: Script your demo

  1. As a team, decide who will take on which role.
  1. Write a rough script for your 5-minute presentation. You don’t have to read it word-for-word, but it helps to have a plan.
  1. Practice, practice, practice! The more you run through it, the smoother it will be.
How to self-validate: Open a Zoom or Google Meet room with just your team, hit record, and run through the full 5-minute presentation. Watch the recording back. Did you hit all the key points within the time limit?

3. Final touches 🛠️

This week is also for final bug fixes, polish, and making sure your app is ready for Demo Day. There are no new feature tickets this week — the focus is on quality.
  • Bug Bash: As a team, go through your application and try to find and fix any bugs.
  • README: Make sure your project’s README.md file is up-to-date. Your README should include:
      1. Your team name and the community your hub is for
      1. A screenshot of your app
      1. A list of the features you built
      1. How to run the app locally (pnpm install → add .env.local → pnpm run dev)

💡 Presenting an incomplete app

Not every feature needs to be 100% done for a great demo! If your team didn't finish all 12 tickets, that is completely normal.
When you demo, focus entirely on what does work. Don't apologize for what isn't finished. Instead of saying "We tried to build a search filter but it's broken," say: "We focused our time on making the comment system really robust." Own your work!

4. Looking ahead: how to put this on your resume 📄

You haven't just learned "how to use Codex." You've learned how to be an AI-assisted developer. You developed agentic AI skills! This is a highly sought-after skill in the tech industry right now.
When you talk about this project and the BuildLab in interviews or on your resume, don't just list the tools. Focus on the process of building with AI. Here are a few bullet points you can steal:
  • "Leveraged agentic AI tools (LLM-assisted development) to accelerate full-stack feature delivery."
  • "Applied prompt engineering and AI code review practices to build and deploy Next.js features."
  • "Collaborated in a cross-functional team to integrate AI-generated code into a shared repository using Git and GitHub."
You now have the universal skills to pick up Cursor, GitHub Copilot, or any future AI coding tool and immediately start building.
Good luck with your preparations! We can’t wait to see what you’ve built! 🎉