Choosing management software for a language center: 10 criteria

10 criteria for choosing language center management software (English, Japanese centers...)

Every language center — whether it teaches English, Japanese, Korean, or several languages — goes through the same journey: someone leaves their contact details, gets consulted, gets placed in a class, studies, pays tuition, and then decides whether to continue. Good management software for an English center needs to cover this whole journey, not just admissions or just attendance. Before sitting through a demo, list out these 10 groups of features and mark which ones your center needs on day one:

• Lead and admissions pipeline: track contacts from the website, Facebook, and Zalo OA through stages — new, contacted, consultation booked, enrolled — so no lead waiting for a callback slips through.
• Consultation and placement testing: log consultation history, placement test results, and staff notes so whoever picks up the case next doesn't have to ask from scratch.
• Class placement and scheduling: assign students to classes by level, room, and teacher while avoiding room or teacher double-booking.
• Attendance: teachers or assistants mark attendance per session, and the system flags students who miss classes in a row so the center can follow up early.
• Tuition and outstanding balances: track sessions paid for, sessions attended, and the amount still owed per student, instead of relying on a cashier's memory.
• Tuition and schedule reminders over Zalo: automatically send tuition due dates, class reminders, and exam reminders over Zalo instead of calling or messaging each person by hand.
• Reporting: see leads by source, close rate, tuition revenue, and re-enrollment rate by course or by staff member without manually adding up spreadsheets.
• Multi-branch permissions: each branch sees only its own data, while regional managers see figures across the whole system, without exposing tuition numbers between branches.
• Website, Zalo OA, and Facebook integration: leads from a website form or Page message flow into the system automatically instead of a staff member copying them by hand every morning.
• Data ownership and export: the ability to export all student and tuition data to Excel or CSV at any time, including after you stop using the software.

SaaS or custom-built software: which one to choose

There are two main paths on the market. Packaged SaaS software is a shared system used by many centers at once — you sign up and start using it right away, paying a monthly subscription based on time or number of users. Custom-built software is built around a center's exact admissions and class-placement process, and it usually takes a discovery phase before it can go live.

Neither option is right for every center — it depends on size, number of branches, and how different a center's process already is from what off-the-shelf software offers. The table below compares both by specific criteria:

Questions to ask in a software demo

A demo is usually led by a salesperson following a rehearsed script, which can gloss over exactly the parts a center needs to check closely. Ask the following questions directly instead of judging the software by how polished the interface looks:

• Can student and parent data be exported to Excel or CSV — the full dataset, or only part of it?
• If we stop using the software, how long do we have to download all our data, and is there a fee?
• Who can see tuition information versus who can only see the schedule — can permissions be configured by role?
• Does each plan limit the number of branches, students, or staff who can use it at once?
• What type of message is used for tuition and schedule reminders on Zalo, whose Zalo OA account sends them, and is there a separate messaging fee?
• Do leads from the website or Facebook flow into the system automatically, or does staff still enter them by hand every day?
• Does the system log who changed tuition data and when, so we can investigate if a dispute comes up?
• How is the added cost calculated later on if we add a branch, a user, or a feature?

Migrating student data from Excel to new software

Most centers manage students across several separate spreadsheets — one for leads, one for attendance, one for tuition — built up over time by different people. Before importing into new software, merge these files and agree on one shared column structure: student name, phone number, course, start date, sessions paid for.

The next step is cleaning the data: remove duplicate records created when the same student was entered twice under different phone numbers, standardize date and amount formats, and flag students who have already left so they aren't counted in active outstanding balances.

Try importing one class or one small branch first, and check that sessions attended and amounts paid match the old records before importing everything. In the first 2–4 weeks, many centers run the old and new systems side by side to cross-check before retiring the spreadsheets entirely, so a flaw in the new software doesn't cause data loss.

How language center management software is priced

Packaged SaaS software is usually priced as a monthly subscription based on number of users or number of active students — cost rises as the center grows. Custom-built software is priced by the scope agreed during discovery: number of screens, number of branches, the level of integration with a website or Zalo OA, and the volume of data to migrate from Excel.

Because scope differs from one center to the next, there is no single price that applies everywhere — the actual cost is only confirmed after reviewing the specific process. AdSys builds custom CRMs for language centers and quotes after reviewing the admissions process, student care needs, and number of branches to manage.

Study abroad consultancies need similar software

A study abroad consultancy follows a journey close to a language center's: a contact leaves their details, gets consulted on their needs, and then goes through case processing instead of class placement. Instead of schedules and attendance, software for a study abroad consultancy needs document checklists, submission deadlines, and progress tracking per applicant.

The criteria above about data ownership, multi-branch permissions, Zalo OA integration, and reminders apply the same way to a study abroad consultancy. AdSys also builds custom CRMs for study abroad consultancies around each organization's own case-handling process.

Checklist before signing a software contract

Before signing, go through the following items to avoid unexpected costs or being locked out of your own data:

• You've listed the 10 criteria above and marked which ones you need right away.
• You've asked exactly how data export works and what rights you have to your data if the contract ends.
• You've reviewed detailed pricing by number of branches, users, and students — not just the lowest advertised plan.
• You've tried importing real sample data from your own spreadsheets, not just looked at the vendor's demo data.
• You've confirmed support hours and channels for when the system breaks during peak admissions hours.
• You've agreed in writing on the scope of work, delivery timeline, and any added costs.