Software for a faculty, not a logo on someone else's product

Universities do not fail for lack of software. They fail because the software was built for a different institution and then renamed. Staff learn a workaround, the workaround becomes the process, and the next academic year starts with last year's argument.

The pieces that actually matter are unglamorous. Who is teaching what, in which room, and whether the students who should be there were. Module scores that a lecturer can enter without a training afternoon. A record the faculty office can trust when someone asks a straight question.

We build that as custom software, next to the IT support rather than instead of it. The same partner who watches the mailboxes can watch the system the faculty depends on. When term starts, you do not want two suppliers pointing at each other.

A good education system is boring on a normal Tuesday. It is fast to open, obvious about who can see a student's record, and honest when something has not been marked. The clever parts stay in the background: reminders, clashes in the timetable, a clean export when an external body asks for one.

If you already have a system and the complaint is that nobody uses it, we would rather repair the workflow than sell you another login. Sometimes the right job is a smaller tool that sits beside the official one and does the one task the official one makes hard.