How to choose a CRM for an educational consultancy: the features that matter, the questions to ask vendors, and a checklist for comparing systems.
What is an educational consultancy CRM?
In short
Software that keeps one record per student (profile, sessions, applications, documents, tasks and fees) so you see any student's status and next action without rebuilding it from email and spreadsheets.
One requirement separates it from every other CRM: one student, many applications at once, each with its own stage, deadline and paperwork.
Generic CRM or education-specific?
Both work. They fail in different ways.
| Generic CRM | Education-specific CRM | |
|---|---|---|
| Setup | Weeks. Custom objects, fields and pipelines. | Days. The concepts already exist. |
| Fit | Whatever you build, and whatever you forgot to build. | Opinionated. Good if the opinions match your work. |
| Ecosystem | Large. Integrations, consultants, documentation. | Smaller. Fewer integrations, more direct support. |
| Ongoing cost | Someone must maintain it, and becomes a dependency. | The vendor maintains it. |
| Risk | The person who configured it leaves. | The vendor is smaller. Check the export path. |
If someone internal enjoys configuring software and will still be there in two years, a generic CRM works. If not, the debt lands on the founder, in November.
The features that matter
Student data
Parent contacts as real fields, not a notes box. A unique ID per student. Notes attached to dated sessions, not one growing text field. See student management.
Application management
The non-negotiable: several open applications per student, each with its own stage, deadline, documents and owner. Ask to see one student with six applications at different stages. If they show a status field, the answer is no. See application tracking.
Follow-ups
You need two lists: everything overdue, and every active student with no dated next action. Most systems cannot produce the second: the one that finds students going quiet.
Payments and invoicing
Fees are staged and often paid by a parent. At minimum: what is invoiced, paid and outstanding, plus invoice and receipt generation. Accounting integration can wait.
Team collaboration
Roles that really restrict access, one named owner per student, and enough shared visibility to cover an absence. See education agency CRM.
Enquiry capture
Anything needing manual re-typing eventually stops happening. A hosted form that writes straight into the system removes the step.
Reporting
Be honest about what you will act on. Most consultancies need two numbers (enquiry-to-qualified conversion, and days from enquiry to first application) plus a live view of students, sessions, follow-ups, deadlines and payments. Anything more is bought and never opened. What matters is whether you can export.
Data protection and security
You hold minors' data, passports and financial information. Be strict here.
Ask every vendor
- Which region is the data stored in?
- Is data encrypted in transit and at rest, and with what?
- Who are the sub-processors, and is that list published?
- Is a Data Processing Agreement available?
- Is there an audit log of access and changes?
- If you leave, what happens to your data, in what format, how quickly?
- Is access role-based, and can a viewer be genuinely read-only?
EduCRM's answers are on the security page: europe-west1, TLS 1.2+, workspace isolation, role-based permissions, an audit log, a published sub-processor list and a DPA on request.
Implementation
Budget four weeks even if the software is ready in an hour. The work is your stage model, your data and where enquiries arrive.
- Week 1. Agree your stages, and what counts as an active student.
- Week 2. Clean the spreadsheet, then migrate active students, open applications and unpaid balances.
- Week 3. Repoint enquiry channels, add the team, book the weekly review.
- Week 4. One week in parallel, then make the old system read-only.
Detail in the CRM implementation checklist.
Migrating from spreadsheets
Active students, then open applications, then unpaid balances. Do not migrate history. Cleanup is where the time goes, and it is far easier before the import. See moving from spreadsheets to a CRM.
Questions to ask vendors
Take this list to the demo
- Show me one student with six applications at different stages.
- Show me every application in preparation with a deadline inside six weeks, across all counsellors.
- Show me every active student with no dated next action.
- How do parent contacts work, and can I invoice a parent for a student?
- What happens when two people edit the same record?
- What is in the price, and what costs extra per user?
- How do I get my data out, and how long does it take?
- What is your support response time, and who answers?
- What has shipped in the last six months?
The three "show me" questions do more than the rest combined. Ask them live.
Evaluation checklist
Score each candidate
- Several applications per student, staged separately. Pass or fail.
- Deadlines and sessions on one calendar.
- Parent and guardian contacts as real fields.
- Documents attached where they are used.
- Enquiry capture with no re-typing.
- Payments and invoices against the student.
- Role-based team access.
- Data export you have seen demonstrated.
- Published security posture and sub-processors.
- A price you can afford at three times your student count.
- Someone on your team willing to own the rollout.
Common mistakes
| Mistake | What it costs |
|---|---|
| Choosing on feature count | You pay for what you never switch on. |
| Skipping the data cleanup | A migration abandoned three weeks in, leaving two half-systems. |
| Twelve pipeline stages | A board nobody updates, which is worse than no board. |
| Not repointing enquiry forms | New data keeps arriving in the old system. Neither is complete. |
| Not checking export before signing | A vendor you cannot leave. |
Test EduCRM against this guide
The live software. Free for 10 students, no card.
Keep reading
CRM vs Spreadsheets
When a spreadsheet is enough, where it starts to cost you, and what changes if you move.
Read moreApplication Tracking
Every application with its stage, deadline, documents and owner, on one board.
Read moreEducation Agencies
One shared student database, a caseload per counsellor, and the whole agency's pipeline in one view.
Read moreStudent Management
One record per student: contacts, sessions, applications, documents, payments and notes.
Read moreFrequently asked questions
What should an educational consultancy CRM include?
One record per student with parent contacts. Several separately staged applications each. Deadlines and sessions on one calendar. Documents where they are used. Follow-ups with dates and owners. Payment and invoice tracking. Role-based access. An export you have seen work.
How much should a CRM for an education consultancy cost?
Between nothing and a few hundred euros a month, depending on team size. EduCRM is free to 10 students and €49.99 a month to 1499, with extra members at €49.99. Judge it at three times your current size.
Can educational consultants use a generic CRM like HubSpot or Salesforce?
Yes, with configuration. Generic CRMs model one deal per contact, so applications become custom objects and parent contacts custom relationships. That works if someone owns it long term. The risk is they leave.
How long does implementation take?
Plan four weeks. The software is usable in an hour. The time goes on your stage model, your data and where enquiries arrive.
What is the single most important requirement?
Several open applications per student, each with its own stage, deadline and documents. One status field per student will be wrong within two weeks.