We started this because we kept being the team that inherited the mess.
We build and operate critical infrastructure for organisations that cannot afford to get it wrong — and the AI systems that increasingly run on top of it.
The experience we are reacting to.
You have probably lived this. The partners come to the pitch. A different team turns up on day one. Six months later there is a platform nobody internally understands, a documentation folder written in the last fortnight, and a renewal conversation you cannot really say no to.
None of that is anyone being dishonest. It is what happens when a firm is structured so that selling and delivering are different jobs done by different people, and when the commercial model quietly rewards you not being able to leave.
So we structured against it. The engineer who scopes your work delivers it. Everything ships as code into your repository as we go, not in a tidy-up at the end. And we take no commission from any vendor — which is the only reason we are able to tell you that the right answer is to change nothing, on the occasions when it is.
The name comes from Kano, a trading city that has spent about a thousand years making systems from different places work together. It seemed like a reasonable standard to aim at.
What the four commitments actually cost us.
Senior engineers on the tools
No pyramid staffing. The people in the pitch are the people in the pull requests.
Vendor-neutral, always
We do not resell what we recommend — and we keep AI systems model-neutral for the same reason.
Handover is the deliverable
Code, runbooks, recorded knowledge transfer. If we vanished, you would be fine. That is the test.
We say the uncomfortable thing
Some estates should not migrate. Some AI projects should not start. Saying so costs us work and earns the relationship.
Work with us.
Whether you're hiring us or joining us, the conversation starts the same way.