Back to all updates

3 months ago

Demo Day is THIS SUNDAY β€” Claim Your Slot + Everything You Need to Know!

Hey Builder,

Demo Day is 4 days away β€” and this is your official heads up on everything you need to show up, show out, and submit a complete project on March 8th, International Women's Day.

🎯 Reserve Your Demo Day Slot

If you're planning to present, you must sign up in advance. Slots are limited and not automatic β€” reserve yours now.

You do NOT need to be finished to sign up. You just need to commit to showing up.

πŸ‘‰ Reserve your Demo Day presentation slot β†’

πŸ“… Demo Day Schedule β€” March 8, 2026

Demo Day runs 9:00 AM – 12:00 PM EST. Each track has its own time slot:

Track Time (EST)
πŸ€– AI / ML 9:00 AM – 10:00 AM
πŸ₯½ AR / VR / XR 10:10 AM – 11:00 AM
⛓️ Blockchain 11:10 AM – 12:00 PM

Times are approximate and may adjust based on the number of teams per track. The platform link will be sent to all registered presenters ahead of Demo Day.

🎬 How Demo Day Works

Each team gets:

  • 3–5 minutes to present their working prototype (live demo or pre-recorded backup)
  • 2 minutes of live Q&A with judges
  • A brief transition before the next team

Come ready to show your build, explain the problem you're solving, and walk judges through your technical implementation. You don't need it to be perfect!

βš–οΈ What Judges Are Looking For

Your project will be scored across 5 criteria:

  • Clarity (25%) β€” Is your 4-Line Problem Frame crisp? Can your demo run from a clean start?
  • Proof (25%) β€” Does it actually work? Are your sources cited in an Evidence Log?
  • Usability (20%) β€” Can a non-technical person understand your 3-Line Pitch? Is it accessible?
  • Rigor (20%) β€” Did you document your decisions, risks, and ethical considerations?
  • Polish (10%) β€” Clean repo, no broken links, no committed secrets, professional presentation

Strong projects show how you think, not just what you built. Both communication and technical depth matter.

πŸ€– AI/ML Track: Goose Requirement

A reminder for all AI/ML participants: your project must incorporate Goose β€” Block's open-source agentic AI framework β€” in a meaningful way. Surface-level usage won't score as well as genuine integration. Check past updates or the participant guide on how to get access and how to incorporate it.

βœ… Submission Checklist β€” Due March 7 @ 11:59 PM EST

Before you submit on Devpost, make sure you have all of the following:

πŸ“¦ Core Requirements

  • ☐ Working prototype β€” hosted link (preferred) OR demo file with setup instructions. Must run from a clean start with no login required for core functionality
  • ☐ Demo video (3–5 min, YouTube, public or unlisted) β€” covers your problem, solution, live demo, and SDG alignment. Captions required
  • ☐ Public GitHub or GitLab repo β€” with a comprehensive README

πŸ“ README Must Include

  • ☐ Quickstart instructions β€” 1-command setup that actually works
  • ☐ 4-Line Problem Frame β€” User, Problem, Constraints, Success Test
  • ☐ 3-Line Pitch β€” Headline (6–10 words), Subhead (14–24 words), CTA verb
  • ☐ Decision Log β€” 3–5 bullets on key technical choices and tradeoffs
  • ☐ Evidence Log β€” table of sources, links, licenses, and attributions
  • ☐ Risk Log β€” at least 1 issue caught and fixed before submission
  • ☐ Known issues & next steps β€” what's not done and what you'd build next
  • ☐ License declared β€” MIT, Apache 2.0, or equivalent
  • ☐ .env.example file β€” with dummy values; no real API keys committed

πŸ’‘ Not sure how to format your Decision Log, Evidence Log, or Risk Log? Templates for all documentation requirements are available in the Participant Guide β†’ Copy, fill in, and submit (or use a tool like goose to help you fill it in!).

β™Ώ Accessibility Requirements

  • ☐ Demo video has captions
  • ☐ Images include alt text
  • ☐ Public-facing copy is grade-8 readable (check with Hemingway Editor)
  • ☐ Color contrast meets WCAG AA standards (for web apps)
  • ☐ Links use descriptive text β€” not "click here"

🚨 Instant Disqualification β€” Avoid These

  • ❌ Exposed PII (emails, names, or data) in screenshots, logs, or repos
  • ❌ Fabricated statistics or unverifiable claims
  • ❌ Committed secrets (API keys, passwords, tokens)
  • ❌ Broken demo β€” hosted link doesn't work, video doesn't load, code doesn't run
  • ❌ IP violations β€” unpermitted logos, unlicensed assets, plagiarized code
🎁 Every Live Presenter Gets a Special Prize

Everyone who demos live on March 8th receives a special prize β€” we're keeping it a surprise, but trust us: it's absolutely worth showing up for. You must be present and presenting live to receive it.

πŸ™‹ Need Help? Office Hours β€” March 5th

Not sure if your submission is complete? Come to Office Hours on Thursday, March 5th β€” we'll help you work through any last-minute questions, technical issues, or checklist gaps before the March 7 deadline.

Pick the slot that works for you. Both sessions cover the same material β€” come with your questions, your repo, and your Devpost draft.

πŸ“¬ Key Dates
Date What's Happening
March 5 @ 1:00 PM & 6:00 PM ET πŸ™‹ Submission Office Hours β€” 1 PM | 6 PM
March 7 @ 11:59 PM EST Final project submission deadline on Devpost
March 8, 9 AM–12 PM EST πŸŽ‰ Demo Day β€” Live on International Women's Day
March 15 @ 11:59 PM EST Judge scoring deadline
March 16 πŸ† Winners announced
πŸŽ‰ After Demo Day: Join the BuildHER Parade

The celebration doesn't stop at noon. Starting March 8th, we're launching the BuildHER Parade β€” a month-long community celebration of your builder journey.

Grab your custom social graphics from the IWD 2026 BuildHER Kit β†’, personalize them, and share your story. Use #IWD2026 #75HER #BuildHERParade #HERstory and tag @CreateHERFest β€” we'll be amplifying you all month.

You spent 75 days building. Now let the world see it!

Questions? Drop them in Discord or email darlyze@createherfest.org or adriann@createherfest.org.

See you on the stage. πŸ’œ

β€” The CreateHER Fest Team