Skip to content
Who runs the room

Operators teach this. Not lecturers.

You can’t coach someone to build a running system if you’ve only described one. Everyone who holds this room has shipped the work first — agents, workflows and dashboards in production, on real data. The credential is the artifact.

Real data. · Live. · Yours to keep.

The standard

Shipped, not titled.

We don’t list degrees or company logos here. We list what each operator has built and kept running, because that is the only thing that transfers to your stack on a Saturday.

When a coach sits beside you and your integration throws an error at 4pm on day two, you want someone who has hit that exact wall in their own work — not someone reading from a slide. That is the whole hiring bar: have you operated the thing you’re here to teach.

The operators

The people holding the room.

One lead runs the build from the front; two floor coaches move through the room. Each seat is filled against the same bar — has this person shipped and kept running the kind of system they’re here to coach. The names go on the record with the first public Protocol.

Lead

Lead operator · runs the build

Lead operator

The lead has spent years building and running the kind of systems this room builds in two days — agents, orchestration and dashboards in production, not in slides.

Shipped / run

  • Shipped multi-agent orchestration that runs unattended inside a live business.
  • Stood up self-refreshing operations dashboards on real revenue and ops data.
  • Wrote the operator-brain context files and skills the cohort spine is taught from.
Clauden8nMCPShopifyNotion

Floor coach

Floor coach · works the room

Floor coach

A coach who has shipped data and reconciliation agents inside finance and ops teams — fluent in the failure modes a non-technical builder hits at 4pm on day two.

Shipped / run

  • Built reconciliation and reporting agents that run before the workday starts.
  • Connected scoped MCP integrations against live ledgers without data ever leaving the owner's control.
  • Coached non-technical operators from frozen to running on their own data.
ClaudeExcelMCPPython

Floor coach

Floor coach · works the room

Floor coach

A coach who builds comms, research and synthesis workflows — the second-you systems chiefs of staff and PMs walk out with, shipped and kept alive across model changes.

Shipped / run

  • Shipped Claude → ElevenLabs → HeyGen content pipelines triggered by one command.
  • Built living product and exec dashboards that answer questions from the team's own data.
  • Kept artifacts model-agnostic so they survive underlying tool churn.
ClaudeElevenLabsHeyGenn8nJira
The ratio is the moat

Three operators for twenty-four builders. On purpose.

The coach ratio is what makes “you will build it live” true for someone who has never written a line of code. It is a fixed cost per cohort, and it is non-negotiable down — if a room fills past twenty-four, the cap holds and the overflow rolls forward. We never thin the ratio to take more money.

The ratio

1 lead + 2 coaches

Roughly one coach for every eight builders, so the moment something breaks on your stack, someone is already there. This ratio is a fixed cost we never thin to take more money.

The room

~24 seats

Application-only, one cohort a month. Small enough that the operators learn your stack — not a generic demo deck.

Built to outlast one person

A teachable system

The spine is written down, not locked in one head. Coaches co-lead before they lead. The school is designed to survive any single operator.

Application-only · One cohort a month · ~24 seats

Build in the room these operators run.

The same people who shipped these systems sit beside you while you build yours, on your real data, across one live weekend.

$500Rs 41,500
No-cost EMI in India

Built, or your money back.