Questions before you hire us

With an email describing the problem. We reply with the questions we need answered, then send a written scope: what we will do, what we need from you, what we will hand over and how it will be checked. Work starts when you accept that scope in writing.

No. Describe the symptom, such as pages missing from search, a slow checkout or a process that takes too many hands. We place it on the depth scale and tell you which line it belongs to, or that it belongs to none of them.

Yes, when the problem runs through more than one layer. A slow site can be a front end issue at 14 and a database issue at 20. We scope each depth as its own item so you can approve them separately.

Yes. Most of the work is written and asynchronous: tickets, pull requests and reports. For calls we agree a fixed overlap window with your team at the start. Every document, code comment, ticket and call is in English.

You own all of it. Repositories, cloud and tool accounts are created in your name, and every document we write is handed over in a format you can edit. Our access is granted by you and can be withdrawn by you.

Each person gets their own named account with the least access the work needs, never a shared login. Secrets are kept in a password manager or secrets store, not in email or chat. At the end of the work we list every access we held so you can remove it, and we confirm in writing once it is gone.

Yes. We sign a reasonable mutual or one way non-disclosure agreement before you share anything confidential, and we can send our own if you do not have one.

Only with your written agreement, and only tools whose terms exclude training on your inputs. The tools are named in the scope. Every AI assisted change goes through the same human review as any other change before it is merged.

We are, for the system we built, and it is designed for that case. Answers carry their sources, uncertain cases go to a person, and an evaluation set catches regressions before release. When a wrong answer reaches a user, we log it, add it to the evaluation set and fix the cause, and the change record shows what was done.