Most school management software is built somewhere else and sold everywhere. The assumptions baked into it — academic calendars, billing models, connectivity, class structures — are usually somebody else’s.

Katanga is being built in Zambia, by the Think Zambia Foundation, for schools in Zambia. That shows up less as a feature list and more as a set of decisions about what the product assumes and what it refuses to assume.

Built around how Zambian schools run

Zambian schools run on terms within an academic year, with students grouped into grades and classes. Katanga’s records are organized the same way — enrollment happens per term and year, and attendance, subjects and fees are scoped to those periods rather than to a generic semester model.

Fees are denominated and managed in ZMW, and schools can accept online payments through ZANACO — meeting parents where they actually pay, rather than assuming card rails that many families do not use.

School sizes vary enormously — a community primary school and a large private secondary school have the same categories of work but very different volumes. Katanga’s plans are tiered by student numbers and staff accounts so a school can adopt the size of system it actually needs instead of paying for an enterprise platform.

Respect for the transition

The biggest difference between software designed for a market and software adapted to one is how it treats the starting point.

Many Zambian schools run on paper registers, mark books and a small number of critical spreadsheets — and they run well enough that the system they replace has to earn its place. We assume the transition is gradual: a school may start with its student list, add fee tracking next term, and bring attendance online later. Katanga’s entry plan is deliberately small for exactly that reason — a school should be able to digitize its most painful record first rather than migrating everything on day one.

We also assume not every user is technical. The people who will actually use the system — administrators, class teachers, bursars — need clear screens and familiar structures more than they need configurability. The product is organized around the jobs those roles already do.

Different users, different doors

Schools are not single-user environments. The administrator setting up the year, the teacher marking a register, and the student checking their record should not see the same thing. Katanga separates experiences by role — administration for staff running the school, a teacher dashboard for classroom work, and student login for learners on higher plans. Schools that grow into multiple campuses can manage up to five under one account on the top tier.

Some schools also want a public face. Katanga includes a website feature so a school can maintain its public presence alongside its administration.

Built in the open, with schools

Because the product is developed here, the feedback loop is short. When a school tells us that their fee structure works differently, or that a class needs to be organized another way, that conversation does not disappear into a foreign support queue — it shapes what we build next. Several of the features above started as a Zambian school’s description of a problem.

That is also a standing invitation. If something in your school’s administration does not fit what Katanga currently does, telling us is the fastest route to it being considered.

What we are not claiming

Being built for Zambia does not make Katanga automatically right for every Zambian school, and we try to be plain about that. It is not a curriculum authority, an examination system, or a government reporting tool. It is a school management platform: student records, enrollment, attendance, grading, billing and the people who use them — done properly, for the schools we are building it alongside.

Where to go from here

If you run or work with a school in Zambia and want to see whether Katanga fits how your school actually operates, create an account and try it — the pricing page shows what each plan includes. You can also read about the product, or browse the rest of this blog for deeper looks at attendance, grading and fee management.