Course and cohort delivery
Curriculum structure, scheduling, live and self-paced modes, and the enrolment logic institutions actually need.
- Curriculum
- Cohorts
- Enrolment
We make progress and assessment models explicit, then build the feedback loops that show instructors where a learner needs help while there is still time to give it.
Where engagements usually start

Mastery-based
progress measured against evidence
WCAG 2.2 AA
accessible across devices and abilities
Early signal
at-risk learners visible in week two
A learning platform serves students, instructors, administrators, and institutions, and each measures success differently. Most systems record activity because activity is easy to capture, then report completion as if it were understanding. We define the mastery model first, instrument against it, and design intervention tools so the insight reaches the person who can act on it.
Video watched and modules finished are easy to record and tell you very little. Without an evidence model, reporting flatters everyone and helps nobody.
Learners want momentum, instructors want signal, administrators want compliance, institutions want outcomes. A single undifferentiated interface serves none of them well.
Learners arrive on shared devices, slow networks, and assistive technology. Anything that assumes a modern laptop excludes part of the cohort.
Each one can be built on its own or added to what you already run. Together they cover delivery, evidence, and the institutional plumbing around both.
Curriculum structure, scheduling, live and self-paced modes, and the enrolment logic institutions actually need.
Item banks, rubrics, integrity controls, and verifiable credentials tied to demonstrated evidence rather than attendance.
Learner models that adjust sequence and difficulty from real performance, with the reasoning visible to instructors.
Dashboards built around the next action, surfacing which learners need contact this week and why.
LTI, SIS, roster sync, and single sign-on so the platform fits the systems a school or employer already runs.
Screen-reader support, captioning, keyboard paths, and low-bandwidth modes designed in rather than remediated.
Every stage produces something the next one needs, which is why the mastery definition comes before a line of tracking code.
Stage 1 of 4
We agree the evidence that counts as learning for your subject before deciding what the product will record.
Stage 2 of 4
Interactions are captured against a standard model, so analysis is possible without re-instrumenting later.
Stage 3 of 4
Signals are turned into a weekly action list, and we measure whether intervention actually changed the outcome.
Stage 4 of 4
Assistive-technology testing and load rehearsal for enrolment peaks happen before launch, not after the first term.
Usually not the whole thing. Enrolment, delivery, and grading are commodity. The defensible part is your pedagogy, your assessment model, and your data. We often build that as a product that integrates over LTI with whatever LMS an institution already runs.
Tell us what mastery means in your subject and where the current product stops short. We will come back with an evidence model and a first release plan.