AI integration services
What an AI integration connects, and where the agent does the work
An AI integration is the join between an agent and the software your business already runs: the inbox the work arrives in, the accounting system it has to end up in, the diary, the CRM. The agent does its work inside those systems rather than in a chat window you would have to copy out of, and the integration is what makes that possible.
Most of what the phrase is sold as is enterprise work, and it is worth saying so before you read any further. This page is the small-business version of the same question: one agent, two or three systems you already pay for, and the joins between them.
When AI integration means ERP and data-warehouse work, and why that is not us
Read the firms selling this phrase and most of them mean something larger than a business of twenty people needs. The work they describe is wiring models into an ERP that stays the system of record, change-data-capture into a data warehouse, middleware and adapters over a mainframe nobody dares touch, single sign-on across a staff of thousands. It is real work and it is expensive, and if that is the shape of your problem, a systems integrator is the right firm and we are not.
What we do sits a long way below that. The systems are ones you log into yourself, the integration takes days of somebody's attention rather than a programme, and the thing on the other end is an agent doing a job rather than a model serving a platform. The two get the same name, which is why this section exists: the sections below are the small-business version throughout.
What connecting an AI agent to accounting software looks like at the level of one invoice
Here is the whole of one join, on our own books, because an integration is easier to judge from one document than from a diagram. A £150 supplier invoice arrived in the accounting system at 20% UK VAT, flagged for review, with no receipt attached. The PDF said something else: a UK VAT number, no VAT charged, and a reverse-charge note. It belonged at 0%.
The connection is what let the agent settle that. It reads the PDF out of the inbox, applies the VAT rules the accountants wrote, records the entry in FreeAgent against the payment from the business bank account, and attaches the PDF to the entry. No PDF, no entry. Our invoice processing case study has that invoice in it — the accounting system's guess beside the entry the agent made — and it is a better test of an integration than anything we could claim about method.
What access an AI integration needs from you, and who has to grant it
Only what the job needs, at the narrowest permission that does it, and you get it as a written list before anything is connected: what the agent can reach, what it may do there, and what it cannot touch. In practice it is one or two of the inbox, the CRM, the diary and the accounting software, not all four.
The part nobody warns you about is that granting it is your week rather than ours. It is finding who holds the admin login for the accounting software. It is a mailbox belonging to somebody who left. It is two-factor authentication on a phone in a van. We can tell you in advance which access the job needs, which is the only honest way to make that week shorter. AI implementation services is the page about that whole stretch — getting from a working agent to one that is used — where this page is about the joins themselves.
Why an AI integration stops working weeks after it started
Because the software on the other side of the join keeps moving, and none of its changes are announced to you. A field gets renamed. An invoice template is redesigned. A supplier updates its interface. The agent carries on running and quietly stops doing the thing you are paying it for, which is worse than it failing loudly, because nobody is looking.
So the question that decides whether an integration is worth buying is not how it gets built. It is who repairs it in month four, and whether that repair arrives as work or as a quote. With us the running is the service: One flat monthly fee for unlimited agents, the repair is ours, and it is not a new statement of work. That is the reason we charge monthly rather than per project.
AI integration against AI automation, in the words an owner uses
Integration is the plumbing and automation is the work running through it. A connection on its own moves data; what earns its keep is the judgement applied to each item as it passes — reading this invoice, deciding this caller needs a person, noticing this case is the awkward one.
That distinction is also where the cheaper option stops. A trigger-and-action connector is enough when the rule is fixed: when this happens, do that, every time. It is not enough when each item has to be read and weighed before anything is done with it, which is most of the work a small business actually wants off its hands. AI automation services takes the same subject process by process.
What to do when your software has no way in
Some systems have no interface to connect to, and the honest answer is a different design rather than a workaround. The routes a connection can take, in the order we would rather have them:
| Route in | What the agent can do through it | What it cannot |
|---|---|---|
| The system's own interface | Read and write the records the permission covers, and see its own result | Anything the permission excludes, which is deliberate and written down first |
| Take in whatever arrives as a message or an attachment, and reply | Look anything up inside the system, or correct an entry already in it | |
| A scheduled file export | Work on everything the export contains, on the export's own timetable | Act on something the moment it happens, or write back |
| No way in | Nothing, and the honest move is to redesign the job around a system that has a route | Be rescued by screen-scraping, which works once and then fails without telling anyone |
Screen-scraping a system with no way in is the one we will talk you out of. It works on the day it is built, breaks on the next interface change, and breaks silently.
Which of your tools we have a live connection to today
Two systems have a page each, and both are connections you can inspect rather than a logo wall: FreeAgent, where the invoice agent records entries against the bank, and Google Search Console, where the SEO agent reads which pages are losing clicks. The integrations list is the current one. The same invoice agent also reads a mailbox for the supplier invoices themselves, which is the email route above doing the work it is actually good at, and it has no page because reading an inbox is not a connection into a system.
A tool gets a page here only once an agent is actually reading or writing it, which is why that list is short and why it is worth something. If the system you need is not on it, that is a question for the call rather than a no: what matters is which route into it exists, and the section above is how we would answer it.
What an AI integration costs
One flat monthly fee for unlimited agents. Nothing extra per call, minute or message. Stop any month. There is no separate integration fee, because splitting the connection from the upkeep of it is what creates the gap this page is about. What an AI agent costs sets out what UK agencies charge to build an agent and what the off-the-shelf tools cost per month, so you have the going rates in front of you before you talk to anyone. We give you the price on the call.
The usual shape of this market is a fixed-scope connection priced as a project, with its upkeep quoted afterwards or not priced at all. The consequence is worth seeing before you sign: the second connection is another project. Ours is flat and the agents are unlimited, so the second job is a conversation rather than a negotiation.
What to ask an AI integration company before you sign
Three questions, all about the joins rather than the build, and the answers are what separate firms that sound alike:
- Which route does this connection take, and what can it not do through that route? An answer that names the route — the interface, an email route, a scheduled export — is a firm that has looked. "We'll integrate with anything" is a firm that has not.
- What access do you need, and what will you not be able to touch? You should be handed that as a list, before anything is connected, not discover it in week three.
- Who repairs it when the software on the other side changes, and is that repair in the fee? Keep asking until the answer has a name and a price in it. This is the question most proposals leave out, and it is the one that decides what you own in a year.
What the agent may do through a connection on its own, and what waits for a person
Every connection is given two things when it is scoped: the narrowest permission that does the job, and a standing instruction about where its own authority ends. Routine cases the written rules cover, it completes itself. Anything new, unclear, or turning on a question the rules do not answer goes to a named person, with the reason and the document attached, and nothing is recorded or sent in the meantime.
That is what makes a connection safe to leave running, and it is checkable rather than a promise: our own invoice agent keeps a written list of the questions its accountants have not answered, and any invoice that turns on one of them is passed on rather than guessed at. The other half is the record. Somebody on your side reads a plain list of what the agent handled and what it passed on, which is how an integration that has quietly stopped working gets noticed in a day instead of a quarter.
Data, and the limits a connection works inside
An agent given access to your inbox, your CRM or your accounting software is handling personal data, so UK GDPR and the Data Protection Act 2018 apply to it exactly as they apply to the systems it reads. The government's data protection guidance sets out what that obliges you to do.
Which systems the agent may reach, what it may do on its own and what waits for a person are decisions made when the connection is scoped and written down then, rather than discovered later. They are worth reviewing once a quarter, because an agent's remit tends to widen and the written version tends not to.
Where to go next on this site
AI implementation services answers what it takes to get an agent from decided to running, where this page answers how it reaches your software. AI agent development is the build itself. AI agents for business is the question before all of them — which jobs are worth handing over at all. AI consultancy in the UK is the conversation that ends in an answer rather than a build, and our agency page covers how we work across the lot. The agents we build are one page away.
Frequently asked questions
- What are AI integration services?
The work of joining an AI agent to the software a business already runs, so the agent does its job inside those systems rather than beside them. In practice that means a route into one or two of the inbox, the CRM, the diary and the accounting software, the access to use it, and the upkeep of that join afterwards. The phrase is used mostly for enterprise work; this is the small-business version of the same question.
- What is the difference between AI integration and AI implementation?
Integration is the join between the agent and your software. Implementation is everything it takes to get from a working agent to one that is actually used — the access, the pilot on real work, what your staff do differently, who owns it after go-live. AI implementation services covers that stretch; this page covers the joins.
- How do you integrate AI into existing systems?
By the narrowest route the system offers, with the narrowest permission that does the job. The agent connects to the system's own interface where there is one, works through an email or file route where there is not, and where there is no way in at all the honest answer is a different design rather than a workaround built on screen-scraping, which breaks on the next interface change and breaks quietly.
- What access does an AI integration need to our systems?
Only what the job needs, and you get it as a written list before anything is connected, naming each system, the permission it is given there and the limit on it. Granting that access is the slow part, and it is your side rather than ours — admin logins, a mailbox nobody owns any more, two-factor authentication on somebody's phone. We tell you which access the job needs in advance, which is the only thing that makes that shorter.
- Can an AI agent work with software that has no API?
Often, through an email route or a scheduled file export, and the section above sets out what each route can and cannot support. What we will talk you out of is screen-scraping a system with no way in: it works on the day it is built and then breaks silently, and an integration that fails without telling anyone is worse than one that never started.
- Who maintains an AI integration after it is working?
Somebody has to, because the software on the other side of the join keeps changing — a renamed field, a redesigned document, an updated interface — and any of those can stop the agent while everything still looks healthy. With us the repair is part of the service rather than a change request, which is why the fee is monthly. It is the question worth putting to anybody quoting you an integration, until the answer has a name in it.
- Is AI integration the same as using a connector like a trigger-and-action tool?
No, and the difference is judgement. A connector is enough when the rule is fixed: when this happens, do that, every time. An agent is for work where each item has to be read and weighed first — which VAT rule this invoice falls under, whether this caller needs a person — which is most of the work a small business wants to hand over.
- Which systems do you already connect to?
Two have pages of their own, because a tool gets one here only once an agent is really reading or writing it: FreeAgent, where our invoice agent records entries against the bank, and Google Search Console, where our SEO agent reads which pages are losing clicks. The integrations list is the current one, and a system that is not on it is a question for the call about which route into it exists.
- What does an AI integration cost?
One flat monthly fee for unlimited agents, with no separate integration fee, because splitting the connection from its upkeep is what creates the gap this page describes. What an AI agent costs sets out what UK agencies charge to build an agent and what the off-the-shelf tools cost per month, so you can see the going rates. Agent Place gives you the price on the call.
- How long are we tied in for?
You are not. It is month to month and you can stop at the end of any month. We would rather be judged on whether the connections are still carrying the work than hold anybody to a term.
Bring us the job
Tell us the work, and which systems it lives in. On the call we will say which route into each of them exists, what access it would need from you, which part of it worries us, and the price.
Unlimited agents. One flat monthly fee. Fully functioning and delivering value in 30 days guaranteed, or you pay nothing more until your agents are.
Written by Kole Ogundipe for Agent Place, an AI automation agency and consultancy based in the UK which builds bespoke agents for operations, sales and marketing.