Common questions
Questions enterprises ask before they engage.
Straight answers on scope, cost, timeline, data security, and what you get at the end. If something is missing, email us at hello@cadanti.ai.
01
What does the free audit actually involve?
- The audit is 3–5 working days of structured discovery inside your operation. We conduct interviews with the process owners and adjacent teams, observe the workflows in motion, and examine the data your systems produce. You don't need to prepare a slide deck or a requirements document — we bring the diagnostic framework. At the end you receive a ranked list of automation targets, each with an estimated complexity score and a rationale for prioritisation. That document is yours regardless of whether you proceed with a pilot.
02
How long does an engagement take?
- The free process audit runs 3–5 working days. A scoped pilot that follows typically runs 4–8 weeks, depending on the complexity of the target process and the availability of your team for review cycles. We agree the timeline and milestones in the scope of work before any paid work begins, so there are no surprises. If your internal procurement or legal review adds lead time, we account for that in the schedule.
03
What do I need to provide?
- Access to the right people is the primary input — the team members who run the process day-to-day and the colleagues who handle the exceptions. We will also need read-only access to the relevant data sources and systems involved in the target workflow. We do not require you to migrate data, spin up new infrastructure, or prepare documentation in advance. The audit is designed to surface what is there, not to validate a pre-written brief.
04
What if it doesn't work?
- Our pilots have defined success metrics agreed in writing before work begins. If the agent we deploy does not meet those metrics at the end of the pilot period, we continue working the problem until it does — at no additional cost — or we refund the pilot fee. We are also honest during the audit phase: if a process is not a good automation candidate because the data is too noisy, the decision logic is too ambiguous, or the volume does not justify the build cost, we will tell you that before quoting a pilot, not after spending your budget.
05
How is this different from hiring consultants?
- Traditional consulting engagements typically produce recommendations — slide decks and frameworks that require a separate implementation effort. We produce working software: deployed AI agents running in your environment by the end of the engagement. The billing model is also different. We use fixed-price pilots rather than time-and-materials billing, which means we share the delivery risk. And because you own the agent code outright at handover, there is no ongoing licence fee or vendor dependency built into the output.
06
What processes are best suited for AI agents?
- The highest-return candidates share a few characteristics: high volume, repetitive decision logic, clear inputs and outputs, and meaningful cost or time attached to the current manual effort. Typical examples include invoice and billing exception handling, data extraction and routing from unstructured documents, cross-system reconciliation, quote and order processing, and operational dispatch workflows. Processes where the rules change frequently or where expert judgement is the primary value are generally weaker candidates — we flag those during the audit.
07
What does a pilot cost?
- Pilot pricing is set after the audit, once we understand exactly what we are building and what the integration surface looks like. We quote a fixed price before any paid work begins — not a range, a number. Pilot engagements typically start in the mid-five-figures for a well-scoped single process. The audit that precedes it is free. We do not charge time-and-materials rates at any stage of the engagement.
08
Do we need to change our existing systems?
- In most cases, no. The agents we build integrate with your existing systems via their available APIs, webhooks, or data exports. We work with what is there — ERP platforms, CRMs, ticketing systems, document stores — rather than requiring a migration or a platform purchase. Where a system genuinely lacks an integration point, we surface that during the audit as a constraint on automation scope, not as a surprise mid-pilot.
09
How do you handle data security and confidentiality?
- We sign a mutual NDA before the audit begins. The data we access during discovery is used solely to scope the engagement and is not retained beyond that phase. For pilot deployments, the agent runs inside your environment — your cloud account or your on-premise infrastructure — so your data does not transit our systems. We can work within your information security review process and will provide documentation or questionnaire responses as required by your team.
10
What happens after the pilot?
- At handover you receive the deployed agent, full source code, and operational documentation — runbooks, monitoring guidance, and a description of the architecture. If you want us to maintain and extend the system, we can discuss a retainer arrangement. If you want to hand it to your internal engineering team, we provide a structured transition. There is no lock-in: the code is yours, and it runs on infrastructure you control.
Ready to start?
The audit answers the rest of the questions.
Most of the detail that matters — whether your process is a strong candidate, what the integration looks like, what the realistic timeline is — only becomes clear once we have looked at your actual operation. The free audit is designed to answer all of that without any cost or commitment on your side.
Book a free audit →