Cohort.software · Recurring-series enrollment & roster continuity · 2026
Eight weeks. One enrollment. The same roster on week eight as week one.
One enrollment covers every occurrence the recurrence rule generates — move a week, skip a holiday, add someone in week three, and the roster holds. 0% commission on cohort tuition or dues, at any tier, ever — a facilitator keeps the whole tuition, not ninety percent of it.
Pricing shown on this page is the plan, display-only — no checkout, no card is charged anywhere on this site.
The product commitment
0% commission on cohort tuition, ever
Maven charges roughly 10% commission on cohort-style program revenue. Momence’s tiers are fee-heavy. Both scale their bite with the ticket — and a cohort’s ticket is tuition, not a drop-in fee, so the commission bite is structural, not incidental. Cohort.software takes 0% commission on tuition or dues at any tier, a promise Maven and Momence cannot structurally make while they monetize per-transaction. This is a product commitment, named factually against named competitors — not a dig, and no competitor copy or code is reused here.
The series lifecycle
One enrollment is a claim on every session in the series
It survives a moved week, a holiday skip, and a mid-series join. Five stages, a different grammar from a single-session booking flow:
1 · Set the cadence
A facilitator defines the recurrence rule once — “Tuesdays 6pm for eight weeks,” a term, an intake — and the rule expands to a deterministic set of occurrences. This is the recurrence-math layer the substrate names RFC-5545; a moved week or a holiday skip is stored as an exception on that set, not a hand-edit of twelve separate rows.
2 · Open enrollment for the whole series
Enrollment is sold once, for the arc, not per occurrence. Capacity-N applies to the series as a whole — the same shared booking law that governs a single session, extended over every occurrence the recurrence rule generates.
3 · The roster locks and travels with it
At intake the roster is decided once. From that point the roster is bound to the series identifier, not to any one dated occurrence — the seat is held for every occurrence in the series, not re-contested night to night.
4 · The calendar shifts and the roster doesn’t
A moved session, a holiday skip, or a mid-series join are exceptions applied to the occurrence set. The roster is untouched by any of them: nobody loses their seat when a week moves, and a facilitator can prorate a week-three join without re-keying the other eleven weeks.
5 · The cohort completes and rolls into the next intake
The series has a start date and an end date. Completion is a first-class state — “finished together” — not an ongoing schedule with no edge. A finished cohort can roll its roster into the next intake as a distinct, opt-in step.
What’s built, what’s planned
Honest about the engine and the skin
Capacity-N is a shared, built engine mode across the schedule family — named once here as the seat law under every occurrence, and not re-argued. The recurrence-expansion, series-enrollment, and roster-continuity surface that makes cohort.software cohort.software is planned, not yet live on this site.
Capacity-N seat law
The shared seat-law engine mode the schedule family rides. Cohort composes it as the seat law under every occurrence in a series — engine mechanics, shared with classly, stated once here and not re-argued: the single-session concurrency story is classly’s page, not this one.
Recurrence rule & occurrence expansion (RFC-5545)
A cadence — “Tuesdays 6pm for eight weeks” — expands to a deterministic occurrence set on the RFC-5545 recurrence standard, with exceptions (a moved week, a holiday skip) stored as data. This is planned: the cohort.software-branded expansion surface is not yet live on this site.
Series-enrollment layer
One enrollment action that claims a seat across an entire occurrence set, instead of one booking per dated session. Planned: the enrollment surface described on this page is the product plan, not a live flow today.
Fixed-roster continuity
The roster travels with the series identifier through a moved week, a holiday skip, and a mid-series join, instead of being re-derived from who showed up that night. Planned: this continuity behavior is the product plan, not a live guarantee today.
Boundary
classly sells a seat in a session. cohort enrolls a person in a series. classly is drop-in group sessions where the roster is whoever booked that night and the hard problem is the last seat. cohort is a fixed roster progressing through a recurring series together, where the roster is decided once at intake and the hard problem is holding it intact across every occurrence the recurrence rule generates — through a moved week, a holiday skip, a mid-series join, and a term boundary. Same capacity-N booking law underneath, stated once, honestly, as a shared engine mode; the recurrence and roster-continuity layer on top is what cohort.software is. classly.software is named here as a sibling brand built on the same core — it is never described as live, shipped, or in production; cohort enforces nothing about classly’s status.
Who this is for
A facilitator running a finite program, not a studio filling tonight’s room
Corporate L&D and training-cohort leads, bootcamp section leads and tutoring pods, coaches and therapists running an 8-week group, and wellness studios selling a term or session block rather than drop-ins. Their pain is continuity and completion, not fill rate: who is continuing next term, how to prorate a week-three join, how to move a session off a holiday without twelve people re-booking, and whether the group that started together actually finished together.
Explicitly out of scope on this page: K-12 institutional timetabling, 1:1 appointments, and field dispatch — K-12 and dispatch are schedule.software’s lane and 1:1 is a planned sibling module (dibs), not this product. What either of those ships is stated on its own page; cohort.software claims nothing about their status.
Pricing (display-only)
The plan — no checkout, no card charged
Self-serve entry with a custom domain not gated to a top tier, unlike Disco (quote-only entry) or Teachfloor (custom domain gated to a roughly $349/mo tier). Every tier: 0% commission on tuition, ever.
Solo
Solo
$29/mo (plan)
One facilitator, one series at a time — display-only, no card charged
- Recurring-series enrollment (planned)
- Fixed-roster continuity (planned)
- Capacity-N seat law (shared engine)
- 0% commission on tuition, ever
Pro
Pro
$79/mo (plan)
Multiple concurrent series/intakes — display-only, no card charged
- Everything in Solo
- Mid-series join & proration tools (planned)
- Next-intake roster roll-over (planned)
- Custom domain, not top-tier-gated
Business
Business
Custom (plan)
Corporate L&D / multi-cohort programs — display-only, no card charged
- Everything in Pro
- Multi-cohort / multi-facilitator programs
- Self-serve entry, no quote-only gate
- 0% commission on tuition or dues, ever
All figures above are the plan, not live billing. No live Stripe or checkout integration exists on this site; no card is charged.
FAQ
Questions, answered honestly
What is the difference between cohort.software and classly.software?
classly sells a seat in a session. Cohort enrolls a person in a series. classly’s roster is whoever booked that one dated night; cohort’s roster is decided once at intake and held across every occurrence a recurrence rule generates. classly is named here as a sibling brand built on the same capacity-N engine — it is never described as live, shipped, or in production on this page.
Is the recurring-series enrollment live yet?
No. Recurrence expansion, series-enrollment, and roster-continuity are PLANNED on this snapshot: they are the product plan for cohort.software, not a live flow you can enroll through today. The capacity-N seat law underneath is the one piece that is a shared, built engine mode across the schedule family.
Is the 0% commission on tuition a live billing feature?
The commitment is a product commitment, not a live billing state: cohort takes 0% commission on cohort tuition or dues, at any tier, ever — a promise Maven’s 10% commission and Momence’s fee-heavy tiers cannot structurally make. All pricing shown on this page is the plan, display-only. There is no live checkout and no card is charged anywhere on this site.
Who is cohort.software actually for?
A facilitator running a finite program with a start date and an end date — not a studio owner filling tonight’s room. Corporate L&D and training-cohort leads, bootcamp section leads and tutoring pods, coaches and therapists running an 8-week group, and wellness studios selling a term or session block rather than drop-ins.
What happens when a session moves, or someone joins in week three?
A moved session or a holiday skip is planned to be an exception stored as data against the occurrence set, not a hand-edit of twelve rows — nobody loses their seat when a week moves. A mid-series join is planned to carry proration and a makeup-session path so a week-three joiner does not simply lose the first two weeks.
What is explicitly out of scope for cohort.software?
K-12 institutional timetabling, 1:1 appointments, and field dispatch are explicitly out of scope here. K-12 timetabling and field dispatch live on schedule.software; 1:1 appointment booking is a distinct planned sibling module, not this product.
How is cohort priced against Maven, Momence, Disco, Circle, and Teachfloor?
Maven charges roughly 10% commission on cohort-style program revenue; Momence’s tiers are fee-heavy; Circle bundles community and cohort tooling with its own transaction and tier costs. Disco is quote-only for entry; Teachfloor gates a custom domain behind a roughly $349/mo tier. Cohort’s plan is self-serve entry with a custom domain not gated to a top tier, and 0% commission on tuition at any tier — named factually as the competitive comparison; no competitor copy or code is reused here.
What happens if a facilitator outgrows cohort.software?
The same shared booking-law substrate that underlies cohort also underlies the rest of the schedule family, so a facilitator can grow into 1:1 appointments (dibs, planned), a resource-booking module (room.software, planned), or K-12/dispatch scheduling (schedule.software) without migrating off the engine their roster already runs on. This growth path is planned. schedule.software and homeroom.software are the two sibling sites linked from this page; what each of them ships is stated on its own page, and cohort.software asserts nothing about any sibling’s status.
Next step
Book a conversation
There is no pricing commitment and no signup. If the series-enrollment model fits your program, we walk through what access looks like as the recurrence and roster-continuity surface comes online.