Vendor pitches and a principal's actual needs frequently diverge, not out of dishonesty, but because a sales conversation optimizes for what sounds impressive in a demo, not for what a specific school will actually use every week. A requirements framework, built independently of any specific product, is a better starting point than any single sales pitch — including a page like this one, which is why the criteria below are stated first and any product mention comes only afterward, clearly marked as one example, not the framework itself.
Must-haves, the things that make software actually usable rather than just impressive: a self-serve way to see and reassign which teacher is on which class and subject, without a support ticket. Output — report cards, test papers, worksheets — branded consistently with the school's own identity by default, not dependent on each teacher remembering to add a logo. Genuine Urdu and Roman Urdu support where the school actually communicates in those languages, not an English tool with a translation button bolted on. And a real way to try it with actual staff before committing a budget — a capped free tier or trial that isn't gated behind a sales call.
Nice-to-haves, genuinely useful but not dealbreakers if missing today: integrated parent communication drafting, which most tools — including Muallim — are still building toward rather than shipping today, worth checking the current state of rather than assuming either way. Multi-campus support, relevant only if the school actually operates more than one campus. And board-specific content scoping across every board a school might touch, not just the primary one, useful for schools that run mixed curricula.
What to actively avoid, the red flags worth screening for specifically: vendor lock-in with no way to export what's been generated or entered, which turns switching software later into losing a school's own accumulated content. Opaque, per-student pricing that scales unpredictably as enrollment grows, making a school's own success the thing that makes the tool more expensive. And any tool that treats every school's curriculum the same regardless of board — a strong signal it was built for a different market and adapted superficially, not built for Pakistani boards from the start.
Rollout expectations are worth setting honestly before signing anything, too. Even a genuinely easy-to-use tool takes a real school a few weeks to settle into — staff need to actually try it on live classes, not just watch a demo, before anyone can fairly judge whether it fits. A principal expecting instant, universal adoption in week one is setting the evaluation up to look like a failure regardless of how good the tool actually is; a more realistic timeline is one or two teachers piloting it for a few weeks, then a wider rollout once it's clear it holds up on real material.
Training needs scale with how different the new tool is from what staff already know. A tool that mirrors how teachers already plan on paper — subject, chapter, SLOs, activities, homework — needs far less training than one that introduces an entirely new mental model for organizing content. Asking a vendor directly "what does a teacher who's never used this need to learn before their first real week" is a more useful question than asking about the feature list.
Put together, the actual need underneath most of the framework above isn't a longer feature list — it's confidence that a tool fits how this specific school already works, rather than asking the school to reshape itself around the tool. Every criterion here, from the must-haves down to rollout expectations, is really one question asked from different angles: will this make a teacher's actual Monday morning easier, or just look impressive in a sales deck on some Tuesday afternoon that nobody in the actual staffroom ever ends up seeing, reading, or genuinely caring about at all?
Running Muallim, built by DIGIT Pakistan, against this framework honestly: it meets the must-haves for the academic-content and teacher-management category specifically — the Admin Dashboard for reassignment and branding, Urdu and Roman Urdu as first-class outputs across the Lesson Planner and the Worksheet Builder, and a genuinely free-to-try tier capped by usage, not a sales call. Parent communication is on the nice-to-have list still on the roadmap, not live yet. And pricing is seat-based per teacher rather than per-student, which avoids the specific red flag named above, though it's still worth checking current plan tiers on the Pricing page directly rather than taking that as a permanent guarantee.
The actual point of a framework like this isn't to arrive at one right answer — it's to make sure a principal is evaluating any option, Muallim included, against what the school actually needs this term, rather than against whichever feature list reads most impressively in a sales conversation.