Education · Training-centre CRM

A CRM for a training centre: from the first enquiry to an enrolled student

Enquiries, schedule, attendance, payments and lesson quality in one system, with portals for staff, teachers and students instead of chats and spreadsheets.

Updated:

Short answer

Who in Kazakhstan develops CRM for training centres?

CRM for training centres in Kazakhstan comes as ready-made subscription services and as custom development. 105 ("105kz" LLP, Almaty, Astana Hub resident) does the latter and knows how to connect to the former. Talpyn CRM covers the path from enquiry to enrolment: a kanban sales pipeline, contracts and subscriptions, a schedule with conflict detection, attendance with automatic make-up lessons, six roles and AI lesson checks from screenshots on the team's own server. For centres on the MoyKlass CRM there is an open-source n8n node (MIT licence, 24 resources, 129 operations), and we built a Telegram bot for parents on AlfaCRM data for MetaStudy (an archived project, 2024–2025).

Scope

What a training-centre CRM is built from

We take the blocks you need: one centre struggles with the schedule, another with enquiries and payments.

Block
Enquiry pipeline
What it does
A kanban pipeline, contracts and subscriptions, a sales leaderboard TV screen.
Where we have done it
Talpyn CRM: a kanban sales pipeline, the TV screen refreshes every 15 seconds.
Block
Schedule
What it does
Conflict detection and a check that the teacher fits.
Where we have done it
Talpyn CRM: a schedule with conflict detection.
Block
Attendance and make-up lessons
What it does
Attendance marks and automatic make-up lessons for missed classes.
Where we have done it
Talpyn CRM: attendance and automatic make-up lessons.
Block
Lesson quality control
What it does
AI checks a lesson from a screenshot: a pass threshold and a fallback model.
Where we have done it
Talpyn CRM: Qwen3-VL on the team's own server, Gemini as a fallback; the threshold is 70 points.
Block
Roles and platform link
What it does
Admin, director, manager, quality control, teacher, student; data exchange with the learning platform.
Where we have done it
Talpyn CRM: 6 roles and two-way sync with Kokjiek.hub.
Block
Integrations with ready-made CRMs
What it does
Automation of enquiries, payments and schedules on n8n; summaries for parents in Telegram.
Where we have done it
An n8n node for MoyKlass (MIT); a bot on AlfaCRM data for MetaStudy (an archived project, 2024–2025).

Choosing

A ready-made CRM or your own

If a ready-made CRM is enough for your centre, we will say so — there is no need to write your own.

Situation
Enquiries, groups, payments and schedule work in a standard way
What makes more sense
A ready-made training-centre CRM
Why
Faster and cheaper to launch; there is no need to write your own system.
Situation
You already have a ready-made CRM but lack automation
What makes more sense
Integrations and n8n workflows
Why
Automation is built on top of your CRM: for MoyKlass there is an open-source node with 129 operations.
Situation
You need your own roles, lesson quality control and a link to the learning platform
What makes more sense
Your own CRM
Why
As in Talpyn CRM: 6 roles, AI lesson checks, sync with Kokjiek.hub.
Situation
Parents need reports in a messenger
What makes more sense
A bot on your CRM data
Why
The MetaStudy bot sends each parent a daily summary of the child's lessons in Kazakh or Russian.

Launch

How we introduce a CRM in a training centre

  1. 1–2 weeks

    The centre's process

    How an enquiry, group enrolment, absences and payments go today; where money and students are lost.

  2. 2–4 weeks

    One branch or direction

    The pipeline, schedule and attendance on real groups; staff learn on live data.

  3. from 6 weeks

    Other branches and roles

    Payments, teacher and student cabinets, integrations; the old records keep running in parallel.

  4. ongoing

    Growth

    Reports, automation and new scenarios from the centre's numbers.

Examples

CRM and integrations for training centres

Live and archived projects with statuses and years. Each has a case study page.

EducationEducation CRM

