The product had to scale administration without making classroom execution harder.
The client’s business model required centralized control, but learning quality depended on local teacher execution.
The platform had to manage many roles and permissions while keeping daily workflows clear.
Schools, users, licenses, learning materials, reports, and support needed one operating layer.
Teachers and admins needed usable workflows for timetables, activities, materials, and assessments.
Classroom workflows needed to continue offline when networks were weak.
Super admins, school owners, school admins, assessors, collaborators, and teachers required different privileges.
A SaaS operating layer for early learning delivery.
School setup, roles, licenses, sessions, batches, learning materials, reports, attendance, and support workflows.
Daily timetables, activities, assessments, offline materials, repositories, calendars, and progress reports.
Role-based access, license management, reporting, dynamic forms, ticketing, help modules, and assessment trackers.
Learning materials and selected classroom workflows remained available despite weak connectivity.
The solution separated administrative depth into the web app and classroom execution into the mobile app.
From central setup to daily classroom delivery.
- 01Configure
Admins create schools, users, roles, licenses, sessions, and batches.
- 02Assign
Learning plans and materials are assigned to schools and teachers.
- 03Deliver
Teachers use mobile workflows for classroom activities online or offline.
- 04Assess
Individual and group assessments are captured in structured flows.
- 05Report
Progress, support, and quality signals move back to central teams.
The platform had to reflect the business architecture, not just the feature list.
What changed when the workflow became connected.
Distributed preschools were governed through disconnected administration.
Schools, users, licenses, learning materials, and reports moved into a central SaaS platform.
Teacher workflows depended on manual tracking and local materials.
Teachers gained a mobile app for classroom activity, materials, assessments, and reports.
Connectivity issues could interrupt classroom activity.
Offline functionality supported continuity in weak connectivity contexts.
Role and license management were operationally complex.
Dynamic role-based access matched the operating hierarchy.
The hard part was translating a distributed preschool operating model into permissioned software.
Each role needed enough control to do the job without overwhelming the interface.
Teacher workflows needed speed, offline support, and simple daily access.
Licenses, roles, reports, schools, sessions, and support required structured governance.
Child progress and classroom activity needed repeatable capture and reporting.
Mantra can build SaaS platforms around the way distributed operations actually work.
The platform matched permissions and workflows to operating hierarchy.
Classroom execution remained viable under connectivity constraints.
Reports, assessments, tickets, and licenses moved into structured paths.
The build supported both central governance and frontline teaching.
The capabilities behind the build.
Web and mobile product layers supported school administration and classroom work.
Reusable SaaS foundations handled roles, licenses, reports, tickets, and forms.
Teacher-facing workflows were simplified around daily classroom use.
Shared workflow records, operating logic, and integration patterns connected the freight marketplace.