Українська
РусскийEvery cohort is put together from scratch
A new student spreadsheet, a new chat, materials moved by hand and accounts created one by one. The producer spends a week on preparation that adds nothing to the product.
For online schools
Cohorts, curators and sales in one account
Put a cohort together, get your students to the finish line and work out the return — without merging data from five services by hand.
A new cohort is a copy of the course
The previous cohort stays untouched, with its whole history
Follow-up on a Kanban board
You see who hasn't paid and which stage they are stuck at
Curators and lecturers
Each of them has their own account and their own group
Completion rate lesson by lesson
Visible at lesson three, not at the end of the cohort
What eats a school's margin between cohorts
When there is one course and thirty students, the manual work goes unnoticed. By the third cohort and the second program it turns into a separate salary line in the team.
Follow-up rests on the manager's memory
Who left a request and never paid, who has already been called, who asked to be reminded after payday. Half of the unpaid orders simply drop out of sight.
Curators work in messengers
Assignments arrive in direct messages, submissions get lost, there is no review history. When a curator leaves, the context for the whole group leaves with them.
The completion rate falls and nobody knows why
Out of a hundred who start, fewer than half reach the certificate. What exactly happened is anyone's guess: maybe the fourth module turned out to be too heavy, maybe the assignment was worded badly, maybe the group simply lost its pace after the holidays. Without data on every lesson the next cohort will walk into the same trap, and the review will again come after the fact.
The unit economics of a cohort are counted by hand
Traffic in the ad account, payments in the payment system, the completion rate in the curator's spreadsheet, refunds in an email thread with the accountant. To find out whether the launch paid off, the producer spends a week merging exports. The decision about the next cohort is taken at the point when it is already too late to change anything in the current one.
Problem and solution
What a setting closes instead of a new hire
On the left — the tasks schools usually hire an assistant for. On the right — how they are handled inside the account.
Preparing a cohort takes a week
Materials are moved over again, accounts are created by hand, the chat is set up from scratch.
A copy of the course for a new group
You copy the course, change the dates and the plan. The previous cohort stays untouched, together with its whole history of reviews and grades.
Unpaid requests get lost
The list is in a spreadsheet, the statuses are in someone's head, reminders happen whenever there is time.
A Kanban board for order processing
Every request sits at its own stage, statuses change in one click, and the sales manager works only with the unpaid ones and sees nothing else.
The upsell to the plan with a curator is done by hand
A duplicate course for the second plan, the extra payment by bank transfer, access granted manually.
Differentiated plans inside one course
One course with a different set of lessons and a different price. The access upgrade is bought right in the student's account, at the moment of peak interest.
Homework review lives in the curator's direct messages
Submissions get lost, no history is kept, and nobody sees the quality of the review.
Review inside the account, with a history
Assignments, grades, comments and attempts are stored with the course. The curator sees only their own group — and you see the curator's work.
The landing page sits with a contractor and a separate subscription
Editing a block means a ticket for the contractor, and requests are transferred by hand.
A website builder inside the platform
The course page is assembled from blocks, takes registrations and payments right away and needs no separate bill. The demo lesson opens right on the landing page.
The results of a cohort are summed up after the fact
The summary takes a week to put together, by which point there is nothing left to fix.
A performance table and per-lesson analytics
You see how much time the group spends on each lesson, where it stalls and who dropped out. Fixes go in during the cohort, not after it.
Three typical school scenarios
The situations people come to us with most often, and how they get sorted out on the platform.
A school of digital professions, 4 cohorts a year
Preparing a cohort took a week of the producer's time
The situation
Before every intake the producer moved the materials over, created accounts, set up a chat and matched payments against a spreadsheet by hand. The completion rate was counted at the end, when there was nothing left to fix.
What we did
We copied the course to a new group and changed the dates. We switched on the Kanban board for unpaid orders. The curators got roles with access only to their own lessons and their own group.
The result
Preparing a cohort came down to copying the course and changing the dates. Follow-up runs in one window. A dip on a lesson is visible in week three, and the program is fixed as the cohort runs.
A school with two plans
The plan with a curator was sold as a duplicate course
The situation
The “on your own” package and the “with a curator” package lived as two separate courses. The upgrade was handled by a manager: the extra payment by transfer, access granted by hand, edits in two places for any change to the program.
What we did
We built one course with differentiated plans: a basic set of lessons and an extended one with curator review. The upgrade was moved into the student's account. The curator was tied to their own group.
The result
One course instead of two: the program is edited once. The student pays the difference themselves at the moment they feel they can't cope alone — with no messages back and forth with a manager.
A school with an international audience
Some payments failed and the revenue sat with the platform
The situation
Students from different countries, but only one payment method was available. Some payments never went through, and the school found out about it only from complaints to support. The money arrived on the previous platform's payout schedule.
What we did
We connected several payment gateways with different currencies and crypto payments. We set up notifications about failed payments in the owner's chatbot.
The result
A student pays the way people in their country normally do. The money lands in the school's account on the day of payment. A failed payment is visible immediately, and the manager writes to the person while they are still at their computer.
The life of a cohort on the platform
Five stages, and at every one of them a school usually loses either money or students.
- Announcing the intakeA landing page with a demo lesson
- Requests and follow-upA Kanban board with order statuses
- Cohort startAccess opens automatically
- Curator reviewHomework and grades in the account
- Completion rate reviewAnalytics for every lesson
The next cohort starts as a copy of the course, not as a build from scratch
For the school team
Roles, reports and money paid direct
A school is no longer one person. The platform is built on the assumption that the instructional designer fills the course, the curator reviews the work, the manager sells and the producer looks at the numbers.
- Co-organizer, lecturer, curator and manager roles with separate accounts
- A Kanban board for order processing and a dashboard with sales statistics
- Payments straight to the school's own account, with no percentage of turnover
- Certificates with a QR code and a graduate database that works as a specialist board
- Push and triggered campaigns to bring back the students who dropped off
We speak the language of a school, not of an abstract LMS
- cohort
- launch
- follow-up
- completion rate
- curator
- instructional designer
- producer
- upsell
- stop-lesson
- performance table
- module deadline
- graduate database
Questions from school owners and producers
Put your next cohort together in one evening
15 days of full access: the course, the landing page, the plans, the curator roles and the analytics. Enough to run the whole cycle from the announcement to the first payment.
No card needed. We'll help you move your courses over from another platform.