Make value visible.

For four days in November, a campus at the foot of the Bavarian Alps becomes an XR lab. Five teams from TUM School of Management and ETH Zürich take the business problem from their project proposal, turn it into a prototype that runs on a Meta Quest 3, and defend it in front of a jury.

The question isn't "can you build something cool in VR?" It's harder, and it's the one businesses actually ask:

Does extended reality create value you can measure?

One user. One place. One loop. One number.

Every project is built around the same four ideas:

  • 👤 User: who wears the headset, and what do they want right now?
  • 🏔️ Place: the space they stand in, at real scale.
  • 🔁 Loop: the one thing they act on, and the feedback that tells them it worked.
  • 📈 Number: the business outcome you would measure, logged by the headset itself.

Four days, four sprints

Thursday 19 November

  • 14:00 Official kick-off, then the starter challenge: problem, persona, scenario, market, business model and sprint plan
  • 16:45 Intro pitches (40 % of the grade) and jury feedback
  • 19:00 Sprint 1: your project builds and runs on the Quest

Friday 20 November

  • 09:00 Sprint 2: the core interaction, with 1:1 coaching for every team
  • 13:15 Sprint 3: an end-to-end prototype that others can test
  • 17:30 Cross-team user testing, round 1

Saturday 21 November

  • 08:45 Sprint 4: the complete MVP
  • 13:00 User testing, round 2
  • 16:15 Feature freeze, then pitch and demo preparation
  • 17:45 Final pitches (40 % of the grade). Winners are announced at dinner.

Sunday 22 November

  • Check-out and the journey home

What you build with

  • Meta Quest 3 headsets and two laptops per team
  • Unity 6 LTS (6000.3.25f1) and the PRISM starter, a complete VR showroom with grab, place, press, scenario steps and CSV logging already wired
  • Coaches in the room for scope and concept, for builds and devices, and for organisation
  • Two rounds of cross-team user testing, because the best feedback comes from someone who has never seen your app

What wins

Not the flashiest scene: the clearest case. A problem worth solving, a persona who feels real, a loop that runs live on the headset, and a number that shows why XR is the right medium.

Requirements

What to build

A VR or mixed-reality prototype for Meta Quest 3, built in Unity 6000.3.25f1, around the problem from your team's project proposal.

  • Minimum: one working interaction loop on the headset (grab, place or press, and the user sees that it worked).
  • Target: a short scenario with a start, a few steps, a result, and data about what happened.
  • It must run as a build on the headset, without a cable. A Quest Link session is not a build.

How to submit as a team

  • Every team member creates a Devpost account and joins this hackathon (Join hackathon, top of the page).
  • One member submits the project and adds the others as team members. One submission per team.
  • You can edit your submission until the deadline, so submit a first version early on Saturday and update it.

What to submit by Saturday 21 November, 17:30

  1. Project name and all team members added to the project
  2. Elevator pitch: your one loop sentence
  3. Trailer video, 60 to 90 seconds, made like a product trailer, not a raw headset recording (see below). Upload to YouTube or Vimeo; unlisted is fine.
  4. At least three screenshots
  5. About the project: problem, persona, scenario, business model and pricing, and the number you measured
  6. Link to your team's GitHub repository
  7. Final pitch slides as PDF
  8. Credits list for every asset that is not yours, and your AI log

Your trailer

Think launch trailer, not screen recording. It is the first thing the jury and everyone after the event will see.

  1. Hook (first 5 seconds): the problem in one shot or one line.
  2. Who and where: your persona and the place they are in.
  3. The loop in action: your best headset clips, cut tight, ideally next to footage of a real person using it.
  4. The number: what changes for the business, on screen.
  5. End card: project name, team name, "TUM × ETH Zürich XR Value Creation Hackathon 2026".

Add captions (many people watch without sound), use only royalty-free music, and no third-party logos or trademarks. Record clips with the Quest's built-in recorder or through casting, and cut them in any editor (Clipchamp, CapCut, DaVinci Resolve). Keep a plain recording of your loop on a phone as well: that is your backup if the live demo fails.

Prizes

1 non-cash prize
Overall winner
1 winner

The team with the highest weighted score: intro pitch 40 %, final pitch 40 %, team spirit 20 %. Announced at the Saturday dinner and shown as the winner on this page. No cash prize: the hackathon is part of the course assessment.

Judges

Prof. Dr. Martin Meißner

Prof. Dr. Martin Meißner
Professor of Digital Marketing, TUM School of Management

Prof. Dr. David Finken

Prof. Dr. David Finken
Research Group Lead, Marketing & Technology, TUM School of Management

Mohamed Mansuri

Mohamed Mansuri
Extended Reality Researcher & XR Developer, TUM School of Management

Ehbal Ablimit

Ehbal Ablimit
Research Associate, Marketing & Technology, TUM School of Management

Justin Eymann

Justin Eymann
Professorship for Technology Marketing, ETH Zürich

Dr. Thomas Scheurer

Dr. Thomas Scheurer
Postdoctoral Researcher, Technology Marketing, ETH Zürich

Judging Criteria

  • Intro pitch, Thursday (40 %)
    Problem statement · target group and persona · scenario walkthrough and why XR · market (TAM), competitors, business model and pricing · a realistic four-day sprint plan with scope exclusions. Each scored 0 (not met), 1 (partly met) or 2 (fully met).
  • Final pitch, Saturday (40 %)
    Live, stable demo on the Quest · milestones delivered against Thursday's plan · intuitive, comfortable XR · test feedback fixed, with a clear before and after · on time at 7 minutes, confident Q&A. Each scored 0, 1 or 2.
  • Team spirit, Thursday to Saturday (20 %)
    Collaboration within the team · clear roles and a fair workload · help offered to other teams · thorough, honest feedback as testers · punctuality and reliability. Each scored 0, 1 or 2.

Questions? Email the hackathon manager

Invite others to compete