Programme
Thirty days, start to Demo Day.
You arrive without an idea, without a team and without permission. Thirty days later you have shipped something real to real users, in public, and pitched it live to people who fund companies.
- Builders per batch
- 24
- Teams per batch
- 6
- Days, start to Demo Day
- 30
Discover
Nobody arrives with an idea. That is the point.
Ideas brought from outside are usually untested affection. We strip that away and make every team find a problem by talking to five real people in the first seventy-two hours.
- D1
- Kickoff. Teams announced.
- D3
- Five user conversations, logged.
- D5
- One problem committed. No pivots after this.
5user conversations, logged, before day three.
Validate
Prove demand before you deserve to build.
Most first-time builders spend six months building something nobody asked for. Five days of forced validation is the single highest-leverage constraint in the programme.
- D7
- Fake door, landing page or waitlist live.
- D9
- Ten interviews on the solution, not the problem.
- D10
- Public checkpoint. Mentors respond. Public
0lines of product code before there is evidence someone wants it.
Build
Fourteen days, and the progress is public.
Teams choose their own stack. AI tooling is how a non-technical builder ships in fourteen days; it is not the identity of the programme. Mentor hours go to the teams struggling, not shared out for fairness.
- D15
- Public checkpoint. Every team demos. Public
- D20
- Public checkpoint. Stalling becomes visible. Public
- D25
- Freeze. Rehearse the launch.
2public checkpoints. Every team demos to every other team, so stalling becomes visible.
Launch
The highest-leverage day we own.
Demo Day is not a wrap-up. It is the single event that produces our marketing for the next batch, our credibility with incubators, and the first look investors get at teams nobody else has seen.
- D26
- Public launch. Product Hunt, X, wherever it fits.
- D28
- First users. First revenue attempts.
- D30
- Live pitch. Mentors, alumni, investors, audience. Public
1live pitch, in front of mentors, alumni, investors and an audience.
Four public checkpoints
Nowhere to hide.
Four times in thirty days, every team stands up in front of every other team. Each one is documented. It is how stalling gets caught by day fifteen, and it is the only content the batch ever needs to produce.
Day 10Six teams, one wall of interview notes. D10
Validation
Evidence on the table. Mentors respond to what was learned, not what was built.
Day 15A laptop turned to the room. D15
First demo
Every team shows every other team something that runs. Progress becomes visible.
Day 20The same laptop, a different screen. D20
Second demo
Five days later, the same room. Stalling has nowhere to hide.
Day 30Stage wide, audience in shot. D30
Demo Day
The live pitch, streamed. Mentors, alumni, investors and the audience for the next batch.
Who enters a batch
Ambition is the qualifier. Nothing else is.
Builder 01Portrait · at a desk, mid-build. 01
Can code, cannot ship
Has the skill, has never turned it into a product, a team or a launch.
Builder 02Portrait · whiteboard behind, marker in hand. 02
Cannot code, will anyway
No technical background. Builds with AI tooling and teammates. Ambition is the qualifier.
Builder 03Three people, one table. 03
Already has a team
Enters intact, skips matching, goes straight to problem validation.
Not for
- A certificate
- Passive learning
- Capital without building
Those are downstream of us.
How you get in
Paid, and selective, on purpose.
A free programme fills with people who will not be there on day twenty. Payment is the cheapest available proxy for commitment, and completion rate is the metric that decides whether we have anything to show.
Low enough that no serious builder is excluded. High enough that no casual one enrols.
- 011 form
Apply
One form. What you have built, and what you have done without being asked.
- 021 rubric
Interview
One conversation, scored against one shared rubric for every applicant.
- 0330–40
Accept
We accept thirty to forty, never exactly twenty-four. The payment link ships with the acceptance.
- 0448–72 h
Confirm
Forty-eight to seventy-two hours to confirm the seat. Seats are confirmed by payment, not acceptance.
- 05Day −5
Cutoff
Lapsed seats backfill from a ranked waitlist. Hard cutoff five days before day one.
Batch C23-01
Twenty-four seats.
Thirty days.
- Seats available
- 24
- Seat price
- TBC
- Applications close
- TBC
Apply, interview, then a payment link if you’re in. Seats are confirmed by payment, not acceptance.