The flow
Five quiet steps from enquiry to closing review.
We keep the path into a cohort short, mostly because the cohorts themselves are not short. The flow below is the sequence we walk every participant through, from the first note to the closing handover. None of the steps involve a sales call; the recommendation to join — or to wait a quarter — is made in writing.
- 01
Tell us where you sit
A short note via the contact form is enough — the engine you run, the shape of your team, and the operational habit you would like to change. We reply within two business days.
- 02
Map a fitting cohort
Together we pick a single cohort or a corporate engagement that aligns with the operational change you described. We will sometimes recommend waiting a quarter; that is part of the conversation.
- 03
Receive the studio packet
On confirmation we send a packet: schedule, sandbox credentials, mentor introductions, and the small reading list to skim before week one. The packet stays useful as a reference after the cohort.
- 04
Practise in the cohort
Two live mentor sessions per week, lab work in your own time, and one written review of your submitted scripts each week. The cadence is steady; the labs are deliberately small.
- 05
Closing review and handover
The final week converts the cohort into a single artefact you can show your team — a verification report, an autovacuum worksheet, or a refactored query with its rollback note attached.
Workflow before / after
What participants describe at the closing review.
- Before · After
Inherited runbooks updated only after incidents.
Runbooks updated after every cohort drill, in the same format every time.
- Before · After
EXPLAIN read in panic, fixed by trial and error.
EXPLAIN read slowly, fixed against a measured baseline.
- Before · After
Backups assumed to work because nobody has tested.
Backups verified monthly with a written report nobody hides from leadership.