Know every student before they slip away
A student CRM built for academies, not for salespeople. Attendance, progress, schedules, assignments and parent contacts — one record per learner, updating itself as your classes run.
Most churn is visible weeks in advance
Ask an academy owner why a student left and you usually get a shrug and a theory. It's rarely a mystery — the warning signs were there. Attendance quietly slid from reliable to patchy over a few weeks. Assignments stopped being submitted. The parent went quiet.
The signals aren't hard to spot. They're hard to spot when they live in three different tools and nobody has time to join them up. So the record stays a spreadsheet somebody updates on Fridays, if they remember, and the student is gone before anyone notices.
Clasify keeps one record per learner and fills it in as classes actually happen — so when a teacher asks "how is Sara doing?", the answer takes four seconds, not four tabs.
What you get
Everything below is in the admin dashboard today.
One record per student
Contact details, level, assigned teacher, parent name and notes — the whole history of a learner in one place, not spread across a spreadsheet and three chat threads.
A directory that scales
Search your entire roster instantly and page through hundreds of learners without the list ever slowing down. Finding a student takes seconds, not tabs.
Attendance without a register
Presence is recorded the moment a student joins the live room. Attended, missed and excused are tracked per lesson and roll up into reports on their own.
Progress you can actually see
Lessons taken, lessons remaining, attendance rate and last activity — per student. The signals that predict churn, visible in week three instead of month three.
Schedules and enrollments
Enroll a student into classes, or give them a recurring weekly timetable that generates its own sessions. Set the rule once; the calendar builds itself.
Assignments and submissions
Set work, collect submissions and keep every piece of it attached to the student it belongs to — so a teacher can see the whole picture before a lesson starts.
Contact details encrypted at rest
Phone numbers and parent names are the most sensitive data a school holds and the most casually handled. Here they're encrypted, not sitting in plain text.
Deleting is reversible
Removing a student is a soft delete that needs your admin password, and it lands in Trash. Someone will eventually delete the wrong record — this makes it an inconvenience, not a catastrophe.
How it works
Three steps, then it runs itself.
Add the student
Name, email, level, parent contact. They get their own login to your branded academy — not to ours.
Assign a teacher and a timetable
Attach them to a teacher and enroll them into classes, or set a recurring weekly schedule and let the sessions generate themselves.
Let the record fill itself in
Attendance, progress and submissions land on the student's record automatically as classes happen. You read it; you don't maintain it.
Excused absences don't count against anyone
An excused absence is recorded, but it's excluded from the denominator when attendance rates are calculated. It's a small detail that stops illness from making a perfectly healthy cohort look like it's disengaging — and stops you from acting on a number that was never true.
Put your roster somewhere it works for you
Every plan includes the full student CRM — the tiers only change how many learners you can hold. Launch your branded academy and bring your students with you.
Plans start at EGP 1,999/month. No free tier — every plan includes every feature.
Straight answers
What admins ask before they move a roster across.
Only an admin of that academy. Those two fields are encrypted at rest and are decrypted for an academy admin and nobody else — not the teachers, who see the learners assigned to them by name, schedule and attendance, and not our own staff. Each academy is an isolated tenant, so one academy's contact details are never reachable from another's.
Nothing is destroyed. Removing a student is a soft delete: the record moves to Trash, where an admin can restore it with its enrolments, attendance history and lesson reports intact. The delete itself is behind your admin password, so a shared browser or a misclick cannot take a learner off your roster.
Not today — there is no CSV or bulk import, and students are added one at a time. For an academy moving fifty learners across, that is an afternoon of typing, which is worth knowing before you plan the switch. The usual way round it is to move one class first, run it alongside whatever you use now, and add the rest as they renew.
No — provided an admin marks it excused, which is a deliberate edit to the attendance record rather than something an apology does on its own. An absence recorded as excused is left out of the denominator when that learner's rate is calculated, so a fortnight of flu does not turn a committed student into a statistic that looks like drifting. The absence itself stays visible on the record — it is excluded from the rate, not erased from the history.
The entry plan holds fifty students and ten teachers, and each tier above it raises those ceilings. Capacity is the only thing the tiers change: every plan includes the whole student CRM, so you are never paying for permission to use a feature, only for the size of your roster. The current figures for each tier are on the pricing page.
Yes, and it belongs to you. An academy admin can export the academy's records — students, teachers, lessons, attendance, enrolments and payment history — and the export is gated behind that admin's own password. Students do not have a self-service download of their own file today; the request goes through your admins, who hold the export.