Most schools and colleges already pay for a learning management system, and most of them still run admissions on spreadsheets, chase fees by email and rebuild the same attendance report every week. The LMS handles courses and coursework well.
Everything around it is left to whatever staff can piece together. Education software development fills that gap: building or extending software for the work your off-the-shelf tools do not cover, connected to the systems you already run.
This guide is for the person who runs the institution, not the IT team. It will help you decide when to buy, when to extend and when to build, and what any custom system must get right on student data and accessibility.
Where the off-the-shelf LMS stops
A learning platform is built for teaching: courses, assignments, grades, discussion. The operational side of a school or college is a different job, and it is often where the hours go:
Admissions. Inquiries from your website, agents and open days, then applications, documents, interviews and offers.
Fees and finance. Installment plans, scholarships, sibling discounts, reminders and reconciliation with the bank.
Timetabling and rooms. Clashes, cover for absent staff, exam schedules.
Parent and student communication. Notices, consent forms, progress updates, in more than one language.
Transport, hostels and canteens. Routes, rosters and payments.
Compliance reporting. Returns to regulators, accreditation bodies and funders.
When each of these lives in a separate tool or spreadsheet, staff re-enter the same student details again and again, and nobody has one view of a student from inquiry to graduation.
Buy, extend or build: a decision framework
Custom software is not always the answer. Use these questions to decide, one area at a time.
Situation | Usually the right move | Why |
|---|---|---|
A common job done the same way everywhere, such as course delivery or payroll | Buy | Mature products exist and your process is standard |
A good product that does 80% of the job but lacks a report or a connection | Extend | Add the missing piece through its API instead of replacing it |
Staff copy data between two systems every day | Extend | A connection between them removes the re-typing |
A process that is specific to you, such as a unique fee structure or a multi-campus admissions flow | Build | Off-the-shelf tools force you to work around them |
A student or parent experience that sets you apart | Build | It is part of what families choose you for |
A system that is old, unsupported and holds years of records | Replace in stages | Move one module at a time, so records and daily work are not disrupted |
Questions to ask before you build anything
Which task costs your staff the most hours each week, and which tools does it pass through?
Is the problem the software, or a process nobody has written down?
Does your current LMS or student information system have an API you can connect to?
Who on your side will own the new system after launch?
Can you start with one department, prove it works, then expand?
What good education software development gets right
One record per student
The single most useful thing custom software can do is keep one record that follows a student from first inquiry to alumni. Admissions, fees, attendance and the LMS read from and write to the same place. Reports stop being a weekly copy-and-paste exercise.
Works on the devices people already own
Parents check updates on their phones. Teachers mark attendance between classes. Staff and students should be able to use the system in a browser or on Android and iPhone, without new hardware. We have built a school admin system that staff use this way, in the browser or on Android and iPhone.
Connects to the tools you keep
Good custom software sits alongside your LMS, your accounting package and your email, rather than replacing them for the sake of it. If a tool works, keep it and connect to it.
Student data: the rules your system has to follow
Schools and colleges hold some of the most sensitive data there is: children's records, health information, family finances, disciplinary notes. Any software you build or buy has to respect the rules that apply where you operate. What follows is general information, not legal advice.
United States: FERPA
FERPA protects personally identifiable information in students' education records. Guidance from the U.S. Department of Education's Privacy Technical Assistance Center explains that when a school shares that information with a software provider under the "school official" exception, the provider must be under the school's direct control over how the records are used and kept.
It must use them only for authorized purposes, and may not pass them on without the school's authorization. Records a provider holds on the school's behalf count as education records too.
In practice: your contract should say what data the vendor can access, what it can do with it, and how it is returned or deleted at the end.
UK and Europe: GDPR and the Children's code
Under UK and EU GDPR, the school is usually the controller and the software provider a processor acting on its instructions. The UK regulator's guidance on edtech and the Children's code makes the point that the label in the contract does not settle this. What decides it is whether the provider in fact controls how and why the data is used.
That point has teeth. When the ICO audited 28 edtech providers widely used in UK schools, it reported in its "Edtech examined" statement that common issues included providers not correctly identifying whether they were processors or controllers. Other gaps were contracts with schools that lacked detail, incomplete mapping of data flows and gaps in data protection impact assessments. Each of those is something to check before you sign.
Other markets
The Middle East and other regions have their own data protection laws, and some limit when personal data can be sent abroad. Agree where data will be hosted before any build starts.
Plan for accessibility from the first screen
Students, parents and staff with disabilities need to use your system too. In the United States, a Department of Justice rule under the ADA requires the websites and mobile apps of state and local governments, which includes public schools, community colleges and public universities, to meet WCAG 2.1 Level AA.
Compliance dates fall in 2027 and 2028 depending on the size of the population served. Private institutions face their own obligations, and the UK and EU have accessibility rules of their own.
Building accessibility in from the first screen is far cheaper than fixing it after launch. Ask any developer how they test for it.
A sensible first project
Start where the hours go. For many institutions that is admissions or fees, because both involve heavy re-typing, many emails and clear rules. Build that one module, connect it to the systems you keep, and let staff use it for a term. Then decide what comes next with real results in hand.
That is how we approach custom software development in general: a small first release, a working demo every week, and code that sits in your own repository and cloud account from day one. Depending on the problem, that might be a web application for staff, a mobile app for parents, or both. Our industries page covers education alongside the other sectors we work in.
See it in practice: Candidate Assessment Software with Biometric Verification
See it in practice: School Website Design for Admissions Information
Talk through custom software for your school
If your staff spend their days re-entering the same student details, a 30-minute call with a founder is enough to work out whether to buy, extend or build. Book a time here. If an off-the-shelf tool will do the job, we will tell you.








