Industries
EdTech software development
Education software has an unusual mix: the buyer is an administrator, the daily user is a teacher with no spare minutes, and a large share of the audience are minors, which changes the data rules.
Systems built for the administrator, not the teacher
Most school software is bought on a feature list and used by someone who has four minutes between classes. If registering attendance takes eleven clicks, it gets done at the end of the week from memory, and the data everyone is reporting on becomes fiction. The measure of education software is how fast the most repeated daily task is.
What we build
- Learning management and course delivery
- Student information and enrolment systems
- Attendance and grading workflows
- Parent and guardian portals
- Assessment and quiz engines
- Timetabling and resource scheduling
What makes this sector hard
Minors change the data rules
Where users are children, GDPR Article 8 puts consent in the hands of a parent or guardian below the national age threshold, and the bar for data minimisation is higher. That affects account creation, analytics and any third-party script on the page. It is a design constraint, not a checkbox.
Accessibility is not optional here
Public and publicly funded institutions are typically required to meet WCAG standards, and beyond the legal point, a portion of every student body uses assistive technology. We build to keyboard navigation, screen reader semantics and contrast requirements as we go, because accessibility retrofitted at the end is always worse and more expensive.
Load is violently seasonal
Enrolment week and results day generate more traffic in a few hours than the rest of the term combined. Infrastructure sized for the average will fall over on the two days that matter most, so we load test against the peak rather than the mean.
On experience in your sector
We are straight about this: these are capability pages, not a client list. Where we have delivered in a sector we will name the client on the projects page. Where we have not, what we bring is the engineering, the compliance groundwork and a willingness to learn your domain quickly rather than pretend we already have.
FAQ
Yes, and for a lot of schools this is the deciding requirement. We identify which tasks must survive a dropped connection, usually attendance and grade entry, and build those to work offline and sync when the network returns. Doing this selectively is far cheaper than making the whole system offline-capable.
Where it exposes an API or a scheduled export, yes. Many older school systems only offer a CSV dump, which still works for a nightly sync but rules out real-time features. We check this before scoping, because it changes what is possible.
Have a product that needs to ship?
Tell us where things stand and what you're trying to hit. We'll respond within one business day with next steps.