Our own software
Two products we build, run and maintain.
We are an engineering company first, and these came out of the engineering. Each one started as a problem we kept meeting in client work and decided to solve properly — which means we live with our own architectural decisions rather than handing them over and walking away.
Both are in production and maintained by the same team that built them.
School management software
ScholarAIMS
A school runs on records that have to agree with each other — who enrolled, who attended, what was taught, what was paid and what the parents were told. ScholarAIMS keeps those in one system, with a parent-facing app on top of the same data rather than beside it.
What it does
Admission and enrolment
An enquiry becomes a student record without anyone re-typing it. The details captured at admission are the same details the rest of the system reads.
Attendance
Daily marking by class, readable as a pattern per student rather than a stack of registers — so a child who is quietly slipping shows up before the term ends.
Academics
Classes, subjects, assessments and results held against the student record, so academic history travels with the student instead of living in a teacher's file.
Fees
Fee structures, dues and receipts in one place, with a straight answer to the question every school office is asked daily: who has paid, and who has not.
Notices and parent communication
School-to-home messaging that reaches the right class or the right parent, with a record of what was sent — not a message group nobody can audit.
Parent app
Parents see their own child's attendance, academics, fees and notices. One source of truth means the office stops fielding calls that the app has already answered.
ScholarAIMS is where we learned how much of institutional software is really about reconciliation — making separate records agree. That is the same problem most of our custom ERP work turns out to be.
Digital catalogue and QR menu platform
ShowShelf
Most small sellers already have a catalogue. It is a PDF that is three weeks out of date, or a printed menu with a sticker over the price. ShowShelf turns it into a link and a QR code that stay correct, and sends enquiries to the channel the customer is already using.
What it does
Changes go live immediately
Edit a price or add an item and the live catalogue updates at once. No reprint, no re-sending a PDF, no stale copy circulating in someone's chat history.
One link, one QR, permanently
Every catalogue gets a stable link and QR code. Print the QR once and it keeps working — the content behind it changes, the code does not.
Enquiries on WhatsApp
A customer taps an item and messages you with it already filled in. No order form to abandon, no account to create, no new app on their phone.
Built for the phone first
A fast storefront that behaves on a mid-range phone on mobile data, because that is what the customer is actually holding.
Menu mode for restaurants
The same engine arranged for food service — sections, dishes and a QR menu for the table, instead of a product grid.
ShowShelf is our answer to a pattern we kept meeting: the problem was never that the business lacked software, it was that updating the software cost more than living with it being wrong.
If neither fits
Most of what we build is not on this page.
A product only helps when your problem is close to the shape it was designed for. When it is not, forcing it costs more than building the right thing — so the majority of our work is custom engineering against a business’s actual process.
The honest version of this page is that ScholarAIMS and ShowShelf exist because two problems turned out to be general. Yours may not be, and that is a normal answer rather than a disappointing one.
Start a project
Want one of these,
or something only you need?
Tell us how the work is done today. We will say which of these fits, or that neither does and what we would build instead.