Tag: Europe

The Return of Industrial Time
For the last two decades, a lot of management culture has learned to think in software time.

Build. Test. Release. Measure. Iterate.

That operating logic changed how companies build products, how teams organize work, and how boards talk about speed. It made experimentation respectable in places that used to reward only long planning cycles.

My read on this: that lesson is still useful, but it is no longer enough.

A growing part of the strategic agenda is not moving on software time. Electricity grids, energy systems, ports, factories, semiconductor supply chains, defense production, railway capacity, industrial permitting, and resilient sourcing all run on a different clock.

They require capital before certainty arrives. They depend on permits, suppliers, safety, skills, land, regulation, maintenance discipline, and long-term demand signals. They take years to build and decades to amortize.

This is the return of industrial time.

The interesting leadership problem is not choosing between speed and patience. It is knowing which clock a decision belongs to.

The software clock changed executive expectations

Software gave leaders a powerful idea: speed can reduce risk.

If a team can release a small version quickly, observe real behavior, and adjust, it does not need to pretend that every answer is known upfront. That logic has shaped far more than product development. It influenced strategy processes, innovation portfolios, transformation programs, and investor communication.

The software clock is visible in how companies now talk about pilots, minimum viable products, agile delivery, platform thinking, data loops, and continuous improvement.

I think that mindset still has enormous value. Faster feedback improves capital allocation. Faster decision loops reduce internal friction. Better data can reveal what customers, suppliers, and employees are actually doing, not only what the organization hopes they are doing.

But the software clock also creates a temptation: the belief that every important problem can be de-risked through rapid iteration.

That belief breaks down when the strategic problem is physical.

You cannot A/B test a power grid in the same way you test a landing page. You cannot scale a defense-industrial base with the same reversibility as a software feature. You cannot rebuild semiconductor resilience quarter by quarter. You cannot fix underinvestment in infrastructure with a sprint review.

Industrial systems can and should become more digital, more transparent, and more adaptive. But their underlying constraints remain material. Increasingly, they come with a price tag and a lead time that no roadmap can compress.

Industrial time is slower because reality is harder

Industrial time is slow because physical capacity, permits and infrastructure cannot be compressed into software cycles.

Industrial time is not slow because managers are old-fashioned. It is slow because the work sits inside physical, financial, and institutional constraints.

Three numbers make the point.

Grids. The International Energy Agency has warned that grids risk becoming the weak link in the energy transition unless investment accelerates. Its grid report says annual grid investment needs to double to more than USD 600 billion by 2030, and new transmission lines routinely take 5 to 15 years to plan, permit, and complete. IEA Executive Director Fatih Birol put it bluntly: "We must invest in grids today or face gridlock tomorrow." In the United States, the Department of Energy's National Transmission Needs Study estimates the country must more than double regional transmission capacity by 2035. That is not a communications problem. It is a capacity problem.

Europe's investment gap. Mario Draghi's report on European competitiveness matters because it turns a familiar policy debate into an industrial-time problem. Its headline figure – roughly EUR 750-800 billion of additional investment per year – is not just a financing number. It is a statement about the scale of energy, defense, deep tech, infrastructure, and productivity capacity Europe would have to build. The report's core message is that Europe needs a different growth trajectory, not just better language around competitiveness. That lands as a management signal as much as a policy one.

Semiconductors. A chip ecosystem is not one factory. It is design capability, advanced tools, specialty chemicals, materials, packaging, testing, energy, talent, customers, and export-control exposure. The CHIPS Act logic itself reflects this: the United States put USD 52.7 billion behind domestic semiconductor manufacturing and research because capacity is a multi-year industrial problem. TSMC's Arizona build-out, which began as a USD 12 billion project and later expanded, is now reported as a USD 165 billion U.S. investment. In mid-2026, TSMC CEO C.C. Wei told shareholders it would be "a long time before we can meet customer demand".

Semiconductor capacity is an ecosystem of tools, materials, energy, talent and long ramp-up times.

The same pattern appears in defense. Europe can announce higher defense ambitions quickly, but ammunition output, supplier depth, testing capacity, skilled labor, and common procurement cannot be improvised. NATO's Jens Stoltenberg described the need to "shift from the slow pace of peacetime, to the high-tempo production demanded by conflict". That is industrial time in one sentence.

The binding constraint is no longer the speed of the interface. It is the speed at which physical capacity, capital, skills, and permits can be brought into being.

What this looks like inside companies

