Run the weekend privately, on your team’s data.
The same two days, scoped to one team, run on your own stack — everyone builds one system and keeps it.
Your stack. · Your data. · Everyone building.
Scoped to your team. Built on your systems.
A private cohort is a different engagement, not a bulk order of seats. The two days get built around your stack and your data, so what the team keeps is the real thing.
01
We scope the room.
One call: your stack, the work eating the week, what you want running by Sunday. The two days get shaped around that, not a syllabus.
02
Module 0, against your environment.
Redact-then-prompt, scoped connections, no-train settings, configured before anything real is touched. Your data stays in your accounts; the connection comes off afterwards.
03
Two live days, your team only.
Lead instructor and floor coaches, the same ratio as a public room. Everyone builds the same thing at once, which is why it gets used.
04
Everyone keeps it.
Prompts, skills, agent configs, workflows and dashboards go to the team, with recordings, rollout plan and a follow-up office hour. Yours to re-run and extend.
One system, owned by the people running it.
Training one person and waiting for it to spread is how most of this dies. Building it together, in one room, on the team’s own systems, is why the private format works.
One system, not eight tabs.
Eight private chat windows share nothing: not the prompts, not the context, not the standard. The weekend ends with one system all eight run.
Your team's judgment, written down once.
The context and orchestration layer holds how your team decides, so the output carries your standards, not a vendor's defaults.
Built to outlast the tools.
Model-agnostic by design. Swap the model or the connector underneath and the layer your team owns keeps working.
Working systems on your data, kept for good — not a hardened production deployment with a support contract. We say which is which before you buy.
The same spine, pointed at your team’s work.
Founders & ops
The week stops being spent rebuilding the same reports, posts and follow-ups by hand.
Keeps: a shared command center over orders, ads and ops.
Product
Answers pulled from your own data by whoever needs them, instead of a PRD nobody reads.
Keeps: a living product dashboard the whole team can query.
Finance
Reconciliation and reporting agents on your real ledgers, owned by the people who run the close.
Keeps: a one-command close that runs on a schedule.
Chiefs of staff & ops leads
Nothing gets dropped between back-to-backs, because the triage happens whether or not you're in the room.
Keeps: comms triage, research and a self-refreshing exec dashboard.
Quoted per engagement, not per seat.
A private cohort is priced on team size and integration depth, so there is no single number to publish. You see the whole figure in writing before anything is booked.
No checkout, no coupons, no regional markup. The number is quoted once we’ve scoped the room.
Tell us the team and the work; a real number and a date come back.
Talk to us
Bring the weekend to your team.
Tell us the team, the stack, and what’s eating the week. A person reads every enquiry and comes back with scoping questions and a date or two.
Private cohorts run alongside the public calendar, so the dates bend to your team’s.