Cohorts
Programs that run again, without a rebuild
A cohort-based program is not a product page. It is the same curriculum, run again in March, and again in July, with different people in it and different numbers behind it.
- Sessions per cohort
- Unlimited
- Scaffold a 6-week grid
- 1 click
- Archived cohort history
- Permanent
- Schedule access
- Server-gated
01
Cohorts are objects, not duplicates
Open cohort eight and cohort seven closes behind it with everything intact. No copied pages, no drifting content, no guessing which version someone enrolled in.
- Archived cohorts keep their enrollment count and status breakdown
- Every enrollment stays attached to the cohort it belonged to
- Editing the program never rewrites a finished cohort's numbers
- Compare cohorts side by side on enrollment, revenue and completion
02
A schedule down to the session
Thirty sessions across six weeks, each with its own detail. Scaffold the whole grid in one action, then fill it in as hosts confirm.
- Time, host, join link, passcode, materials and recording per session
- A default room for cohorts that reuse one recurring link
- Live, upcoming and finished states that update themselves
- Recordings attach to the session they belong to
03
Access follows enrollment
The schedule is not merely hidden from people who have not paid. It is never sent to their browser in the first place.
- Session links are withheld server-side, not hidden with CSS
- Enrolled students see the schedule above the marketing content
- Unpaid students see the program page and an invoice
- Revoking enrollment removes access on the next request
Run your next cohort on it
We will set up one real cohort during the call so you can see the archive behaviour for yourself.