The point becomes clearer when you look at company cases.

Ford's electric-vehicle build-out is one example. A product with heavy software content still depends on battery plants, cell production, equipment orders, supply chains, trained workers, and industrial ramp-up. Ford described BlueOval City as part of its more-than-USD-30-billion EV investment through 2025. That is not a quarterly optimization exercise. It is a multi-year industrial bet.

Orsted is another. The company took an impairment of roughly USD 4 billion in 2023 and cancelled its Ocean Wind 1 and 2 projects in New Jersey after supply-chain inflation, higher interest rates, and permitting delays made fixed-price contracts uneconomic. CEO Mads Nipper pointed to "significant adverse developments" in the supply chain and said the company was "extremely disappointed" to cease the projects. The deeper point is that industrial-time projects front-load commitment, then absorb the variance of a multi-year supply chain.

Boeing shows a different version of the same issue. After the January 2024 737 MAX door-plug blowout, the FAA blocked Boeing from expanding 737 MAX production until quality systems were fixed. Demand was not the bottleneck. Industrial integrity was.

And TSMC's Arizona expansion shows why industrial capability cannot simply be copied from one geography to another. The company has had to manage cost and timeline pressure in the United States, with reporting around TSMC's Arizona build-out pointing to substantially higher U.S. construction costs than in Taiwan. A fab is not just a building. It is an ecosystem.

These are not failures of intelligence. They are encounters with a clock that does not negotiate.

The harder management problem: two clocks, one company

I do not think the answer is to become slower.

The harder task is integration.

A company that only thinks in industrial time becomes too slow. It over-plans, protects legacy processes, and treats every decision as irreversible. It may preserve reliability, but it loses learning velocity.

A company that only thinks in software time becomes careless. It mistakes optionality for strategy. It launches too many pilots, underestimates physical dependencies, and treats capital-intensive systems as if they can be refactored later without cost.

The way I see it, modern leadership needs both disciplines.

Digital speed matters where reversibility is high and learning is valuable: customer insight, forecasting, demand sensing, workflow automation, internal transparency, scenario modeling, and decision support.

Industrial patience matters where reversibility is low and execution risk compounds: plants, grids, logistics nodes, critical suppliers, regulatory approvals, safety systems, and long-lived assets.

The mistake is applying the wrong rhythm to the wrong problem.

Capital allocation becomes the test

The real management test is whether capital, skills and capacity line up before the next shock arrives.

Industrial time turns strategy into a capital-allocation test.

It is easy to endorse resilience in a board presentation. It is harder to fund redundant capacity, dual sourcing, inventory buffers, grid connections, cybersecurity hardening, supplier development, and workforce training before the next disruption makes the need obvious.

The same is true at national scale. The Draghi investment gap and the IEA grid investment number describe the same uncomfortable truth: agreement does not build capacity. Capacity follows from committed capital, credible timelines, aligned incentives, and operational ownership.

The question I would be asking myself is simple:

Where are we pretending that a strategic dependency is only an operating cost?

If energy availability can constrain growth, it is strategic. If a supplier bottleneck can stop production, it is strategic. If a missing skill base can delay execution for years, it is strategic. If regulatory approval, grid access, or logistics capacity determines market entry, it is strategic.

Industrial time makes these dependencies visible.

It also changes the meaning of efficiency. In software time, efficiency often means reducing waste, shortening cycles, and automating repetitive work. In industrial time, efficiency also means keeping enough capacity, redundancy, and competence to survive stress.

A system optimized only for the normal case can be financially elegant and strategically fragile.

Andreas's view

My read on this: the next advantage is temporal discipline.

The companies that do this well will not become nostalgic industrial planners. They will still use digital tools aggressively. They will use better forecasting, better data, better scenario models, and faster feedback loops to make long-cycle decisions less political and less blind.

But they will also recognize that some commitments have to be made before certainty arrives.

I don't think the next decade rewards organizations that simply move fast. It rewards organizations that know when speed is a learning tool and when early commitment is the real advantage.

Three things I'm watching:
- Whether Europe can turn the Draghi diagnosis into actual capacity: energy, defense, capital markets, compute, and industrial execution.
- Whether AI infrastructure pushes grid access, power contracts, cooling, chips, and data-center permitting into the center of corporate strategy.
- Whether companies start treating suppliers, energy, skills, and resilience as strategic assets rather than procurement line items.
The telling indicator will be whether management teams can hold both clocks in their head at the same time.

