Custom AI agent development for business operations
Fettler is an AI agent development company. We build agents that complete business workflows inside your existing systems, with named approval gates and ongoing monitoring.
Working with 40+ clients across sizes and industries.
Scope
Workflows an agent can complete
An agent owns a workflow from the trigger to the record it leaves behind. Three of the ones we are asked for most often, set out the way we would scope them.
Scroll sideways to read the table.
| workflow | trigger | what it reads | what it produces | who takes the exception |
|---|---|---|---|---|
| Export documentation | The shipment reaches its agreed readiness date. | Sales order, packing list, invoice, and the buyer instructions that only exist in a mail thread. | The assembled pack, with every mismatch listed rather than quietly corrected. | Export desk |
| Supplier invoice matching | An invoice arrives in the shared mailbox. | The invoice document, the purchase order it claims to be against, and the goods receipt. | An entry ready to post, or a named difference held for a person. | Accounts payable lead |
| Inbound triage | A message lands in a shared inbox or channel. | The message, the thread it belongs to, and the account behind it. | A classification, an owner, and a reply drafted in your voice and held for release. | The desk that owns the account |
Demonstration data. Not a client system.
The shape does not change: name the trigger, name the rules, name the person who signs. What changes is the vocabulary of your business, which is what the diagnostic is for.
What we deliver
Agents, skills, automations and integrations
Four delivery items. You buy one workflow at a time, not a platform to grow into.
- Agents
- A digital worker that owns a whole workflow end to end. It starts itself, decides using your rules, acts, and escalates what it cannot resolve.
- builds the full export documentation pack and stops on any mismatch
- Skills
- One reusable competence that any agent or any person can call. Read this invoice format.
- one "read a supplier invoice" skill, every vendor, every layout
- Automations
- Scheduled unattended runs, with monitoring and retries. It happens at 06:00 whether or not anybody remembers.
- the daily close pack is on the desk before the desk is occupied
- Integrations
- Getting data out of systems never meant to share it: a legacy ERP, a supplier portal, bank mail, PDFs. A controlled data collection layer with an audit record.
- platform integration where no API was ever published
A skill is not a workflow, and the difference decides what you are buying. Reading a supplier invoice is a skill: one competence, one input, one output, callable by any agent or any person. Matching every supplier invoice to its purchase order, applying your tolerances and holding the differences for a named approver is an agent: it starts itself and it finishes with a record.
Systems
Built inside the systems you already use
Nothing new for your people to open. The work appears in the screen they already use, the mailbox they already read, or the sheet they already keep.
-
Your ERP and finance systems
Read and write through whatever route your administrator approves, with the same permissions a member of your team would be given for the same job.
-
Mail and shared inboxes
Half of every operational workflow lives in a mail thread: the buyer instruction, the remittance advice, the approval that was never entered anywhere. An agent reads that thread as an input, not as an afterthought.
-
Documents and PDFs
Supplier invoices, remittance workbooks, buyer instructions, certificates. Read by meaning rather than by cell position, because the layout changes without notice and a position based reader breaks the week it does.
-
Spreadsheets
The number everyone actually trusts often lives in one person's sheet. That sheet is a system too, and an agent treats it as one rather than pretending it away.
-
Portals with no published interface
Where a system was never meant to share its data, we build a controlled data collection layer instead: scheduled runs, session management, retries, and an audit record of what was read on each run.
We hold no certified partnership with any software vendor and we do not claim one. Access is what your administrator grants, in writing, using credentials you issue and can revoke, and we tell you what an agent touches before it touches it.
Control
Where human approval sits
The agent prepares. A person releases. Anything that leaves your company or moves your money waits for a named approver.
Scroll sideways to read the table.
| raised | action | approver | state |
|---|---|---|---|
| 09:12 | release tax invoice to customer | finance lead | held for approval |
| 09:31 | post credit note, ledger write | finance controller | held for approval |
| 10:58 | send documentation pack to buyer | export desk | released 11:04 |
| nothing in this queue moves without a named human | |||
What the record holds afterwards
Every released action leaves a row that answers the four questions an auditor asks.
Scroll sideways to read the table.
| field | example entry |
|---|---|
| What it read | one remittance workbook, four open invoices |
| Which rule applied | deductions inside the agreed tolerance match, anything else is named and held |
| What it produced | three matched lines, one difference held |
| Who released it | finance lead, 11:04 |
Demonstration data. Not a client system.
Operation
What we run and monitor
Building an agent is the cheap part. Keeping it correct in production for a year is what you are actually paying for.
-
Scheduled runs and retries
Unattended runs happen on the clock, and a run that fails is retried on a pattern we agree rather than left for somebody to notice. A run that keeps failing raises a person, because a silent retry loop is a failure that has learned to hide.
-
Format and portal changes
A supplier changes an invoice layout, a portal moves a screen, a workbook grows a column. This is the ordinary weather of production automation and absorbing it is part of the monthly fee, not a change request.
-
Failures have a named owner
An alert goes to the person who owns the workflow, with the diagnosis already in the message, rather than to a room where everybody assumes somebody else is looking. Silence means healthy.
-
Rules change, so maintenance is continuous
New tolerances, a new approver, a new document type, a new exception you did not have last quarter. We change the rules with you and record what changed and when.
We publish no service level on this page, because a response time written before we have seen your systems is not a commitment. Monitoring, response and recovery expectations are agreed in writing during the build, against the workflow they apply to.
Ownership
What you own and can take back
We build for the day you might leave, from the beginning. It makes the work better while you stay.
-
You own what was built for you
The workflow logic, the rules, the integrations and the documentation for everything built specifically for you. This is written down before the first build, not negotiated after it.
-
Documentation is a deliverable
The rules an agent applies, the systems it touches and the approvals it waits for are written down as the agent is built, because documentation produced later is a description rather than a record.
-
The handover pack
If you stop working with us you get documented rules and integrations, credentials returned, your data exported in a format you can read, and a walkthrough with the people who will hold it next.
Start with a workflow diagnostic
Two weeks beside your team, eight to twelve workflows mapped and costed, and a ranked backlog with an expected payback against each one. The first agent is on real work by week six, and the manual process stays in place until the two reconcile.
Or write to us and describe the workflow that annoys you most. That is usually the right one.