Your processes, automated with AI. Six kinds of agents.
An order that arrives by mail. An invoice that has to match. A ticket that has to go somewhere. We build the agents that do that work, next to the ERP or CRM you have or inside software we build for you. Within limits you set.
Next to new software, AI engineering and legacy: the work in between.
For twenty years we have built software for companies. Most of the work in a company is not inside that software but between the systems: reading, retyping, sorting, checking, answering. Agents now do that work. One process at a time, and the next one when the first one runs.
Six kinds of agents. Each with a limit.
Not one black box that “takes over a department”. Six plain kinds, each with what it reads, what it does and what it never decides. You point at the process, we say which agents it takes.
The Reader
A document, a mail or a photo goes in. Structured data comes out, in your system.
Never decides. Reads and hands over.The Sorter
Whatever comes in gets a type, a priority and an owner, with a one-line summary.
Decides the route, never the outcome.The Answerer
A question goes in. An answer comes out, with the source it came from.
Answers only from your sources, and shows them.The Drafter
Your data and your templates go in. A document ready for review comes out.
Drafts. A person sends.The Checker
Two things that should agree go in. The exceptions come out, each with the reason.
Flags by a rule you can read.The Worker
A case goes in. It reads, decides within the limits you set, acts in your software and logs every step. Exceptions go to a person.
Acts inside the limit. Outside it, a person.Together they are a process. An order, for example.
One agent does one thing. The power is in the chain: five agents, one workflow, running in your ERP without anyone retyping. This is what an incoming order looks like.
- 01The Reader The order arrives as a mail with a PDF. Customer, lines, quantities and delivery date come out as data.Reads only
- 02The Checker Prices against the price list, quantities against stock, the customer against the credit limit. Deviations get a reason.Rule you can read
- 03The Worker Within the limit, the order is booked in your ERP. Outside it, nothing happens until a person says so.Your limit
- 04The Drafter The confirmation to the customer is drafted in your house style, with the delivery date from the ERP.A person sends
- 05The Sorter Everything that fell outside the rules lands with the right colleague, with a one-line summary of why.Logged
On what you have. Or in what we build.
Where the agents live depends on how good your current systems are. Both routes start the same way: with one process and a proof on your own files.
Route 1: on top of your ERP or CRM
You keep your package. The agents sit next to it and read from and write to it through its connections. The package keeps the ledger and the master data, the agents take the typing, sorting and checking around it. Nothing changes for the people who work in the package, except that less lands on their desk.
For whom: companies whose package works but whose people spend their days feeding it.
Route 2: your own software, with AI built in
More and more often the answer is not yet another package. Software that does exactly what your company does, with the agents built in rather than bolted on. Built with AI, so faster than it used to be. And yours.
For whom: companies that have outgrown their package, or never fitted one. How we build your own software.
Six processes we see everywhere. Which one is yours?
Scenarios, not references: this is what the six agents do with processes every company has. Below it, what already runs in production.
Purchase invoices
Read, matched to the order and the receipt, booked when everything agrees. Exceptions to a person, with the reason. Reader, Checker, Worker.
Quote requests
The request read, the products pulled from your catalogue, your agreements applied, the quote drafted in your template with the doubtful lines marked. Sales checks and sends. Reader, Drafter.
Complaints and objections
Type and urgency, the transaction pulled up, checked against your policy, a reply or a decision proposal drafted. The employee decides, every time. Sorter, Checker, Drafter.
Claims and refunds
Was the service delivered, was it paid for, was it already refunded. Within the rule the Worker pays out, outside it a person looks. Checker, Worker.
Questions from customers and staff
Answered from your own manuals, contracts and policies, with the source shown. What it cannot find goes to a colleague, with the question already summarised. Answerer, Sorter.
Documents that arrive as PDF and photo
Filed against the right customer and year, the figures extracted, the ones that do not match the expectation flagged. The adviser reviews the exceptions instead of typing everything. Reader, Checker.
Built and in production. Not a slide.
From one process to a running agent.
- 01The proof You send one slice of real work: twenty invoices, fifty tickets, a week of a mailbox. You see what the agent did with it. Under NDA.Proof
- 02The limits Together we write down what the agent may decide on its own, what goes to a person, and what is measured before and after.On paper
- 03The proposal One proposal, fixed scope, fixed price, for the first process. No programme, no retainer.Fixed price
- 04The build Agents write most of the code, under our gates. Your people test it on their own work before it touches anything live.Weeks
- 05Live, and kept It runs in your environment, logs every step, and we keep it running. Then the next process.Yours
What people ask before they send anything.
Does this replace our ERP?
Usually not. Route 1 keeps your package and puts the agents next to it. Route 2, your own software with AI built in, is for companies that have outgrown their package. We tell you which route fits after the proof, not before.
What does the AI decide on its own?
Nothing you have not written down. The Reader and the Drafter never decide. The Checker decides by a rule you can read. The Worker decides inside limits you set and hands everything outside them to a person, with the reason.
Where does our data go?
It stays in your environment, in the EU. Our developers do not work with production data. Development, test, acceptance and production are strictly separated. We are ISO 27001 certified and put the data processing agreement on the table before the proof.
What does it cost?
The first process gets one proposal with a fixed scope and a fixed price. What that is depends on the process, so we do not print amounts. You know before you commit.
Which process costs you a person a day?
Send a slice of it. You see what the agents did with it, which of the six it takes, and what the first process would cost. Under NDA, deleted afterwards.
Enigmatry, Rotterdam. Software company since 2006, ISO 27001.