What does the price of a learning-centre CRM depend on?

The price depends on the size of the centre — students and branches — and on the modules you need. Naming a figure before a plan is chosen would be misleading: the exact figure is agreed with the centre during the demo and setup. A useful rule: ask any vendor to put in writing what the price depends on.

Is a CRM worth it for a small centre with only two groups?

Use a simple test: if collecting attendance, payments and outstanding fees costs you several hours a month, a system pays for itself. Two groups can be run from a notebook. A common rule of thumb is that past a hundred students manual bookkeeping starts producing errors — check that against your own centre. So choose for the size you expect in a year, not the size you are today.

What happens to the data we keep in Excel today?

Moving it is a one-off job, but agree in advance who does it. Ask directly whether you enter the records or the vendor helps, and how long it will take. The easiest moment to move a database is the start of a new academic season, and keep the old file for at least another month.

What can AI actually do in a learning-centre CRM?

The useful part is prediction: from each student’s record it produces payment risk, a score forecast and recommendations. The analysis runs per student and for the whole centre. When choosing, ask two things — which decision the analysis makes easier, and whether student names are sent to an external service.

How to choose a CRM for your learning centre: a director’s checklist

Published 2026-07-266 min read

Most directors choose a CRM for a learning centre after a good presentation. The screens look tidy, the answers sound confident, the contract gets signed. A few months later attendance is back in a paper notebook and the debtor list is back in Excel.

The reason is always the same: the system was compared with a presentation rather than with the centre’s daily work. Here is the process that prevents it.

Describe your centre in numbers first

Before the first demo, write your own centre down on one sheet of paper. Twenty minutes of work makes every later conversation concrete.

Students today, and the number you expect in a year.
Groups, and how many lessons run in a day.
Branches now, and how likely a second one is.
Fee types in use: monthly, daily, discounted, refunded.
How teachers are paid — a percentage or a fixed rate.
Who logs in: director, administrators, teachers — how many people.
The three jobs that eat the most time today.

Start from the last line. If you retype the debtor list by hand every month, payments and outstanding fees are your first requirement — not a voice assistant and not a prettier chart.

Eight things to check in a CRM for a learning centre

Student profile

What appears on one student’s card? Group, attendance, payment history, exam scores and a parent contact belong on the same screen. If that takes three separate sections, your administrators will quietly stop using the system.

Attendance

Marking a register should take a minute, on one screen. The real question is who hears about it. When a parent hears about an absence during the lesson rather than in the evening, the arguments largely stop. An automatic Telegram message does that without anyone lifting a finger.

Payments and outstanding fees

Outstanding fees must never be worked out by hand. The system should handle monthly and daily fees, discounts and refunds itself, and print an official receipt in one click. During the demo, compare the cash-desk balance with the figure in the report — the two have to agree.

Groups and timetable

Does the timetable show a clash of time or teacher? How is the amount due recalculated when a student moves to another group? These are the two questions most often skipped.

Reports

You need no more than three reports: revenue and net profit, outstanding fees, attendance. They should open on one screen and show today. A report your accountant assembles once a month is not a decision-making tool.

Teacher and staff access

Every member of staff needs a role of their own. A teacher sees their groups and not the cash desk. An administrator takes payments and cannot change payroll. If everyone shares one login, that is not a system — it is a shared notebook.

Who owns the data

The most commonly forgotten question. Can you take your own database whenever you want? Does your data stay inside your own centre — can other centres see it? Do student names leave for an external service during AI analysis? The answers should be written down and unambiguous.

Language and the phone

The system should speak the language your administrators and teachers use every day. Then open it on a phone: a director spends much of the day away from the centre, and a report that cannot be read on a phone will not be read at all.

What you can safely ignore

Module counts. Thirty modules are not better than ten — only the ones you use matter.
Animation and colour. You stop noticing both soon enough.
Features that are not about you: a single-branch centre has no use for multi-branch management.
The word “AI” on its own. The question is not whether there is AI, but which of your decisions it makes easier.

That last one deserves a sentence more. In a learning centre, artificial intelligence earns its place in one job: telling you in advance who is likely to fall behind on fees and where a student’s scores are heading. If the analysis only returns general advice, it is a text generator.

Seven questions to ask a vendor

In what format, and how quickly, will you hand our data back to us?
What happens to the database if we stop after a year?
What does the price depend on — students, branches or modules?
How does the cost change when we open a second branch?
Who trains my staff, and for how long?
Where do we report a fault, and when do we get an answer?
Which three modules do centres my size use most?

Signs of a system you will outgrow

There is no export, or you are told “we do not do that”.
Every small change arrives with a separate invoice.
No roles — everyone sees everything.
Reports are only calculated at month end.
Questions about a second branch get vague answers.
The screens in the demo come from a slide deck, not the product.

The last sign matters most. Ask during the demo: “show us a new student being added on this screen, now”. In a working system that is a minute of work. In a mock-up, the subject changes.

How the demo should go

A demo is a test, not a show. Ask to see three real jobs from your own centre done in the system:

Adding a new student to a group and setting the monthly fee.
Marking attendance for today’s lesson — and the parent’s message going out.
Taking a payment, printing the receipt, then opening the list of outstanding fees.

Ten minutes for all three means the system works. Anything answered with “we will configure that later” is exactly where your daily pain will sit. And do not watch those three jobs alone — bring the administrator who would work in the system every day, because they will judge the handling faster than you will.

The decision

The final choice rests on two things: your three daily jobs get faster, and your data stays isolated to your own centre. Everything else is a detail you can negotiate.

Some items on this list are handled in MUDARRIS CRM like this: marking attendance sends the parent a Telegram message at that same moment, outstanding fees are calculated automatically, an official receipt prints in one click, every member of staff has a role of their own, and the Gemini-powered analysis shows payment risk and a score forecast. There are 16 modules, and every screen comes from the real product. Check the remaining items yourself, in any system — ours included.

If you have worked through this list against your own centre, the next step is simple — walk through a demo with your own centre’s numbers. Leave your name and phone number — we will call you within one working day. Or request a demo straight away on Telegram: @Oybek_Jalolov. Put your centre in order starting today.

Frequently asked questions

What does the price of a learning-centre CRM depend on?: The price depends on the size of the centre — students and branches — and on the modules you need. Naming a figure before a plan is chosen would be misleading: the exact figure is agreed with the centre during the demo and setup. A useful rule: ask any vendor to put in writing what the price depends on.
Is a CRM worth it for a small centre with only two groups?: Use a simple test: if collecting attendance, payments and outstanding fees costs you several hours a month, a system pays for itself. Two groups can be run from a notebook. A common rule of thumb is that past a hundred students manual bookkeeping starts producing errors — check that against your own centre. So choose for the size you expect in a year, not the size you are today.
What happens to the data we keep in Excel today?: Moving it is a one-off job, but agree in advance who does it. Ask directly whether you enter the records or the vendor helps, and how long it will take. The easiest moment to move a database is the start of a new academic season, and keep the old file for at least another month.
What can AI actually do in a learning-centre CRM?: The useful part is prediction: from each student’s record it produces payment risk, a score forecast and recommendations. The analysis runs per student and for the whole centre. When choosing, ask two things — which decision the analysis makes easier, and whether student names are sent to an external service.