Move fast where learning is cheap. Commit early where capacity will be scarce. Use data to shorten decision cycles, but respect the physics of assets, infrastructure, and institutions.

The world is becoming more digital and more industrial at the same time.

That is the leadership rhythm I think matters now.

Sources

https://commission.europa.eu/topics/competitiveness/draghi-report_en

https://www.iea.org/reports/electricity-grids-and-secure-energy-transitions

https://www.iea.org/news/lack-of-ambition-and-attention-risks-making-electricity-grids-the-weak-link-in-clean-energy-transitions

https://www.energy.gov/oe/national-transmission-needs-study

https://www.semiconductors.org/chips/

https://pr.tsmc.com/english/news/3210

https://www.cnbc.com/2025/03/03/tsmc-to-announce-100-billion-investment-in-us-chip-plants.html

https://www.tomshardware.com/tech-industry/semiconductors/tsmc-ceo-c-c-wei-says-it-will-be-a-long-time-before-we-can-meet-customer-demand-tells-shareholders-that-he-will-keep-prices-stable-refrain-from-implementing-price-hikes

https://9to5mac.com/2023/08/04/us-made-tsmc-chips/

https://corporate.ford.com/articles/electrification/blue-oval-city/www/

https://www.cnbc.com/2023/11/01/orsted-axes-two-new-jersey-wind-projects-takes-4-billion-writedown.html

https://www.faa.gov/newsroom/faa-halts-boeing-max-production-expansion-improve-quality-control-also-lays-out-extensive

https://www.nato.int/en/news-and-events/events/transcripts/2024/02/15/press-conference
- European Commission: The Draghi report on the future of European competitiveness
- International Energy Agency: Electricity Grids and Secure Energy Transitions
- International Energy Agency: "Invest in grids today or face gridlock tomorrow"
- US Department of Energy: National Transmission Needs Study
- Semiconductor Industry Association: CHIPS Act overview
- TSMC: U.S. investment expanded to USD 165 billion
- CNBC: TSMC total U.S. investment reported at USD 165 billion
- Tom's Hardware: TSMC CEO C.C. Wei on customer demand
- 9to5Mac / NYT summary: TSMC Arizona construction-cost premium
- Ford: BlueOval City and EV investment
- CNBC: Orsted offshore wind impairment and cancellations
- FAA: Boeing 737 MAX production expansion halted
- NATO: Defense industrial production remarks
2026-06-28
Germany and France put digital sovereignty into operational terms
Germany and France have published a joint paper on digital sovereignty, dated 17 June 2026. It is only six pages long, but it does something useful: it gives the term digital sovereignty a set of testable criteria.

Europe has spent years talking about sovereignty in broad terms. The Franco-German paper asks a narrower question: when a government, company or public institution buys digital technology, what would make that technology more or less sovereign?

The paper does not pretend this is easy. It says digital sovereignty should be risk-based, modular and scalable. It avoids protectionism and isolation. It leaves defence and national security outside its scope. It creates no direct budget obligation and does not impose conditions on private procurement.

The document is cautious by design. That is useful for consensus. It is also the problem.

Germany and France are not proposing a simple "buy European at any cost" doctrine. They are proposing criteria that could feed into the EU Tech Sovereignty Package, including the Cloud and AI Development Act. If those criteria survive the legislative process, they could start shaping procurement, cloud architecture, sensitive-data handling and public-sector technology choices.

The paper's value is the checklist. Its weakness is that it stops there. It does not yet create the kind of aggressive investment push now visible in other regions.

The definition is broader than cloud

Digital sovereignty has to be assessed across the stack, from chips and networks to cloud platforms and AI.

The core definition is worth reading carefully. Digital sovereignty is described as the capability and capacity to develop, provide, use, adapt and control digital technologies, including hardware, in an independent, self-determined and secure manner.

Data location is only one part of it.

It includes hardware, software, data handling, AI, semiconductors, cloud, quantum, robotics, cybersecurity, standards, supply chains, skills and control over operational processes. The paper says critical dependencies exist across the entire stack, from IT infrastructure and semiconductors to software, data and AI.

This maps better to how dependency actually works.

Europe's dependency problem is scattered across the stack: hyperscale cloud, chips, operating systems, cybersecurity tools, AI models, productivity platforms, data infrastructure, technical standards, venture capital depth, and the ability to scale startups into global companies.

One datapoint stands out: in Europe's digital industrial ecosystem, most companies have fewer than 250 employees, based on the European Commission/JRC SME report cited in the paper. That captures one of Europe's structural problems. Europe has plenty of innovation. It has too few digital companies with global scale.

