FAQs
- Home
- FAQs
FAQ
The questions we get asked first
How do you decide whether a use case is worth building?
We score every candidate on four axes: the quality and accessibility of the data, the cost of a wrong answer, how measurably the outcome can be tracked, and whether a person can realistically review the output. Anything that fails on data readiness goes back to the data roadmap before a model is trained — we would rather tell you that in week two than in month six.
Do our teams need technical backgrounds to use what you build?
No. Every system ships with an interface designed around the role that uses it, and our enablement programmes are written for analysts, operators and managers rather than engineers. Deeper technical tracks are available for the people who want them, but they are never a prerequisite for using what we build.
How do you handle data security and regulatory compliance?
We work inside your environment by default — your cloud tenancy, your identity provider, your retention rules. Your data does not leave the perimeter you control, and we do not train shared models on it. Every engagement includes a data flow map, a model card and an audit trail of inputs, outputs and human overrides. We have delivered under GDPR, HIPAA and financial services supervision.
How long before we see something working?
A readiness review takes two weeks and ends with a scored shortlist. A first production-grade system typically runs eight to sixteen weeks, depending on data access and how much integration is involved. Enablement runs alongside delivery rather than after it, so your team is ready on the day it goes live rather than three months later.