One system, from the first enrolment to the final exam.
Schools rarely lack software. They have a spreadsheet for fees, a group chat for staff, a video tool for online classes, a folder of PDFs for content and a notebook for everything else. The cost is not the licences — it is that none of them know about each other, so a human has to be the integration.
Five tools, and you are the glue
Every disconnected tool adds a translation step performed by a person. That person is usually your best assistant, and the translation is usually done twice.
- A student enrolled in one system, invoiced in another, and taught in a third.
- A cancelled session that has to be remembered in the calendar, the payroll and the parent's message.
- Reports that are only as current as the last time somebody exported something.
- Nobody can trace a number back to the action that produced it.
The six parts, and why they belong together
Each one is useful alone. The reason to have them in one place is that the joins are where the work actually disappears.
School, branches and identity
Your own subdomain or custom domain, your logo and signature on printed documents, and a branch structure the rest of the system respects everywhere.
People and roles
Principals, assistants, teachers and students, with named access keys per area. Promotion, blocking and branch moves are one action, not a support ticket.
Classes and timetable
In-class and online groups, teacher availability, a shared calendar and attendance — feeding straight into both payroll and student progress.
Curriculum and practice
Subjects, units, rich lessons, exercises with structured retakes and level tests. Built once, owned by the school, improved every term.
Live and AI
Browser-based live classrooms with recording, AI lesson drafting, and voice and chat tutors bounded to the lesson a student is on.
Money and insight
Fees, overdue, receipts, teacher payroll and camps — with results, attendance and capacity in the same reports so a number always has a cause.
Systems touched to complete one task
The saving is not a faster tool. It is the second and third tool disappearing, and with them the re-typing between them.
- Separate tools
- With Mujtahid
Illustrative figures — the shape of the report, not anyone's real numbers.
How the pieces connect in practice
One student's journey, and how many times anybody has to type their name.
- 1
Enrolled once
The assistant registers the student, places them in a class and opens the payment folder in one flow.
- 2
Taught and measured
The teacher's lesson and exercises reach that student automatically, and their attempts roll up to the class view.
- 3
Billed and receipted
The payment lands against the same folder, prints a receipt, and updates the branch's collected figure instantly.
- 4
Reported without a report
The principal's view is those same records, grouped. Nothing is exported, re-keyed or reconciled.
The joins are the product
Any of these modules can be bought separately and most schools already have some of them. What cannot be bought separately is the fact that they agree with each other.
One record, many views
A payment, a session and an attempt are stored once and read by whoever needs them. There is no export step, so there is no version that has gone stale.
Tenancy runs all the way down
Branch scoping is not a filter on a screen — it is enforced on every read and every write, so combining modules never accidentally combines schools.
Every action is attributable
The activity log ties a change to the person and branch that made it, which is what makes a shared system safe to give to twelve people.
Adding a module does not add an integration
Turning on live classes or AI tutoring does not start a project. They already share the same students, classes and lessons.
Questions about the whole system
- Do we have to use all of it?
- No. Most schools start with people, classes and fees, then add curriculum, then live and AI. Each part works alone; they just work better together.
- Does it work for a single-branch school?
- Yes. Multi-branch is the model, but one branch is simply the smallest case — nothing extra to configure.
- What about in-class teaching, not online?
- Offline classes are first-class: attendance, payments and payroll are built for a physical branch. Online and live are additions, not the assumption.
- Can we bring our own domain and branding?
- Yes — your domain, your logo, your director's word and signature on printed documents, and a public catalogue page for parents.
Keep reading
The parts of the platform this page touches.
See the whole system on your own school
Create an account and we will open your school space with you.