Start with workflows, not modules.
A school system should reduce duplicate work. Before comparing products, map how a new student moves from admission into a class, a fee account and later an academic report. Then map how a payment becomes a receipt and management report.
Look for a system that allows those workflows to share the same underlying student and school records. A long feature list has limited value if staff still have to reconcile spreadsheets between departments.
Evaluate the finance reality
Zimbabwean schools may need to deal with more than one currency, different fee groups, billing adjustments, receipts and account statements. Test these scenarios in the demonstration instead of relying on screenshots.
Evaluate the academic cycle
Ask how subjects and assessments are configured, how teachers enter marks, how comments are added and how report cards are generated. The strongest workflow is the one that is clear from setup to final report.