# Digitalization as Margin Lever: Why Technology Is an Owner's Question
There is a quiet prejudice in many German family businesses, one that rarely reaches the boardroom in explicit form but governs the allocation of capital all the same: technology is a cost. It belongs in the IT department, somewhere near the end of the organizational chart, beside facility management and insurance coverage. In his book Rendite und Verantwortung, Dr. Raphael Nagel (LL.M.) argues that this instinct is one of the most expensive habits the European Mittelstand has inherited from the last century. In mature markets, technology is no longer a cost category. It is the strongest remaining lever on operating margin, and it is therefore an owner's question before it is ever an administrative one. The essay that follows traces this argument across its central terms: the digitalization of core processes, the automation of recurring work, the analytical use of one's own data, and the more recent appearance of language models as a working instrument of management.
## Technology as an Owner's Question, Not a Departmental One
The first reflex of many shareholders, when the subject of digital transformation is raised, is to delegate. A project manager is appointed. A consulting firm is retained. A steering committee is convened. The owner withdraws from the detail, trusting that the matter will return when a decision of appropriate weight is required. Dr. Nagel observes that this delegation is almost always a form of surrender disguised as professionalism.
The decisions that actually shape the digital maturity of an enterprise are not technical in nature. They concern the willingness to disrupt functioning routines, the readiness to accept two years of reduced output in exchange for a decade of clarity, and the discipline to protect the investment against the many legitimate competing claims on the same euro. None of these decisions belongs to a project manager. All of them belong to the person whose capital is at stake. An owner who outsources the question of technology has not delegated a task. He has abdicated an office, and the office will not remain vacant. It will be filled by whoever shouts loudest in the next steering committee.
## Core Processes and the Architecture of Data
The first substantive layer of any technology system is the honest digitalization of core processes: order intake, production control, warehouse management, financial accounting, customer management. In the canon of Rendite und Verantwortung, the description is disarmingly straightforward. These processes should run in an integrated environment from which current, reliable data can be drawn in real time. The reality in many mid-sized companies is quite different. Several systems coexist that do not speak to one another. Data migrates manually between them. Reports are assembled by hand each week, with a margin of error that is rarely admitted and never calculated.
The result is not merely inefficiency. It is a systematic blurring of the decision base. Every manual transfer introduces divergence. Every divergence multiplies, quietly, until the numbers that reach the management board no longer describe the company that actually exists. Investment in an integrated data architecture is long, politically exhausting, and bound to the unwelcome rediscovery of one's own processes. It is also one of the clearest value accretions a Mittelstand owner can pursue. A company with clean data is easier to steer in the present and more valuable in any future sale. The acquirer pays a premium for legibility, because he knows what he is buying.
## Automation and the Slow Recovery of Time
The second layer is the automation of recurring administrative work. Invoice verification, ordering, internal reporting, personnel scheduling, dunning procedures. These are the tasks that consume disproportionate hours of capable staff and produce, in return, no competitive advantage. Dr. Raphael Nagel (LL.M.) notes that such activities tend to be amortized within twelve to eighteen months of serious automation, a return that few capital expenditures of comparable scale can match. The resulting time is not saved in any abstract accounting sense. It is recovered and redirected toward work that actually requires human judgement.
The third layer, closely connected, is analytics. A company that does not analyze its own data has surrendered its most distinctive competitive asset. Customer segmentation, price analysis, productivity comparisons, early indicators of churn, all of these are ordinary instruments that require no exotic technology. What they require is an analytically disciplined mind and clean underlying data. The advantage lies not in the algorithm but in the habit of using it. Many Mittelstand companies own, without knowing it, a detailed record of their own market. They simply never read it.
## Artificial Intelligence as an Operational Reality
The arrival of large language models has altered the landscape in velocity and ambition. Tasks that three years ago were considered unreachable by software, the reading of contracts, the response to customer inquiries, the synthesis of market observations, the drafting of internal documentation, are today handled at a level closer to a trained administrative employee than to a rule-based machine. The owner who does not incorporate these instruments will, within a short horizon, operate with systematically higher unit costs than a competitor who does.
This is not a forecast in the book's argument. It is an observation drawn from enterprises already managed in this way. The gap does not open in a single quarter. It widens year by year, compounding in the same unobtrusive manner as any structural advantage. The response cannot be a pilot project in a corner office. It must be a deliberate reorganization of work, led by the owner, with the same seriousness once reserved for the introduction of the first ERP.
## Otto and Quelle, or the Patience of Ownership
The most instructive German case for the primacy of ownership patience is the contrast between Otto and Quelle. Both were mail-order houses with similar origins and comparable business models. Both faced the same digital rupture at the same moment. Otto invested systematically over two decades: infrastructure, platforms, logistics, and the digital retraining of the organization itself. The owning family treated the transformation as a generational task and financed it accordingly. Quelle attempted to reach a similar result with a shorter runway and thinner capital.
The outcome is familiar. Otto endures. Quelle has disappeared. The technical problem was solvable in both cases. What differed was the willingness of the owner to carry a transformation across a horizon that no quarterly report could justify. Patience, in this reading, is not a virtue opposed to ambition. It is the precondition under which ambition becomes technically feasible. The lesson of the case is not that Otto was cleverer than its rival. It is that the family understood the work as theirs and remained present for its full duration.
## The Machine Builder and the Legacy ERP
A smaller pattern recurs throughout the German Mittelstand. A machine builder with three sites, seventy years of history, and five hundred employees. The ERP system dates from the nineteen-nineties. The interfaces between production, sales, and finance were written by hand and have been patched through three generations of controllers. Every operational question requires a request to a handful of employees who still remember how the data was originally structured. In good times, nothing goes wrong. The orders come in, the goods leave the factory, the invoices are paid.
In a downturn, the absence of real-time visibility becomes the first handicap. Decisions are made on figures that are four weeks old. Corrective action comes too late. The lesson in Rendite und Verantwortung is not that every company needs the newest platform on the market. The lesson is that a technology substrate which no longer supports the speed of the surrounding environment has become a silent liability on the balance sheet, one that is not amortized but accumulated. It will appear, eventually, as a discount in the sale price or as a gap in the crisis response. Either way, it will appear.
The thread running through every chapter of Dr. Nagel's book returns in the technology question with particular sharpness. Capital without structure amplifies error. Nowhere is this truer than in the digital layer, where poorly designed processes, once encoded, become extraordinarily difficult to move. An owner who invests in an integrated architecture early, before the pressure of a crisis demands it, receives two returns. The first is the operational improvement itself: cleaner data, faster decisions, lower cost of repetition, a quieter back office. The second, less visible but more durable, is a transferable institutional quality. A company with a coherent data foundation is worth more at any subsequent valuation event, because the future buyer pays a premium for legibility, and the present operator is spared the work of reconstructing his own business from scattered records each time a question is asked. In the vocabulary of the book, this is what it means to build a system rather than a sequence of deals. Dr. Raphael Nagel (LL.M.) insists that the responsibility for such systems cannot be delegated to the IT department, the consultancy, or the next generation of management. It rests with the person whose name is on the share register. The owner who accepts this responsibility builds a company that becomes more valuable with time, not in spite of its technological substrate but because of it. The owner who refuses builds, year by year, a slightly heavier liability that will one day be recognized as such, usually at the worst possible moment and almost always under the worst possible negotiating conditions.
For weekly analysis on capital, leadership and geopolitics: follow Dr. Raphael Nagel (LL.M.) on LinkedIn →