The biggest school platforms were shaped around one kind of customer: the giant public institution. That heritage runs deep — layers of government-compliance reporting, funding-formula math, and pricing built for six-figure budgets. It's a real product for a real need. It just isn't the one most private schools have.
A different unit of scale
A fast-growing part of the school-software market doesn't look like a giant institution at all. It looks like a group of campuses under one owner — a family that runs five schools across a city, a brand franchising into new towns, a trust operating a dozen sites with shared staff and one back office.
That owner has questions a single-school product can't answer cleanly:
- How is collection tracking across every campus this month?
- Which teachers are shared between sites, and who approves their leave?
- Can a new campus inherit the group's branding and fee structure on day one?
Modelling the group, not bolting it on
Qalamaly puts an organization layer above schools. A group dashboard aggregates every campus; staff can hold affiliations across sites; branding and structures cascade from the group down. Onboarding the sixth campus is a form, not a migration.
This isn't a reporting view stapled onto a single-school product. It's the shape of the data model — because the group is the customer, and the group is who signs.
Focus is a feature
Modelling the multi-campus group well means saying no to enterprise bloat. We don't do heavyweight government-compliance reporting, special-education case management, or a full learning-management system. For an owner running a handful of campuses, none of that is missing — it's weight they'd otherwise pay to carry.
We'd rather do the school day exceptionally well, across every campus, than do everything adequately for a customer we were never built to serve.