We build for the school you actually run — not the one the software assumes.
Every school platform encodes a set of assumptions about what a school is. Most of them assume one campus, card payments, a laptop per student and a syllabus in one language. Get those wrong and every screen is slightly hostile. We started from the other end.
Where imported software breaks
The failure is rarely a missing feature. It is an assumption buried so deep in the product that no configuration screen can undo it, and the school ends up maintaining a workaround forever.
- Multi-branch added as a report filter rather than a boundary, so a mistake leaks data.
- Cash payments treated as an exception, so the fast path is the one nobody uses.
- Interfaces that assume a laptop, when the student's only device is a phone.
- Pricing tiers that charge more exactly when a school grows, punishing the outcome you wanted.
What we decided, and why
These are not features. They are the choices everything else was built on top of, and the reason the product feels different to use.
Multi-branch is the model
Not a filter. A principal's action covers the school, an assistant's covers their branch, and that distinction is enforced on every read and write — including the mobile API.
The UI is never the gate
Every mutation re-checks the caller's role and that the record belongs to their school. Hiding a button is a convenience, not a control, and we treat it that way.
Offline money is first-class
Cash and transfer are the fast path. Quotes freeze at submission so a hand-reviewed payment never costs a school days it spent in a queue.
One plan, no tiers
There is a subscription or there is not. Nothing is locked behind a bigger package, so we never have to make the product worse to sell an upgrade.
Capacity is a tank you own
Minutes, credits and storage accumulate and never expire. If a subscription lapses the balance is frozen, not zeroed — you lose access, never your property.
Bounded spending, on purpose
Every path that costs money on a third party is capped and rate-limited before the call. Predictability matters more to a school than an unbounded feature.
Where the month's admin hours go
The claim is not that the work is exciting. It is that most of it is transcription between systems, and transcription is the part software should absorb.
- Before
- With Mujtahid
Illustrative figures — the shape of the report, not anyone's real numbers.
How we work with a school
The product is half of it. The other half is not leaving you to configure it alone.
- 1
We learn your structure first
Branches, subjects, levels, how you price, how you pay teachers. The setup follows your school rather than a template.
- 2
We open the space with you
Domain, logo, branches and staff. You end the session with a school that already looks like yours.
- 3
We start with one thing that hurts
Usually fees or enrolment. One visible win before anyone is asked to change how they teach.
- 4
We stay through the first month
The first enrolment run and the first month close are where a rollout succeeds or quietly dies. We are there for both.
The part nobody else does
Plenty of products can list the same modules. The difference is in decisions that only matter once you have run a school for a year, and that are expensive to retrofit.
We refuse to sell you a tier
Feature-gating by package forces a vendor to keep useful things out of reach. One plan means our incentive is to make the single product better, not to design an upgrade path.
We will not burn what you paid for
Quota is frozen on lapse, never subtracted. It is the clearest possible statement of who the purchased capacity belongs to.
The AI is deliberately restrained
It drafts for teachers and explains to students, and it will not hand over an answer. A tutor that finishes the homework destroys the exact signal a teacher needs.
We build for the phone in the student's pocket
Lessons ship drawings as images, pages stay light, and there is a real mobile app. The device a student actually owns is the device that has to work.
Fair questions
- Are you not just another LMS?
- An LMS handles content. Most of a school's day is enrolment, fees, timetables, payroll and branches. We do both, and the value is that they agree with each other.
- What if we only want one part?
- Start with one. Most schools begin with people, classes and fees. Nothing forces you to adopt content or AI before you want them.
- Why should we trust a smaller platform?
- Because it is built for a school like yours rather than adapted from one that is not — and because you can reach the people who build it.
- What happens to our data if we leave?
- It is your school's data. Nothing is deleted because a subscription lapsed, and purchased capacity is frozen rather than burned.
Keep reading
The parts of the platform this page touches.
Judge it against your own school
Create an account and put your real structure into it with us.