WHO WE BUILD FOR / SCHOOLS & PRESCHOOLS

Websites and automation for schools and preschools

Admission season floods the office, and the rest of the year is circulars, fees, and calls. We build the site parents trust — and the workflows that answer, remind, and reach every parent without the notice-in-the-bag lottery.

WEBSITE ONLY · AUTOMATION ONLY · OR JOINED — EVERY SPEC SOLD SEPARATELY

What's still done by hand

Every one of these is a workflow waiting to exist. None of them needs new software your team has to learn.

THE REAL COST

Admission season is a queue of identical questions arriving faster than the office can answer them — while the follow-up that converts a tour into an admission never happens. The rest of the year, the circular-in-the-schoolbag system loses exactly the notices that matter.

  • Admission enquiries pile up during the exact weeks the office is busiest
  • Campus tours are scheduled over phone rounds
  • Circulars travel in school bags and half the parents never see them
  • Fee reminders are printed slips and awkward front-office conversations

Two pieces — take one, or join them

Each side is a separate engagement with its own scope and price. Plenty of clients start with one and add the other only when it earns its place.

PIECE A — THE WEBSITE

  • A school site that answers what parents check: curriculum, fees range, safety, faculty
  • Admission enquiry forms by grade, with documents listed up front
  • News and circular sections the office publishes in minutes
  • Virtual tour and facility pages that work on a parent's phone
WEBSITE SPECS →

PIECE B — THE OPERATIONS

  • Admission replies with the right grade's process and a tour slot
  • Tour scheduling with confirmations and day-before reminders
  • Circulars delivered to exactly the affected classes, delivery tracked
  • Fee reminders on schedule with receipts on payment
AUTOMATION SPECS →

Three we'd start with

Written the way we'd actually spec them — trigger, steps, outcome. Yours would be drafted from your operation, on the call.

WORKFLOW 01

The admission season absorber

TRIGGER: ENQUIRY FOR ANY GRADE

  1. 01Parent gets the grade's process, documents, and a tour slot link
  2. 02The enquiry is logged by grade and intake year
  3. 03Tours booked → reminders; no tour in a week → one follow-up

Season enquiries get same-minute answers while the office breathes.

WORKFLOW 02

The circular that arrives

TRIGGER: CIRCULAR PUBLISHED FOR SELECTED CLASSES

  1. 01Parents of exactly those classes get it on their phones
  2. 02Delivery and reads are tracked per class
  3. 03Unreached parents surface as a short list for the class teacher

No more "we never got the notice" at the front desk.

WORKFLOW 03

The fee cycle

TRIGGER: TERM FEE DUE IN 7 DAYS

  1. 01A reminder with the amount, due date, and payment link goes out
  2. 02Payment lands → receipt sent, records updated
  3. 03Overdue cases surface as a list — with history — for the office

Fee collection runs on schedule without a single printed slip.

The questions your customers repeat

A chatbot grounded in your own pages answers these in seconds, cites the source, and hands anything unusual to your team.

  • What's the fee structure for nursery / class 5?
  • When do admissions open? What documents are needed?
  • What's the student-teacher ratio? Which board?
  • Is transport available on my route?
  • What are the school timings and holiday list?
HOW THE CHATBOT SPEC WORKS →

What stays human

Automation earns its keep on the repetitive work. These lines don't move — they're where your judgment and your relationships live.

01

Teaching and pastoral care — nothing here goes near the classroom

02

Admission decisions — the workflow schedules tours; the school chooses students

03

Sensitive conversations — fees hardship and student issues get a person, privately

Asked by schools & preschools

Parent phone numbers change constantly. How does delivery stay accurate?

Bounced messages surface immediately, so numbers get corrected the week they break — not discovered at report-card time.

Is student data safe?

Workflows carry the minimum — a parent contact, a class, an amount due. Records stay in your systems, and every flow is documented for the management to audit.

We already use a school app nobody opens.

That's why these run on WhatsApp and SMS — the channels parents already read. No new app to ignore.

Can this work alongside our existing school ERP?

Yes — the ERP stays the record; workflows handle what it doesn't: instant answers, reminders that arrive, and circulars that confirm delivery.

Who writes the circulars?

Your office, exactly as today — the workflow only handles addressing, delivery, and the unreached list.

Do we have to take both the website and the automation?

No. Every service is scoped and sold separately — website only, automation only, or a single workflow to start. The two compound when joined, which is why the page shows both, but nothing requires buying both.

Tell us what your team still does by hand.

Thirty minutes. You'll leave knowing what we'd build, what it would cost, and whether it's worth doing at all.

Prefer to write first? Use the full form.