Loading…
Loading…
Built for the front office, not the classroom. If your admin team spends its day chasing permission forms, coordinating relief staff and answering the same enrolment question by phone, that's the work we take off their plate.
Most of the pressure in a school office isn't teaching work at all. It's the paperwork, the phone calls and the chasing that sit around it, and it lands on a small team that's already stretched.
If three or more of these are true, there is a straightforward first project in here.
Frequent, repetitive and expensive to get wrong — in that order.
Forms go out, and reminders go automatically to whichever families haven't responded, on a schedule your office sets. Your team sees a simple list of who's outstanding instead of manually tracking replies, and reminders stop the moment a form comes back.
Instead of working down a phone list one call at a time, a coverage need goes out to your relief pool at once, and responses are collected in one place so the office can confirm the first available person quickly. It doesn't replace the judgement call on who's suitable — it removes the hour of dialling to find out who's free.
Current school and departmental policies live in one place your staff can search in plain language, instead of a shared drive full of old versions. It always points to the current, approved document rather than generating an answer of its own, which matters when the question is about policy.
This is strictly front-office and administrative work — enrolment enquiries, forms, bookings, newsletters, rostering and grant paperwork. We do not build anything that touches student wellbeing, assessment, safeguarding or any record involving a child's personal or health information; those stay exactly where they are, in the systems and processes your school and department already require for them. Where your department has a policy, a preferred platform or a data handling rule that affects a piece of admin work, that policy takes precedence over anything we'd suggest, and we'll ask to see it rather than assume. The honest goal here is time back for a stretched admin team, not a new system for its own sake — if the paperwork isn't costing your office real hours, it's not worth automating.
Related reading: AI in schools: what the office can safely automate
Everything is built inside your own accounts, under your own logins, and you can revoke our access at any time. We will tell you plainly which third parties touch your data and what they do with it, and we keep personal information out of general-purpose AI tools unless there is a proper arrangement in place for it.
You will always know what is being built, what it costs and how to switch it off.
You describe a normal week. We listen for the parts that get done twice.
As it really happens, including the workarounds nobody admits to.
A written definition of done, a fixed price, tested on your real jobs.
Your team trained, documentation left behind, and a check-in a few weeks later.
No. We scope this work to front-office administration — enquiries, forms, bookings, rosters, newsletters and grant paperwork. Anything involving student assessment, wellbeing or safeguarding data stays in your school's existing systems and processes, which are governed by rules well outside what a general automation should touch.
No, it's built to do the opposite. The intent is to take the repetitive chasing and re-typing off a small office team so the people already doing that job have time for the parts that need a human — a worried parent on the phone, a tricky enrolment case, the daily judgement calls.
We build around what your school already uses rather than asking you to replace departmental systems. Where a departmental platform is mandated for something, that stays as the system of record, and any automation we build fits in around it rather than working against it.
We treat any information connected to a student or family as sensitive by default, and keep it out of general-purpose tools unless there's a clear, specific reason and your school has agreed to it. Where there's any doubt, the answer is to leave it in your existing, governed system rather than move it somewhere new.
Twenty minutes, no slides, no obligation. Worst case you get a clear opinion on whether it is worth doing at all.