Method
How we work.
Five principles that apply to every engagement, whatever the format. They are written here so that you can hold us to them.
01 · Principles
One contact, from scoping to production.
The person who scopes is the person who delivers. You speak directly with the person doing the work, and that person knows your file because they built it.
A short scoping phase before any commitment.
Two to three weeks to understand your system, your data and your constraints. The scoping sets the scope, the price, the acceptance criteria, and what we recommend not doing. Its terms depend on the engagement that follows, and its conclusions are yours, whether or not you continue with us.
Modern tools, under human control.
We practise AI-assisted engineering, like most technical teams today. What sets us apart is the written framework: which data may be processed by these tools and which never, where processing is hosted, who reviews and who signs off each delivery.
Security by construction.
Secrets never in plain text, neither in code nor in configuration files. Least privilege for every component, human or not. A log of architecture decisions. Review of dependencies and of the software supply chain. From day one, not at the end of the project.
Hand-over as a deliverable.
Documentation, training of your teams and hand-over planned from the scoping phase. The code, the access and the documentation belong to you. A good provider makes itself replaceable.
02 · AI in our work
The tools are not the point. The framework is.
Your data is never used to train any model. Before we start, we write with you the list of what may be processed by AI tools and what never will be, where processing is hosted, and who reviews and signs off each delivery. This framework is a deliverable of the scoping phase, and it stays with you.
Whatever tools produced a deliverable, it is reviewed, tested and signed off by a named human before it reaches you. It is the firm's simplest rule, and the most important.
03 · What you receive
At the end of an engagement, something remains.
The code and the access
In your repositories, under your identity, with the history.
The documentation
Architecture, decisions taken and rejected, operating procedures, AI usage framework.
Teams that know how to take over
Training and hand-over are planned from the scoping phase, not improvised at the end.
Describe your subject in a few lines.
You will hear back from the person who will do the work, not from a salesperson. If we are not the right fit for your subject, we will tell you and point you elsewhere.