Attendance is attendance. Fee collection is fee collection. Two thousand institutions do these the same way, and any of them building custom software for it is burning money that should go into teaching.
But the curriculum side is where institutions genuinely diverge. A madrasha tracking Hifz progress needs a completely different progress model from a school tracking term grades, and an institution running both needs them side by side on one student record.
This is where most generic school software fails locally. It assumes a single national curriculum, so anything running Dakhil or Alim alongside the general syllabus ends up maintaining a parallel paper system, which defeats the purpose.
Our rule is to buy the common parts and configure the divergent ones. Admissions, attendance, fees and guardian communication are the same product for everyone. Curriculum, grading and progress tracking are configuration, not code.
The test for whether you need custom work is simple: can you describe your requirement as a setting? If yes, it is configuration. If describing it requires explaining a process no other institution runs, that is the part worth building.
