One question.One day to answer it.
Claude Impact Lab is a full day in Munich where we build our own answer to the question the conversation evening left open: what does AI actually mean for my job? Two threads straight from that room, one wildcard, and pitches before the doors close.
- When
- 12 Aug · 09:00 – 17:00
- Where
- Make
- Groups
- Mixed
- Projects submitted
- 15
Two weeks ago, a room talked. Today we build.
Different jobs, different backgrounds, different worries — no panel, no pitches, just small groups working through one question over cheese boards and wine. People described getting time back for creative work, and the same speed showing up as pressure. They talked about judgment becoming the scarce resource once execution gets cheap, about trusting and checking what the model hands back, and about who gets left behind as access to these tools turns into its own kind of gap. Today we pick up those threads and make something real out of them.
Not a hackathon for its own sake — a working session grounded in what the room actually said.
Two threads from the room. One of your own.
Two come straight out of what people said two weeks ago. The third is yours to define — as long as it answers the same question.
Trust, but check
The same unease kept surfacing: the output looks right, and checking it properly takes longer than making it did.
Build something that makes a model's output checkable in your own line of work — a reviewer that flags what it isn't sure about, a trail back to the source, a second model arguing with the first. The test: would you sign off on the result without re-reading every line?
Who gets left behind
Access to these tools is turning into its own kind of gap — between teams, between roles, between the people who were in that room and the people who weren't.
Build for someone who isn't here today: the colleague who won't open a chat box, the service that has to work in a second language, the person whose job description never mentioned AI. Non-technical teammates are the sharpest testers in the building — use them.
Wildcard — your own thread
The evening threw up more threads than two: time won back and speed turned into pressure, judgment becoming the scarce thing once execution is cheap.
Pick one of those, or bring your own — as long as it answers the question the evening asked: what does AI mean for my job? Say which thread you pulled when you show it.
Eight hours, coffee to prizes
Doors at 09:00, building by 10:00, pitches at 15:15, prizes at 16:25.
- 0109:00Arrive
Coffee, badges, first hellos.
- 0209:30Recap
What came out of the conversation evening, in ten minutes.
- 0309:40Pick a track, find a group
Mixed groups work best. Come alone and we'll place you.
- 0410:00 – 12:30Build, part one
Turn a theme into something real. Hosts circulate.
- 0512:30 – 13:15Lunch
Food, a breather, a look at what everyone else is doing.
- 0613:15 – 15:15Build, part two
Refine it, then get it pitch-ready.
- 0715:15Pitches
Every group presents what they made.
- 0816:25Prizes
Winners announced.
- 0916:40Wrap
What we learned, and where this goes next.
Times are our plan for the day rather than a contract — the hosts will call the room if something shifts.
The vibe
German & English, both fine all day. You don't need to be technical to be useful here — the best groups will be mixed, same as last time. Hosts and experienced builders are on the floor to unstick you. Bring a laptop and expect to use it.
Who's in the room
Everyone who was at the conversation evening, and plenty who weren't. Engineers, designers, operators, founders, and people whose job description has never once mentioned AI. Come alone and we'll help you find a group.
What you get on the day
The lab is free — and built so you leave with real progress, not a tote bag.
What makes a good one
Four things worth getting right in the last hour of the day.
A rough working prototype tells the room more than a polished description of one.
Which theme from the evening you picked up, and who the thing you built is for.
One day is one day. Saying what's real and what's stubbed is the useful part, not a confession.
The question the room will ask anyway: would you keep going, and what would you need?
Pitches start at 15:15 and every group gets the floor. There's no leaderboard and no ranked score — the point is the room seeing what everyone made.
Fun prizes, several categories
Handed out at 16:25. Not a first-second-third — a set of categories, some of which you won't see coming.
The categories get announced on the day. Build the thing you actually want to build; you can't game a list you haven't seen.
Who's running the day
On the floor all day. Grab any of us — that's what we're here for.
- Michael Whelehan
Claude Community Ambassador, Nuremberg
- Dr. Florian Steiner
Claude Community Ambassador, Munich
- Alexander Eiswirth
Freelance agentic AI engineer, cloud & software architect
Five things we ask
They keep the room generous, the energy up, and Make willing to have us back.
The room is full and the list is closed. If you can't make it, release your spot so someone else can.
09:00 to 17:00. Pitches are the whole point — groups that leave early can't pitch.
Ten minutes of working prototype beats forty minutes of deck.
The best teams last time were mixed. If your group is all engineers, go recruit.
Someone here has already done the thing you're stuck on. Say so out loud.
Make
Huge thanks to Make for hosting us again — this time on the first floor. Head for the Celonis building on Theresienstraße; the hosts will send final arrival details before the day.
Make's Munich office, first floor of the Celonis building on Theresienstraße — Maxvorstadt, a short walk from the university quarter.
Built something today?
Get your project in before pitches at 15:15 — fill in the form, or wire up the MCP server and let Claude do it for you.