AI systems for operations. Designed and built in Amsterdam.

Fromprocesstoproduction.

We design and build AI systems that take over the heavy, recurring work of your operation. Custom, inside the systems you already have, and built to run every day.

See the systems
01The shift

Everyone has bought AI. Almost no one has it in production.

95%

of the organisations studied saw no measurable return on generative AI.

MIT NANDA, 2025

Licences, pilots, strategy sessions, a chatbot on the website. Most organisations see nothing of it in their operation yet. There is no shortage of AI. There is a shortage of AI that does work every day.

AI theatre
  • The demo that never went live
  • The pilot that stopped when the consultant left
  • The chatbot nobody uses
  • The strategy deck in a drawer
  • The tool next to the work instead of inside it
Production
  • Systems that run every working day
  • Inside the software you already have
  • Built next to the people who do the work
  • Measured in work that disappears
  • A person with the final word
02What we say no to
  1. 01We don’t build chatbots.
  2. 02We don’t run pilots that end up in a drawer.
  3. 03We don’t deliver a strategy deck without a working system.
  4. 04We don’t ask whether AI can do it.

→We show you that it runs.

04The factory in numbers

What runs.

16,000+

tenders read before a person opened a single page.

10

systems live. In one day.

0

words from a session in our database. Ever.

6.2M

passages broken down, each traceable to its source.

1

command to put a new client live. In another country, under another brand.

05From the logbook

Operation Day One.

iChoosr had eleven AI leads, every licence and months of ideas. In production: nothing. We came for one day.

  1. Before
    Every team hands in the process they hate most.
  2. Morning
    No slides. We open their own systems and start building.
  3. Afternoon
    Testing on real work. What doesn’t run goes back on the bench.
  4. End of day
    Ten systems live.
  5. + 4 months
    Six still run. Every day. Without us.
06How a process reaches production

Four steps. No theatre.

01

Conversation

Half an hour. We ask which work your people would most like gone. If there’s a system in it, we say so. If there isn’t, we say that too.

02

Blueprint

The process mapped, the return calculated, the architecture on paper. Fixed price, credited against the build.

03

Build

On your systems, next to your people. Agreed upfront what it costs and what it must do.

04

In production

The system runs. We monitor it, improve it and stand behind it. Monthly, cancellable.

07The rules of the factory
AI reads.
Code calculates.
A person approves.

AI is unrivalled at reading: email, PDFs, conversations, handwriting. We never let it do the maths. Every amount, rule and check lives in code that does the same thing every time. And whatever leaves the building, a person approves.

AI proposes. Whether it’s allowed, it never decides on its own.

08Why us

We know how AI code fails. We researched it.

While the market sold demos, our founder researched AI-written code at the University of Amsterdam: 1,762 changes, traced back to the line where a vulnerability began. That’s why we build the way we do.

  • 01Maths in code, decisions by people
  • 02Every release tested and verified down to the running version
  • 03Hosted in Europe
  • 04Everything logged, everything traceable
09Questions

What you ask us most.

01What does Agentfabriek do?

We design and build AI systems that take over recurring work in operations: writing reports, reading documents, answering phones, checking invoices, processing orders. Custom, inside the systems you already have, and we only leave once the system runs in production.

02For which companies?

For companies with serious operations where the work grows faster than the team: manufacturing, wholesale, logistics, care, professional services and scale-ups. The sector doesn’t decide the fit; recurring daily work does.

03What does a system cost?

It depends on the process. After the first conversation we make a blueprint at a fixed price, credited against the build. The build is priced upfront; after that you pay monthly for monitoring and improvement, cancellable monthly.

04Do we need to replace our software?

No. We build on what’s there: your ERP, CRM, Microsoft 365, email and telephony. Our systems run next to your software, not instead of it.

05What about errors and privacy?

AI reads, code calculates and a person approves what leaves the building. Amounts and checks live in fixed code, not in the language model. We host in Europe and store no more than the system needs.

Rather read first?

What we run into, worked out per trade (mostly in Dutch).

Which process goes into production first?

Tell us where your people lose their days. After half an hour you’ll know whether there’s a system in it.