Digital Transformation, Germany

Owner-led companies: start with how the business runs

In an owner-managed company the transformation decision often rests with one or two people who know the business in great depth. That is a strength: decisions can be fast and take a long view. The risk is that the plan follows the latest supplier visit or trade fair conversation rather than a clear picture of where the business actually loses time and control.

I begin with that picture. In remote sessions with the owner, management and the staff who handle each step, I trace real transactions: an inquiry turning into an Angebot, an order and a delivery; a purchase from requisition to posted invoice; production orders and their material needs; and the path from the last posting of the month to the data your Steuerberater receives. Each handoff is recorded, together with the workarounds that make it function.

Mittelstand companies frequently hold critical know-how in a few long-serving employees. Pricing rules, special customer arrangements or the reasons behind a certain production sequence may never have been written down. Capturing this knowledge is part of the baseline, and it becomes urgent when succession or retirements are approaching.

Data comes next: duplicate article numbers, customer records maintained in several systems and prices kept in a spreadsheet beside the ERP. I note who owns each type of record. The baseline ends in four documents: process maps, an application landscape, a record ownership table and a prioritized problem list. Process-heavy findings continue in my business process consulting in Germany.

A staged roadmap from bookkeeping discipline to the sales front end

German companies tend to prefer plans that can be executed in controlled steps, and a transformation roadmap should respect that. Each stage must leave the business in a stable state, deliver a visible improvement and prepare the next stage. I order the work by dependency:

• Foundations: agreed processes, clean article, customer and supplier masters, and process documentation that can also feed the procedure description your tax advisor may expect.
• Core system: modernizing or replacing the ERP where the current one cannot carry variants, structured invoices or growth, with interfaces to the advisor, banks and shop designed in the same decision.
• Sales and service: a CRM or improved sales module so quotes, order intake and after-sales contracts connect to the core without retyping.
• Automation: incoming invoice processing, approvals, reminders and document filing on top of stable steps.
• Reporting: margins, order backlog, stock and receivables from one source with agreed definitions, so management no longer depends on manual exports.
• Lead engine: website, search and campaigns connected to the CRM, so new inquiries are visible in the same pipeline.

Each initiative lists an owner, dependencies and cost drivers: licenses or subscriptions, system house effort, interfaces, data cleansing, training and internal time. Where the ERP decision has to come first, ERP selection in Germany explains how I run that comparison.

E-invoicing, digital filings and the skills shortage as drivers

Outside pressures help decide what comes first, provided they are read correctly. I treat them as roadmap inputs and leave legal interpretation to your advisors.

Structured e-invoices. Germany is moving business-to-business invoicing to structured electronic formats, with receiving and issuing obligations introduced in stages. Companies that still print, scan or retype invoices will feel this first in purchasing and accounts payable. The roadmap makes sure systems can receive and issue formats such as XRechnung and ZUGFeRD and that incoming invoices flow into approval and posting. Your Steuerberater confirms what applies to you and when.

Digital filings. Tax returns already reach the tax office electronically through ELSTER, usually via the advisor's software. The cleaner the bookkeeping data at source, the less work each period creates for both sides.

Skilled staff shortage. Many Mittelstand companies struggle to fill commercial and technical roles, and retirements remove experience that is hard to replace. Automation and documented processes protect the capacity you have, and staff tend to accept change more readily when it is presented as relief rather than replacement.

Public support. Federal and state programs have at times supported digitalization in smaller companies. Schemes change, so check what is available; a documented baseline usually helps any application.

None of this points to one product. It favors clean data, structured documents and less manual handling in the first stages.

Works council, long-serving teams and adoption

Change in a German company has to work with its people and, where one exists, with its works council. Systems that can record user activity or evaluate performance generally involve the Betriebsrat, and business software of every kind keeps detailed user logs. I do not advise on co-determination law. For management and HR I prepare factual descriptions: what each planned system logs, which reports could show individual output, how roles and permissions restrict access and which logging can be limited. Management and its advisors decide when and how to involve the council; earlier involvement usually makes the later stages smoother.

Long-serving employees deserve particular care. They often know the processes best and have seen earlier projects come and go. I involve them as key users from the first workshops, so their knowledge shapes the design and they become advocates rather than skeptics.

Each stage then gets:

• A change note per department, drafted in English and finalized in German by your own people.
• Key users who test the system with real cases before go-live.
• Training in German on actual tasks, delivered by key users or a local partner.
• A check after go-live on whether old lists and folders are still in use.

Governance stays lean: the owner or managing director as sponsor, one accountable person per initiative, a written decision record and a defined route for scope changes.

Where an independent consultant fits, and where AI fits

In Germany, ERP and related systems usually reach the buyer through a system house, and specialist vendors cover areas such as document management, e-invoicing or shop connections. They deliver the technology. My place is on the buyer's side of every one of those relationships: maintaining the roadmap, writing requirements per stage, scoring offers against identical criteria, reading project plans and statements of work line by line, and confirming that each stage removes the problem it was meant to fix. No supplier pays me a commission or referral fee.

I am deliberately cautious about AI. Reading incoming invoices, classifying documents, drafting quote texts and searching internal procedures are realistic uses. None of them works well on unstable processes or unreliable master data, so they come after the foundations, with a documented answer to three questions: what data the tool may use, who checks its output and how errors are recorded. GDPR and works council questions about AI tools go to your data protection officer and HR. I attach no savings promises to AI, and suggest skepticism toward proposals that do.

You can engage me for the baseline and roadmap, or as a fractional lead while system houses deliver. Delivery is remote; visits happen only by arrangement. Further reading: my general approach to digital transformation, ERP consulting for German companies and SEO consulting in Germany. The Germany overview lists the rest.