AI in SMEs: what the next generation automates first
Contents
AI in SMEs going through a handover works best when it starts with one Vorgang (one intake, one task, one destination): a document flow that costs time every day and depends on what a few people know. The next generation should automate the reading and sorting first, not the decisions. Three features mark the right first candidate:
- It arrives every day: delivery notes, incoming invoices, orders or complaints that someone reads and types into the ERP by hand today.
- It has one destination: every document answers the same question and lands in exactly one system, usually the ERP or the inventory system.
- It depends on experience: which invoice belongs to which order, or which delivery note has to go to quality assurance, is known mainly to whoever has done it for years.
A handover shows how the business really runs
Succession is no side issue for German SMEs. KfW Research (in German) counts around 545,000 SMEs aiming for a successor by the end of 2029, about 109,000 a year. Owners who plan to hand over by the end of 2026 are 66.5 years old on average.
When the senior generation steps back, knowledge that was never written down can leave with it. The DIHK Succession Report 2025 describes industrial firms whose structures are strongly geared to the previous owner, and owners who stop investing shortly before the handover. The next generation notices this in daily work: in processes that only function because one particular person carries them in their head.
Knowledge held by a few people makes every handover riskier
It is not only the owner who leaves. According to the DIHK Skilled Labour Report 2025/2026, almost a quarter of companies expect company-specific knowledge to be lost as older employees retire; in industry it is more than a third.
In the office, that also affects the Vorgänge that come up every day. The colleague in accounts knows which invoice belongs to which order. The colleague at goods-in knows which supplier lays out its delivery notes differently. As long as both are there, it works.
A Vorgang we build and operate captures the knowledge it needs. In week one your Fachbereich, the department that owns the work, describes the classes in a conversation and shows examples; we build the AI employee from them. Every assignment it makes is recorded with timestamp and reasoning in the decision log, and go-live comes with a handover document. Experience becomes a described process.
The next generation wants relief, not an IT project
Whoever takes over a business with full order books needs capacity above all. The DIHK Succession Report 2025 calls the skills shortage a double challenge: it hampers the handover and at the same time shrinks the pool of potential successors.
Time and people for experiments are then in short supply. KfW Research (in German) names the main obstacles to AI in SMEs: a lack of skilled staff and know-how, limited time, missing data and doubts about reliability. Anyone asked to set up an IT project alongside daily business and a handover is likely to put it off.
That is why a Pilotbetrieb, our fixed-price entry engagement, does not become an IT project. Your Fachbereich answers questions; we build the AI employee and operate it. It uses access your ERP already offers, such as a standard API, a watch folder, sFTP or email. You do not need an IT department of your own.
Four Vorgänge make a good first step
Each of these Vorgänge follows the same pattern: a document arrives, the AI employee assigns it, extracts the details and creates a task in the target system. The work after that stays with your people.
| Vorgang | What the AI employee does | What stays with your people |
|---|---|---|
| Incoming invoice | captures the header data, proposes the assignment and hands the invoice to accounts | checking, approving, posting, paying |
| Delivery note | reads the details, checks them and forwards the note to the warehouse, quality assurance or accounts | resolving discrepancies, accepting or rejecting goods |
| Incoming order | recognises customer, items and requested date and creates a task for the sales back office | confirming the order, committing to a delivery date |
| Complaint | assigns the complaint, extracts order and item numbers and creates a task for quality assurance | finding the cause, arranging a credit note or replacement |
Which comes first depends on where paper piles up today. How the delivery-note Vorgang runs is covered in our piece on delivery note processing. For invoices, invoice capture shows how header data is captured, and invoice processing automation shows where the AI employee's work ends. Why a single Vorgang is the right start is explained in our overview of AI process automation.
In a Pilotbetrieb, both generations work on the same Vorgang
A handover has two sides, and the first Vorgang needs both. The senior generation knows the exceptions; the next generation sets how the business will work in future.
| Who | Role in the Pilotbetrieb |
|---|---|
| Outgoing owner | brings experience to the process conversation: classes, special cases, typical errors |
| Next generation | chooses the Vorgang, agrees the hit rate and assesses the written evaluation |
| Fachbereich | shows examples and resolves the cases the AI employee hands over |
| AI employee | classifies, extracts, routes, creates tasks and hands unsure cases to a person |
| Agentivo | builds the AI employee in the first two weeks and then operates it |
What the AI employee does not do stays your responsibility
A handover redistributes responsibility. An AI employee does not shift it: it does not post, approve, pay or delete anything, and it does not trigger deadlines.
When it is unsure about a document, the agreed confidence threshold applies: it stops and hands the case to a named person. Through a defined human intervention path, your team can stop it, correct it or take over the Vorgang at any time. In daily operation we monitor and correct it and take responsibility for the result.
Seven weeks fit even a tightly planned handover
According to the DIHK Succession Report 2025, 38 percent of the owners advised by the chambers prepare the handover too late, often only one to two years beforehand. That leaves no room for anything open-ended. The Pilotbetrieb has a fixed end: one Vorgang, fixed price, agreed before we start, seven weeks, four of them productive operation on your real documents.
| Week | What happens |
|---|---|
| 1 | Process conversation with the Fachbereich, define classes, review examples, clarify access |
| 2 | We build and train the AI employee, set up quality checks and test on real documents |
| 3 | Acceptance against the agreed hit rate, go-live, handover |
| 4 to 7 | Productive operation on real volume; we monitor and correct |
| End of week 7 | Written evaluation: hit rate achieved, cases processed, time saved |
The hit rate is agreed before the start. If it is met, operation begins under a monthly operating agreement that can be cancelled monthly. If it is missed, the Pilotbetrieb ends with no further obligation. The written evaluation at the end helps with the handover too: it shows in figures what the first step achieved.
AI for SMEs means you answer questions and we operate
Once it is running, small and mid-sized firms face a practical question: who monitors the AI employee, who corrects it when a supplier changes its form, and who answers for the result? With us, the answer is fixed in advance. We operate every AI employee we build: we monitor, correct and take responsibility. Your Fachbereich resolves the cases it hands over. What operating an agent involves is described in our piece on AI agent governance.
Which AI employees we build for which Vorgänge is shown in the overview of AI employees.
Frequently asked questions
Should the next generation wait with AI until the handover is complete?
Not necessarily. A Pilotbetrieb takes seven weeks and mainly needs one process conversation and examples from the Fachbereich in week one. It can therefore run during the handover, provided the outgoing owner and the successor agree which Vorgang comes first. The advantage: the senior generation's knowledge flows into the classes and examples while they are still in the business.
Which Vorgang is worth automating first?
The one where paper piles up today and that arrives every day. Typical candidates are incoming invoices, delivery notes or orders arriving by email. What matters is that every document answers the same question and lands in the same system. Multi-stage processes with branching, such as full complaint handling, do not belong in the first step; assigning incoming complaints does.
What happens when the next generation changes processes?
Then we adapt the AI employee. New suppliers, new cost centres or changed responsibilities are part of ongoing operation: we monitor it and correct it when the Vorgang changes. If a second intake channel or a second decision rule is added, it becomes a Vorgang of its own with its own hit rate. A change of ERP affects the target system and is discussed with us beforehand.
What happens when the AI employee assigns something wrongly?
Because it never posts, approves or pays anything, an error shows up as a task in the wrong place or as a wrong proposal that accounts sees before posting. The responsible person passes the case on; we see the misassignment in the decision log and correct the AI employee. How often it gets things right is measured by the hit rate, agreed before the start and tested in week three.
The next step
If a handover is coming up in your business and delivery notes, invoices or orders pile up on a few desks, that is the Vorgang for a Pilotbetrieb: one intake, one task, one destination. Fixed price, agreed before we start. Seven weeks, four of them productive operation on your real documents.