Built here. For here.

Walk into any school bursar's office in Uganda on the first Monday of Term 1. The desk has a ledger. A phone. A notebook with MTN MoMo transaction numbers written by hand. And somewhere, a spreadsheet that hasn't reconciled with the actual deposits yet.

This is not a problem with the bursar. It is a problem with the software.

Every school management system Uganda schools use was built somewhere else. Built for a monthly billing cycle that no Uganda school uses. Built with grading systems that have nothing to do with PLE, UCE, or UACE. Built without mobile money. Built by people who have never sat in a Uganda classroom or stood in a school gate queue on opening day.

Ugandan school owners know the systems don't fit. They use them anyway, because there was no alternative built here, for here.

Academia Pro started with one question: what would a school management system look like if you started from Uganda's schools, not from a generic template?

The answer changed almost everything.

The billing engine runs on Term 1, Term 2, Term 3 — not January through December. MTN MoMo and Airtel Money reconcile automatically; the bursar sees which student paid, when, and for what, without a single phone call. PLE aggregate calculations are built in — not configured, not worked around, just there. A parent in Jinja can switch their portal to Luganda. A P7 teacher can generate the entire class's UNEB-format report cards in the time it used to take to print one.

This is what it looks like when software starts from the right place.

The ambition is Uganda first. East Africa next. But always built from here, for the reality of running a school on this continent.