A story that starts with the wrong problem
Before KMPUS was software, it was a problem on our own desk. We worked at a school, and not as consultants: we were the people who collected the registers at the end of the day and had to turn them into something the school could use. Teachers marked attendance on paper because paper was the only thing that survived a classroom: nothing to switch on, no password to remember, no signal required.
Getting that pile of sheets into a spreadsheet took about two hours, every day. It was not difficult work: it was work that never finished. So we built the obvious thing. The first version of KMPUS was an attendance module and nothing else: mark a class in seconds, from the room, on a phone.
The two hours disappeared. And the school's admin workload did not drop.
We had measured the data transfer, which had a name and an owner. We had never measured what came after it: rebuilding tomorrow's sheet every time a student changed level mid-week, working out again who teaches what, in which room and to which students. That was the real work, and it was nobody's task. What we built next was exactly that: teacher, level, room and enrolment declared once, with their dates, and everything else coming out of it. We founded KMPUS in 2021 and we have built it the same way ever since: one module at a time, starting from the desk rather than the feature list.
The module that started all of it is still the one schools notice first: academic management, from class lists to daily attendance.
The full story, and the order we would recommend today if you are about to digitise your centre, is in digitising a language school: what comes first.