How to Create a Service Catalog for Private Language Lessons

You probably offer more than one type of lesson. There's the free conversation class, the grammar-focused session, the exam prep package, and business English for professionals. Each one has a different price, a different length, and sometimes a completely different target audience.

The problem starts when you try to keep all of that organized. Without a formal service catalog, you rely on memory, scattered notes, or a spreadsheet that quickly falls out of date. And when it's time to charge, you waste time figuring out which lesson type that student had on which day.

Why clearly defined lesson types make a difference

When you define each lesson format as a separate service - with a name, a price, and a description - you stop improvising at billing time. You know exactly what each type of lesson is worth, and so does your student.

It also makes renewals easier. When a student understands they signed up for "advanced conversation, 50 minutes, fluency-focused," they know what to expect. Renewal becomes a clear conversation, not an informal negotiation every month.

There's another practical benefit: you can track which services generate the most revenue. If most students book conversation classes but very few book grammar-focused lessons, you have real data to adjust your offering.

How most teachers handle this today

The most common solution is a mental table, or at best a spreadsheet. "Conversation = $60, grammar = $50, business = $75." That works when you have two or three students. With ten or fifteen, inconsistencies start showing up: you charge different amounts for the same service, forget to update the price when you decide to change it, or write down the wrong lesson type.

WhatsApp ends up in the mix too. The teacher sends a message to the student confirming "it's the conversation class, right?" before registering the payment. It works, but it's an extra layer of friction that eats up time.

Some teachers use Google Sheets in a more structured way: one tab for the price list, another for scheduling, another for payments. But those three don't connect automatically. You still have to manually cross-reference what was scheduled, what was charged, and what was actually collected.

What's missing from that approach

The core problem is that the service catalog stays separate from scheduling and financial records. You end up with three systems that don't talk to each other: where you define prices, where you schedule lessons, and where you track what you've received.

A well-structured system connects all three. When you create a booking, you select the service being delivered. When the class happens and you record the payment, the system already knows which service it was, what the price is, and which student it belongs to. You don't have to fill that in two or three separate times.

Being able to organize services by category also helps. Conversation lessons go in one group, exam prep goes in another, corporate classes in another. When you're creating a booking, you browse the catalog instead of trying to remember the exact name you used months ago.

How this works in practice

Teachers who manage their service catalog well typically start with the most obvious distinction: lesson type and duration. A 30-minute class is one service, a 60-minute class is another. Conversation is one service, IELTS prep is another.

Then comes pricing. Each service has a fixed price. When you schedule a lesson, you select the service and the price is already filled in. No more "wait, how much did we agree on?"

Once the catalog is set up, you can link each scheduled lesson to a specific service. That creates a useful history: you can look at a student's record and see exactly which lesson types they've had, how often, and what each one cost.

For reporting, this structure is a big help. You can see which services generate the most revenue in a given month, which are most in demand, and which have the lowest renewal rate. That's information you simply can't pull from an informal spreadsheet.

How Noladi solves this

Noladi has a service catalog where you register each lesson type you offer, complete with name, price, description, and categories. When you create a booking, you select the service being delivered and it's automatically linked to that student's history.

When the lesson happens and you record the payment, the system generates the sales record automatically from the service linked to the booking. No need to enter the amount twice or cross-reference spreadsheets.

In the reports panel, you can see which services generate the most revenue and which are most in demand among your students - all based on the catalog you built.

If you'd like to see it in action, visit https://noladi.app/teacher.