The six criteria matter most

The six criteria can be used in procurement, supplier reviews, architecture decisions and exit planning.

The paper defines six dimensions of digital sovereignty.

The first is the capability to implement and enforce. This is about whether Europe can apply its own legal and security conditions in practice. The criteria include EU-law compliance, transparency of ownership and subcontractor chains, disclosure of dependencies on third countries, restriction of sovereignty-critical extraterritorial data access, and the ability to investigate cybercrime and state-backed attacks.

The cloud debate often gets stuck here: legal jurisdiction and operational control do not always sit in the same place as the data center.

The second is the capability to design, deploy and use technologies. This includes scientific ecosystems for AI, microelectronics, robotics, data, quantum and cybersecurity; industrial demand for key technologies; research transfer; startup scaling; open source, open hardware and interoperability; and participation in standardisation.

Europe often underestimates this layer. Regulation can define the rules. It cannot replace the people, companies and institutions that build, operate, buy and improve the technology.

The third is economic value creation. The paper looks at where value is generated: R&D, engineering, skilled employment, operational control and contribution to the European technology ecosystem. It also explicitly allows partial value creation in trusted partner countries. That keeps the framework open enough to be economically realistic.

The fourth is protection of data. The paper calls on the European Commission to define the highest protection standards for the most sensitive data, including safeguards against cybersecurity risks and the effects of non-EU extraterritorial legislation. It also mentions mandatory privacy-enhancing technologies.

Sensitive data policy is now also industrial policy.

The fifth is substitutability and interoperability. The paper asks for modular architecture, open standards, open interfaces, software bills of materials, migration paths, exit concepts and multi-vendor strategies. In plain English: do not build systems that cannot be changed later.

For me, this is the most practical part of the paper. Lock-in rarely arrives as a crisis. It arrives as a procurement decision that cannot be reversed without years of cost and disruption.

The sixth is infrastructure resilience. The paper calls for sovereign data centers, AI, quantum and cloud computing infrastructure, interchangeable hardware and software stacks, diversified supply chains, secure and sustainable energy, high-performance networks and access to critical space resources.

Digital sovereignty depends on the physical layer too: data centers, energy supply, networks and resilience.

This links directly to the SoftBank France data-center story. Digital sovereignty now has a power, land, data-center and network dimension. The debate has moved well beyond data location and cloud labels.

The paper is careful, maybe too careful

The paper is politically careful. It is non-binding. It excludes defence and national security. It does not force public spending. It does not impose rules on private procurement. It stresses trade obligations, trusted partners and cost efficiency.

That makes it weaker than a real industrial plan. It also makes the document harder to dismiss as protectionism.

The gap is not definition. The gap is action.

The paper does not unlock capital. It does not create major public procurement demand. It does not accelerate data-center buildout, AI infrastructure, semiconductor capacity, cloud scale or startup growth. It gives Europe a framework for assessing sovereignty, but it does not yet give European providers the demand, reference customers or balance-sheet confidence needed to scale.

The paper does not argue for closing Europe off. Its more useful move is to make dependency measurable. Who owns the provider? Which subcontractors matter? Where is R&D located? Can the customer exit? Are open interfaces available? Can sensitive data be protected from extraterritorial access? Can Europe still operate if one supplier, jurisdiction or supply chain becomes unavailable?

These questions belong in procurement files, architecture reviews and risk discussions.

For enterprise leaders, digital sovereignty is becoming a procurement and architecture discipline. It will affect cloud strategy, AI deployment, data classification, supplier concentration, cybersecurity, exit planning and board-level risk.

For policymakers, a definition is useful only if it changes incentives. Europe needs procurement demand for sovereign solutions, faster scaling paths for startups, deeper capital markets, serious public-sector reference customers, and infrastructure policy that connects cloud, AI, energy, semiconductors and networks.

Without that, sovereignty stays a vocabulary exercise. Other regions are moving with capital, infrastructure, industrial policy and large anchor customers. Europe cannot answer that with criteria alone.

The executive takeaway

The Franco-German paper stops short of a sovereignty plan. It offers criteria. Criteria still matter because they shape what governments and large buyers start asking for. They shape tenders. They influence compliance teams. They tell suppliers what the next market standard may look like.

If Europe uses this framework well, sovereignty becomes less abstract: fewer lock-ins, clearer exit paths, more transparent supply chains, stronger data protection, more European value creation, and better infrastructure resilience.

