← Back

Frequently asked questions

How much does this cost?
Every business runs differently, so we scope after the audit rather than publishing a number that would be wrong for most readers. The audit itself is a fixed price agreed before it starts, and it is credited against a build if you go ahead.
How long does a build take?
A first working system is usually weeks rather than months, because we deliberately start with one narrow job rather than everything at once. The audit gives you a timeline for your specific case before you commit.
Do you replace our staff?
No. These systems take the repetitive first pass: the same eight questions, the copying between two tools, the enquiry that arrives at midnight. Your people get the work that actually needs judgement.
What happens to our data?
It stays in your systems. Retrieval runs against your own documents, and where possible embeddings are computed locally rather than sent to a third party. Anything we touch during an engagement is covered by the written agreement for it.
What if the AI gets something wrong?
It will, occasionally, which is why nothing that changes state runs unattended by default. Actions that send, book or write are proposed and wait for a person. We also build evaluation suites so a change in behaviour is caught before your customers meet it.
Will it work with the tools we already use?
That is the point. We connect to your CRM, calendar, inbox and databases rather than asking you to move. If something genuinely cannot be integrated, the audit finds that out before you have spent money on a build.
What do we need to have ready?
Someone who knows how the process works today, access to the tools it touches, and any documents the system should answer from. That is enough to start the audit.
What if we want to stop?
The audit is standalone and the findings are yours whether or not you continue. Builds are handed over with documentation and the runbook, so you are not locked to us to keep it running.