Flow

How a cohort actually runs

We borrow from editorial calendars more than software sprints: fixed deadlines, visible redlines, and short written retros. Here is the path most teams follow after they enquire.

Before · messy briefs

PDFs with mismatched UTMs, creative folders named FINAL_v9_really, and exclusion lists living only in someone’s head.

After · boring clarity

Shared diagrams, named owners per arrow, and a stop rule taped beside the monitor — not glamour, just fewer surprises when spend turns on.

1. Step 1 — Enquiry triage

   Admissions reads for risk flags (impossible timelines, missing decision makers) before we schedule a call.

2. Step 2 — Fit call

   30 minutes: map your tools, name blockers, pick a program or hybrid bundle.

3. Step 3 — Pre-work

   Light reading plus one diagram exercise so day one starts mid-thought, not from zero.

4. Step 4 — Lab weeks

   Live critiques, quiet async blocks, and shared boards with explicit “do not target” columns.

5. Step 5 — Ship checklist

   You export UTMs, naming, and QA notes into whatever system your org already tolerates.

6. Step 6 — Retro email

   We send a short retro prompt; replies feed the next syllabus refresh.