How it works
Assess the role
Build the system
Effective automation starts with the process. We define the system’s responsibilities, test against your operating requirements and run the agreed scope for a year.
From the first question to working software
Each stage leaves something you can inspect. The aim is a replacement that fits the role’s real workload, with responsibilities and limits understood before it goes live.
Assess the whole role
We start with what actually happens: incoming work, routine steps, volumes, tools and the decisions people make along the way. We look at the exceptions as carefully as the repeatable tasks. A role is eligible only when the proposed replacement has a clear, testable boundary.
What you leave withA role map, an agreed scope and a decision on whether to proceed.
Define and build
The proposal identifies the workflows we will replace, the systems involved and the usage allowance. We build around the tools you already use where practical, with clear permissions and a named route back to your team when a request needs judgment.
What you leave withA working solution, agreed escalation rules and a written delivery scope.
Test before acceptance
Together, we test representative requests, incomplete information, unusual cases and service failures. Your team checks the output against the acceptance criteria in the proposal. Production acceptance follows those agreed checks; a demonstration alone is not the handover.
What you leave withRecorded test results, operating instructions and a clear production decision.
Operate for 12 months
From production acceptance, the first-year fee covers hosting, AI usage and maintenance within the agreed workflows and usage allowance. The proposal sets the support commitment. Your team remains responsible for approvals and exceptions beyond the automation’s authority.
What you leave withA defined year of operation, with maintenance and change boundaries in writing.
Renew or take it forward
Before the included year ends, you can choose a separately quoted renewal or a documented handover. The agreement sets out ownership, third-party licences and the access your team needs. Renewal is optional and never automatic.
What you leave withA deliberate next step, with the information needed to operate or transition the solution.
Bring the work into view
You do not need a technical specification to start. A practical account of the role helps us ask useful questions and decide whether an assessment is worthwhile.
Useful at the first conversation
- The routine tasks and how often they arrive.
- The tools, documents and systems involved.
- Examples of decisions that need a person.
- The outcome you expect and how you judge it.
Keep sensitive detail for later
The public enquiry form needs only a general description. Leave out employee records, customer data, passwords and confidential documents. Any later access or data-sharing arrangement is agreed before implementation.
Read our security approachThe next step
Start with one eligible role
Tell us what the work involves. We’ll assess the fit before proposing a replacement.