Skip to content
Who runs the room

The credential here is the artifact.

Everyone who holds this room shipped the work first: agents, workflows and dashboards in production, on real data, still running.

Real data. · Live. · Yours to keep.

Apply for a cohortSee the proof
The standard

The bar every seat is filled against.

No degrees, no company logos. Only what an operator built and keeps running transfers to your stack, so that is what gets listed.

When your integration breaks at 4pm on day two, you want someone beside you who has hit that wall. One question fills every seat: have you operated the thing you are here to coach.

The operators

The people holding the room.

Below is the bar each seat is filled against, not who fills it. Names go on the record with the first public Protocol; we would rather leave them blank than invent them.

Lead

Lead operator · runs the build

Lead operator

The lead seat goes to someone who has built and runs what this room builds in two days.

Shipped and still running

  • Multi-agent orchestration that runs unattended inside a live business.
  • Self-refreshing operations dashboards on real revenue and ops data.
  • The operator-brain context files and skills the cohort spine is taught from.
Clauden8nMCPShopifyNotion

Floor coach

Floor coach · works the room

Floor coach

This seat goes to someone who has shipped reconciliation agents inside finance and ops teams. They know where a non-technical builder gets stuck.

Shipped and still running

  • Reconciliation and reporting agents that run before the workday starts.
  • Scoped MCP integrations against live ledgers, with the data never leaving the owner's accounts.
  • Non-technical operators coached from frozen to running on their own data.
ClaudeExcelMCPPython

Floor coach

Floor coach · works the room

Floor coach

This seat goes to someone who builds comms, research and synthesis workflows chiefs of staff and PMs walk out with.

Shipped and still running

  • Claude → ElevenLabs → HeyGen content pipelines triggered by one command.
  • Living product and exec dashboards that answer questions from the team's own data.
  • Artifacts kept model-agnostic, so they survive the tool underneath changing.
ClaudeElevenLabsHeyGenn8nJira
The ratio is the moat

Three operators for twenty-five builders. On purpose.

The ratio is what makes “you will build it live” true for someone who has never coded. If a room fills past twenty-five, the cap holds and the overflow rolls to the next Protocol.

The ratio

1 lead + 2 coaches

About one coach per eight builders, so the moment something breaks, someone is already there. A fixed cost we never thin to take more money.

The room

Twenty-five seats

Application-only, one cohort a month. Small enough that the operators learn your stack instead of running a demo deck.

Built to outlast one person

A written-down spine

The curriculum lives in a document, not in one head. Coaches co-lead before they lead.

Application-only · One cohort a month · 25 seats

Build in the room these operators run.

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

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

Built, or your money back.

Apply for a cohortNot ready? Get the free preview