FAQs
Questions, answered plainly.
How we work, what we need from you and how the technology behaves. Where a point depends on your situation, we say that it is agreed during scoping.
Getting started
Where should we start?
Take the AI assessment for an initial view of your opportunities and foundations. If you already have a specific challenge, contact us to discuss it.
What do I get from the assessment?
The assessment is free. You see two scores out of 10 and a recommended next move straight away, and we email you the full report. It takes about three and a half minutes.
What happens before an engagement begins?
We discuss your objectives and may request a diagnostic from your team. This helps us define the proposed scope before a paid engagement begins.
Can we commission the audit on its own?
Yes. You can review the findings and decide how to proceed.
Outcomes and measurement
How will we measure success?
We agree a baseline and success measures before implementation. Depending on the project, these may include quality, turnaround time, capacity, cost or reliability.
Can you tell us what results to expect?
The examples on our industry pages are results published by other organisations, shown as their sources report them. They are not our results and not a forecast. For your business, we estimate benefits from your own data and assumptions, and we agree how they will be measured before implementation.
How will our people be involved?
We work with process owners to redesign workflows, define responsibilities and prepare teams to use the system. We develop, integrate, test and deploy it alongside the people who will use it.
Data, systems and security
Can you work with our existing systems?
We assess the ERP, CRM, email, document storage and other tools involved in the workflow. We then define the integration options and access required.
Where will our data be processed?
We agree deployment, model access and data handling requirements during scoping. These decisions form part of the proposed architecture.
What data and access will you need?
We identify which systems and records the application needs and how access will be controlled. We agree this during scoping, and it forms part of the proposed architecture.
How are permissions, approvals and audit trails implemented?
Tools enforce read and write permissions, actions beyond agreed authority are held for an approver, and each action is recorded against the task. We define the specific controls with you for each application.
Working with us
Can you work with our existing engineering team?
Yes. We define with your team which components we build, which you own and how they connect. Responsibilities for each component are set out during scoping.
Can we commission an integration, model or evaluation engagement independently?
Yes. You can commission a defined component, such as an integration, a model or an evaluation harness, or a broader programme. The enquiry and the diagnostic help us scope the work before a paid engagement begins.
Who owns the code, model artefacts and training data?
Ownership and licensing are specified in the engagement for each project.
What documentation and handover are included?
Deliverables include operating documentation, and, where models are built, dataset documentation and lifecycle documentation. The handover arrangements are agreed as part of the engagement.
How are infrastructure and model usage costs handled?
We define compute, hosting and model usage requirements during scoping and measure latency, throughput and cost in operation. How those costs are contracted is agreed as part of the engagement.
What maintenance and support can be included?
We can monitor, maintain and support applications, models and integrations, including issue resolution. Support responsibilities are agreed as part of the engagement.
Who supports the system after launch?
We agree monitoring, maintenance and support responsibilities as part of the engagement.
Models, evaluation and reliability
How do you choose between existing models, fine-tuning and dedicated training?
We compare options against the task: quality on your own evaluation data, cost, latency, resource needs and deployment constraints. Dedicated training is considered where the objective, the available data and the compute justify it.
Where can the application and models run?
Cloud, private cloud, on-premises and edge environments are options, subject to project requirements. We agree the deployment approach during scoping and make the trade-offs explicit.
How do you evaluate performance before deployment?
We build evaluation datasets from representative cases, including exceptions, and test task completion, tool use and retrieval quality. We agree release criteria before deployment.
What happens when a model, tool or integration fails?
We design for failure: retries and timeouts within set limits, queued calls, validation of outputs, and escalation to a person with the task state attached. The recovery behaviour for each application is agreed during design.
By industry
Industrials & Manufacturing
Can it run on the line if connectivity is limited?
Edge and cloud inference are both options. Latency, connectivity and data-residency needs decide where models run, including on the line.
What if we have few recorded failures or defects?
Rare events limit what can be learned. We build evaluation sets that include them, report results by defect or failure class, and agree what is feasible before building.
Does it connect to our plant systems?
Results connect to systems such as MES, ERP, CMMS and quality systems, with identifiers that tie each result to a unit, asset and shift.
Consumer & Retail
How much sales history do we need?
Enough to see seasonality at SKU and location level, with a record of when items were out of stock. Short history, volatile demand and unrecorded promotions limit accuracy, and there are methods for new products with limited history.
Will forecasts replace our planners?
No. Planners own the plan and approve purchase quantities, and overrides are recorded with a reason.
Can you work across several channels and marketplaces?
Profitability work reconciles orders, payments, returns and costs across channels using entity resolution. Gaps in channel data limit coverage.
Logistics & Supply Chain
Do we need carrier APIs?
Status can come from carrier APIs or data feeds, or from an agreed way of receiving it. Event-driven integration keeps tasks and records consistent when systems are slow or unavailable.
How accurate are arrival predictions?
We measure predictions against actual arrivals by lane and track them over time. Disruptions can break historical patterns, so estimates need buffers and frequent refresh. We do not promise a figure in advance.
Who stays responsible for customs filings?
Customs responsibilities stay with the licensed party. The system checks entries and routes mismatches to a reviewer.
Investment Firms
How is confidential deal data protected?
Data rooms and investment records can require private or on-premises deployment, with scoped access per deal and team. Information barriers and deal confidentiality are enforced in search and in agent tool access. We establish these controls during scoping.
Does the AI make investment decisions?
What the AI does is established based on the agreed scope. It can do research, qualification and first-pass filtering. We encourage human involvement, and the final say rests with your team.
Does this work for venture capital, private equity and hedge funds?
Yes. Each priority application on our Investment Firms page describes how it applies to each fund type.
Next step
What could AI mean for your business?
Take our free Enterprise AI Adoption Assessment to explore where AI could make a difference. Get two scores, a recommended next move and a full report by email in about three and a half minutes.