What's next on the roadmap

An honest list of what isn't shipped yet.

Three features are next in line after the current beta: an AI Exam Paper Generator for board-pattern monthly tests and finals with a marking scheme; an AI Presentation Builder that turns a lesson or chapter into a classroom slide deck; and Parent Communication, generating homework, exam, absence, and PTM messages ready to send in Urdu, English, or Roman Urdu.

Each of those three traces back to a specific complaint, not a generic "AI can do more" impulse. The Exam Paper Generator exists because a monthly test or final still means manually assembling coverage across every chapter taught that term, roughly matching the marks a board or school expects, and writing a marking scheme separately โ€” the same kind of repetitive, checkable work the three live generators already handle, just at paper length instead of chapter length. The Presentation Builder exists because a lesson plan and a set of classroom slides are two different documents built from the same material, and right now that means writing the content twice. Parent Communication exists because homework reminders, PTM notices, and absence messages get rewritten from scratch in Urdu, Roman Urdu, or English every time, instead of drafted once and adapted โ€” the exact gap covered with ready-to-adapt templates in a separate Journal post.

Alongside those, a handful of add-on packs are planned rather than shipped โ€” a premium curated question bank, a Cambridge/O-Level content pack, an Urdu literature pack, and WhatsApp-ready notice automation among them. None of them are meant to replace the core generators; they're meant to extend them for teachers with a narrower, specific need โ€” a Cambridge or O-Level pack for schools running that syllabus alongside a local board, an Urdu literature pack for a subject the core generators cover more thinly today, and WhatsApp-ready automation as a delivery layer on top of whatever Parent Communication eventually generates.

What decides the order isn't a fixed internal plan set before the beta launched โ€” it's shaped directly by which pain point teachers actually name most often, the same feedback loop described in a separate post on why Muallim is built for teachers, by teachers. That's also why this list stays a roadmap and not a set of promises with dates attached: a specific ship date implies a certainty about scope and timeline that a small team building in public genuinely doesn't have yet.

A fair question worth answering directly: when will these actually ship? We're not going to put dates on it here, and that's a deliberate choice, not evasiveness โ€” a small team attaching a public date to a feature it hasn't started building yet is exactly the kind of promise that gets broken through no fault of anyone's effort, and a broken date does more damage to trust than an honest "no date yet" ever does. What we can commit to is the ordering logic already described above, checked against the Features page whenever that list changes.

That same audience discipline applies to what does and doesn't make this list, too. A student-facing quiz app, a general school communication tool aimed at parents as end users, or a broader school-operations suite aren't on this roadmap, even as ideas โ€” not because they're bad ideas, but because they'd pull Muallim away from being a tool for teachers and school admins specifically, which is the actual product, not a phase on the way to something broader.

It's also worth naming the trade-off in publishing a roadmap this openly at all: it means being visibly, publicly wrong sometimes, when a feature described here as "next" ends up taking longer than expected, or gets reordered because a bigger pain point surfaced first. The alternative โ€” saying nothing until something ships โ€” would look tidier, but it would also mean teachers have no way to weigh in on what gets built before it's already built. That trade favors teachers having a say over the roadmap looking clean, which is the right trade for a product built specifically for them.

None of this is live yet, and we're not going to list it as if it were. The Features page keeps the roadmap clearly separated from the 5 modules actually shipped โ€” Lesson Planner, Worksheet Builder, Quiz & Assessment, Content History, and the Admin Dashboard โ€” and that separation stays as the product grows. A feature only moves off the roadmap once it's something you can actually open and use. If you're reading this list wondering whether a specific pain point of yours is already accounted for somewhere in it, the honest answer is: check the wording carefully, because a near-miss โ€” something close but not quite what you need โ€” is exactly the kind of gap worth telling us about directly, rather than quietly assuming it's already covered somewhere in the list above and never actually saying so.

โ† Back to Journal ยท See what's live