Skip to content
app.educrmapp.com/demo
🟢Live demo · resets every 24h
The requirement

What an institution needs a CRM to do

A different job from the one your student information system does.

In short

It manages the people who are not students yet: every enquiry, the family behind it, the conversations, the application and its documents, the deadlines and the fees.

Your student information system takes over the day someone enrols. It was never built to hold three hundred half-finished conversations about next September. That gap is where an intake leaks.

Who it fits

Institutions that recruit, not only enrol

Always the same shape: an intake with a deadline, a decision at the end, more enquiries than one person can hold.

01

Private and independent schools

Parent enquiries, open days, paperwork, an assessment date and a decision, every year against a fixed September.

02

Language schools

Short courses, rolling intakes, enquiries that convert or go cold inside a fortnight.

03

Colleges and training centres

Several programmes admitting at once from one enquiry pool, each with its own capacity and closing date.

04

Vocational and professional academies

Adult learners paying in instalments, where money is part of the admissions conversation.

05

University international offices

Applicants from abroad, with documents in the wrong format and a visa clock running.

06

Tutoring and exam-prep centres

A parent-facing pipeline where selling, scheduling and invoicing are one relationship.

Read more
The cycle

One admissions year, in one system

In the order it actually happens.

  1. 01

    Enquiries land in one place

    A website form, a phone call, a WhatsApp message, a name written at a fair. What you lose is the three days before someone decides whose it is. A registration form on your own subdomain puts it straight into the system.

  2. 02

    Open days and taster sessions

    Sign-ups come through the same form, attendance is logged as a session, and the follow-up is a dated task with one name.

  3. 03

    The family, not just the applicant

    For a school the decision-maker is a parent; for an adult programme, often an employer. Every conversation is logged with its date and what was agreed, so whoever answers the phone next has the thread.

  4. 04

    Applications, one per programme

    A family applying to two programmes is not one status. Each application is its own record with its stage, deadline, documents and owner.

  5. 05

    Documents that arrive in the wrong order

    School reports, references, ID, medical forms, proof of address. All upload under fixed categories, so nothing lives only in an archived email.

  6. 06

    Assessments, interviews and closing dates

    Entrance tests, interview slots, taster days and the registration deadline share one calendar with every follow-up, with reminders and two-way Google Calendar sync.

  7. 07

    Registration fees and deposits

    Invoiced, paid and outstanding, per family, with numbered invoices and receipts as PDFs.

  8. 08

    The decision, and the ones you turn down

    Offers, acceptances and rejections are stages, not deletions. An applicant who says no this year is a record you still hold next year.

The team

Who sees what

More people sit near the process than in a consultancy: a registrar, a receptionist, a head of admissions, a bursar. Roles let you share the register without sharing everything.

The four roles, read as an admissions office
RoleWho it usually isWhat they can do
OwnerPrincipal or directorEverything, including billing and settings.
AdminHead of admissions or registrarEvery applicant, every programme.
CounsellorAdmissions officer, programme leadTheir own applicants.
ViewerReceptionist, bursar, governorRead-only.
The four roles, read as an admissions office

Every applicant has one named owner. That is what decides whether follow-ups happen. See team roles and permissions and the security page.

Honest limits

What this is not

A page that claims everything is worth nothing when you are comparing.

Four things EduCRM does not do.

  1. 01

    Not a student information system

    No timetabling, gradebook, attendance register or report cards. Run it alongside the system holding your enrolled students, and hand over at enrolment.

  2. 02

    It does not take payments online

    Fees, invoices and receipts are tracked and generated here. The money still moves through your bank or payment provider.

  3. 03

    There is no family login

    Parents and applicants are contacted from the platform. There is no family portal.

  4. 04

    Not a reporting suite

    The dashboard answers the live questions, plus a revenue chart. Anything more is built outside, from the Premium data export.

Getting there

Starting mid-year, which is when everyone starts

  1. Step 01

    Bring in the list you have

    Upload the office enquiry spreadsheet. The column mapping is proposed for you and checked for duplicates before anything is written.

  2. Step 02

    Name your own stages

    Stages, pipeline, session types and payment methods are all settings. Use the words people already say in the office.

  3. Step 03

    Put the form on the website

    From that day every enquiry arrives typed, dated and owned.

  4. Step 04

    Run one intake before moving the rest

    One programme, or one year group, for a term. See the CRM implementation checklist.

Pricing

What it costs an institution

  • Free, up to 10 students. Enough to pilot one programme's intake. No card.
  • Premium, €49.99/month, up to 1499 students, plus registration forms, voice tasks, custom branding and data export. Extra staff accounts €49.99 each. 14-day trial.
  • Business, €1,500 setup plus Premium. Done for you: custom website, lead capture form and professional email.

Data sits in Google Cloud's europe-west1 region. Sub-processors and retention are on the security page.

Frequently asked questions

What is a CRM for educational institutions?

Software that manages everyone you are talking to before they enrol: enquiries, open-day sign-ups, the family behind each applicant, applications with their own stages and deadlines, documents, fees and follow-ups. A student information system is not built for that.

Is EduCRM a student information system or a school management system?

No. No timetabling, gradebook, attendance register or learning management. It covers admissions, and runs alongside the system holding your enrolled students.

Can different programmes or year groups be admitted separately?

Yes. Each application is its own record with its programme, stage, deadline, documents and owner, so several intakes run at once from one enquiry pool.

Can parents or applicants log in to check their status?

No. There is no family portal. Applicants and parents are contacted by email from the platform, and what was said stays on their file.

How many staff can use it?

€49.99 each on Premium, with owner, admin, counsellor and viewer roles. The plan covers up to 1499 students, with no fixed cap on staff.

Where is applicant data stored?

In Google Cloud's europe-west1 region, with TLS 1.2 or higher in transit and each workspace isolated. Full detail on the security page.