If Europe uses it badly, it becomes another vocabulary layer on top of slow procurement and fragmented national initiatives.

My read: this paper is strongest where it is most practical. It connects sovereignty to ownership, enforceability, interoperability, data protection, value creation and infrastructure. It avoids the fantasy of full autarky. It accepts trusted partners. It treats sovereignty as a risk-based capability, not as a flag on a server.

But the next test is not another definition. It is demand.

Without procurement demand, budgets, infrastructure, reference customers and scale, European providers will stay small. Without scale, the dependency problem stays exactly where it is.

Bottom line: good start. Now Europe needs action.

Sources and further reading
- Franco-German Joint Paper on Digital Sovereignty, 17 June 2026
- BMDS: Germany and France present joint definition of digital sovereignty
2026-06-21
Model Dependency Is the New AI Business Continuity Risk
Claude Fable 5, model dependency risk, and why AI sovereignty is no longer only about where data lives.

Andreas's view

I would have liked more time with Claude Fable 5.

Not because a new benchmark table matters by itself. It does not. But because frontier models are now becoming operating infrastructure. When access disappears, the issue is no longer product disappointment. It is continuity risk.

The early description sounded like a model that pushed several practical boundaries at once: longer autonomous work, stronger coding, better vision, better long-context memory, more capable scientific reasoning. That is exactly the kind of model you want to test yourself. Not in a demo. In messy work. In a real harness. In the kind of workflow where you can feel whether the model changes what is possible.

Unfortunately, that window closed almost immediately.

Anthropic announced Claude Fable 5 and Claude Mythos 5 on June 9, 2026. The launch framed Fable 5 as a generally available Mythos-class model with safeguards, and Mythos 5 as the same underlying model with some safeguards lifted for trusted cyber and biology use cases.

Three days later, Anthropic added an update: access to Fable 5 and Mythos 5 was unavailable.

The follow-up statement is the more important business story. Anthropic said the US government had issued an export-control directive requiring it to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States. To comply, Anthropic said it had to abruptly disable both models for all customers. Other Anthropic models were not affected.

Based on Anthropic's public account, the directive was triggered by national-security concerns around model misuse; as of this writing, the government's full rationale has not been publicly detailed.

This is where the story stops being about one model release.

It becomes a preview of a much larger question: what happens when an enterprise builds critical workflows around a model that can disappear, degrade, fall back, become restricted, change policy, or become unavailable for reasons outside the enterprise's control?

The model is becoming part of the process

As AI moves into real workflows, the model becomes part of the operating process rather than a standalone tool.

Most companies still talk about AI models as if they were tools. You pick one, connect it to a use case, monitor cost and quality, and move on.

That framing is becoming too simple.

In real deployments, the model is increasingly part of the operating process. It sits inside support flows, developer environments, research workflows, compliance review, sales operations, procurement analysis, risk triage, security workflows, and internal knowledge systems.

The more capable the model, the more tempting it becomes to build around its specific behavior.

That is where the dependency starts.

A company does not only depend on the model name. It depends on latency, context length, tool use, refusal behavior, reasoning style, pricing, data-retention policy, regional availability, safety fallbacks, API contracts, rate limits, and the model's ability to work inside a specific harness.

The harness matters. A workflow may depend on prompt structure, tool calls, memory files, evaluation thresholds, orchestration logic, fallback assumptions, and human review steps. If the underlying model changes, the process can change with it.

Sometimes that is manageable. Sometimes it breaks the economics. Sometimes it changes the risk profile. Sometimes it simply means the workflow no longer works.

Fable 5 is a case study in availability risk

The Fable 5 launch itself was ambitious. Anthropic described strong performance in software engineering, knowledge work, vision, scientific research, long-context memory, and life sciences. It also described safeguards that would route some sensitive requests to Claude Opus 4.8 instead of allowing Fable 5 to answer directly.

That already shows the new shape of frontier AI products. The "model" is no longer a single stable object. It is a capability layer plus policy logic, classifiers, routing, monitoring, data-retention rules, trusted-access programs, and usage conditions.

Then came the suspension.

Anthropic said the government directive was based on national-security authorities and that it had to remove access for all users. It also said it disagreed with the action and believed that applying this standard across the industry could halt new frontier model deployments.

Whether Anthropic or the government is right is not the central issue for enterprise leaders.

