Software for language schools

Most small online language schools are not running on software. They are running on a patchwork. There is a spreadsheet to track enrollment, Google Calendar for each teacher's schedule, Zoom for the classroom, WhatsApp to notify students about everything, a standalone tool to charge tuition, and one more financial spreadsheet at the end of the month to reconcile it all. It works until it stops working.

This article is about what separates real software for a language school, designed for this specific way of operating, from a patch stitched together out of six tools nobody chose on purpose.

Why a language school does not fit into generic software

There is plenty of school management software on the market, and almost none of it was designed for an online language school. Most of it is built for a physical school, with report cards, printed enrollment forms, a physical room per class, attendance logs. All of that is deadweight for a school that operates entirely over the internet, with one-on-one lessons or small groups, and whose classroom is a browser tab, not a room full of chairs.

At the other end of the market there is generic scheduling software, like Calendly, and generic video conferencing, like Google Meet and Zoom. Each one solves a well defined slice, and none of them understands what running an entire language school actually looks like. Calendly books a time slot, but it has no idea that the student bought a package and has lesson credits to consume. A video call opens a room, but it does not know the room needs to carry the school's brand, not the platform's, and that the lesson should turn into material the student can review afterward.

In between those two extremes sits a real operation that no one serves well, and that is exactly where most small schools live.

The typical setup of a small online school

Picture a school with five teachers and eighty online students. The operation probably runs like this. The coordinator keeps a master spreadsheet with every student, which teacher each one has, which package they bought, when it expires. Each teacher keeps their own calendar, usually in Google Calendar, with time slots and video links they generated themselves. Tuition is charged through a standalone tool, like a payment intermediary or a bank slip link, and when the student pays someone has to remember to mark it as paid in the spreadsheet. Each lesson's material ends up in a Drive folder, usually in the teacher's personal account. The WhatsApp group announces everything, and six months later nobody can find the message that mattered.

Each of these pieces works on its own. The problem is that none of them talk to each other. When a student cancels a lesson, the spreadsheet does not know, the teacher finds out by walking into an empty room, and finance keeps deducting a credit that was never used. When a new student joins, someone has to open five tabs to register the same person in five places. When a teacher leaves the school, the school loses partial access to the student's history, because part of the material lived in that teacher's personal account.

The hidden cost of the six-tool stack

This arrangement carries three costs that nobody adds up when they start using it, and that only show up on the bill at the end of the quarter.

The first is coordination time. A good chunk of the coordinator's hours are not spent teaching or bringing in new students. They are spent reconciling the spreadsheet against finance, checking teachers' calendars, updating package status, answering a student asking how many lessons they have left. That is work that exists only because the system does not.

The second is operational error. A student charged twice because nobody saw they had cancelled. A lesson booked in a slot that was already taken, because the spreadsheet was out of date. A package that expired without anyone noticing, with the student walking into a lesson assuming they were still entitled to it. Each of these errors costs money in refunds, friction with the student, or a student who quietly walks away.

The third is how the student perceives the school. A student pays tuition she considers expensive, only to enter a generic video room with someone else's logo in the corner and her name spelled wrong because the teacher typed it on the spot. The lesson material arrives over WhatsApp two days later, with no defined format. The invoice comes from a company name she does not recognize. In everything she sees of the school, the school's brand shows up less than the brands of the standalone tools the school uses.

What software for a language school needs to cover

Software designed specifically for an online language school needs to cover five integrated fronts, all in one place, on the same database.

The first is centralized student and class records. Each student has a single profile at the school, with lesson history, the package they bought, the teacher in charge, and payment status. It does not matter how many teachers have come and gone. The information does not live duplicated in everyone's spreadsheet.

The second is a multi-teacher schedule. The coordinator sees the school's entire calendar in one place. Each teacher sees only their own. The student sees only the slots opened up for them to book. When the student books, the lesson lands on the teacher's calendar automatically, and the credit on their package is deducted in the same move.

The third is an online classroom carrying the school's brand. The lesson happens inside the browser, at an address like yourschool.noladi.app, with the school's logo and name visible on every screen. Student and teacher join without installing anything. There is no generic video link, no third party showing up in the experience.

The fourth is plan and package control. Each plan defines how many lessons the student is entitled to per month. The credit is deducted automatically when the lesson happens, with nobody having to open a spreadsheet to update the count. The coordinator sees in real time who still has credit, whose plan is expiring, who needs to renew.

The fifth is consolidated receivables. Who has an active plan, who has an open balance, how much the school is due to receive this month. The school records what was received (the software manages this flow, without processing the charge on the student's card itself) and gets financial visibility in a single dashboard.

And, ideally, a sixth front that changes the retention game. Post-class review, with the lesson recorded automatically, transcribed speaker by speaker, and organized for the student to work through during the week. It is what lets the student see progress, and it is what makes renewal happen without the coordinator having to push for it.

Why this becomes inevitable as the school grows

A school with two teachers and twenty students gets by fine on Notion and a video tool. A school with seven teachers and one hundred and fifty students does not. What was an inconvenience at small scale turns into a recurring error at mid scale.

The coordinator starts becoming a hostage to the operation. The time of the person who should be bringing in new students is spent reconciling a spreadsheet. Each teacher operates in a slightly different way, and the sum reads as inconsistency in the student's eyes. The school's brand disappears among the brands of the tools the school uses. And at a certain point it becomes clear the school does not have a system. It has a spreadsheet that became the school's system, with everything else patched around it.

That is the point where integrated software stops being a convenience and becomes a prerequisite.

Meet Noladi

Noladi is software built specifically for a small language school operating online. In one place, it brings together student records, a multi-teacher schedule, a live classroom with a collaborative whiteboard and the school's own brand, plan and credit control, receivables, and post-class review with automatic transcription and artificial intelligence.

The school has its own address (yourschool.noladi.app), its own visual identity in the student dashboard and in the live class, and roles and permissions so each teacher sees only the students under their responsibility, while the coordinator sees everything. The school plan starts at R$499 per month, with live class hours shared across every teacher in the operation. There is no charge per registered teacher, and no charge per registered student.

If your school is at that point where the spreadsheet became the system and the coordinator became a spreadsheet, it is worth getting to know Noladi at your own pace and seeing how the whole operation fits into one piece of software.