FAQ

That's what we recommend. The diagnostic has a fixed price, takes days, and delivers a document with what can and cannot be done and how much it costs. If we continue, it is deducted.

The diagnostic, days. An automated process, one or two weeks. A model, between four and six, though in the first week you already know whether the data is sufficient.

Little, but not zero. A few hours at the beginning to provide access and explain how the business really works, and a short weekly review. For automation, someone who validates outputs during development. That cannot be delegated: it is what ensures the system aligns with your judgement.

Yes, on the terms your IT team sets. Read-only, the minimum necessary, within your environment and agreed in writing before we start. No access is needed for the initial call.

The process is designed to find out early. If the diagnostic concludes it is not viable, there is no project. If it is built and does not reach the agreed level, it is not deployed and not billed as if it were. That level is defined at the start and with your team.

Everything developed for your project remains yours when it is finished: the code, the systems, and the documentation. No licences or permissions involved. You can continue with us, another provider, or your own team.

No. Everything runs within your environment and your data does not leave it. When a project needs an external language model, the provider and configuration are chosen so that data is not retained or used for training, and this is agreed in writing.

Yes, and that is the norm. Infrastructure costs are yours from day one. We estimate them in the diagnostic so they do not appear as a surprise.

You are left with everything running, with the code and documentation, and your team can operate it. What does not resolve itself is the passage of time: systems age and processes change. That is why the proposal includes the monitoring option from the start, with its scope and price.