The customer was not in control. Even a short-lived availability window is enough to expose the broader risk: pilots, evaluations, procurement decisions, and roadmap assumptions can all form around capabilities that may not remain available.

The sharper lesson is that access to frontier capability has become a business continuity variable.

The hidden risk: model concentration

Model concentration is becoming a real operational risk.

The risk is not that one provider has an outage. Enterprises already understand cloud outages. The risk is that AI capability is becoming more specific and less interchangeable.

If two models both answer emails, switching is easy.

If one model can run a long-horizon code migration, interpret screenshots, manage tool calls, maintain working memory, and reason through edge cases in a particular way, switching becomes harder. The replacement may be available, but the workflow may need to be redesigned.

That is a different kind of lock-in.

It is not only commercial lock-in. It is cognitive and procedural lock-in. Over time, the organization's workflows, prompts, review habits, and escalation paths start to conform to the model's strengths and weaknesses.

This will matter most in high-value use cases: engineering modernization, cyber defense, regulated research, legal work, finance analysis, industrial design, life sciences, and autonomous operations.

The more strategic the use case, the less acceptable it is to rely on a single model path with no tested fallback.

What enterprise architecture needs to change

A model continuity plan needs tested fallback paths, evaluations and escalation logic, not just a procurement preference.

The practical answer is not to avoid frontier models. That would be the wrong lesson.

The answer is to treat model dependency as architecture, not procurement.

Companies need a model continuity plan.

For every important AI workflow, leaders should know which assumptions are model-specific. What breaks if the model is removed? What happens if it falls back to a weaker model? What if data-retention rules change? What if the API remains available in the US but not in Europe? What if a safety classifier suddenly routes part of the work elsewhere?

This is not theoretical governance paperwork. It is operational design.

The risks are different, and they need to be named differently. An outage is not the same as a policy withdrawal. A safety-routing change is not the same as capability degradation. A regional access restriction is not the same as a pricing change. But all of them can alter a workflow that the business has started to rely on.

The better pattern is a portfolio:
- a primary frontier model for maximum capability
- a tested fallback model for continuity
- evaluations that measure task quality across model options
- abstraction layers that keep prompts, tools, memory and workflow logic portable where possible
- logs that show when fallbacks happen and why
- contracts that address availability, regional access, data policy and notice periods
- human escalation when model behavior changes materially
The important word is tested. A fallback that has never been used under realistic workload is not a fallback. It is a slide in an architecture deck.

The board-level questions are practical:
- Which AI workflows would stop if the primary model disappeared?
- Which fallbacks have been tested under real workload?
- Which model-specific assumptions are embedded in prompts, tools, policies and contracts?
- Who owns model continuity: procurement, architecture, risk or the business unit?
Why this becomes a sovereignty issue

AI sovereignty increasingly means asking who can interrupt a capability, not only where data is stored.

For Europe, this is where the story becomes uncomfortable.

AI sovereignty is often discussed as data residency, cloud location, compliance, or whether a model is hosted in Europe. Those questions matter. But they are no longer enough.

The Fable 5 episode shows another layer: model availability can be shaped by decisions outside the customer's jurisdiction.

A European company may comply with European law, host data in Europe, and still depend on an AI capability that can be changed or removed because of a US policy decision, provider safety decision, capacity constraint, licensing change, or export-control interpretation.

That does not mean every company needs to train its own frontier model. That would be unrealistic for most. It is also not an argument for isolationism or for purely national AI stacks.

It does mean Europe needs to think about sovereignty at the level of operating capability.

Can critical public-sector, industrial, defense, healthcare, financial and infrastructure workflows continue if a non-European model is restricted? Are there European or allied alternatives? Are there open-weight or locally deployable fallbacks for lower-risk parts of the workflow? Are procurement teams asking for exit paths? Are regulators looking at operational resilience, not only privacy?

The sovereignty question is shifting from "Where is the data?" to "Who can interrupt the capability?"

That is a much harder question.

The strategic lesson

I still would have liked to play with Fable 5.

That is partly curiosity. Frontier models are easiest to understand when you test them against real work. You learn more from one serious workflow than from a benchmark chart.

But the more important lesson is the one created by not being able to use it.

The future of enterprise AI will not be decided only by who has the strongest model. It will also be decided by who can build resilient operating models around unstable capability layers.

Models will improve. Policies will change. Access rules will shift. Providers will make safety decisions. Governments will intervene. Capacity will be constrained. Prices will move.

For CIOs, CTOs and risk leaders, the question is no longer whether to use frontier models. It is whether every critical AI workflow has a tested continuity path.

