ASKED FIRST.

Frequently asked questions

• 01 How do you price a project?

  We do not quote before the scope is clear. First comes a short discovery — a few conversations and a scope document; then a written, itemised quote. If you decide at the end of discovery not to build it with us, the scope document is still yours.

• 02 How long does a project take?

  It depends on scope; there is no single honest answer. We give the schedule at the end of discovery and work in two-week cycles — you try a working build at the end of each one, so whether the schedule holds becomes visible along the way rather than at the end.

• 03 Who owns the source code?

  You do. Source code, servers and store accounts are opened in your name and stay there. At handover you get the repository, the setup steps and the documentation; if another team takes over later, nothing is in their way.

• 04 Is there maintenance and support after handover?

  Yes, under a separate agreement. If you choose not to take it, the system keeps running — we do not leave a lock behind. Setup and update steps are documented at handover so your own team can run it.

• 05 Will you take over an existing project?

  Yes. We read the code first and put what we found in writing: risks, technical debt and a priority order. After that assessment we decide together whether taking it over makes sense — sometimes the right answer is not to, and we say so.

• 06 Fixed price or time based?

  Fixed price where the scope is clear. Where scope takes shape along the way — research, taking over an existing system, AI experiments — time based is the more honest arrangement: a fixed price there either overcharges you or corners us.

• 07 Do you take small jobs?

  We do, if the calendar allows. Because we cap the number of projects rather than growing the team, there may be a queue; we say so up front rather than claiming availability we do not have.

• 08 Will you sign an NDA?

  Yes, before the first conversation if you like. If you have your own template we work from it; otherwise we propose a standard one. We never use a client's name on this site or in references without permission.

• 09 Where does our data go in an AI project?

  We decide together, up front, which data may leave the building. Where company data must not leave, we use local models or an on-premise install. When a model provider is used, what is sent to which endpoint is written down.

• 10 Do you work remotely?

  Mostly. We come on site for the steps where being there speeds things up, such as discovery and handover. Working remotely does not put anyone between you and the person doing the work — there is no account manager in the middle.