3 hours
Quick Build
Wednesday afternoon. A clear brief, fast team formation and just enough time to surprise yourself.
Best for first-timers, unfinished ideas and meeting collaborators.The programme
Every event starts with a simple promise: you will leave having made something you did not arrive with.
Explore the formats↗Next programme: in development
Four to five builds per semester · Birmingham
Choose your depth
3 hours
Wednesday afternoon. A clear brief, fast team formation and just enough time to surprise yourself.
Best for first-timers, unfinished ideas and meeting collaborators.6–8 hours
A full Saturday to go beyond the sketch: build, test, break, improve and show the room what changed.
Best for deeper prototypes, sponsor briefs and serious momentum.Curated
A deliberately smaller room assembled around a demanding problem or particular technology.
Best for ambitious builders ready to contribute at pace.
What the day feels like
We kill the hackathon stereotype. No all-nighters, no gatekeeping, no pretending that exhaustion is the same thing as ambition.
You can arrive without a team. You can arrive without code. Bring curiosity, taste and a willingness to make your work visible.
A typical build
Meet the room. Hear the brief. Find the people whose skills and questions complement yours.
Cut the idea down to something your team can prove before the clock runs out.
Build in public. Ask for help early. Change direction when the evidence tells you to.
Put the work in front of the room. Share what works, what broke and what you would do next.
No team required