Management system for online language schools

Most small online language schools don't run inside a system. They run inside a spreadsheet. Around that spreadsheet there's a Notion, a Google Meet, a Drive full of folders named after students, one WhatsApp group per class, and a separate Excel file for each teacher to log their hours at the end of the month. Each of those pieces solves part of the problem, and together they charge a high price in time, rework, and lost information.

This article is about what changes when that whole operation fits into a single system.

The typical setup of a small online school

A school with three to ten teachers and a few dozen online students usually works something like this. The coordinator manages the schedule in a master spreadsheet. Each teacher keeps their own, with time slots, confirmed students, absences, and notes. Classes happen on Google Meet or Zoom, using links each teacher generates alone. Materials end up in a Drive folder, usually with no naming convention shared across teachers. Finances live in yet another spreadsheet, tracking who paid, who owes, and how many classes each student still has left.

Each of these pieces works in isolation. The problem is that none of them talk to each other. When a student cancels, the coordinator updates the spreadsheet, but the teacher only finds out when they walk into an empty room. When a class buys a new package, finance has to manually tell whoever is supposed to unlock the next sessions. When a teacher leaves, the school partially loses access to that student's history, because some of the material lived in the teacher's personal account.

What a single system solves

A management system built for an online language school consolidates these pieces into a single database, branded as the school's own, with roles and permissions so each person sees only what they need.

In Noladi, that design starts from a few clear decisions:

• Team and permissions. The school registers each teacher as a member with their own access. The coordinator sees everything. Each teacher sees only the students and classes under their responsibility.
• Centralized students and classes. Each student has a single record at the school, with class history, purchased packages, and financial status. No matter how many teachers have worked with them.
• Shared schedule. The coordinator sees the school's full schedule. Each teacher sees their own. The student sees only the time slots available for their booking.
• Live classroom branded as the school. Classes happen inside the system itself, at an address like yourschool.noladi.app, with the school's logo and name visible on every screen. No install, no third-party link, no confusion about who is delivering the class.
• Centralized receivables. The school sees in one place who has an active plan, who has an outstanding balance, and how many classes are left in each package. Noladi controls this flow (it doesn't charge the student's card), and the coordinator records what was received.
• Packages and plans with credit control. Each plan defines how many classes a student is entitled to per month. The credit is deducted automatically when a class happens, with no one having to open a spreadsheet to update the count.

Why this matters as the school grows

A school with three teachers and thirty students gets by fine with Notion and WhatsApp. A school with seven teachers and a hundred and twenty students does not. What was inconvenient at a small scale becomes an operational error at a larger one: a student charged twice, a class booked into an occupied slot, a teacher complaining that the student's package had run out and no one said a word.

A single system reduces that friction in three ways. First, information has one home, so there's no diverging version between coordination, teacher, and finance. Second, repetitive processes like unlocking a class, deducting a credit, and generating an attendance list leave the team's hands and become standard system behavior. Third, the school's brand stays visible in every interaction with the student, instead of diluted across Google, Zoom, and each teacher's personal WhatsApp.

How Noladi positions itself for schools

Noladi delivers this package with small online schools specifically in mind: schools that want to move past the patchwork of standalone tools without migrating to a giant traditional-school system full of modules that make no sense for a 100% online operation.

The school gets its own address, its visual identity applied to the student panel and the live classroom, and a single place to coordinate scheduling, teachers, students, packages, and finances. The post-class layer powered by artificial intelligence delivers a lesson review, transcription, and stats for every session, which helps the coordinator track student progress without relying solely on the teacher's account of it.

The plan for schools starts at R$ 499 per month, with class hours shared across all the teachers in the operation. There's no charge per registered teacher or per registered student.

If you coordinate an online school and you're realizing the spreadsheet has become the school's system, it's worth seeing how Noladi organizes that operation in one place.