Batch C23-01 · applications open
Thirty days, start to Demo Day.
- Builders
- 24
- Teams
- 6
- Days
- 30
- Checkpoints
- 4
01The month
Four phases, drawn to scale.
01Days 1–5
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.
- Day 01Kickoff. Teams announced.
- Day 03Five user conversations, logged.
- Day 05One problem committed. No pivots after this.
5user conversations, logged, before day three.
Fig. 01Day 1 · Teams announced
02Days 6–10
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.
- Day 07Fake door, landing page or waitlist live.
- Day 09Ten interviews on the solution, not the problem.
- Day 10Public checkpoint. Mentors respond.
0lines of product code before there is evidence someone wants it.
Fig. 02Day 7 · The fake door
03Days 11–25
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.
- Day 15Public checkpoint. Every team demos.
- Day 20Public checkpoint. Stalling becomes visible.
- Day 25Freeze. Rehearse the launch.
2public checkpoints. Every team demos to every other team, so stalling becomes visible.
Fig. 03Day 15 · Checkpoint
04Days 26–30
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.
- Day 26Public launch. Product Hunt, X, wherever it fits.
- Day 28First users. First revenue attempts.
- Day 30Live pitch. Mentors, alumni, investors, audience.
1live pitch, in front of mentors, alumni, investors and an audience.
Fig. 04Day 30 · Demo Day
02Four public checkpoints
Nowhere to hide.
- Day10
Validation
Evidence on the table. Mentors respond to what was learned, not what was built.
- Day15
First demo
Every team shows every other team something that runs. Progress becomes visible.
- Day20
Second demo
Five days later, the same room. Stalling has nowhere to hide.
- Day30
Demo Day
The live pitch, streamed. Mentors, alumni, investors and the audience for the next batch.
03Who enters a batch
Ambition is the qualifier.
- 01
Can code, cannot ship
Has the skill, has never turned it into a product, a team or a launch.
- 02
Cannot code, will anyway
No technical background. Builds with AI tooling and teammates. Ambition is the qualifier.
- 03
Already has a team
Enters intact, skips matching, goes straight to problem validation.
Not for
- A certificate
- Passive learning
- Capital without building
04How you get in
Paid, and selective, on purpose.
- 01
Apply
One form
One form. What you have built, and what you have done without being asked.
- 02
Interview
One rubric
One conversation, scored against one shared rubric for every applicant.
- 03
Accept
30–40 accepted
We accept thirty to forty, never exactly twenty-four. The payment link ships with the acceptance.
- 04
Confirm
48–72 hours
Forty-eight to seventy-two hours to confirm the seat. Seats are confirmed by payment, not acceptance.
- 05
Cutoff
5 days before day one
Lapsed seats backfill from a ranked waitlist. Hard cutoff five days before day one.
- Seats
- 24
- Seat price
- TBC
- Applications close
- TBC