The companies that win will not be the ones that pretend this volatility does not exist. They will be the ones that treat model volatility as a design constraint from the beginning.

Sources and further reading
- Anthropic: Claude Fable 5 and Claude Mythos 5
- Anthropic: Statement on the US government directive to suspend access to Fable 5 and Mythos 5
2026-06-14
AI Funding Is Turning Into Infrastructure Capital
Crunchbase‘s April report reads, at first, like one more data point in the AI boom. Global venture funding hit $56 billion in April 2026 – the third-biggest month in a year, and roughly double April 2025. AI took $37 billion of that, about two-thirds of all venture money in the month.

What matters is where the money went. Two rounds did most of the work. Anthropic raised $15 billion. Jeff Bezos’s Project Prometheus, aimed at AI for manufacturing and the physical world, raised $10 billion. Together they accounted for 45% of all venture funding in April. Five weeks later, on 28 May, Anthropic closed a $65 billion Series H at a $965 billion valuation – the largest equity round ever raised by an AI company, and enough to pass OpenAI as the most valuable startup in the world.

These rounds work differently from the software rounds that came before them. Venture capital has started to behave like strategic industrial capital, and the AI race has become a contest over who can assemble enough capital, compute, power, data, and industrial access to own the next operating layer of the economy.

The money is pooling at the top

The headline funding number can rise while the market underneath it narrows.

Venture has always followed a power law: a few companies take most of the returns. April pushed that to an extreme. Through April, global venture investment was up 139% year over year, and nearly 60% of that capital went to just five companies – most of them backed by cash-rich public tech firms, private equity, and the largest VC funds. Q1 looked the same: OpenAI ($122 billion at an $852 billion valuation), Anthropic, xAI, and Waymo took roughly two-thirds of all global venture funding between them.

This changes what the funding totals tell you. In an ordinary cycle, rising funding signals broad risk appetite – more founders backed, more categories opening, more experiments running. Right now the total can climb while the market narrows underneath it. Plenty of money is flowing, but it reaches very few companies, and the ones it reaches have started to look like national-scale infrastructure projects.

That is why the comparison to past SaaS or internet cycles falls apart. A $15 billion AI round belongs to an entirely different category of capital formation than even the largest software growth round.

Models have become capital assets

A frontier model is no longer just an algorithm. It is a capital asset tied to compute, chips, cloud and distribution.

AI model companies raised $26.7 billion in April – by far the largest single category, ahead of physical AI ($5.3 billion) and AI infrastructure like chips and data centers ($1.8 billion).

The reason is structural. Frontier labs are expensive in ways software companies never were: they need long compute contracts, data-center capacity, advanced chips, large engineering and safety teams, enterprise sales, and deep ties to the hyperscalers. They sell software and spend like heavy industry.

The cloud era made infrastructure feel weightless. You rented compute, scaled on demand, and built globally without owning anything. AI has partly reversed that. Compute has turned back into a scarce, physical input that decides who can compete, so the companies with privileged access to chips, power, and distribution hold a real structural edge. That is why hyperscalers, sovereign funds, and private equity keep moving closer to the center of AI financing.

Anthropic‘s Series H is the clearest example. Look at who funded it: alongside the crossover investors sit the companies that supply the infrastructure Claude runs on – the cloud it trains on, the memory chips that serve its inference. Those backers have a direct operating interest, since their own businesses grow as Anthropic grows. A model company has become a capital asset that its own suppliers want a stake in.

Physical AI is the second signal – and maybe the bigger one

Physical AI shifts the question from digital productivity to industrial leverage.

The Prometheus round may matter more than Anthropic‘s, even though it is smaller. Anthropic represents the frontier-model race. Prometheus points to the phase after it: AI moving out of language and code and into engineering, manufacturing, robotics, aerospace, automotive, and physical production. Crunchbase counted about $5.3 billion of April’s AI funding as physical AI – a small slice today, with an outsized claim on the real economy.

For a few years, AI has mostly been a knowledge-work story: it writes, summarizes, codes, plans, and automates digital tasks. The physical-AI bet says the next contest is over the industrial system itself – compressing engineering cycles, simulating physical systems, optimizing factories, improving robotics, speeding up materials discovery. If that works, the real value sits in industrial leverage: how quickly companies can design, test, and build physical things.

