AI agents for your ERP
You already have an ERP. The problem is rarely the ERP itself — it is everything that happens around it: the enquiry that arrives by email, the pricing that lives in a spreadsheet, the specification buried in a PDF, and the person who retypes all of it into a screen. An AI agent is the piece that reads those inputs, finds what it needs in your systems, prepares the work and hands it to a human to approve.
What an agent actually is
Not a chat window bolted to your ERP. An agent is a process with access and rules: it can read a defined set of sources, take a defined set of actions, and it stops at the points you tell it to stop. The useful mental model is a capable new joiner who never forgets a step, has read every past enquiry, and is not allowed to send anything without a signature.
Where it usually starts
| Process | What the agent does | What stays human |
|---|---|---|
| Enquiry to quotation | Reads the enquiry, identifies the items, pulls stock and pricing, drafts the quotation | Pricing judgement and the decision to send |
| Documents into data | Extracts fields from PDFs and scans, checks them against the order, flags mismatches | Anything the system marks as uncertain |
| Order to dispatch | Watches status, chases the gaps, prepares the paperwork | Exceptions and customer commitments |
| Ask your own company | Answers "have we done this before, and what did we charge" from your own history | The decision the answer informs |
Access, and how we keep it boring
An agent can only see what you give it access to. That list is written down, it is yours to change, and you do not need us to change it. Every action it takes is logged with what it read and why, and every action can be undone. Before anything becomes automatic, it runs alongside your team and drafts — you compare its output to what your people would have done, on your real work, and only then decide what it is allowed to do unattended.
What this does not do
It does not fix a process nobody can describe. If three people do the same job three different ways and none of it is written down, the first engagement is working out what the process actually is — which is useful, but it is not automation and we will say so.
It also does not replace your ERP, your ERP partner, or the people who know your customers. If someone is pitching you AI as a reason to rip out working software, be careful.
Questions people ask
Will this change our ERP?
No. We read and write through the interfaces your ERP already exposes. Nothing is modified inside it, and your ERP vendor's support position does not change.
What if the AI enters something wrong?
It does not enter anything on its own until you have watched it work and told it to. The first version drafts and a person approves. Every step is logged and reversible, and you decide which actions ever become automatic.
Which ERPs can you connect to?
Anything with an API, a database we can read, or an export we can watch. What matters more than the brand is whether your installation allows programmatic access — some do out of the box, some need your ERP partner to switch it on.
Do we have to replace our spreadsheets?
Not at the start. Spreadsheets are usually where the real process lives, so the first job is to read them, not to abolish them.
Related
Private LLM deployment in India · AI workflow automation for manufacturers · How we work
Last updated August 2026