Education has a constraint most sectors do not: the people using the software include children, and the rules around their data are stricter for good reason.
What actually goes wrong
Parent communication across four channels. Email, text, a paper letter in a bag, and an app nobody opens.
Attendance and registers on paper. Then typed into a system later.
Homework and resources scattered. Across email, a shared drive, and a platform.
Safeguarding requirements met manually. Which is both burdensome and inconsistent.
MIS software that is rigid and expensive. It does the statutory core and nothing beyond it.
What we build
- Parent communication appsOne channel, with read receipts, so you know the message landed.
- Attendance and registersCaptured where it happens rather than transcribed later.
- Course and resource deliveryFor tutoring businesses and training providers.
- Booking and paymentFor tutoring, clubs, trips, and courses.
The constraints that matter here
Safeguarding is a gate. Somebody will have to approve this, and they will ask specific questions. Have the answers ready before the meeting rather than after it.
Accessibility, genuinely. Including for students with additional needs. This is a design requirement from day one.
The budget calendar rules everything. Decisions cluster in spring for September delivery. If you want something for the new academic year, the constraint is your process, not our build.
MIS integration. Establish whether your system has an API before you commit to anything that depends on it.
Common questions
How do you handle children's data?
With more care than adult data, because the law requires it and because the consequences are worse. Minimal collection, no behavioural tracking, parental consent where it applies, data in your own account, and you as the controller.
Will it integrate with our MIS?
Depends on the system. Several UK management information systems have APIs and integrate cleanly. Some do not, and the honest answer is a scheduled import rather than live sync.
When should we start if we want it for September?
Book the sprint by early summer. The build is two weeks, but procurement, safeguarding review, and your own decision cycle are not, and those are the parts that consume the calendar.