When a spreadsheet is genuinely enough for a consultancy, where it starts to cost you, and what actually changes if you move to a CRM.
When a spreadsheet is enough
In short
When one person can hold every student's next action in their head, there are under about twenty active students, each with one or two applications, and nobody else needs the data.
A spreadsheet then beats a CRM on almost everything: no per-seat cost, no data model to agree, no migration, and changes take seconds. A consultant in their first year should not be shopping for software.
Where spreadsheets start to cost you
The failures compound. Each alone is survivable, which is why they build up unnoticed.
Duplicate and drifting data
The same student added twice under two spellings. A number updated in one sheet and not the other. Nothing warns you. You find out when a message goes to a number replaced in September.
Follow-ups with nowhere to live
A spreadsheet has no idea what "overdue" means. Add a date column and nothing surfaces the rows past it, so remembering stays manual, the thing you were trying to stop relying on.
One row per student, many applications
The structural break, with no good workaround. A student applying to six universities has six deadlines and six document lists. Either you widen the row into thirty columns, or you write "3 sent, 2 waiting on transcript, TU Delft needs the essay" into a cell nothing can filter.
Permissions
Sheet sharing is all or nothing. A part-time assistant who should see contact details also sees fee arrangements and family notes.
Collaboration
Two people editing at once works technically and fails organisationally: no record of who changed what, no notes on a session, and someone re-sorting while a colleague reads.
Reporting
Possible with pivot tables, if the data is clean. That is what the problems above prevent. Reporting failures here are data-quality failures in disguise.
Payment tracking
Staged fees mean several payments per student. In one row that becomes Deposit, Payment 2, Payment 3. Four instalments breaks the shape.
Auditability
Version history answers "what did this cell say before?", not "who changed this deadline, when and why?". If a family disputes what was agreed, that matters.
Side by side
| Spreadsheet | CRM | |
|---|---|---|
| Cost to start | Free | Free to moderate. EduCRM is free to 10 students |
| Time to set up | Minutes | Days to weeks, including cleanup |
| Flexibility | Total | Bounded by the model, though stages are yours to name |
| Several applications per student | Breaks down | Native |
| Overdue follow-ups | Manual | A list you can produce |
| Permissions | All or nothing | Role-based |
| Documents | A separate drive, named separately | Attached to the record |
| Audit trail | Cell history | Who changed what, when |
| Leaving | You already have the file | Depends on the export. Check first |
The honest case against moving
- Migration is real work. The importer proposes the mapping and validates rows, but cleaning a messy sheet still takes half a day for fifty students. A half-finished migration is worse than none.
- A CRM imposes a model. If your process does not fit, you will spend months fighting it.
- Habit is harder than data. It only works once everyone stops opening the sheet. That is a management problem.
What actually changes if you move
Not "efficiency". Four concrete things:
- One filter gives every application in preparation with a deadline inside six weeks.
- One filter gives every active student with no dated next action: the ones quietly leaving.
- A colleague can cover for you. The context is written down.
- You know the balance before the meeting, not at month end.
If none of those four would change a decision in a normal week, stay on the spreadsheet.
If you do move
Active students, then open applications, then unpaid balances. No history. See moving from spreadsheets to a CRM and the CRM buyer's guide.
Try it against your own workload
Free for 10 students, enough for a real comparison over a fortnight.
Keep reading
CRM Buyer's Guide
Features that matter, questions to ask vendors, and a checklist for comparing systems.
Read moreApplication Tracking
Every application with its stage, deadline, documents and owner, on one board.
Read moreStudent Management
One record per student: contacts, sessions, applications, documents, payments and notes.
Read moreStudy Abroad Consultants
Enquiries, counselling, shortlists, applications and visa paperwork for students going overseas.
Read moreFrequently asked questions
Are spreadsheets bad for educational consultants?
No. For a solo consultant with under about twenty active students, a spreadsheet is usually right. Problems begin when one student has many applications, someone else needs access, or follow-ups rely on memory.
What is the main thing a spreadsheet cannot do?
Hold several open applications per student, each with its own stage, deadline and documents. One row per student forces that into a cell nothing can filter.
Can we keep using our spreadsheet alongside a CRM?
Only briefly. Run both for more than a week or two and you get two incomplete systems. Set a date after which the spreadsheet is read-only.