About MySchoola
We build software for the people who run education, not just for those who teach it
MySchoola exists because course-based education centers were left with two bad options: a generic school ERP built for academic years, or a pile of spreadsheets. We are building the third one.
Our mission
Make excellent administration accessible to independent education centers
A language school or training center is a real business with rooms, contracts, cash flow and reputation. Yet the software market treats it as a smaller version of a high school, with rigid academic years, term-based grade books and pricing designed for institutions with a full IT department.
We started MySchoola from the opposite end: the session. A session has a time, a room, a teacher, a group of learners and a cost. Everything an education center needs — enrolment, attendance, billing, payroll, reporting — can be built cleanly on top of that reality.
Our first market is Morocco, where thousands of language centers, training centers and academies run on spreadsheets. The product is built to work anywhere the same model applies, which is why Arabic, French and English are first-class from day one.
Course-first, not year-first
Programmes, levels, groups and sessions are the core of the data model, so rolling intakes and packages are normal cases.
Arabic as a primary language
A fully mirrored right-to-left interface, designed alongside the French and English versions rather than retrofitted.
Built for small teams
No IT department required. If the front desk cannot learn it in a day, we consider it a design problem.
How we work
Product decisions made next to the front desk
We design with the people who will use MySchoola every day: administrators, coordinators, teachers and owners.
We start with your workflow
Before writing a feature we map how a center enrols, schedules and invoices today, including the parts that happen on paper.
We optimise the repeated tasks
The screens used fifty times a day get the most attention. Saving ten seconds there matters more than any dashboard.
We design in three languages at once
Every screen is reviewed in Arabic, French and English, so no language ends up as a second-class experience.
We treat your data as yours
Clear permissions, exportable records and no hidden lock-in. Trust is a product feature, not a policy page.
What we believe
Principles we do not trade away
These are the rules we apply when a shortcut would be faster but worse for the centers using MySchoola.
- Clarity over feature count
- A shorter menu that people understand beats a long one that needs training. We remove as often as we add.
- Honest communication
- We describe what the product does today, not what a roadmap might deliver. No inflated numbers, no invented references.
- Respect for local reality
- Cash payments, instalments, evening classes and mixed teaching contracts are normal. The software should not fight them.
- Long-term partnership
- Centers keep their software for years. We optimise for the fifth year of use, not for the first demo.
Where we are heading
Growing with the centers that adopt us
Our priorities are set by the operational problems our early centers bring us, in this order.
- 01
Core operations, done properly
Enrolments, courses, timetables, attendance and billing that hold up under a full peak season without workarounds.
- 02
Deeper insight for owners
Better analytics on occupancy, retention and profitability per course, so decisions stop relying on intuition.
- 03
International readiness
Additional languages, currencies and local payment habits, so a center anywhere can run MySchoola in its own context.
Let us look at your center together
The best conversations we have start with a real operational problem. Bring yours to a demo and we will be straight with you about whether MySchoola solves it.