Making business processes AI-ready: Agility stays mandatory

AI-ready is not a seal of approval and not a software feature. It is a property of the process itself. A process is AI-ready to the extent that three conditions are met.

First, it must be describable. What nobody can write down in clear steps, no AI can reliably take over either. Second, the necessary data must exist in a form a machine can read, not just as an email attachment or in the head of an experienced colleague. Third, the systems involved must release and accept their data, meaning they need interfaces.

These three conditions are why the first three steps of this guide have nothing to do with AI. They are process work. That is exactly where it is decided whether an AI project will hold up later or become expensive technical decoration, meaning technology that looks good and achieves nothing. What an AI can do at its core and what it cannot is set out in our knowledge article on artificial intelligence.

The first step sounds unspectacular and is the most important: write down how the process actually runs today, not how it should run according to the manual. In our projects, this gap between target and reality is almost always larger than expected, and the special cases that later break an automation hide exactly inside it.

A usable documentation needs no software and no layer model. Four entries per process step are enough to start: what triggers the step, who carries it out, what information goes in and what comes out. Half a page per process, created in conversation with the people who do it every day, beats any unread flow chart.

Here is what such a recording looks like for a quoting process, kept brief:

Even this small table achieves two things. It makes visible where an AI can sensibly start. In the example that is the jump from the calculation to the finished quote document, a structured and error-tolerant step. And it shows the handover points where information is passed on by hand. Each of these points is a candidate for a later interface and a typical place for delays and transmission errors.

Once the workflow is clear, the data follows. The guiding question is: where does each piece of information come from, and which source counts in case of doubt? This second question decides the reliability of every later AI answer. If prices sit in the ERP, in the web shop and on top of that in a maintained spreadsheet, then an AI delivers three different truths depending on the source, and none of them is recognisably the right one.

So for each important piece of information, define one leading source before you automate. Three questions help:

1. Which system owns this information? The ERP for prices, the CRM for customer data, the editorial system for product texts. One piece of information, one responsible system. 2. How current does the information have to be? A price list updated once a week is no basis for a same-day quoting automation. Currency is a data requirement, not a detail. 3. Is the data structured or free text? A maintained "net price" field is something different to a machine than a price that appears mid-sentence inside a quote paragraph.

Where you run into scanned PDFs, manually maintained lists or contradictory systems here, you have not found an AI problem but an upstream data project. That is good news, because clean data pays off for every undertaking, not just AI.

An AI is only as useful as its access to the right systems. In the third step you therefore check whether the systems involved release their data in machine-readable form and whether they accept results back. Information that can only be pulled from a system by hand export cannot be built into a running workflow. It becomes a daily manual intermediate step that eats up the promised time savings again.

The honest interface inventory is manageable. Go through the handover points from step 1 and answer two questions for each: does the upstream system release the data through an interface, such as an API? And does the downstream system accept the result back through an interface, or does a human have to type it in?

In practice the result is mixed. Modern cloud systems usually come with interfaces. Older industry software or homegrown island solutions often do not, or only at extra cost and with restrictions. This finding is no defeat but a planning basis. It tells you which automation is possible tomorrow and which first needs a technical connection. Whether you build that connection yourself or buy it is a separate trade-off, which our article Make or buy for AI solutions works through.

The first three steps might give the impression that AI-ready is a state you reach once and then tick off. The opposite is true. Processes, data and systems change constantly, and AI tools develop even faster. Agility here is not a methodology fashion but the only way of working that keeps up with this pace.

Concretely that means: do not spend half a year building the perfect fully automated solution, but get a small, useful version into real operation within four to six weeks. Let the people who know the process use it, measure the result against the starting value and improve it in the next short cycle. That way the solution learns from the real case, and you notice early when a path leads into a dead end, while the correction is still cheap.

Three principles keep this iteration healthy:

• Start small. One sub-step of the process, not the whole process at once. In the quoting example the draft of the document, not the complete request-to-order stretch.
• Keep a human in the loop. The AI suggests, a human approves, especially while trust in the results is still growing. From the corrections you learn where to improve.
• Measure every iteration. Without a before-and-after comparison, improving turns into tinkering. One simple metric per process, such as processing time or error rate, is enough to start.

This iterative path is also why mid-sized companies have an advantage here. Short paths and processes that one person can still fully oversee are what make fast cycles possible in the first place. Use this advantage instead of giving it away with a heavyweight big project.

Pick a single process that occurs often and where an error does not hurt. Sit down for an hour with the people who do it every day and fill in the small table from step 1: trigger, owner, input and output per step. This one hour alone usually already shows you where AI can sensibly start and where data or interfaces are missing first.

If you then want to assess which processes offer the greatest leverage and in which order to proceed, talk to us. In a Future Check we sort your processes out together and name the realistic first step. If you would rather get straight into a conversation, you can reach us via the contact page.