Help · Cohort.software

How the lifecycle works, what's built, and the honest answer to what isn't.

This page is the long answer. Every section is grounded in the same data the rest of the site renders from — nothing here is a separate story, and nothing is a stub.

Getting started

Three steps before anything else.

1 · Tell us the shape of your cohort

Email [email protected] with how many people, how many weeks, and what breaks today. One paragraph is plenty.

2 · An honest built-vs-planned walkthrough

We show the capacity-N engine that is real today and name that recurrence, series-enrollment, and roster-continuity are the plan — not a live flow.

3 · Reserve early access

No account and no charge is created. The full walkthrough lives on Getting started.

How the lifecycle works

Stage by stage, with the honest build status.

The five-stage series lifecycle described on the home page. Every stage below is the product plan; the one piece that is a shared, built engine mode is the capacity-N seat law that the enrollment stage will ride — it is not itself a lifecycle stage, and none of these stages is live on this site yet:

The series lifecycle, stage by stage
#StageStatus today
1Set the cadencePlanned — not yet live on this site
2Open enrollment for the whole seriesPlanned — not yet live on this site
3The roster locks and travels with itPlanned — not yet live on this site
4The calendar shifts and the roster doesn’tPlanned — not yet live on this site
5The cohort completes and rolls into the next intakePlanned — not yet live on this site

What’s built, what’s planned

The full honesty inventory.

Capacity-N is a shared, built engine mode; recurrence expansion, series-enrollment, and roster-continuity are the product plan, not live on this site today.

Shared engine mode · built

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.

Planned · not yet live on this site

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.

Planned · 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.

Planned · not yet live on this site

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.

White-label & custom domain

Named at Solo, removed at Pro.

A custom domain is named starting at the Solo tier; white-label branding removes the badge starting at Pro; per-tenant licensing is a Business-tier plan. Domain and brand binding is handled by the shared owner-context engine the platform is built around; the self-serve connect-your-domain and theming surface for cohort.software is not built yet. The consent/legal footer and the outbound sending domain stay ours at every tier. Full scope is on the home page’s white-label & domain section.

Troubleshooting the edge cases

What happens when a session moves, or someone joins late.

A session moves, or a holiday is skipped

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. Not yet live on this site.

Someone joins in week three

Planned to carry proration and a makeup-session path, so a week-three joiner does not simply lose the first two weeks. Not yet live on this site.

A cohort finishes and the next intake starts

Completion is planned as a first-class state — a finished cohort can roll its roster into the next intake as a distinct, opt-in step. Not yet live on this site.

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.

Do I need to pay extra to use my own domain and remove your branding?

No, not for the domain. A custom domain is named starting at the Solo tier — most cohort and program tools charge for that and reserve full white-label for an enterprise contract. Removing our branding is one paid tier up, at Pro, not a sales call. The self-serve connect-your-domain and theming surface for cohort.software is not built yet, the same honest scope as the recurring-series enrollment surface itself. Notification emails carry your display name and reply-to; the legal and consent footer stays ours by design. Pricing is the plan; there is no live checkout on this page.

Where do I go to actually start, or to read the full detail on any of this?

“Getting started” walks the three-step, no-sign-up process and the three buyer tracks. “Help” is the long page: the series lifecycle stage by stage, the white-label and domain scope, the build inventory, and every edge case — a moved session, a late join, a finished cohort rolling into the next intake. Both are linked in the footer and the main nav.

What a cohort enrollment record holds

A scheduling product’s narrow appetite, said plainly.

Cohort.software books time and holds a roster tied to a series identifier — not a photo store, not a facial-recognition surface, not an advertising profile. This product is explicitly out of scope for K-12 institutional timetabling; it does not target minors by design, and it runs no third-party analytics or advertising script.