“ERP” sounds like enterprise software costing millions. For a school, clinic or growing business it usually starts smaller: you have operations that run on separate spreadsheets, group chats and paper, and someone — usually the operations lead — is doing the integration work by hand every day. That manual work is what you’re already paying for; it just isn’t on an invoice.
Signals that you’ve outgrown the tools
- The same record is typed into three different places, and the versions disagree.
- “You’ll hear from the admin” is a daily phrase — updates move by chasing people.
- Monthly reports take days to assemble from exports and emails.
- Finance is reconciled by hand from exports nobody fully trusts.
- New staff need weeks to learn where information actually lives.
When it’s not yet time
If the whole operation fits in two spreadsheets and one person, an ERP is overhead — automation of a single task is cheaper. The line is crossed when multiple people must work the same records and the process of reconciling them is itself a job.
What a good outcome looks like
- One record per entity — student, customer, item — used by every department.
- Modules that exist because the business uses them, not because a vendor sells them.
- Notifications that actually reach people — confirmed delivery, not a sent flag.
- Reporting you trust, produced while the month is happening, not after.
- A system the staff want to use because it removes work, not adds it.
Custom build vs buying off-the-shelf
Off-the-shelf ERP wins when your processes already match the vendor’s defaults and the licence fits. A custom build wins when the org’s differences are what generate value — unusual workflows, existing institutional practices, or integration needs the shelf product can’t reach. The school ERP was custom because the workflows — attendance, billing, parent communication — were specific to how that institution runs.