Ask a director how enrolment enquiries are managed and the honest answer is usually a tour of good intentions: the shared inbox, a spreadsheet someone started in 2023, sticky notes on the office monitor, and the director's own memory, which is excellent until the week it isn't. Every centre has lost a family this way. Almost none knows how many.
A CRM (customer relationship management system, though nobody needs the long form) exists to make that loss impossible. This guide explains what one actually does in a childcare context, without the software-industry fog.
The job, in plain terms
A CRM does four things for a centre. It captures every enquiry from every channel, the website form, the phone call, the walk-in, the Facebook message, into one list, so nothing lives only in someone's head. It remembers the whole story per family: first contact, what was said, tour date, hesitations, siblings, preferred start month. It prompts the next action: who needs a call today, which tour needs confirming, which family went quiet after a visit. And it shows the pattern: how many enquiries became tours, how many tours became enrolments, and where families fall out.
That's the whole mystery. Everything else is packaging.
What it is not
A CRM is not your childcare management platform. The systems that run your rosters, attendance, billing and subsidy claims are built for families already enrolled; most have thin or no tools for the courting stage before that. The distinction matters enough that we've written a separate guide to it.
It's also not a marketing strategy. A CRM is a container and a prompt. If nothing worth saying goes into your follow-ups, the system just delivers emptiness more reliably. And it's not a robot receptionist; the point of automating the clerical layer is to give humans back the time for the conversations that decide enrolments.
The signs you've outgrown the inbox
Some centres genuinely run fine on a tidy inbox and one meticulous person. The tells that you've passed that point: you can't say how many open enquiries you have right now without an archaeology session. Follow-up depends on who happens to remember. A staff absence stalls enquiries for days. Families occasionally say "I never heard back" and you can't tell whether that's true. Or you're spending on marketing to generate enquiries that then leak out of an unmanaged funnel, which is buying water for a cracked bucket.
Two or more of those and the question isn't whether a system would help; it's which one and who sets it up.
The graveyard problem
The uncomfortable statistic in small-business software is how many CRMs are paid for and abandoned. The pattern is always the same: a generic tool arrives empty, someone spends a weekend half-configuring it, the pipeline stages don't match how enrolment actually works, and by week six everyone is back in the inbox. The failure isn't the software; it's that a childcare enrolment funnel has a specific shape, enquiry, tour booked, tour completed, offered, enrolled, waitlisted, and generic tools don't know it.
So the buying question isn't "which CRM has the most features". It's "who will make this fit the way a centre actually enrols families, and keep it fitted". That can be a capable person in-house with genuine time budgeted, or it can be bought as a done-for-you system. What it can't be is nobody.
Where we stand, declared plainly
EEVA runs a done-for-you version of exactly this: the Enrolment Content Engine, an enrolment CRM configured for early education, with the pipeline, follow-up sequences, tour booking and review workflows already built, at $490 per month plus GST, or as part of the complete Story and Engine partnership at $590 per week plus GST. We think a specialist system beats a general one for centres, and we're obviously not neutral about it. The free Enrolment Story Audit is the neutral-ish first step: it looks at how enquiries flow through your current setup and shows you where families are leaking, whatever system you end up choosing.
