Three enquiries landed in my inbox last month asking the same question in different words: “can you build us a custom AI agent?” In two of those three cases the honest answer was no, you should buy one, and I told them so. The third was a genuinely good fit for a build. This post is the reasoning I walked all three through, written down so you can run it on your own business before you spend anything.
If you are still working out what an AI agent even is, start with the plain English explainer on AI agents for small businesses and come back. This piece assumes you already know you want one and are deciding how to get it.
The three routes, honestly described
When a small business wants an AI agent in 2026, there are three ways to get one. The marketing around all three is muddled, so here is what each actually means.
| Route | What it really is | Typical UK cost | Best for |
|---|---|---|---|
| Buy | An off-the-shelf SaaS tool with agent features for one workflow | £15 to £60 per user per month | Common workflows: email, scheduling, basic support |
| Build | Software written for your specific workflow, calling an AI model under the hood | £3,000 to £20,000+ to build, plus running costs | Workflows unique to your business or your data |
| Hire | ”AI agents as a service”: an agency runs agents for you | £300 to £2,000+ per month | Businesses that want outcomes and no involvement |
Two warnings before we go further.
First, most products advertising themselves as “custom AI agents for SMBs” are route one wearing route two’s clothes. You are configuring someone else’s product, not getting custom software. That is fine, and often the right choice, but you should know which one you are paying for.
Second, “hire an AI agent” is the route with the widest quality range. Some providers are excellent. Many are reselling a £30 a month tool with a 10x markup and a Slack channel. Ask any provider what software sits underneath their service. If they will not say, walk away.
The three-question test
I use the same three questions on every enquiry. They settle the build vs buy question faster than any feature comparison.
1. Is your workflow genuinely unusual?
Not “we do things a bit differently.” Genuinely unusual: a structured supplier feed nobody else uses, a regulated communication trail, a pricing model with rules that no off-the-shelf tool can express. If 500 other UK businesses have roughly your workflow, a product already exists for it, and buying it will be cheaper and faster than anything I could build you.
In my experience around four in five small business agent ideas fail this question, and that is the end of the conversation. Email triage, meeting booking, invoice chasing and FAQ-style customer support are all solved categories. For email specifically, the practical setup guide covers what to buy and how to configure it.
2. Does the agent need your data to be useful?
The strongest case for building is not a fancier workflow. It is proprietary data. If the agent’s value comes from reading your job history, your stock levels, your customer records, your sensor data, then an off-the-shelf tool will only ever see a sliver of that through whatever integrations it happens to support. A built agent sits directly on your database and uses all of it.
This was the deciding factor for the one enquiry I said yes to last month: a trade business with eight years of job records who wanted quoting suggestions grounded in what similar jobs had actually cost them. No SaaS product can do that, because no SaaS product has their data.
3. Can you afford for it to be wrong?
Every agent makes mistakes. The question is what a mistake costs. A misfiled email costs seconds. A wrong quote sent to a customer costs real money and reputation. The higher the cost of an error, the more the design needs human checkpoints, and the more a custom build earns its keep, because checkpoints are exactly the thing generic tools let you configure least.
If your answer to all three questions is no, buy. If you answered yes to question one or two, a build is worth pricing up. If you only answered yes to question three, you do not need a custom agent; you need a cheaper tool used more carefully.
What building actually costs, and where the money goes
The £3,000 to £20,000 range above is wide, so here is what moves the number, based on builds we have scoped and shipped.
- Integration count. An agent that reads one database is cheap. An agent that has to talk to your accounts package, your calendar and a supplier API is not. Each integration adds days, not hours.
- Autonomy level. “Drafts for a human to approve” is roughly half the cost of “acts on its own,” because acting alone needs guardrails, logging and rollback paths that draft-only designs do not.
- Data tidiness. If your eight years of records live in a clean database, great. If they live in 14 spreadsheets and a retired employee’s memory, the first chunk of budget is data work, not AI work.
And the part most quotes leave out: running costs. A custom agent calls a commercial AI model, and those calls are metered. For a typical small business agent that is £20 to £150 a month in model fees, plus hosting, plus someone keeping it working when the model provider changes something. Models get deprecated, APIs shift, and an agent nobody maintains degrades quietly. This is the same after-launch problem every piece of custom software has, and it is why we wrote who manages your app after launch. If a build quote does not mention ongoing care, the quote is incomplete.
The trap in the middle: vibe-coding your own agent
There is a tempting fourth route: open an AI app builder, describe the agent you want, and let the tool generate it. For a demo, this works alarmingly well. For a production agent with access to your customer data, it is the riskiest option on this page.
The failure mode is the same one we documented in the wall problem with AI app builders: the first 80% arrives in an afternoon, and the remaining 20%, which is error handling, permissions, audit logging and data protection, never arrives at all. With a customer-facing form, that gap is embarrassing. With an autonomous agent that can send messages or change records, it is dangerous. The hidden costs of vibe coding apply double when the software can act on its own.
Data protection is not optional
Whichever route you choose, an AI agent that touches personal data makes you responsible for how that data is processed. Buying a tool means checking its data residency and signing a data processing agreement. Building means deciding which model provider sees your data and under what terms. The ICO’s guidance on AI and data protection ↗ is the authoritative UK starting point.
On the security side, an agent is a new set of credentials with real permissions in your business. The NCSC small business guide ↗ baseline applies: multi-factor authentication on every connected account, and a quarterly review of what the agent can access. An agent you set up in March and forgot about is an open door by September.
Frequently asked questions
How long does a custom AI agent take to build?
For a single-workflow agent with one or two integrations, four to eight weeks from kickoff to a supervised pilot. Most of that time is integration and guardrail work, not the AI itself. Anyone promising a production agent in a week is selling a demo.
Can I start with a bought tool and build later?
Yes, and for most businesses that is the right sequence. Run an off-the-shelf agent for six months, learn where it falls short, then build only the part it cannot do. The bought tool’s shortcomings become your build specification, which makes the build cheaper and better targeted.
What is the minimum budget where building makes sense?
If your total appetite is under £3,000, buy. Below that line you cannot fund the guardrail and integration work that separates a safe agent from a demo, and a well-chosen £40 a month tool will serve you better.
Do I need my own AI model?
No. Custom agents for small businesses call commercial models over an API. Training or fine-tuning your own model is enterprise territory and almost never justified at small business scale. Your competitive advantage is your data and your workflow, not the model.
Who owns a custom-built agent?
That depends on your contract, so check it. Under a managed software arrangement like ours, the customer owns the code and the data, and pays for the ongoing care. The what is managed software explainer covers how that model works.
Want a straight answer on your idea?
If you have an agent idea and want it run through the three-question test by someone with no stake in the answer, get in touch. Two of the last three people who asked were told to go and buy a £30 a month tool, so you can trust that “build” is not the default answer. The first conversation is free, and if buying is the right call I will say so and point you at the category to look in.