Built from 35+ playbooks & research papers

Turn a room of consumers into a room of builders.

The operating system for running exceptional hackathons, on a campus, in a company, at a school, or around your kitchen table. Everything MLH, ElevenLabs, Spotify, Junction, NASA and the research literature learned the hard way, compressed into a 10-minute onboarding. Built in Brussels, at befounders.eu.

35+
playbooks & papers distilled
15
rules that carry the whole event
10 min
to a fully planned event
1 prompt
the agent scaffolds the rest
Step 1 · Who are you?

Three doors. Pick yours.

The single biggest research finding: hackathons fail through goal-incoherence, not bad logistics. So we start with you, not with the checklist.

Step 2 · The format picker

There isn't one hackathon. There are fifteen.

MIT Hack-Nation and a Lovable vibe-jam share almost none of the same playbook. Answer five questions and we'll point you at the single best-fit format, then browse the rest below. Plenty of them are European, from ElevenLabs in London to Junction in Helsinki to EUvsVirus across the whole union, because this is built in Brussels, at befounders.eu.

1 What are you really trying to do?
Launch or fund startups Drive adoption of my product / API Recruit or change my company Move a real-world / public-good problem Onboard beginners, grow a community Convene elites and make deals Manufacture a big launch moment
2 Who's in the room?
Anyone who signs up Vetted / elite builders & founders Students My own employees Devs on a specific stack The affected community & end-users
3 How long can it run?
A few hours One day (~24h) A weekend (36–54h) Weeks
4 Where does it happen?
One room, in person One big single-venue event Many cities, same night Federated: many local events, one challenge Fully online Internal / multi-office
5 What's the reward, and how selective are you?
Cash + bounties Product credits / compute Access: funding, accelerator, a job Pure recognition / no prizes Invite-only / heavily vetted door

The fifteen formats

Tap any card to open it. Sourced in the Field Manual.
Step 3 · The 10-minute path

Fifteen rules. Each one is the consensus of the entire source base.

Check them off as you internalise them, your progress is saved in this browser. Then open the Master Timeline and you're operational.

0 / 15, the room is waiting
“Hackathons sometimes produce technologies, and they always produce subjects.” Lilly Irani, Science, Technology & Human Values
~9% of “hackathon code” is written at the hackathon
~7% of projects survive six months, by default

Judged as software factories, hackathons are a scam. Judged as identity factories, they're the best deal in civilization: deadline + strangers + witnessed demo = a person who has publicly enacted “I am someone who builds.” Design for the conversion; make shipping the designed add-on, and done right survival jumps to 25–40%.

My goal is to take builders from 1% to 51% of people. The same way we crossed the majority line on internet access, then on mobile phones. AI is the next step, so more people get more able. That makes this one of the best levers we have against inequality. Reframe someone into a builder and you have changed who gets to shape the world.

The cheat numbers

Numbers that survive contact with reality

Screenshot this. Every value is sourced in the manual's appendix.

200%
Register double your capacity
Free events no-show at ~50%
⌈P×3×4′⁄T⌉
The judge formula
3 judges, 4 min per project; P ≈ attendees ÷ 4
~25%
Of scope actually ships
Checkpoint at half-time; force the cut early
2–3 min
Demos. Live. No slides.
Hard-cut timer; everyone demos
3–4
People per team, cap 5
Formed before hour zero, or lose 3 hours
≤25%
Of budget from any one sponsor
3 tiers, prize parity, invoice on yes
0
Links in a first sponsor email
Spam filters. Plain text. 3 follow-ups.
$8–10
Per person per meal
Never pizza-only; claims decay 90%→30%
2 wks
What winning buys you
A written 30-day plan buys months
80–85%
Of a slot you may plan
Slack time is a design requirement
40%
Of your effort the venue can eat
3 warm pitches/week, start 5 months out
≥4
Prizes, priced in access
Dinner with founders > an iPad
The toolkit

Three artifacts, one operating system

Open source · participatory

This playbook gets better when you push to it.

Ran an event that broke the mould? Spotted a format we're missing, a number that's moved, or a template that actually worked? The whole doctrine lives on GitHub. Open an issue or a pull request and put your field data into the canon.

Curated from Brussels by Cedric at Seven Events, Brussels ambassador for hackathonhub.eu.