NETRAUTECH
Concept Build

One place for parents to find what they need.

Concept build: a modern school website with announcements, fee information and a parent portal, replacing paper notices and phone calls.

Peewee School
Client
Concept
Status
Web & Apps
Pillars
The challenge

A school relied on paper notices sent home in schoolbags and phone calls to the office for parent communication. Notices got lost, phone calls piled up around fee deadlines and event dates, and parents who worked during office hours had no reliable way to check basic information without waiting for a call to be answered.

There was also no consistent public information for a prospective parent researching schools — admissions details, fee structure and term dates existed only as answers office staff gave verbally, which meant the same information could be described slightly differently depending on who answered the phone that day.

Our approach

A modern school website centres on the information parents actually need repeatedly: announcements, an academic calendar, fee information, and admissions details presented clearly enough that a prospective parent can self-serve most of their early questions before ever calling the office.

A lightweight parent portal sits on top of the public site for existing families — a single place to check announcements and fee status without a phone call, reducing the office’s call volume during the specific weeks of the term when it spikes hardest, around fee deadlines and event announcements.

Outcome

A single, reliable place for parents to find what they need, cutting down the volume of repeat phone calls to the office and giving prospective parents a consistent, self-serve answer to the questions they ask most.

Why this is labelled a concept, not a delivered result

This project is a concept build, not a completed client engagement. It is built as a reference for the specific pattern independent schools tend to share: strong reputation among current families, weak digital presence for anyone outside that circle, and an office that spends a meaningful share of its week answering the same handful of questions by phone. Working through the design forced decisions we would carry into a real school engagement — what belongs on the public site versus behind a parent login, and how to keep the admissions information accurate without creating extra admin work for office staff.

The parent portal is intentionally lightweight rather than a full school-management system, because most of the value for a school this size comes from solving the communication gap first, not from replacing every internal process on day one.

A real school engagement would start from the same principle — solve the highest-friction communication problem first, then expand only where the school actually feels the next bottleneck.

Technology
Next.jsTailwindSupabase

Facing a similar problem?

Tell us what's breaking, and we'll tell you honestly what it would take to fix it.

Start a Project