In short
Software that keeps one record per student with their profile, sessions, university applications, documents, tasks and payments, so you can see any student's status and next action without searching email, spreadsheets and message threads.
The name comes from sales software, and that causes the confusion. A sales CRM is built around a deal that closes once. You manage a relationship running for months or years, throwing off dated obligations the whole time: a session next Tuesday, a transcript before submission, a deadline in January, an instalment in March.
What it stores
The test is whether one record answers every question you would otherwise have to piece together:
- Profile. Contact details, parent contacts, school, year group, subjects, direction, target countries and the goals agreed in the first meeting.
- Sessions. Every consultation with its date, duration, status and notes.
- Applications. Each university and course, with its own stage, deadline and paperwork.
- Documents. Transcripts, passports, references and personal statements, attached where they are needed.
- Money. What has been invoiced, paid and is outstanding.
- Next action. The nearest follow-up, task or deadline.
How it differs from a generic CRM
A generic CRM can be bent into this shape. The cost is a month building it and every month after maintaining it. Three mismatches come up repeatedly:
| Sales CRM assumes | An education consultancy needs |
|---|---|
| One deal per contact | One student with five to fifteen applications at once, each with its own stage and deadline |
| The contact is the buyer | The student is the subject, but a parent often pays and must be reachable |
| A pipeline that ends at 'closed won' | A relationship that runs on through offers, acceptance, deposits and enrolment |
| Revenue tracked as deal value | Instalments, part-payments and receipts, per student, over a year |
That does not make a generic CRM unusable. It makes it expensive in a currency easy to overlook: hours spent configuring custom objects, and nobody else understanding the result.
Do you need one yet?
In short
If you can hold every student's next action in your head, you do not need one yet. The moment you start writing yourself reminders about students, you are already building one, badly.
The threshold is somewhere between fifteen and thirty active students, and it moves with how many applications each makes. Longer comparison: CRM vs spreadsheets.
What to look at next
The CRM buyer's guide covers the features that matter, what to ask vendors, and a scoring checklist. Student management shows what a single record holds.
See a real student record
The EduCRM demo runs on the live software with sample data. No account, no card.
Keep reading
Frequently asked questions
Is a CRM for educational consultants the same as a student information system?
No. A student information system belongs to a school or university and records enrolled students' grades, attendance and transcripts. A consultancy CRM belongs to the adviser and records the advisory relationship: enquiries, sessions, applications to other institutions, and fees.
Can a small consultancy use one?
Yes. The work does not change with size: a solo consultant with twelve students has the same deadlines and paperwork as an agency, just fewer. EduCRM's free plan covers 10 students, so trying costs nothing.