In you're already running on AFAS or Exact: what does an AI brain still add the answer was given in the negative form. If your question falls within your ERP, don't buy anything extra, and first check what your vendor already delivers.

That post left one question open: fine, so when do you? This piece answers that, and it won't re-explain what AFAS and Exact build themselves. That's covered there.

01 / the reversalWhat changes when you flip the question?

The test becomes usable instead of philosophical.

"Do I need AI" can't be answered. "Which work in my week doesn't end in a record" can, and that's the same question in workable form. An ERP is a ledger: it records what's finished and has a number. Anything that doesn't get a number falls outside it by definition.

Don't look for what your system can't do. Look for work that never enters it.

That produces four recognizable categories. They overlap at most companies, but only one or two of them are dominant, and that's where to start.

02 / situation oneKnowledge that never enters the system

The clearest of the four, and the reason this field exists.

How you build a price. Why that one client got an exception. Which supplier you no longer call and what happened back then. That's the knowledge your business runs on, and there's no field in AFAS or Exact where it belongs, because it isn't a transaction.

The tell: a new employee can operate every screen and still can't produce a quote that's correct. Then your problem isn't in the software but in what isn't in it. How to get that out of your head without writing a manual nobody reads is covered in getting knowledge out of your head.

03 / situation twoWork that happens before the record

This is the biggest and the least noticed.

A quote only becomes a record once it's sent. Everything before that happens outside the system: the conversation, the assumptions, the three drafts, the email where the client asks something back. The same goes for an intake, a tender, or a case file that only opens once the assignment is confirmed.

Measure it honestly once. At many companies, most time isn't spent handling assignments but in the run-up to them, and that run-up is the worst supported part. The ERP only enters the picture once the decision has already been made.

What works here is preparation: the draft that's ready, the data that's gathered, the previous similar case laid alongside. What doesn't work here is sending without a human step, because this phase holds exactly the judgment you shouldn't give away.

04 / situation threeWork that runs across multiple systems

Your ERP is rarely your only system. There's a mailbox next to it, a calendar, a project environment, a folder of documents, and at many companies a niche industry package nobody dares touch.

Work that crosses those boundaries costs a disproportionate amount of time, because a person is the connector. Someone reads the email, looks up the file, copies a few fields, puts it in the calendar. Each step is small and the total is a day's work per week.

Note that the gain here lies in removing retyping work, not in clever answers. That's less exciting and easier to justify: you can calculate in advance how many actions disappear.

05 / situation fourExceptions that nobody writes down

The fourth is the hardest to spot, because it hides itself as normal work.

Every company has arrangements that deviate from the standard. A client with their own invoice format. A customer who insists on a different field being filled in. A delivery term that's different for two relationships. The ERP holds the standard; the deviation sits in the head of whoever knows the client.

They can be found without research. Go through the last twenty assignments and mark, for each one, what went differently from standard. Whatever shows up two or three times isn't an exception anymore but an unwritten rule, and that deserves to be recorded. Whatever shows up once, leave alone.

That goes fine for a long time, and it breaks down on holiday. Whoever recognizes this category doesn't need a big system but does need a place where the deviations live, traceable and adjustable one by one. That's small work with a large effect on how exposed your business is.

06 / the executionHow do you keep it small?

Three rules that in projects like this make the difference between something that runs and something that stalls halfway.

• One process at a time. Not "we're connecting our ERP", but one clearly bounded flow from start to finish. Whoever tackles everything at once delivers nothing that works tomorrow.
• One direction first. Start with reading from the ERP. Writing back is a separate decision with its own risk, and you usually don't need it in the first phase.
• One internal owner. Someone it belongs to after delivery. Without that person, it becomes nobody's job and stalls within half a year, no matter how well it was built.

Want to know first what systems are actually running now and where it's leaking, then a system diagnosis is the cheapest first step. What we build ourselves and on what, is on the systems page.

And the honesty line that belongs with this topic: if your question does fall within your ERP, you should hear that from us before there's a quote on the table. That happens regularly, and then the answer is that you should be talking to your own vendor or implementation partner. What else you should ask any provider is covered in four questions to ask any AI provider.

This text was created with AI assistance and reviewed and approved by a human before publication.