How I designed and built the core system for a growing music school: one data model, four role-based portals, and a single settings layer that cascades to every role.
The school had no booking or management tooling. Registrations, schedules, invoices, and attendance lived in separate places, and the business was heading toward multiple branches, so the system had to be branch-aware from the first migration rather than retrofitted later.
I led this build end to end for Allegra, delivered through Triglobs: requirements, system design, development, and handover. This page covers the engineering decisions; the client-facing summary lives on the Triglobs project page.
The system is one codebase with four role-based portals (parent/student, teacher, admin, super admin). The super-admin layer owns branches, per-grade session pricing, and teacher rates, and every change there propagates to the other three roles, which removed the usual "two screens, two truths" problem. Classes can be scheduled at a student's home or in a studio, with 45- or 60-minute sessions priced separately.