All services

    02 · Agent Deployments

    AI agents that handle the steps your team repeats

    We build and test AI agents that take on repeated steps in your workflows, in the systems you already use, with a person approving their work.

    • Claude
    • OpenAI
    • Outlook
    • HubSpot
    • Xero
    • WhatsApp

    See one run

    An agent at work

    Type a task and the agent works through the steps in the tools your team already uses, then stops for a named person to approve the result.

    • Tested with your team before wider use
    • A named person signs off each result
    • Every action recorded
    Task
    Reformat Labs · Agent run#2,318
    AgentWaiting for a task
    Idle
      Waiting for sign-off

      Example · every action recorded

      Agents we have built

      Agents built for client tasks

      Each tab is an agent we built for a client, shown as it runs. Sample records based on each project.

      Allbright Law · Contract review against the firm’s playbook

      The agent checks incoming contracts against the firm's own playbook, flags deviations with a risk rating and writes a structured summary. A fee-earner validates it before anything goes to the client.

      11 minaverage first-pass review, down from 72

      Overview

      What Agent Deployments means in practice

      You get an agent doing one repeated task, measured against how it runs today.

      An agent is software that reads what comes in, decides what to do with it within the rules we agree, and does it. We agree what it can access, which actions a named person approves and how unusual cases reach that person, then test it on your own records before wider use. We choose the model for each task on performance, cost and data handling. Where ordinary rules-based automation would do the job, we say so.

      What you receive

      1. 01
        A tested workflow in use

        An agent carrying out an agreed workflow after testing, starting with a pilot.

      2. 02
        Measured results

        Time spent, error rates and volume handled, compared with the baseline recorded before the pilot.

      3. 03
        Monitoring and logs

        Dashboards, alerts and audit logs that record the agent's actions and decisions.

      4. 04
        Handover

        The code, documentation and operating knowledge, so your team can run and change the agent.

      Each agent works within agreed limits and approval points. A written proposal sets out the pilot, its price and the timeline before work starts.

      Talk to us

      Built for daily use

      Monitoring, error handling and the route to a person go into each agent from the start.

      Connected to your systems

      Agents read from and write to your existing tools through their application programming interfaces (APIs), so they work on your real records.

      A person approves the work

      Each agent has agreed points where a named person reviews or approves its work. The agent handles routine cases and sends unusual ones to that person.

      After the pilot

      Results measured against the baseline

      Before the pilot we record how the task works today. The pilot review compares the agent with that baseline and recommends whether to continue.

      Example document. Names and figures are illustrative.

      How it works

      How we deliver Agent Deployments

      Step 1 of 4

      Choose the workflow

      We choose a workflow with you and map its inputs, outputs and unusual cases.

      Questions

      Questions about Agent Deployments

      What is an AI agent?

      Software that uses a language model to carry out agreed steps, such as reading documents, searching records, drafting messages or updating a system. We limit what it can access and which actions need a person's approval. Its output still needs checking, especially on customer or financial records.

      How long does a deployment take?

      It depends on how many systems the agent connects to and how complex its decisions are. You get an estimated timeline, with its assumptions, before work starts.

      How are security and data protection handled?

      Each agent gets access controls, audit logging and data handling rules, and where needed runs on your own servers or a private cloud. We agree the rules that apply with you, including UK GDPR and any sector requirements, and the checks before anything goes live.

      Which platforms and models do you use?

      We choose the model for each task, for example Claude (Anthropic), OpenAI models, Google Gemini or open-source models, on accuracy, cost, speed and privacy needs.

      How do agents connect to our systems?

      Through APIs, webhooks and direct database connections, depending on what each system supports. The connection work is planned and priced before the build starts.

      Who looks after the agent once it is live?

      We can monitor and improve it through Managed Services, including model updates. Or we hand it over with documentation and training so your team runs it.

      What does an agent cost to build and run?

      The build price is set out in the proposal. Running costs, mainly model usage and hosting, depend on volume, and we estimate the cost per task before you commit.

      What happens when an agent gets something wrong?

      We test each agent on agreed examples before it goes live. In use, unusual or uncertain cases go to a named person, and agreed actions need their approval. These checks reduce errors but do not remove them, so we review the output regularly and fix the rule when we find a mistake.

      Talk to us

      Which task does your team repeat most?

      Bring one task your team repeats every day and how it runs now. We will tell you if an agent suits it, or if ordinary automation would do the job.