Written correspondence,
read by a human.
We prefer to begin new conversations in writing. It lets us understand the situation carefully before responding, and it gives both sides a record to come back to.
The address above is the primary channel for all inquiries. Please write in English.
To let us respond usefully on the first exchange, please share the following in your initial email:
- 01Your name and the organisation you are writing on behalf of.
- 02A short description of the problem, product or system you have in mind.
- 03The current situation — an existing codebase, an idea on paper, a live system, or something else.
- 04The outcome that would qualify the work as a success.
- 05Any constraints that already apply — budget range, deadlines, regulatory context, existing technology choices.
- 06How you prefer us to reply, and any window of time in which you expect an answer.
The kinds of message we receive most often.
An organisation with a defined problem looking for an engineering team to design and build a solution.
A production system that needs stabilisation, modernisation or ongoing maintenance.
A request for an independent review of an architecture, codebase or technology decision.
An in-house team looking for engineers to work alongside them for a defined period.
A discussion about a decision that has not yet been made, without commitment on either side.
Questions about our practice, our services or how we work in a specific context.
What happens after you write to us.
- 01Acknowledgement
We confirm that we have received your message and let you know when a detailed answer can be expected.
- 02Clarification
Where useful, we reply in writing with a small number of specific questions to make sure we understand the situation.
- 03First conversation
Once the written picture is clear, we schedule a first conversation, usually a short call, to talk through the work.
- 04Written proposal
If the fit seems right, we prepare a short written proposal describing the first phase, its scope and its terms.
Frequently asked questions about getting in touch.
Q · 01Do you take on smaller engagements or only long-term projects?↳
Both. A short, well-defined engagement — a review, a prototype, a stabilisation exercise — is often the best way to begin working together and to see whether a longer collaboration makes sense.
Q · 02How quickly do you respond to new inquiries?↳
We aim to acknowledge new correspondence within a few working days. A more detailed response follows once we have understood the request.
Q · 03In what language should I write?↳
English is the working language of our correspondence and documentation.
Q · 04Will my message be treated confidentially?↳
Yes. We treat everything shared in an initial inquiry as confidential and only use it internally to evaluate whether we can help.