How we thinkbefore we ship.
We don't ship principles. We ship systems. The principles are why those systems behave the way they do.
- 01
The software is the operation.
In the businesses we work with, software isn't a support function. It is the operation. A slow POS on a Friday night isn't a UX issue, it's lost revenue. We build with that weight in mind from the first line: the team on the floor uses what we ship every shift.
- 02
End to end, on purpose.
Most projects break at the seams: the app disagrees with the backend, the AI doesn't reconcile with the source of truth, integrations are taped together. We keep web, mobile, APIs, AI and data in one team and one head. Fewer seams, fewer surprises.
- 03
Offline-first where it matters.
Some of our systems run where connectivity is a wish, not a guarantee. A Linux mini-PC on the local network, phones that sync locally, batches to the cloud when it comes back. We design for the bad day. The good day takes care of itself.
- 04
AI that has to be right.
When AI sits inside an ERP that moves $5M+ a week, "usually works" isn't a standard. Local models where they fit, retrieval shaped around real data, caching, mathematical validation. When agents write exam questions, other agents answer them blind before a student sees one. The model proposes. The system checks before anything reaches a customer.
- 05
Production over polish.
Clear failure modes, real monitoring, sane defaults, observable behaviour, and code someone can still read in three years. A beautiful repo that breaks in month six isn't a win. We optimise for what's still running in 2029.
- 06
Long horizons.
The systems we're proudest of are still shipping. Five years in, zero churn on the long-term restaurant work. We'd rather work with people who think on that timescale than build something meant to be torn out next quarter.