Home About Case Studies Hire Me Contact
Currently available for select engagements

Hire CRM Expert for Schools
Senior, direct, no layers

CRMs that keep every enquiry, application, and conversation in one place, with follow-up that does not depend on memory.

15+
Years Experience
100+
Projects Delivered
6
Countries Served
$25M+
Revenue Enabled
Schools — CRM Expert

A senior crm expert for schools

For a schools business, the customer record is the memory of the business. It should hold child age group, preferred entry year, application stage, tour date, offer status and sibling links, for customers such as parents and guardians enquiring about admissions, plus alumni, donors and partner organisations. When that memory is split across application spreadsheets, tour bookings and offer letters held separately, follow-up depends on whoever happens to remember.

The engagement starts from how schools customers actually arrive and return, through website enquiries, open days, referrals from current parents and partner organisations. A family that tours and is never followed up before the application deadline. That is why the record, the follow-up routine and the person responsible for each step are agreed before any software is chosen.

It fits a school where enquiries, tours, applications and offers live in different files. It does not fit a tiny school with a handful of applicants and a full roll. Book a free discovery call to check which side of that line the business sits on, before scoping anything.

What you get

What this engagement covers for schools

  • Pipeline stages — Stages follow the real schools sale or service path: enquiry, open day or tour, application submitted, assessment or interview, offer made, offer accepted, enrolment, induction. Each stage has a named next step, so nothing sits in a stage with nobody responsible for moving it.
  • System choice — The system is an admissions record that ties enquiries, tours, applications, offers and enrolment together, chosen against the real customer journey for schools, not from a feature list. A tool the team opens daily beats a powerful one nobody opens.
  • Follow-up routines — Follow-up is built in, not left to memory: a tour reminder, an application-stage update, and an offer follow-up before the acceptance deadline. Reminders and tasks are tied to the record, so an enquiry or a repeat customer never waits on someone remembering.
  • Clean migration — Existing records from application spreadsheets, tour bookings and offer letters held separately are cleaned, deduplicated and imported with their history, so the new system starts complete rather than empty and distrusted. Duplicates are flagged for the business to confirm, not silently deleted.
  • Training that sticks — Training is by role: admissions staff own applications and offers, school offices own tours and induction. Each role gets a short guide for its own job in the system, so recording a customer becomes part of the working day rather than extra work at the end of it.
  • Useful segments — Customers are grouped as families by entry year, by application stage, by sibling status and by offer status, so messages and reminders go to people they are relevant to, instead of the whole list getting the same message.
Systems you already run

Built around the tools schools actually use

Tool choice follows the schools workflow, not the other way round: an admissions record that ties enquiries, tours, applications, offers and enrolment together. The connected routes are the ones customers already use, website enquiries, open days, referrals from current parents and partner organisations, so enquiries land on the customer record at the moment they arrive.

The switch is staged, because a pilot on one entry year, then the remaining years. The pilot runs on live customers, rough edges are fixed while only part of the team is on the system, and full rollout happens once the record matches real work. A family that tours and is never followed up before the application deadline.

How it works

From kickoff to delivery for schools

  1. Map the journey

    The team walks through how schools customers actually arrive, through website enquiries, open days, referrals from current parents and partner organisations, and where follow-up currently breaks. Pipeline stages are agreed as enquiry, open day or tour, application submitted, assessment or interview, offer made, offer accepted, enrolment, induction.

  2. Configure the system

    Configuration follows that map: a record holding child age group, preferred entry year, application stage, tour date, offer status and sibling links, stages matching the real path, and reminders built around a tour reminder, an application-stage update, and an offer follow-up before the acceptance deadline.

  3. Migrate and pilot

    Migration cleans and imports the old records, and a pilot group works live customers in the new system before everyone switches. A pilot on one entry year, then the remaining years.

  4. Train and hand over

    Role-based training (admissions staff own applications and offers, school offices own tours and induction) and a short written guide close the engagement, with the account and the data belonging to the business.

Realistic outcomes

What to expect, honestly

The realistic outcome is calmer operations for the schools business: enquiries from website enquiries, open days, referrals from current parents and partner organisations land on a record, follow-up (a tour reminder, an application-stage update, and an offer follow-up before the acceptance deadline) happens on schedule, and nobody has to reconstruct a customer history from messages. The record holds child age group, preferred entry year, application stage, tour date, offer status and sibling links, so a different team member can pick up where the last one left off.

That outcome is not guaranteed by software alone. It depends on the routine fitting the working day, which is why a pilot on one entry year, then the remaining years. And it does not promise more customers on its own: it makes sure the customers already enquiring or returning are not lost in the gaps.

Why Omer

Why hire Omer

  • Shaped to this business: The pipeline (enquiry, open day or tour, application submitted, assessment or interview, offer made, offer accepted, enrolment, induction) and the record fields (child age group, preferred entry year, application stage, tour date, offer status and sibling links) are set from how schools customers actually behave.
  • Migration checked twice: Old records from application spreadsheets, tour bookings and offer letters held separately are deduplicated and confirmed with the business before import, not bulk-loaded blind.
  • Roles, not generic training: Training follows the job: admissions staff own applications and offers, school offices own tours and induction.
  • Ownership from day one: Account, data and subscription sit with the business, never held hostage by the engagement.
  • Habits after handover: Reminders and segments (families by entry year, by application stage, by sibling status and by offer status) keep working after the project ends, because they match the working day.
FAQ

Questions, answered

For schools, which CRM is the right fit?
Start from the journey, not the vendor list. For schools, the deciding factors are the pipeline (enquiry, open day or tour, application submitted, assessment or interview, offer made, offer accepted, enrolment, induction), the team size and what the team will open daily. The likely shape is an admissions record that ties enquiries, tours, applications, offers and enrolment together. A simpler system that gets used beats a fuller one that gets avoided.
For schools, what happens to existing customer lists?
Old lists are treated as the business memory: application spreadsheets, tour bookings and offer letters held separately are cleaned, matched against each other and imported with history intact. Anything ambiguous is flagged for the business, never deleted quietly.
For schools, will the team actually use the system?
Only if the routine fits the day. Training is by role (admissions staff own applications and offers, school offices own tours and induction), the pilot runs on live customers, and a pilot on one entry year, then the remaining years. A system that adds end-of-day admin will be abandoned, so the routine is redesigned until it is not extra work.
For schools, does a CRM replace personal relationships?
It should do the opposite. The system remembers promises, dates and preferences (child age group, preferred entry year, application stage, tour date, offer status and sibling links), so the conversation with parents and guardians enquiring about admissions, plus alumni, donors and partner organisations can focus on the person rather than on reconstructing what happened last time.
For schools, can current tools stay connected?
Where they are genuinely used, yes. The connected routes are website enquiries, open days, referrals from current parents and partner organisations. Anything that merely duplicates the CRM is a candidate for retirement, but only with the business's agreement.
Currently available for select engagements

Ready to get started?

The best way to explore working together is a quick conversation. Reach out through your preferred channel and let us discuss your project.