From experiment to capability: AI adoption lessons from the Mittelstand

The Mittelstand – the dense network of small and medium-sized enterprises widely regarded as one of the defining strengths of the German economy – is built on world-class craft and specialization. Many Mittelstand companies are experimenting with AI. The most successful ones treat it not as a project, but as a capability they build themselves. That way they win twice: operational impact in the short term, independence in the long term. Their experience holds lessons for companies of all sizes — in Germany and beyond.

In many mid‑sized companies today, a similar picture emerges: several AI initiatives run in parallel, often for years, without being successfully absorbed into daily operations. At the same time, every one of these companies has pockets where AI quietly but reliably creates value. The difference between the two rarely lies in the tool, but in the approach.

Companies that generate tangible value with AI rarely have the fastest technology or the largest budget. They have something else: a clear view of where AI truly changes something in their processes, and the discipline to start exactly there.

The decisive question is therefore less “Which AI tool should we buy?” and more: How do we build the capability to integrate AI into our work for the long term and steer it ourselves? Those who answer this question win twice: operational effects visible in the first months, and a resilient independence that pays off year after year.

When AI really delivers in the Mittelstand

Before turning to the typical pitfalls, it is worth looking at what demonstrably works. Out of hundreds of projects, three factors consistently come together in successful AI applications.

First: a clear goal inside the process. Which concrete decision or action should AI make better, faster, or more reliable? “Cut the time from customer enquiry to finished quote in half so that sales can respond faster and with greater accuracy” is a goal teams can tackle immediately. And one against which success can be measured.

Second: the right data, understandable and reliable. The Mittelstand typically has rich operational data from ERP, MES, CRM, lab, and field systems. The leverage appears when the data points relevant to the specific use case are cleanly defined and stably available. That is usually far more focused and reachable than the much‑invoked “data cleanup across the whole company.”

Third: results where the decision is made. For classic operations use cases such as maintenance, quality, or planning, this usually means: directly in the ERP, MES, or CRM, i.e. where people are already working. For agentic applications in sales, procurement, technical support, or medical affairs, by contrast, the point of decision often sits outside the core systems: in the email inbox, the ticketing system, the document repository. Good agentic AI orchestrates those sources, prepares the decision, and flows the result back into the ERP or CRM. The rule is therefore not “always into the core system,” but: wherever the human decides.

Where these three elements come together, impact emerges that is measurable and scalable. That is not theory; it is the pattern behind the most successful AI initiatives we accompany in the Mittelstand.

Beyond the Mittelstand: four patterns that mark successful AI delivery

However different industries and maturity levels may be, companies that are making visible progress with AI attend to the same four themes. Each one is a step closer to the double win of operational impact and independence.

1. Enable the right people, not only the technologists

The greatest leverage does not sit in IT, but at the process.

A common assumption is that AI competence is primarily a matter of additional data scientists. In practice, the larger leverage emerges elsewhere: with the people who truly know processes, customers, and equipment. Process owners, key users, team leads, shop‑floor foremen.

This group brings exactly what makes AI projects take off: context. They know how a manufacturing order moves through the ERP, what sales decides first thing in the morning, and which supplier data can be trusted. When these people are deliberately enabled, in short, practice‑oriented sessions and on real use cases, a technical initiative becomes a working tool.

A typical pattern in practice: Data scientists and the business form joint tandems. Domain knowledge flows into requirements, AI results flow back into the process. The time from idea to first productive version typically halves, without additional tools or additional headcount.

2. Focus on a few, genuinely viable use cases

Two running use cases beat twenty planned ones.

“We have twenty proofs of concept.” That sounds like momentum, and in the early phase often is. The next step, however, decides whether experiments turn into impact: prioritize clearly, hand over ownership clearly, scale clearly.

Successful portfolios in the Mittelstand are deliberately lean: three to five use cases with visible leverage on core processes, each with a named owner and clear success criteria. Equally important is the culture of finishing things. When a pilot has exhausted its potential, or impact fails to materialize, it is deliberately closed and makes room for the next.

An illustrative picture from sales: Mid‑sized industrial equipment suppliers often have an inside sales team that simultaneously handles quote requests, spare‑parts enquiries, and service coordination. Instead of working on many ideas in parallel, successful approaches concentrate on one clearly defined step, for example pre‑qualifying incoming enquiries through an agentic assistant that pulls customer data from the CRM and proposes a first draft offer. The benefit shows up less in a single KPI than in the inside sales team being noticeably relieved and enquiries being answered more consistently.

3. Anchor AI directly where decisions are made

The “last mile” decides between “AI introduced” and “AI in use.”

Perhaps the most important lever sits in the “last mile”: how does the AI result reach the person who has to work with it? The companies that are consistent here do not build AI as a separate dashboard, but as a natural part of the workflow.

In practice: a notification in the existing system rather than an additional interface. Clear accountability for who decides on the basis of the forecast. A defined escalation when the model is uncertain. A “human‑in‑the‑loop” where experience makes the call. AI then becomes not an add‑on, but an extra pair of eyes and hands in daily operations.

An illustrative picture from procurement & supply chain: In technical wholesale, supplier risk is increasingly monitored agentically. An agent scans news, commercial register updates, and logistics data, evaluates changes, and on critical signals creates a task directly in the procurement system, including a recommended action and point of contact. The buyer still decides, as always. But knows sooner where to look.

4. Treat AI as a product, not as a project

Software projects have an end. AI systems do not.

This is a shift at first, but not a major hurdle when planned for from the start. Successful companies give their AI systems after launch the same attention they give their products: a responsible owner, an operating concept, regular quality checks, versioning, and cost control.

The effect is remarkable: the model stays reliable even as inputs or processes change. Trust in the systems grows steadily, and with it the willingness to extend AI into further areas.

A typical pattern in practice: Operating concept and ownership are built into development from the start, not bolted on after going live. Those who do this incur little extra effort. Those who have to add it later pay noticeably more. Experience points to two to three times the original development cost.

Doing AI, not just having AI

The four patterns share one thing: they shift the emphasis from “buying AI” to “doing AI.” And this is exactly where the Mittelstand plays to its strengths: closeness to the process, pragmatism, clear accountability, fast decisions.

Companies that stay ahead with AI build capability: teams that understand and steer AI; data products that are maintained and reliable; systems that run in everyday use, not in the test environment; and an operating logic that secures the value tomorrow as well.

That does not require a corporate apparatus. It requires focus: three to five use cases with real leverage on core processes, the right people behind them, and the decision to treat AI as a capability you develop, rather than a project you finish.

So the arc closes: those who build AI as a core capability win twice. In the short term through operational effects that become measurable in weeks and months: less downtime, faster quotes, sharper decisions. In the long term through an independence that makes them resilient to vendor fashions, market cycles, and the next technology wave. The Mittelstand brings everything needed for this path: depth of craft, closeness to execution, and a culture in which things count as finished only when they are running in operations.

Which of these four themes is currently moving you most in your AI work? We would be happy to exchange views with you, as peers and from the perspective of delivery.

---

This article was written by Philipp Diesinger, Partner at Rewire. His focus is on AI transformations that make the leap from pilot to productive operations: in life sciences, industry, energy, and the German Mittelstand.

Building your AI capabilities, end-to-end

Our strategies elevate the impact of AI from marginal or tactical to transformational successes.

Explore our AI strategy services