The key points
- Ready-made software is faster to start and cheaper for standard needs.
- Custom software fits unusual fee structures, multi-branch groups and special integrations.
- The deciding questions are how different your workflows are and how long you will use the system.
- Whichever route you take, insist on owning your data and being able to export it.
When does ready-made school ERP work well?
If your fee structure, attendance routine and report cards look like those of most schools on the same board, a packaged product will cover them. You can start within weeks, the vendor carries maintenance and updates, and other schools have already found and reported the common problems. For a new school or a small preschool, this is usually the sensible first step.
The trade-off is that you adopt the vendor's way of working. When a rule does not fit, you either change your process or pay for a customisation that the vendor schedules on their own timeline. Licences are often charged per student each year, so the cost grows as you do.
When is a custom build worth considering?
A custom build starts to make sense when the software has to follow your rules rather than the other way round. Examples include layered fee structures with trust-funded concessions, several branches that share students and staff, unusual admission workflows, or a requirement to connect an existing accounting system, transport tracker or regional-language messaging.
It also suits groups that expect to use the system for many years. A fixed-price build you own has fewer recurring charges and no per-student licence, but you take on responsibility for hosting, support and improvements, or you pay a partner to do so. Our guide to building versus buying software sets out that decision for any business.
Is there a middle path?
Yes, and it is often the best fit. Buy a core product for the standard parts, such as records and attendance, and build only the pieces that make your school different: a fee module with your own rules, a parent messaging flow, or a dashboard that combines data from several systems. This keeps the build small and still gives you control where it matters.
Before choosing, ask every option the same questions: who owns the data, how is it exported, what happens if the vendor closes or raises prices, and how are changes requested and priced. The answers matter more than the feature list. If a custom build looks right, our custom software service and the school management solution describe how we scope and deliver one.
Ready-made ERP compared with a custom build for a school
| Question | Ready-made ERP | Custom build |
|---|---|---|
| How fast can you start? | Within weeks | After scoping and build |
| How well does it fit unusual rules? | Limited to what the vendor supports | Follows your rules |
| What recurs after launch? | Per-student or per-branch licence | Hosting and support |
| Who controls changes? | The vendor's roadmap | You and your build partner |
| What is the main risk? | Lock-in and rising licence costs | Scope creep and maintenance |
Questions to settle before you decide
- How different are our fee and report-card rules from a typical school on our board?
- Do we run several branches that must share data?
- Which systems must it connect to, and does the product support them?
- How many years do we plan to use it?
- Who owns the data, and how is it exported?
- What happens to our records if the vendor stops supporting the product?
Sources
Rules and guidance this answer relies on. Policies change, so check the current version before acting on it.