We Could Not Afford a School ERP, So I Built One
Every school ERP demo ends the same way: a polished dashboard, a long feature list, and a price that assumes you are not a school in Rawalpindi working with a real budget. When I became Director IT at Rhizome School, the
Every school ERP demo ends the same way: a polished dashboard, a long feature list, and a price that assumes you are not a school in Rawalpindi working with a real budget. When I became Director IT at Rhizome School, the choice was not between vendors. It was between building our own system and staying on paper registers and scattered spreadsheets.
So I built it. The Rhizome ERP and learning management system is written in TypeScript and runs the school's daily operations: student records, timetables, examinations, and the administration workflows around them. It serves around 300 students and 34 staff, and I maintain it myself alongside running the school's IT, its timetables, and its examinations.
This was not my first system. At the Arfa Karim Technology Incubator, where I was Director IT and Business Development, I built a digital administration and document generation system in PHP and MySQL. Staff entered data once, and the system produced the official documents from templates. It removed an entire category of copy paste errors and the queues of people waiting for paperwork. I also wrote Python automation bots at both institutions for the small, boring, repetitive tasks that quietly eat a working day: renaming, sorting, generating, checking.
Three lessons from building institutional software with no budget:
Process first, code second. A school does not need features, it needs its actual workflow, mapped honestly. The timetable does not care about your architecture. Sit with the office staff and the exam cell before you write a line.
One source of truth fixes arguments. Most school office conflict is two versions of the same record. A single database, with clear roles for who can change what, ends those arguments permanently.
Maintainability beats cleverness. If you are also the IT department, the network admin, and the person who fixes the projector, the system has to be one you can debug at 8 in the morning before classes start. Boring technology, chosen deliberately, wins.
The infrastructure mattered as much as the software. At both institutions I built the IT foundation from zero: networks, systems, Google Workspace administration for hundreds of accounts, and basic security. Software on top of a broken network is decoration.
I am not a computer science graduate. My background is customer support, then IT administration, learned on live systems where a mistake meant a real office stopped working. That background shaped how I build: everything has to survive contact with a busy school morning.
If your institution cannot afford the ERP in the demo, that is not the end of the road. It might be the start of a better one.
β Mohammed Ahmed, often referred to as "Sheikh Mohammed Ahmed," Director IT at Rhizome School, Rawalpindi. LinkedIn: https://www.linkedin.com/in/theycallmesheikhahmed
Originally published by Dev.to WebDev. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.