Digital sovereignty: why the cost of dependency is never budgeted

Digital sovereignty has broad political and corporate support, but very little of it is turning into action. An analysis published this week argues that the gap has a simple cause: the costs of dependency on a few foreign technology providers do not appear in any standard business case.

A cost that stays off the books

When organizations compare IT options, the visible items dominate the spreadsheet: licence fees, migration effort, training and integration. What is missing is the price of being tied to one vendor, for example the loss of bargaining power at renewal time, the risk of sudden changes to terms or products, and the cost of having no realistic exit path. Because these items are not entered anywhere, the alternative that promotes sovereignty looks more expensive than it may actually be.

The analysis stresses that this is not an unsolvable problem. Dependency costs can be put into numbers, which means they can be built into procurement decisions and budgets instead of being left to appeals and strategy papers.

Why it matters

For public administrations and companies alike, the finding changes the debate. If sovereignty is treated as a vague value, it loses against concrete savings on a price list. If its absence is treated as a measurable risk with a price tag, decision-makers can weigh both sides on equal terms.

That is also a test for the many declarations of intent on digital independence. Without a transparent calculation, the pattern described in the analysis is likely to continue: broad agreement in principle, and unchanged purchasing habits in practice.

The next step for IT leaders and procurement teams is to add dependency to their own total-cost calculations, so the comparison with sovereign alternatives is complete.