Skip to content

Running a school

CRM for a language school: what student records really have to do

Most software sold to schools as a CRM is a sales funnel with a timetable bolted on. A school earns and loses its money after the sale, in the register, the schedule and the books, and that is what its records have to cover.

A CRM for a language school has to keep what happens after a student signs up: who came to which lesson, what was covered, what the month charged and what was paid. When all of that sits in one record, the numbers agree without anyone reconciling spreadsheets at the end of the month. A list of leads matters too, but it is the smallest part.

Why the search results are full of sales software

Search for a CRM for a language school and most of what comes up was built for selling: leads, pipeline stages, call-back reminders, conversion rates. A school that pays for ads does need some of that. But a person is a lead for a week or two and a student for a year or longer, and a funnel has nothing to say about that year.

What a school has to keep track of

Ask anyone who runs a language school and you hear the same list:

When the register is also the bill

Four subscriptions cost less than keeping four tools in agreement with each other. If attendance sits in a spreadsheet and invoices in another service, somebody copies one into the other every month, and every copy is a chance to miss a lesson or bill a student twice.

If the charge comes from the register, marking who came already takes care of the bookkeeping. Each student is on a plan, per lesson, a package or a monthly fee, and the plan is counted against the attendance the teacher recorded.

Where the sales funnel fits

If a school needs a funnel, it should have one, and a small school can start with a plain list. A lead nobody called back costs one sale. A register that disagrees with the invoices costs money every month, on students the school already has. That is why the second part matters more.

Questions to ask before moving your school to any system

How this works in EdTechCore

EdTechCore keeps the register, the schedule, every student's account and double-entry books in one system, next to the lessons themselves. Attendance is marked in the same schedule the lesson opens from, and each student's plan is counted against it. Courses belong to the school, not to whoever typed them up. The page for schools shows how it fits together.

Request a demo