AI agents just got cheaper: what £45 a month buys

A year ago, building a simple AI agent for a small business meant a day or two of an engineer’s time, and the price reflected that. This year the same job takes hours. The tools have got better, the platforms inside Microsoft 365 have matured, and a lot of the fiddly plumbing has disappeared.

So we had a choice: keep charging last year’s price for less work, or cut the price. We cut the price. Here is what that looks like in practice.

The prices, plainly

Each automation or AI agent we build is priced per solution, as a monthly fee. That fee includes the design, the build, testing, documentation, and then maintenance, monitoring and support for as long as you use it. There are three sizes:

  • Small, £45 per month. Up to half a day to build. Simple automations and AI agents: accounts mailbox monitoring and triage, simple email or data triggers, straightforward Power Automate flows.
  • Medium, £75 per month. Up to a day to build. Multi-step workflows and AI agents that connect two or more systems, automated reporting and dashboards, document generation.
  • Large, £125 per month. Up to two days to build. Complex multi-system workflows, bespoke AI agents, end-to-end process automation and Azure-based solutions.

Anything bigger than two days is quoted separately, though most useful automation rarely needs more. Everything is built inside your own Microsoft 365 or Azure, and you own what we build. Microsoft licensing, Azure usage and any third-party costs are yours, and we tell you what they will be before we start. Each solution has a 12-month minimum term, then runs on a 90-day rolling basis. That is the one exception to our usual no-long-term-contract approach, so we would rather say it up front.

What £45 a month actually does

The example we use most is the accounts mailbox, because almost every business has one and almost every business hates it.

Picture a shared inbox that receives supplier invoices, remittance advices, statement queries, the odd complaint and a steady stream of things that should have gone to sales. Someone in the finance team opens it every morning and spends the first hour sorting: which ones are invoices, which have a purchase order number, which need a reply, which are junk. A Small build handles that hour. An agent reads each email as it arrives, works out what it is, files it, pulls out the key details, flags anything unusual and drafts the routine replies for a person to check. The person still decides. They just do not do the sorting.

Other jobs that sit comfortably in Small: sending a reminder when a form has not been completed, dropping a new enquiry into a spreadsheet or your CRM, or watching a folder and renaming and filing whatever lands in it.

When Medium and Large make sense

Medium is where two systems need to talk to each other. A new client is won in the CRM, and the agent creates the project folder, the onboarding checklist and the welcome document, then tells the right people. Or your monthly report pulls figures from three places and lands in Teams on the first of the month, formatted and ready, instead of half a day late.

Large is for whole processes: an approval chain that runs from request to sign-off with the right people nudged at the right time, or a bespoke agent that works across your finance, project and email systems. These are rarer than people expect. Most of the value in a small business sits in Small and Medium builds, which is one of the reasons the pricing has come down.

What this means for a business with 5 to 50 people

At £45 a month, an automation pays for itself if it saves about an hour a week. Most of the ones we build save more than that, because the tasks they replace are the repetitive ones nobody enjoys, done every day rather than every week. The point is not to replace anyone. It is to give a small team the admin capacity of a bigger one without adding headcount.

Two honest caveats. First, automation does not fix a messy process; it just runs the mess faster, so sometimes the right answer is to tidy the process and skip the build. Second, an agent that reads your emails needs sensible permissions and a clear policy behind it, which is why we ask about your Microsoft 365 setup before we build anything. Our AI and automation page has the full detail on how the three steps fit together.

Where to start

Not with a build. Start with a conversation about where your team actually loses time. Every business is different, and the thing that is worth automating is usually not the thing the owner first thinks of.

That is what our free Automation Discovery call is for. It takes 60 to 90 minutes, it is done remotely, and you come away with a short list of things worth looking at in more detail, each with an honest view of whether it is a Small, a Medium or not worth doing at all. You do not need to be an ISS support customer. Book your free Discovery call and we will find your hour.

Scroll to Top