Choosing school management software in Qatar

A school buying software is at an unusual disadvantage. The purchase happens once a decade, the people choosing are educators rather than software buyers, and every vendor demonstrates the same polished forty minutes. Meanwhile the cost of choosing wrongly is not the licence fee — it is migrating a decade of student records a second time, under pressure, mid-year.

This page is the evaluation we would want a school to run against us. It is deliberately not a list of our features, and it will point out where the cheaper option is the right one.

The four tests to run before anything else

If a product fails one of these, the feature comparison does not matter. Run them in the demo, on the vendor's screen, and do not accept a promise to follow up.

• The Arabic document test — ask them to generate a report card, fee receipt and transfer certificate in Arabic, using a real Qatari name, and to export each as a PDF. Screen rendering is easy; PDF output in right-to-left Arabic is where products break
• The second curriculum test — ask them to show two streams with genuinely different assessment models and report layouts in the same system, populated. Many products support one template and call the rest configuration
• The pricing test — ask for the cost at your current roll and at double it, in writing. Per-student pricing looks reasonable at 400 students and becomes the largest line item at 1,200
• The exit test — ask them to export the complete database, in a readable format, without a support ticket. If that requires their help, they hold your records rather than you

What the price usually excludes

The licence is rarely the real number. The gap between quoted and final is nearly always in the same four places, so ask about each explicitly and get the answer in the quotation.

• Data migration — moving existing students, historical fees and staff records, sometimes quoted separately and sometimes not quoted at all
• Report card design — the single most underestimated item, because each curriculum needs its own layout and schools want them to look exactly as they always have
• Training, and specifically training for teachers rather than only for the two administrators who will be in the room
• Annual support and version upgrades, which for some products is a modest renewal and for others is most of the original cost again

Where a cheaper product is the right answer

A small school of two or three hundred students with one curriculum, no transport fleet and simple fee structures does not need a full platform, and will be happier and poorer with one. A well-chosen simple product implemented properly beats a capable one implemented badly.

The point at which this changes is usually multiple curricula, transport as a real operation, fee arrangements complicated enough that a spreadsheet has grown up beside the system, or a finance team reconciling student data by hand. Those are the conditions that justify a platform, and short of them, they do not.

Questions worth asking about the vendor, not the product

Software lasts a decade in a school. Who supports it matters as much as what it does.

• Which schools in Qatar are running this now, and may we speak to one without you present?
• Who answers the phone in the first week of term, and are they in this time zone?
• Is the education module a supported product for you, or a community project you have adopted?
• If we want a report format changed in year three, is that support, or a chargeable project?
• What happens to our data and our system if this business closes?

Our own position, stated plainly

We implement school systems on ERPNext, so we are not neutral. What we would say against ourselves is this: the ERPNext education module is community-maintained rather than a commercially supported product, and school-specific reporting is configuration work rather than something that arrives finished. For a small single-curriculum school, a packaged product is often the better and cheaper buy.

Where we are the right choice is a school that also wants finance, payroll and procurement on one platform, that runs multiple curricula, that objects to per-student pricing, or that wants to keep its database on its own terms. If that is not you, the four tests above will find you a better fit, and you should use them.

At a glance