industries · education & edtech
education software
students do not abandon by week 3.
we ship lms, school management, and edtech products in mena. our ams platform as a base, custom builds for ambitious institutions. designed for the student, the teacher, and the parent.
three things this industry actually needs from a software partner. nobody else says them out loud.
01
three users, one product.
education software has students, teachers, and parents. they want different things from the same product. the systems that win are the ones that design three coherent surfaces, not one screen with three tabs.
02
engagement is not the metric. progress is.
edtech that optimizes for time-on-app produces gamification fatigue. edtech that optimizes for measurable progress produces students who finish the course. we design for the second.
03
arabic + english, plus a hijri academic calendar.
mena schools and universities run bilingual schedules with hijri-aware terms. shipping that correctly means designing the calendar surface and the data model around it from day one.
what we ship for education teams, ranked by what most engagements actually need.
+50% retention
edtech that survives week 3 is the edtech that respects the student's time.
student week-3 retention uplift seen on platforms that design for progress, not for engagement metrics.
lms + course delivery
video, quizzes, assignments, gradebook. arabic + english, hijri + gregorian calendar.
school management
enrollment, attendance, grading, parent portal, fee collection. multi-school multi-tenant.
student + parent app
sso + identity
arabic + english + hijri calendar
every screen, every notification, every certificate. bilingual and dual-calendar from the data model up.
four stages. fixed deliverables at each. no scope-creep invoices.
week 1 — discover
discover
we map student, teacher, and parent journeys, plus the institutional workflow behind them.
week 2 — design
design
three coherent surfaces (student / teacher / parent), each designed for the right job.
week 3 — build
build
production-grade engineering with multi-tenant institutional support, sso, and parent communications.
week 4 — operate
operate
launch, monitor student progress and abandonment, iterate weekly with the academic team.
every agency lists what they do. here is what we explicitly won't do for education teams.
we will not gamify learning into addiction
streaks, badges, and notifications can be designed for healthy engagement or for compulsion. we choose the first. parents notice the difference.
we will not ship one screen for three users
students, teachers, and parents have different jobs. shipping one screen with three role-toggles is a sign the product was scoped, not designed.
we will not skip the parent surface
in mena, parent buy-in determines whether a school adopts software at scale. the parent app is not a nice-to-have; it is the procurement decision.
pick the path that matches where you are.
how a education build at maxiphy actually runs.