We filled a room in Frankfurt with 152+ builders for Build Day × Cursor. No pitch decks. No spectator mode. People showed up with their own projects and left closer to something they could ship.
What we set out to do
Build Day is the format I care about most: a working session where adoption happens in the room. Sponsors and mentors are there to unblock, not to lecture. The goal is simple. Help people use Cursor to build, adopt AI in their workflow, and leave as practitioners.
Frankfurt was the biggest room we have run so far.
The room
Builders came with real ideas: side projects, startup prototypes, internal tools, and experiments they had been putting off. Mentors rotated through tables. Sponsors kept coffee, power, and Wi-Fi honest.
The energy was not "watch a demo and leave." It was keyboards open, questions asked out loud, and people comparing notes on what actually worked in their stack.
What stuck
Three patterns kept showing up:
- Start from a real repo. The best sessions began with an existing codebase or a concrete problem, not a blank canvas and a vague prompt.
- Human review stays in the loop. Even when Composer moved fast, teams still paused to read diffs, run the app, and catch assumptions before merge.
- Adoption is social. People learned as much from the person next to them as from the mentor at the front of the room.
Thank you
To everyone who registered, showed up, and built: you made the day. To our sponsors and mentors: you kept the room moving. To the Cursor community in Germany: this is what adoption looks like when it leaves the slide deck.
If you want the next one, watch cursorgermany.com and the event page on Luma.