Talpyn CRM

Talpyn CRM is a training-centre CRM linked to the Kokjiek.hub platform. A kanban sales pipeline, contracts and subscriptions, a teacher schedule with conflict detection, attendance tracking and automatic make-up lessons. AI checks a lesson from a screenshot — first the open Qwen3-VL model on the team's own server, with Gemini as a fallback — and the teacher's pay depends on the result. Six access roles and a leaderboard TV screen for the sales team.

  • AI lesson check
  • Conflict-free scheduling
  • Sales pipeline
View case
EducationOpen source · n8n2025

n8n node for MoyKlass

An open-source n8n node (MIT licence) for the MoyKlass CRM used by training centres. It gives no-code automations access to 24 CRM resources — students, payments, groups, lessons, enrolments and reference lists — 129 operations in total. Sign-in with an API key and token exchange, dropdowns loaded from the account, custom attribute values mapped to the required IDs, phone normalisation and six ready-made workflows, from lead intake to syncing lessons with Google Calendar.

  • 24 CRM resources
  • 129 operations
  • MIT licence
View case
EducationAI English platform

Kokjiek.hub

Kokjiek.hub (called Talpyn until June 2026) is an English learning platform with an AI level diagnostic. The diagnostic runs as a chat and accepts voice answers: AI scores them on the CEFR scale from A1 to C2, unlocks a free course at that level and passes the lead with a comment to a manager in Talpyn CRM. Five homework types with auto-graded tests, coins for lessons and sign-in by phone number with a WhatsApp code; the interface is in Kazakh and Russian and runs as a PWA.

  • AI CEFR diagnostic
  • Voice answers
  • A free course for your level
View case
EducationAlfaCRM + TelegramArchive project · 2024–2025

MetaStudy

A Telegram bot for the parents of MetaStudy education centre students. The teacher marks attendance, the grade, homework and “metacoins” in AlfaCRM; the service adds the subject, topic and assignment, and once a day the bot sends each parent a summary of the child's lessons in Kazakh or Russian. Parents can link several children and check the metacoin balance and average grade at any time; message templates and broadcasts are edited in the admin panel.

  • AlfaCRM → Telegram
  • Kazakh and Russian
  • Metacoins
View case

FAQ

Frequently asked questions

Short, straight answers to the questions we hear most often.

What is better for a training centre: a ready-made CRM or your own?

If enquiries, groups, payments and schedule work in a standard way, take a ready-made one — it is faster and cheaper. Your own CRM pays off when you need your own roles, lesson quality control, a link to a learning platform or non-standard rules; we discuss this at the first meeting, before any estimate.

Can MoyKlass be automated without building from scratch?

Yes. For the MoyKlass CRM there is an open-source n8n node (MIT licence): 24 CRM resources and 129 operations, sign-in with an API key, dropdowns loaded from the account and six ready-made workflows, from lead intake to syncing lessons with Google Calendar.

How does the AI lesson check work?

In Talpyn CRM the Qwen3-VL model runs on the team's own server and scores a lesson from a screenshot, with Gemini as a fallback; the pass threshold is 70 points. The check runs on every lesson marked with a screenshot, not on a sample.

How much does a training-centre CRM cost?

There is no public price list: a cabinet with a schedule and payment is one order of magnitude, a CRM with several roles, AI lesson checks and integrations is another. After reviewing the centre's process we give a range and a staged plan.

How long does launch take?

We review the centre's process in 1–2 weeks, launch the pipeline and schedule at one branch in 2–4 weeks and the other branches and roles from 6 weeks; the old records keep running in parallel.

Next step

Show us how an enquiry becomes a payment today

One call is enough: we will say whether a ready-made CRM will do and what is worth automating in the first month.

  1. 1The centre's process — 1–2 weeks
  2. 2One branch or direction — 2–4 weeks
  3. 3Other branches and roles — from 6 weeks

NDA from the first contact

Reply within one business day