That also explains the capital intensity. Industrial AI demands labs, data rights, robotics environments, manufacturing partners, domain experts, and access to the messy operational data inside real companies. The winner here will probably be whoever can wire models into real factories, supply chains, machines, and the proprietary data that sits inside them.

Public and private markets are now one loop

The April data also shows how tightly public markets, private markets, and the wider economy are now linked. Alphabet, Microsoft, and Amazon all beat revenue expectations while spending heavily on AI infrastructure. Pantheon Macroeconomics estimates that about half of the 2% U.S. GDP growth in Q1 came from AI buildout. That figure is large enough to matter: AI now shows up directly in the macro data.

The result is a feedback loop. Public tech companies throw off cash and market value. Those balance sheets fund compute and strategic investments. The investments flow into private AI companies, which buy more infrastructure, which lifts hyperscaler revenue and capex again. For now, the loop is strong.

The risk is that it makes AI look broader than it is. When a few capital-rich companies drive both the public-market narrative and the private-market totals, the whole ecosystem leans on a small set of balance sheets and assumptions. The boom is genuine, and it is also concentrated, circular, and dependent on a narrow base of infrastructure.

What this means for Europe

U.S. companies raised $39 billion in April, around 70% of global venture funding. For Europe, the clean comparison is not AI-only funding; it is total venture/startup funding on the same monthly basis. A Crunchbase-based European VC landscape dataset counted $4.8 billion across 327 European investments in April, while Tech.eu counted €5.1 billion across 290 European tech deals. Even allowing for methodology differences, Europe was roughly a one-tenth-of-global market while the U.S. took about 70%. That should sting.

The usual European AI debate is about regulation, foundation models, talent, data, and digital sovereignty. All of it matters. April adds a dimension that gets less attention: capital sovereignty. If AI leadership now takes tens of billions for models, data centers, chips, power, and industrial deployment, then good research and sensible rules will not be enough on their own. Europe also has to mobilize capital at the scale and speed the technology demands.

This is where the Draghi competitiveness argument gets concrete. Europe cannot regulate its way to AI relevance, and it cannot research its way there either while its capital, compute, and adoption stacks stay fragmented.

The position is far from hopeless. Europe has real industrial depth – manufacturing, automotive, aerospace, energy systems – in exactly the domains where physical AI could matter most. That strength does not convert into AI advantage automatically. It has to be connected to capital, compute, data-sharing arrangements, procurement, and faster decisions. Otherwise the industrial data and engineering know-how that should be Europe’s edge will be monetized through platforms funded and controlled elsewhere.

The question for leaders

For executives, the useful question is what kind of market is being built, and whether their company has a place in it. If AI funding is becoming infrastructure capital, then AI strategy belongs in the boardroom as a question about strategic dependency:
- Who controls the models you rely on?
- Who controls the compute?
- Who owns the industrial data?
- Who has the capital to build at scale?
- Who can turn AI capability into operating-model change faster than you can?
This matters most for companies outside tech. Many industrial, financial, logistics, healthcare, and public-sector organizations still treat AI as a vendor-selection exercise, and that framing is too small. The real question is where you sit in the emerging AI capital stack – as a buyer of capability, a supplier of domain data, a deployment partner, a regulated adoption environment, a business whose workflows get compressed by someone else’s model, or a company that uses AI to redesign the economics of its own industry.

What I’m watching next

Three signals matter more than the next monthly funding total.
1. Concentration. If capital keeps pooling in a few frontier-model and infrastructure companies, the AI market will increasingly resemble a strategic infrastructure race.
2. Physical AI. If funding for robotics, manufacturing, and autonomy accelerates, AI starts reshaping the industrial economy, well beyond office work.
3. Europe. If the continent stays strong on regulation and weak on capital mobilization, the sovereignty debate stays rhetorical.
April’s data points to an AI economy that is becoming more capital-intensive, more concentrated, and more physical. The next phase will be won by whoever can put the full stack together: capital, compute, energy, data, industrial access, distribution, and execution speed. That is a different kind of technology race, and it is already running.

Sources: Crunchbase, “Billion-Dollar AI Rounds Push April To Third-Highest Startup Funding Month In A Year” (5 May 2026) and the Q1 2026 global funding report; Trustventure, “European Venture Capital Landscape – April 2026”; Tech.eu, “April 2026’s top 10 European tech deals”; Anthropic’s Series H announcement and reporting from Axios, CNBC, TechCrunch and Fortune (28 May 2026); GDP estimate from Pantheon Macroeconomics.

Sources and further reading
2026-05-31