There's a place for you here, whatever your time allows. The Challenge runs on small, well-defined roles, each built to give students real help and a real bar to clear without asking a whole semester of anyone. Find the one that fits, from a two-hour read to opening a door.
Each is a bounded commitment. Take a single role, or take several. People often fill more than one, and any of them can be as light as your time allows.
Read a team's one-page concept (plus an optional visuals page) and two-minute video and score the idea against a light entry gate: is the finance problem clear, the user defined, the solution buildable? No demo exists yet, so you're weighing how carefully they've thought it through.
Drop in on a Friday build session to give hands-on help: feedback, unblocking the build, sanity-checking the finance, nudging the AI. Stations by expertise (finance/domain, AI & build, UX, product & pitch) so you can lend exactly what you know.
Evaluate teams on working evidence and help pick who advances: watch semi-finalists at work during the final build session and choose the top 10, or join the external panel running live demos to pick the finalists.
Share your experience: a short talk, a reverse-pitch that shows students what “good” looks like, or a ~20-minute remote interview for the podcast series. The lowest-friction way to contribute, and often the first step into a bigger role.
Back the Challenge with cash for prizes and events, AI and software tool credits that go straight to student teams, or in-kind support (venue, food, services, prizes). The tool-credit route is especially valuable for a vibe-coding challenge.
Open doors and spread the word: an introduction to a partner, sponsor, mentor, or judge, or amplification through your network and channels. One name can cover more than one of these. Send it over and we'll do the asking.