Nexa Ed

Most African educational institutions don't have an IT department. They run on WhatsApp groups for announcements, Excel sheets for grade tracking, and manual bank deposits for fee collection. Reconciliation takes weeks, errors go unnoticed for months, and teachers spend more time on administration than on teaching.

The existing solutions — built for Western markets — required dedicated IT setup, expensive annual licences, and integrations with payment providers that simply don't operate in the region. Schools that tried to adopt them gave up during onboarding.

The gap wasn't a feature gap. It was a deployment gap and a payments gap. Any solution had to be live in days, not months — and it had to work with Paystack from day one.

We started by visiting schools in Ghana and Nigeria, sitting with administrators, finance officers, and teachers. The same seven workflows came up every time: fee collection, student records, timetabling, grade management, parent communication, reporting, and staff administration. Everything else was noise.

We built around those seven workflows and nothing else. Paystack was integrated at the architecture level — not bolted on — so every fee, subscription, and ad-hoc payment flows through a reconciled ledger automatically. Daily close became a two-minute task.

AI grading was the most technically intensive module. We built a subject-aware grading engine on top of OpenAI with custom prompt scaffolding per curriculum type. Teachers receive a first-pass grade and written feedback for every submission. They approve, adjust, or override — but they never start from a blank page.

Student portals were designed with a mobile-first constraint: most students access the platform on a phone with inconsistent connectivity. Offline-tolerant architecture with background sync meant no data loss on slow connections.

Student email provisioning was built to cover two scenarios: schools that want students under their own domain (student@yourschool.edu) and schools that don't have a domain — those students get a Nexa Ed address instead. Custom domain setup requires verifying a few DNS records; that's as involved as it gets.

The 72-hour deployment target was a hard constraint, not a marketing claim. Every architectural decision was evaluated against it. Onboarding flows, data migration tooling, and our deployment runbooks were all engineered to get a school live before the end of the week.

Nexa Ed is now live across institutions in three countries. Schools that previously spent two to three weeks on fee reconciliation close their books daily. AI grading returns an average of six hours per week to each teacher across a full school term.

Institutions that couldn't previously afford or deploy a school management system are running full operations on Nexa Ed — payments, portals, grading, and communications — without a single IT hire.

The 72-hour deployment promise has held across every institution. The longest deployment to date took 61 hours.