Project · Education · SaaS
CursFlow
A web and mobile application for music schools. Schedules, students, teachers, payments, contracts and communication — one product, many schools, each with its own branding and separate data.
Context
Music and training schools still run the day on calendars, spreadsheets and separate tools for billing and contracts. The work is operational: rooms, recurring lessons, attendance, invoices, GDPR. It has to hold for one school — and for many schools on the same platform.
What we built
A multi-tenant system with five roles, a scheduler at the centre, CRM and leads, subscriptions and invoicing, online contracts, and messaging. Each school keeps its own theme, settings and data.
Outcome
Daily school operations sit in one environment: from first lead to signed contract, scheduled lesson and paid invoice. New schools can sign up, brand the product, and start teaching without a custom build.
Who uses it
Five roles, five menus. The owner has full control. Managers run the day — schedule, students, rooms, finance, leads — without school-wide settings. Professors see their own calendar, attendance, materials and income. Students see lessons, pay invoices, sign contracts and read materials. A platform operator can administer many schools without being a user of any one of them.
The scheduler
The weekly calendar is where rooms, teachers and students meet. Recurring lessons, trial sessions, studio time without a teacher, cancellations on a single date, attendance against a package balance, and recovery lessons when someone was absent. Double-booking a room is blocked. Schedules export to Excel.
Operations around the calendar
Students live in a CRM-style dossier: profile, schedule, subscriptions, invoices, notes. Leads come in through a public form with GDPR consent, then convert to a student account and an initial lesson. Billing connects to invoicing providers; pending payment can block new lessons. Contracts — GDPR, enrolment, cession — are generated from templates and signed in the product.