- Agents pay off when they save real hours - below that, operating costs eat the gain.
- Precisely describable processes belong in classic automation, not in a language model.
- Without a clean data foundation and a process owner every AI project fails - order matters.
What an agent actually is
An AI agent is not a chatbot with a new name. It understands a task, plans steps, uses your systems - CRM, ERP, email - and delivers a result. The difference to classic automation: it copes with cases nobody defined precisely beforehand.
That is also exactly where the risk lives: what decides flexibly can decide wrongly. Which is why every agent needs clear tool boundaries and a human with the final word. In our projects this is not a footnote but architecture: the AI prepares, humans approve.
"A good process beats a bad model - every time."
DUNA engineering principle
Terminology: "agent" here means an LLM system with tool access and a planning loop - not every chatbot that calls itself one.
The maths: three examples
Whether an agent pays off is not a matter of faith but of arithmetic: hours saved times hourly rate, minus operating costs. Three patterns from our consulting practice:
| Use case | Before | With an agent |
|---|---|---|
| Capturing and checking incoming invoices | Document-by-document manual work | AI reads, checks, pre-books - a human approves |
| Standard support requests | Answered ticket by ticket | An assistant with order and product data handles the routine |
| Internal knowledge search | Search, ask, wait | Answers from your own documents in seconds |
The first case is not a slide for us but production: for the waste-management platform entsorgo a document pipeline reads invoices, delivery notes and weighing slips via OCR, classifies them, checks them against orders and partner prices and pre-books them for accounting. Humans review and approve - nothing is booked automatically. Details in the AI accounting case.
Agent or automation?
Rule of thumb: if the process can be described exactly, use classic automation - cheaper, faster, deterministic. If it needs judgement, language or shifting context, the agent earns its keep. Most good systems are a mix: deterministic rules where possible, AI where necessary.
Practice shows the same: in the entsorgo pipeline a rule-based matcher first groups documents that belong together (same order number, same supplier, plausible date) - only then does the language model fill gaps and fix read errors. Rules first, AI second.
Learning instead of administering
The underrated part of an agent project is not the model but the learning loop. Every human correction is a data point: if the same field gets corrected three times for the same supplier, the system should know it by the fourth.
That is exactly how we built it: corrections are analysed per partner, recurring patterns move into a knowledge base, and that knowledge flows back into the prompt with the next document. The system improves in operation - not through retraining, but through structured remembering.
When to walk away
No clean data foundation, no clear process owner, or savings that cannot carry the operating costs: then the agent does not pay off. Clean up the process first, automate second - in that order. Reverse the order and you automate your chaos.
