No moonshots. Here is exactly how it works.

One conversation, one pilot, one decision based on real numbers. This page tells you everything including the prices.

Step one: the conversation

Free, about an hour, on a call or in person, in plain English. We ask where the hours go, what the team dreads, and what tools you already pay for. By the end we will have named the one workflow worth fixing first, and we will tell you honestly if AI is not the answer. Roughly one in three of these conversations ends with us recommending something cheaper than hiring us.

Step two: the pilot

A pilot is one workflow automated end to end, built in weeks and run alongside the way you work today so nothing breaks while we prove it. A typical pilot looks like:

  • Week 1: we get read access to the systems involved and map the workflow as it really happens, not as the manual says it happens
  • Weeks 2 to 3: we build, and you see working versions early and often rather than a big reveal at the end
  • Week 4: the pilot runs in parallel with your current process while we measure it

Most pilots land between £3,000 and £8,000 depending on how many systems are involved, agreed as a fixed price before we start. No day rates, no meter running.

Step three: roll out what pays

At the end of the pilot you get the numbers: hours saved, errors removed, and what it costs to run each month. If it earns its keep, we extend it. If it does not, you stop, and you keep everything we built. Ongoing support and further workflows are priced the same way: fixed, agreed up front, and justified by the numbers from the last one.

Then, staying on

Most clients keep us on a monthly retainer after roll out, because an automation is not a kitchen fitting: it needs monitoring, backups, and someone who notices when a third party API changes underneath it. The retainer covers running what we built, fixing what wobbles, and a steady stream of improvements from people who already know your systems. Like the pilot, it is a fixed monthly figure agreed in the terms sheet.

Where it runs

Deliverables can be deployed to your own environment, to infrastructure we manage, or to a provider of your choice. Where we host and manage the environment, the running costs, monitoring and backups are an additional monthly cost, set out in the terms sheet, so there are no surprises on either side.

What you will not get: a two-year transformation roadmap, a strategy deck about strategy, or a chatbot bolted on for the sake of it. One workflow, working, measured. Then the next one.

Book the conversation →