Enrolment, cohorts, and completion in one system.
Education has an unusually long, unusually emotional consideration window: people enquire in January and enrol in September. This pack models enquiries, cohorts, and enrolments so that months-long nurture is a workflow rather than a person’s good intentions.
What lands in your workspace on day one.
Not a template gallery — objects with real relationships, a pipeline with real stages, and automations already running.
- Enquiryprogramme of interest, intake, funding route, readiness
- Cohortprogramme, start/end, capacity, enrolled count, tutor
- Enrolmentstudent, cohort, payment plan, status, start date
- Studentprior learning, progress, attendance rate, completion status
- Sessioncohort, date, attendance, materials, tutor
Rename, reorder, or retire any stage. Add a second pipeline for a different motion.
Automations, not suggestions.
These are live the moment the pack installs. Every one is editable, and every run keeps a step-by-step trace.
Long-horizon nurture
An enquiry for a September intake receives a paced sequence over months — content, open-day invitations, and deadline reminders — that adapts to which intake they actually want.
Cohort capacity alerts
Cohorts filling faster or slower than plan surface early, while there’s still time to move marketing spend or open a second cohort.
Attendance and drop-off watch
Two consecutive missed sessions trigger outreach and a tutor task, because early absence is the most reliable predictor of withdrawal.
Completion and alumni
On completion, students move into an alumni segment for testimonials, referrals, and next-programme offers instead of falling out of the database.
The problems this pack was shaped around.
The gap between enquiry and enrolment is where revenue leaks
Nobody can manually keep a relationship warm for eight months across hundreds of enquiries. Because a workflow can genuinely wait months — durably, surviving deploys and restarts — the nurture that decides your intake numbers doesn’t depend on anyone remembering.
Cohorts have capacity, and capacity has a deadline
A cohort that’s 40% full four weeks out is a marketing decision you need to make now, not a fact you discover at the start date. With cohorts modelled and enrolments counted live, fill rate is a dashboard and an automation trigger.
Retention starts at session two
Withdrawal is usually visible in attendance long before it’s announced. Attendance recorded against sessions means drop-off risk is a filter, and outreach is automatic while it can still change the outcome.
The same platform, whatever you sell.
A pack is configuration on top of one shared data model, one filter engine, and one automation engine. That is why you can change any of it without losing the parts that work.
Education, answered.
Can it handle several intakes of the same programme?
Yes — a cohort is its own record, so the same programme can run monthly, quarterly, or annually with separate capacity, tutors, and nurture timing.
Does it handle payment plans?
It tracks payment plan and status on the enrolment and can automate reminders on missed instalments. Actual payment processing stays with your payment provider via the API.
Can tutors see only their own cohorts?
Yes. Row-level permissions scope views and dashboards, so tutors see their cohorts and administrators see everything.
Is it suitable for one-to-one coaching rather than cohorts?
Yes. Coaches typically drop the cohort object and use sessions against the student directly — which is exactly the kind of change the pack format is designed to let you make.
Start with the education pack already installed.
Free workspace, the objects and automations above set up at onboarding, and every price published. Customise from something that works.
Free trial · no card required · every price published