Industries we build for

Not because the code is different. A booking system is a booking system. It matters because the expensive mistakes in each sector are specific, and the second time you meet one you design around it instead of discovering it in week six. Knowing that school fee cycles are per-student-per-term, that a kitchen queue has to be gated on payment, or that industrial buyers eliminate on specifications rather than choose on design — none of that is technical knowledge, and all of it changes what gets built.

It also changes the conversation. We can tell you what comparable organisations did, what we would do differently now, and which features you are about to pay for and never use. That is worth more in the first thirty minutes than a capability list.

The flip side is worth saying plainly: if you work outside these seven sectors, we would be learning your domain at your expense in the early weeks. Sometimes the problem shape is familiar enough that this does not matter, and sometimes it genuinely does. We will tell you which we think it is rather than take the work and find out.

Education dominates the list because that is where the work came from — a preschool group needed a portal, then its campuses needed sites, then other schools asked. The others each began with one client and one problem. None of this was a strategy; it is simply an accurate record of what we have shipped.