Digital employee
Takes over an operational process, from incoming request to closed case.
Lead time
Four to eight weeks
Pricing model
A one-off implementation fee. Where the process lends itself to it you then pay per completed process; otherwise we agree a fixed price for the solution.
What it is
An AI colleague that takes over one operational process, from the incoming request to the closed case. It reads what comes in, works out what is missing, carries out the routine steps in the systems the process touches, and closes the case.
What it replaces
The chasing, retyping and filing, and the routine decisions that come with it: who is responsible, which supplier, what the limit is. What it does not take over is the customer relationship.
How it works
A request comes in, by email, through a portal or from a ticketing system. The digital employee reads it and works out what is needed. It gathers what is missing and, where appropriate, asks the requester directly. It carries out the routine steps in the systems the process touches, closes the case and records the result. Cases that call for judgement it also handles, within the rules and limits agreed with the client. What goes to a person is what genuinely cannot be done without one, such as a phone call or a case outside the agreed limits, and it arrives with everything already gathered. Every action is logged, whether carried out by the digital employee or by a person.
What is included
Build, integration, hosting, monitoring, optimisation and support. Documentation and training at handover. Underneath sits the foundation: the process mapped, the data prepared, the architecture set up. On a first project that is a large part of the work, and it is what makes a second digital employee faster. Where the scope calls for its own discovery, that is quoted separately and comes first.
What is not included
Changes to the client’s own systems or to the connections we depend on. Cleaning up existing data. A second process, because that is a new project.
Who it is for
An organisation with a process that runs a few hundred times a year in the same way. The cases do not have to be identical: the digital employee runs on an AI model and copes with variation in how requests arrive and what they contain.
Just as often the trigger is not cost but capacity. The work is there, the demand is there, and there are no people to be found to pick it up. Then it is not about cutting something but about handling more without waiting on a hire.
