Montessori schools · CRM
Keep every parent enquiry in one record, from first call to enrolment.
A CRM for a Montessori school is a single record of each enquiring family: the child's age, the programme asked about, the visit and what was promised. GullySales sets up a simple record and the stages around it, sized to your admissions team.
Scope, fee, reporting and term are agreed in writing after we have read your brief and spoken to you.

What CRM means
A CRM is the record where every enquiry, call and quote is kept against a customer, replacing separate notebooks, spreadsheets and memory. GullySales sets up or cleans an existing CRM and reports from it by enquiry outcome rather than by activity logged.
Last updated 14 Nov 2026.
For montessori schools
Where it usually goes wrong, and what we would do.
“Enquiries live in three phones and a diary”
The front desk notes one call in a diary, the principal receives a message on a personal phone, and the coordinator holds a list. When a parent calls back, nobody has the whole story. One shared record means any member of the team can pick up the conversation where it stopped.
“Seats depend on age and start date”
A school with fixed places for each age group needs to know which children reach the right age, and when. A record holding the child's birth month lets the coordinator plan the next intake. Without it, seats are offered by memory and a family is told the wrong thing.
“Child details need careful handling”
A record holding names, ages and family details holds private information about children. Who can see it and how long it is kept must be settled at the start and checked with an adviser. Collect only what the admissions team needs and delete what it does not.
“A tool bigger than the team goes unused”
A school with one coordinator does not need a system built for a large sales team. A short list of stages and a few required fields get filled in. Anything beyond that gets skipped. Fitting the record to the real team is what makes it a habit.
What we do
What we deliver for montessori schools.
The work available for this need. We agree the deliverables and responsibilities for your engagement in writing.
An enquiry record design
Fields for the parent, the child's age, the programme, the source and the questions asked.
Result: Every enquiry is entered the same way.
A stage list for admissions
Stages from enquired to visit requested, visited, form returned and enrolled, with a place for families waiting for an intake.
Result: The coordinator sees where each family stands.
Import of existing lists
Names from diaries and spreadsheets cleaned and moved into the new record.
Result: Past enquiries are not lost in the change.
An access and privacy note
A written rule on who may view and edit records, and how long they are kept.
Result: The school can show how family information is protected.
A walk-through for the team
A short session for everyone who will use the record.
Result: Staff know which details to record and at which point.
How the result is measured
- Enquiries logged in the CRM
- Data completeness
- Reports generated from CRM data
Recorded as a baseline before work starts, so every later report has an honest comparison.
Fields worth keeping
Keep these fields so no parent is lost between the first call and the first day.
Enquiries live in three phones and a diary. A short record, kept by one person, is enough for a school of this size.
- Child's age and the start date wanted
- Filled by whoever takes the call. It lets the guide see which age band has a place and who belongs on the waiting list.
- Observation visit date and who attended
- Filled by the guide. It shows whether the parent has seen the room, and who else came, such as a grandparent.
- What the parent asked on the visit
- Filled by the guide. It lets the follow-up answer the real question instead of repeating the school's prospectus.
- Waiting list position and age band
- Updated by the office. It lets you tell a parent honestly where they stand when a place opens.
- Admission status
- Updated by the office from enquiry to enrolled. It lets the principal see where parents stop, as a pattern across the year.
Who it is for
This is written for these montessori schools.
- Standalone Montessori houses for ages two and a half to six
- Montessori schools with a lower elementary programme
- Montessori sections inside a larger school
- Home-based Montessori set-ups run by a trained guide
- Montessori schools affiliated to a training body or association
- Montessori schools with a toddler community
- Montessori teacher training centres that also run a school
- Montessori schools run by a trust or a single founder
Before you decide
When this may not be the right fit.
- The office has one person who writes everything in a diary and will not use a tool, and a system would stay empty
- You have so few enquiries that a notebook shared between two people does the job
- You plan to hold notes on each child's learning in the sales record, which belongs in the school's own files
Before you decide
Agree the work. Know how to judge it.
CRM for Montessori schools: use these checks to prepare, choose the scope, and review what changes.
Bring the right evidence
List the records your team uses and show how an enquiry becomes an order today. Bring examples of duplicate entries, missing owners, and reports that require manual correction.
Make the scope clear
Agree the stages, required fields, access roles, and integrations before configuring the system. Separate software subscriptions from setup, data work, and training.
Check the work in use
Ask the people who will use the CRM to complete a real handover and find the next action without help. Check that the management report can be traced back to individual records.
Know when to change course
If the process is unclear, buying a more complex CRM adds more places for confusion. Start with the minimum fields and rules the team can use consistently.
These are discussion points, not a fixed package. GullySales confirms the deliverables, responsibilities, fee, and term in writing after reading your brief and speaking with you.
Before we start
What to have ready before the work starts.
The records, access and decisions this work needs from montessori schools. Anything missing is noted in the written scope, with who will supply it.
- Every list of enquiries, wherever kept
- Sheets, diaries and phone notes. We import them as they are. Anything left on a personal phone stays out of the record. Please include the forms parents filled in on paper, as they hold dates the phone notes miss.
- The seat plan by age group
- A table of how many places each group has and when they open. The record's stages depend on it. Without it, the waiting list cannot be run.
- A rule on who may read a family's record
- A decision by the principal on who sees what, and who edits. Without it, everyone sees everything, which is a risk for a school. Say also whether a teacher may see a family before enrolment, as that changes how the record is set up.
- A list of what is never recorded
- A note of what stays out, such as a child's health detail or learning notes. Without the list, the coordinator may enter what belongs elsewhere.
- A coordinator who tries it first
- The person who will use the record at the desk, and who says what is awkward. Without them, the principal judges a form the coordinator avoids.
How it works
How the CRM work runs
The work itself, in order. How an engagement starts, from your brief to a written scope, is set out on our method page.
- 1
Trace one family from enquiry to enrolment
We follow a recent family through the paper: the first call, the visit booked, the visit held, the forms sent, the seat offered. The coordinator tells us where each note lived, in a phone, a diary or a sheet. The trace shows which stages the record must cover. We also ask where a family's second enquiry was recorded, since that is where records split.
- 2
Gather the lists held in phones and diaries
The principal, the coordinator and any teacher who takes calls hand over their lists. We merge duplicates and mark families who enquired twice. You decide whose version stands when two differ. What results is a single list of live and past enquiries.
- 3
Design the fields around age and start date
A seat depends on the child's age and the date the child could start. We design fields for those, for the programme asked about, for the visit and for what was promised. The principal removes any field about the child's learning, which belongs in the school's own files.
- 4
Write the stages and the access rules
We write stages from enquiry to enrolment, and a waiting list stage. The principal decides who may see the record and who may edit it. A short privacy note states what is kept and why. Teachers see only their own group's families. We also write what happens to a record when a family withdraws, so closed enquiries are not left in the live list.
- 5
Load real records and watch the team use them
The coordinator enters live enquiries while we watch. Where they hesitate or write the same thing twice, we change the form. The record is accepted when the coordinator can open one family and know what to say.
- 6
Hand over ownership and read the record
The coordinator becomes the owner of the data, with a named backup. Afterwards we count enquiries with a recorded next step against the ones that had none at the start. You see whether any family still waits for a reply that nobody is tracking. A colleague is named to take over when the coordinator is away, and the handover is written on one page.
Where this fits
Three pieces of sales work, in this order.
This work sits inside sales management. A target, a review routine and someone who owns the number.
Step 1
Sales audit
Find where deals are being lost and what to fix first.
Start here if you cannot say where orders are lost.
Step 2
Sales process design
One written way to sell, from first enquiry to repeat order.
Start here if every salesperson sells differently.
Step 3 · you are here
Sales management
A target, a review routine and someone who owns the number.
Start here if the team has targets and no routine.
FAQ
Questions owners ask before they call.
Not here? More answers, or ask on WhatsApp.
Which tool should we use?
Should the record hold notes on a child's learning?
Who should see the record?
What if the person who kept the record leaves?
Can teachers add notes about a child to the enquiry record?
What happens to the record when a family withdraws?
How much does it cost?
How long is the contract?
How soon will we see results?
Who will actually do the work?
More for montessori schools
Related work to consider.
Closest to this: leads and follow-up
Also for montessori schools
Or start from the overview: sales and marketing for montessori schools.
Your next practical step
Tell us what you are trying to grow, and we will read it before we call.
Eight short steps, mostly taps. Skip anything you would rather answer on the call.