CUSTOM AI AGENT · START HERE
Turn incoming enquiries, documents or routine checks into organised work your team can review. We scope and build one pilot around your approved systems, with clear permissions and a person checking the important steps.
Tell us the task and the tools you use. We reply within one working day.
01 · SAMPLE INPUT
“We need a document assistant for 12 people. Our files are in SharePoint. Can we discuss access?”
02 · PROPOSED OUTPUT
Thanks for outlining the task. Which document collection would you start with, and who owns its permissions?
03 · HUMAN REVIEW
A team member checks the original enquiry and draft before sending. Nothing is sent automatically in this example.
Evaluate: time to prepare and review, factual corrections, missed details and handling of an incomplete enquiry. Agree pass criteria before building.
Synthetic input and proposed output. This is a mockup, not a live agent or a customer result.
WORKFLOWS WE COULD SCOPE
These are proposed workflows, not completed customer results. Where ordinary rules or automation are sufficient, we use those rather than an AI model for every step.
Measure: preparation time, corrections needed, missed cases and review effort against the current process.
Discuss enquiry preparation ↗Measure: preparation time, corrections needed, missed cases and review effort against the current process.
Explore file preparation ↗Measure: preparation time, corrections needed, missed cases and review effort against the current process.
Explore rota checking ↗YOUR FIRST PILOT
An agent uses AI and connected tools to carry out agreed steps. Start with one workflow, with its limits defined during scoping.
Name the workflow owner, approved sources, intended outputs and human review responsibilities. Specify the number of sources, integrations and test cases in the proposal.
Test representative work, missing information and exceptions against agreed criteria. Compare preparation time, corrections, missed cases and the effort still needed from your team.
Review the outputs and test results together. Document operation, known limits, review steps and the agreed support arrangements so your team knows how to use the pilot.
Use the evidence to decide whether to refine, expand or stop. Wider production rollout and additional integrations need their own agreed scope and price.
Allow six to eight weeks from agreement of the workflow as an indicative first-pilot schedule: scope and access, build and test, then review and handover. Timely system access, representative examples and feedback from the workflow owner affect the schedule.
We use your details to reply to this enquiry. Scope, responsibilities and price are agreed in writing before any work begins.
A senior consultant will reply within one working day.
YOUR ENQUIRY
You don’t need a technical brief. A few sentences about your tools, your team or the task that takes too long is enough to begin.
BEFORE ANY WORK BEGINS
We quote for the agreed pilot. Additional integrations and data preparation are scoped separately.
The proposal sets out deliverables, responsibilities and timing. Hosting, software subscriptions, model usage and ongoing support are set out separately. Confirm discovery scope and any fee before commissioning it. VAT applies where applicable and is confirmed in your quote.
A chatbot mainly responds in a conversation. An agent can also work through a defined sequence of tasks using connected tools. Some agents include a chat interface, but the workflow determines what is useful.
Often, yes. We check the available integrations, permissions and commercial terms before agreeing the scope. Where a connection is unsuitable, we explain the alternatives.
Only where that action is included in the agreed design and permissions. A first pilot can prepare work for a person to review before anything is sent or changed.
We review the evidence together. You can choose to refine the workflow, expand its use or stop. Ongoing support and any software or model usage costs are agreed separately.
We quote for the defined workflow after reviewing its systems, data preparation and testing needs. Ask us for an investment estimate for your task; the written proposal sets out the scope and price before work begins.
Start with the task, the tools you use, a workflow owner and representative examples. We agree the access needed for the pilot and how examples will be shared securely. Please do not send credentials or confidential documents in the enquiry form.
We check existing features and ordinary automation during scoping. A custom agent may not be needed if your current tools can do the job adequately.
Ownership, licences, account control and access to code and configuration must be specified in the written agreement. These depend on the selected tools and any third-party components; confirm them before commissioning the build.
Hosting, software licences, model usage and support can carry ongoing charges. The proposal sets these out separately from implementation, including who operates the workflow and what maintenance is included.
We review the test results and limitations with you before deciding whether to refine, expand or stop. Any included rework, further paid work and cancellation terms must be set out in the project agreement; a pilot is not a promise of production readiness.
