Your venue · half a day to two days · thirty to ninety members · we bring four engineers
Most members arrive at stage one: they prompt, they get a draft, they paste it somewhere. A few have a prototype that feels productive and has no database, no login, no review and no owner. In one or two days every member moves through the stack to a full stack application on their own data: a login, an admin, real records, a dashboard, deployed on their own domain.
The second day adds hardening, a nurture workflow and the first managed agent. The lesson lands because they build it, not because they hear about it.
The Melbourne play, block by block. A half day runs the first three blocks; two days run all of them.
Why AI systems beat AI tools, then an interview with Claude that writes each member's plan. Before lunch: repository, project, database, a login, a live form and one admin page. The afternoon builds the whole CRM from the plan, then ninety days of realistic data and a dashboard on top.
A QA plan and a senior code review, then every member checks their live site on their own phone. Email follow up that runs on its own. An agent that starts work at seven every morning, and a team of them for anyone whose first agent was already live. A written reflection to close.
Not a prototype in a chat window. A deployed application with a login, an admin and your real records, on your own domain, before the room closes.
Keys in environment variables, the database reached only from the server, every change through a reviewed pull request. The thing security asks for, built in from day one.
An agent that runs on a schedule, reads the company database, acts within its permissions and logs every run. The kind a business can build on.
Product manager, developer, QA and devops, configured on your repository, so the team ships the next feature on Monday without us.
EO Melbourne, October 2026: sixty founders, two days, 25 live sites, NPS 88 from 24 responses.
Each one links to its public recap: the film, the numbers, the builds and the members on camera.
It is quoted per chapter after a call with the learning chair or chapter manager: the number of days, the member count and the engineers it takes set the price. Chapters have run it as a member benefit, as a paid event and as a sponsored one. The quote is in writing within two days.
Thirty to ninety. EO Melbourne ran sixty at Kooyong with four engineers moving between tables. Above ninety we split the room into two sessions so every table still has an engineer within a minute.
No. Most arrive having never opened a terminal. Laptops stay closed for the first hour, every block is one prompt, and engineers are at the tables. By lunch on day one every member has a live page on their own domain.
Each member builds on their own business: their customers, their offers, their messy spreadsheet. Everything lives in accounts in their own name on GitHub, Vercel and Supabase. The chapter holds nothing and neither do we.
Each member sets up the stack from our one page guide, about an hour, and we run a thirty minute online check the week before. The chapter books the room, the wifi and lunch; we bring the engineers, the plan and the prompts.
A live site, a working CRM on their own data, a managed agent running on a schedule, and four agents on their repository to keep building. Plus the written feedback the chapter gets to publish, as EO Melbourne did.
