Education software development
We build student, admissions and communication systems for schools, colleges and education technology firms. The same system has to work for a teacher taking the register at 8.45 and a parent checking a message on the bus home, and those two people need very different things from it.
School software families can use without training
Student, admissions and communication systems for schools, colleges and education technology firms.
Systems we build
- Student informationOne record for admissions, teaching and finance
- Admissions and feesApply, accept and pay in one flow
- Timetables and attendanceTake the register in seconds
- Parent appsReports and messages in plain language
- Assessment and reportingEnter marks once, use them everywhere
- Learning platform linksAccounts and groups kept in step
- Reply within one business day
- Releases planned around school terms
Education software schools ask for
Student information
Each student has one record, and admissions, teachers and the finance office all work from it.
Admissions and fees
A family applies, accepts an offer, enrols and pays in one smooth path, instead of filling in four separate forms.
Timetables and attendance
Timetables that know which rooms, teachers and groups are free, and a register a teacher can take in seconds.
Parent apps
Parents see attendance, reports and messages on their phone, written in plain language, and they don't need to remember yet another password.
Assessment and reporting
Teachers enter marks once, and the same marks feed reports, analysis and official returns.
Learning platform links
We connect to the learning platform you already use, so student accounts and class groups update themselves.
Why schools need a different approach
Schools and colleges tend to collect systems over the years. You might have one tool for records, another for learning, a third for payments and a fourth for messages, each with its own list of students. Someone in the office then spends hours every week keeping those lists roughly in line.
So we design around the people using it. Staff log in every day and soon learn their way round. Families might open it three times a term, on an old phone, and sometimes in a second language. If a parent can't work it out, they'll ring the office, and the time you hoped to save goes straight back into answering calls.
Duties every school system meets
- Student data privacy. Records about children follow stricter rules than ordinary customer data, and sharing them is tightly limited.
- Safeguarding. Only named staff can see sensitive records, and every time someone opens one it's logged and reviewed.
- Parental consent. Parents' consent for photos, trips and data sharing is recorded for each child, and it's easy for them to withdraw.
- Accessibility. We follow WCAG (Web Content Accessibility Guidelines), which many public schools and colleges are legally required to meet.
- Retention. The system keeps records for as long as the rules require and deletes them automatically when that period ends.
Systems we usually connect to
We plug into your student information system, learning platform and payment tools before suggesting anything new. If your staff rely on one of them, replacing it is a choice we'd only make with you, on purpose. Want to try a new tool with one class before the whole school? Our guide on building an MVP that tests your idea shows how.
How a school project unfolds
-
Map the school year
We mark your terms, enrolment weeks and exams on the plan first, because those dates won't move for anyone.
-
Start with one process
We usually begin with admissions or attendance. Both cause staff plenty of grief, and it's easy to measure the time you save.
-
Build with staff and families
Staff and families both see the work every two weeks. We test screens with real parents, so we're not guessing what they'll understand.
-
Release between terms
We switch over during a holiday. Your old system stays available to look things up, but no one can change it.
These are typical ranges. Your real calendar depends on term dates, enrolment windows and exam season, and on how soon the people who approve changes can meet. See our software development process for each stage in detail.
What changes for staff and families
Less duplicate entry
With one record per student, nobody spends Friday afternoon matching up lists.
Fewer calls to the office
When parents can find the answer on their phone, they don't need to call the office for it.
Returns produced from data
Official returns come straight out of the system, so nobody has to build them in a spreadsheet.
What schools ask us first
Usually, yes. Most learning platforms let other systems update accounts, groups and results. Once we keep those in step automatically, a big weekly job disappears from someone's desk.
We keep them apart from other data, with their own access rules, their own log and their own retention period. Only named roles can open them, and every view is recorded.
Between terms, and never in the weeks around enrolment or exams. We plan releases around your school year from our very first conversation.
Tell us about your school’s systems
Tell us which school task eats most of your staff's time, and we'll suggest a first step.