AI agents that do the admin, with a person in charge

An agent is AI that takes actions, not just answers. That’s useful, and it needs care. We build agents for repetitive admin between systems, with an approval step wherever money, customers or records are involved.

Good jobs for an agent

Price and catalogue updates

Apply a supplier’s price list across your website or shop, with a report of every change.

Supplier orders

Fill in and submit a supplier’s web order form from your system, once and only once.

Chasing paperwork

Notice what’s missing, ask for it and file it when it arrives.

Keeping systems in step

Compare two systems, fix what’s safe and explain the rest.

Month-end packs

Gather the figures, draft the commentary and leave it for review.

Not every job needs an agent

If the steps never change, ordinary automation is cheaper and more predictable. We’ll tell you which is which. See workflow automation

Example: a supplier price update

Before

  1. The supplier sends a spreadsheet
  2. Someone updates hundreds of pages over two days
  3. Mistakes go live

After

  1. The agent reads the spreadsheet and matches it to your products
  2. It proposes the changes with an audit report
  3. A person approves
    A person checks
  4. The agent applies them and refreshes the pages that depend on them
  5. The report is kept

Guard rails we build in

  • Only the tools it needs

    An agent gets the narrowest permissions that do the job.

  • Approval where it matters

    Money, customer messages and record changes wait for a person.

  • A budget and an off switch

    Every agent has a spending limit and can be stopped instantly.

  • Every action logged

    What it did, when, and what changed, before and after.

  • Practice first

    New agents run on copies of your data before they touch the real thing.

Illustration: plain boxes on a conveyor belt, with one set aside on a small white table and marked with a brass tag for checking.

Agents we’ve built

Price updates in three languages

For a client with a website in three languages, an AI agent applies the client’s price spreadsheets across every page and writes an audit report of each change.

A robot that places supplier orders

For a client, a robot fills in and submits a supplier’s web order form from the client’s own system, with a lock so an order can never be sent twice.

Our own coding agent

It works on one task at a time and must pass an acceptance test it isn’t allowed to edit.

You choose where the AI runs

Tier 1

A hosted model, through a UK or EU endpoint

The best quality for the least effort. Before any of your data goes to a provider, we check that its business terms rule out training on it, and we tell you which region does the processing.

Tier 2

Inside your own cloud account

The model runs in your AWS or Azure account, under your access controls and your logs.

Tier 3

A private model on hardware in the UK

Open-weight models on your hardware or ours. Nothing goes to an outside AI provider. Our own research and document reading run this way.

Storage location and processing location aren’t the same thing. We’ll tell you both, in writing.

Questions

What stops an agent going wrong?

Narrow permissions, approval steps, budgets, logs and testing on copies first. When a check fails or something doesn’t match what it expects, it’s built to stop and ask a person.

Who’s responsible for what it does?

You stay in charge of the decisions. We’re responsible for building it to the agreed rules and showing you the logs.

Can it work with old systems that have no API?

Often, yes. A robot can use a web screen the way a person would. We’ll tell you how fragile that is before you rely on it.

Get in touch

Tell us which admin you’d hand over first.

One paragraph is enough. We’ll reply with honest thoughts on whether we can help, and what it would cost.

All fields are required unless marked optional.

0 of 4,800 characters

We use your details only to reply. See our privacy policy.