Software for schools and education

Teachers did not sign up to spend their evenings chasing forms.

Schools

What usually goes wrong

If two or three of these sound like your week, the rest of this page is about fixing them.

  • Admissions arrive by email, paper and phone, and get tracked in a spreadsheet.
  • Attendance is taken on paper and typed in later, if there is time.
  • Parents ring the office to ask something the school already sent them.
  • Fee reminders go out by hand and the chasing is somebody's whole afternoon.
  • Reports take a week of staff evenings every term.

The work

What we build here

Most projects are two or three of these rather than all of them. Each one links through to how that kind of work runs.

  • An admissions system that follows the applicant

    Enquiry to application to offer to enrolment, in one place, with automatic follow-ups so nobody falls through and staff can see where every family is.

    Custom Software
  • Attendance taken in the room

    Registers on a phone or tablet, submitted in seconds, with absence notifications to parents the same morning instead of the next week.

    Mobile Apps
  • A parent portal that answers the question

    Timetables, attendance, reports, fees, permission slips and messages. Most calls to the office are for something that could be on a screen.

    Custom Software
  • Fees, invoicing and reminders

    Invoices raised, payment plans tracked, reminders sent automatically before the awkward phone call is needed.

    AI Agents & Automation
  • An office phone line that answers

    Term dates, uniform, absence reporting, admissions questions -- answered at any hour, with anything sensitive going to a member of staff.

    AI Voice Agents

Fits around you

Works with what you already run

We build around the systems you already pay for and your team already knows, rather than asking you to replace them. Where a connection is not possible, we say so before you commit.

  • Student information systems
  • Google Workspace and Microsoft 365
  • Payment providers
  • Learning management systems
  • SMS and email gateways
  • Accounting packages

Questions we get asked about schools

What about children's data and privacy law?

It has to be designed in from the start: data minimisation, access controls by role, audit logs, retention rules and hosting in your own region. We build to that as standard and will work to whatever your regulator or authority requires.

Our staff are not technical. Will they use it?

That is the actual test. We build with the people who will use it daily -- office staff and teachers, not just the head -- and if a register takes more than a few seconds to submit, it has failed.

Can this work with the system our authority requires us to use?

Usually yes. Where a system is mandated we build alongside it and sync, rather than replacing it.

We are a small training provider, not a school. Does this still apply?

Yes, and it is often simpler. Enrolments, attendance, certificates and invoicing are the same shape of problem with less regulation attached.

The same problems turn up in the other trades we build for, usually wearing different words. See who else we build for.

Next step

Tell us what is not working.

Describe the problem in your own words. We reply with an honest read on whether it is worth building, roughly what it takes, and what we would do first.