Contact
Tell us about your system.
Most useful for a first conversation: what you run today, what costs you time, and what you’d rather stop doing by hand.
Write to us in a few lines. We will tell you plainly whether your need fits the studio’s scope.
First contact by email, without a form or additional data collection.
Frequently asked
What people ask before we start.
If your question isn’t here, write to us — the answer is usually short.
Do you work alongside in-house engineering teams?
Yes, that is the most common case. We take on either a scope your team has no time for, or a skill it does not yet have. The code is written to be picked up by your developers, not to make us indispensable.
How does the first stage work?
Through a conversation where you describe what you run today and what costs you time. We turn that into a written framing document. You can stop there and keep it: it is yours.
What happens if we want to stop?
You keep the repository, the documentation and the credentials. We document the exact state of the system on the day we stop, including what is unfinished, so that someone else can pick it up.
Do you host what you build?
We deploy onto your infrastructure or onto platforms you control. Your data stays with you, and the accounts are in your name.
Will you take over a project someone else started?
Yes, provided we can read the code first and say honestly what it is worth. We do not take on a system blind, and we do not promise to rescue what needs rewriting.