top of page

WEF Next-Generation Computing Framework: Readiness Is Not an Investment Case

Writer: Brian Couzens
Brian Couzens
14 minutes ago
8 min read
Front cover of the linkedin carousel illustrated with a processor and data centre infrastructure

Computing capacity is not the same as computing value. Owning infrastructure is not the same as controlling it. A readiness score does not establish that an investment will deliver.

The World Economic Forum’s October 2026 paper, The Next-Generation Computing Framework, brings these questions into a coherent strategic discussion. It connects computing capability with energy, sovereignty, cybersecurity, skills and deployment.

The paper also defines its purpose. It is a diagnostic framework, not a league table or a complete investment appraisal.

At SITG-Consulting, our assessment is straightforward. The framework asks useful questions about national and organisational readiness. Before those answers become investment decisions, leaders need another layer of evidence.

What does the workload require? What does the commitment cost? Which dependencies could interrupt delivery? Who owns the decision?

We are not asking a strategic framework to become a financial model. We are asking leaders not to mistake one for the other.

What the WEF Next-Generation Computing Framework does

WEF describes next-generation computing as an evolving collection of advanced and emerging technologies, rather than a single technology or a wholesale replacement for established systems.

Its scope includes advanced AI infrastructure, high-performance computing, quantum computing, neuromorphic systems, edge and in-orbit computing, and biological or hybrid approaches. The report recognises differences in maturity, physical requirements, security risks and commercial pathways.

The framework combines six supply dimensions:

  • Compute and connectivity.

  • Infrastructure.

  • Data assets and governance.

  • Talent and skills.

  • Partnerships.

  • Cybersecurity and resilience.

A seventh dimension, deployment and diffusion, asks whether these capabilities create economic and social value.

Three enabling pillars run across the framework: sovereignty and interdependence, cybersecurity and resilience, and sustainability.

The distinction between supply and outcomes is important. Access to advanced computing creates an opportunity. It does not establish that an organisation has the skills, processes, suitable data or commercial demand needed to exploit it.

For business leaders, the useful question is not simply how much computing capability they have. It is what they can achieve with that capability, and what could prevent them.

Computing sovereignty: can you operate when access changes?

The paper makes a useful distinction between ownership and effective choice.

Its discussion of sovereignty considers where systems are hosted, how they are used, who controls data, how systems are updated and under what conditions an organisation can switch providers or exit an arrangement. It also connects sovereignty with continuity during disruption.

Domestic ownership cannot answer all those questions.

A locally hosted system can depend on external firmware, licences, maintenance, cloud services or specialist components. The report recognises these dependencies and examines operational control when suppliers become unavailable or access conditions change.

For an enterprise, sovereignty should therefore become a practical test.

Translate sovereignty into procurement questions

Before commitment, we would ask:

  • Which supplier permissions are necessary to keep the service operating?

  • What happens if an update, licence or support agreement becomes unavailable?

  • Can data and workloads move to a credible alternative?

  • How long would that move take, and what would it cost?

  • Which dependencies are shared by apparently different suppliers?

  • What evidence supports the continuity arrangements?

A contractual right to exit and a tested ability to exit are different things.

The report’s discussion of procurement recognises that interoperability, modularity, auditability, portability and exit rights can be established through contractual design.

Our recommendation is to assess those rights alongside the organisation’s ability to exercise them. A procurement decision should identify what the organisation acquires and which choices it retains.

Energy belongs in the investment case

The framework treats sustainability as an enabling pillar. It considers energy and infrastructure constraints, including siting, power and materials, as design-stage concerns rather than later adjustments.

For investment governance, capacity planning cannot stop at the processor specification.

Our proposed assessment would examine:

  • Power availability and the assumptions behind its cost.

  • Cooling and water requirements where applicable.

  • Site and infrastructure constraints.

  • Supporting systems needed to deliver the workload.

  • Expected utilisation rather than theoretical peak capacity.

  • The existing process or alternative technology used for comparison.

That comparison needs to be explicit.

A claim that a component is more efficient does not establish that the proposed operating model uses fewer resources or creates better value.

The assessment should compare defined workloads, service requirements and operating conditions. Otherwise, an efficiency claim can answer a narrower question than the investment committee thinks it answers.

For emerging technologies, we would also separate the resources needed to demonstrate technical feasibility from those needed for sustained operation.

A successful demonstration should not become a production-cost assumption without further evidence.

The investment question is not merely whether the technology performs. It is whether the organisation can operate it on acceptable terms.

Cyber resilience must shape the commitment

Cybersecurity and resilience appear both as a framework dimension and as a cross-cutting pillar.

This makes security part of the computing strategy, rather than a separate discussion after the technology has been selected.

Our enterprise application is to require security and continuity evidence before procurement.

For a significant commitment, leaders should establish:

  1. The essential service or business outcome.

  2. The dependencies needed to sustain it.

  3. The conditions under which those dependencies could fail.

  4. The recovery or substitution measures available.

  5. The evidence that those measures work.

  6. The accountable owner of unresolved exposure.

A strategy can recognise resilience without assigning responsibility for delivering it. An investment decision should not.

Supplier assurances also need a defined scope. A commitment to support migration does not establish compatibility, recovery capability or acceptable performance.

Those questions need documented requirements, testing and named owners.

Quantum readiness requires a separate assurance discussion

WEF places quantum computing within a wider landscape of emerging technologies. It acknowledges different maturity levels and commercial pathways.

We would preserve that distinction in enterprise planning.

Quantum computing adoption and post-quantum cryptographic assurance are related strategic concerns, but they should not be collapsed into a single maturity label.

One concerns whether a computing capability can support a workload. The other concerns the organisation’s cryptographic estate, dependencies, governance and transition evidence.

SITG’s Quantum Trust & PQC Assurance Services address evidence-led assessment of implementations, supplier claims, cryptographic dependencies and governance.

That is a defined assurance scope. It does not replace an assessment of the economics of a quantum computing investment.

Establish what the evidence supports

For cryptographic programmes, our proposed decision questions include:

  • Has discovery established the relevant assets and dependencies?

  • Is the evidence sufficient for the decision being made?

  • Which supplier claims have been independently examined?

  • Who owns remediation and migration decisions?

  • What demonstrates the ability to change cryptographic components?

  • How will the organisation identify regression after deployment?

Our article, Discovery Is Table Stakes for PQC. A CBOM Is Not Discovery, examines the distinction between a structured inventory and the evidence behind it.

A consistent format does not establish consistent assurance. Information can originate from scanning, questionnaires, vendor statements or manual records. Those sources can support different levels of confidence.

The same principle applies to readiness assessments. Before relying on a score, establish what its supporting evidence can justify.

Different technologies need different investment gates

The report recognises uneven maturity and different commercial pathways. Its technology-agnostic approach supports a broad strategic conversation.

That breadth also limits what a common readiness assessment can establish about a specific investment at a specific point in time.

Our recommendation is to separate deployment decisions from experimental decisions.

Deployment decisions

An investment case should identify:

  • The workload and baseline performance.

  • Capacity available to that workload.

  • Acquisition, integration and operating costs.

  • Security, continuity and supplier requirements.

  • Measurable benefits and the basis for estimating them.

  • Conditions under which the business case would fail.

The assessment needs to explain why this capability is appropriate for this workload. A general readiness score cannot supply that explanation.

Experimental decisions

An approval should identify:

  • The technical question being tested.

  • A measurable milestone.

  • A spending limit.

  • The evidence required at the review point.

  • Clear scale, pause or stop criteria.

An experiment can produce useful knowledge without producing a deployable service. That can be a legitimate outcome when the purpose and spending boundary are agreed beforehand.

Our article, Why PQC Vendors Are Not the Starting Point for Your Post-Quantum Transition, describes a gated transformation approach.

The governance principle applies here too: define the evidence needed to pass the gate before approving the next commitment.

A strong average can conceal a critical weakness

Consider a hypothetical assessment with three capability scores: 5, 5 and 1.

Their arithmetic mean is approximately 3.7 out of 5.

The calculation is correct. It does not establish that the capability scoring 1 is unimportant.

This is an illustration, not a WEF assessment. It shows why a summary score cannot answer all operational questions.

Our recommendation is to supplement readiness assessments used for investment decisions with minimum requirements for critical capabilities.

Depending on the workload, those requirements might concern continuity, security, data access, power availability or supplier substitutability.

The decision record should distinguish:

  • What is measured.

  • What evidence supports the measurement.

  • What remains uncertain.

  • Which weaknesses can be tolerated.

  • Which weaknesses block commitment.

A score can prompt investigation. It should not provide a reason to stop investigating.

The investment figures require clarification

The report gives two different figures for global computing infrastructure investment in 2025.

The executive summary, on page 4, states $448 billion. The introduction, on page 6, states $459 billion.

Both passages describe investment in computing infrastructure for the same year. The difference is not reconciled in those passages.

This does not invalidate the framework. It means that anyone reusing the figure should resolve the discrepancy rather than select a number without explanation.

The executive summary also forecasts investment exceeding $1.5 trillion by 2027.

That is a forecast attributed to the report, not an established outcome.

Before using it in a board paper or commercial model, we would verify the underlying sources, category boundaries and assumptions.

An aggregate infrastructure forecast does not establish that a particular workload, supplier or technology will deliver an acceptable return.

Precision matters when a headline becomes an input to a decision.

Turn the framework into an accountable decision

Our proposed enterprise application adds four responsibilities to the strategic discussion.

Business owner

Define the workload and the outcome worth funding.

Record a baseline before the pilot so that subsequent claims of improvement have a meaningful comparison.

The business owner should identify the value expected, the operational change required and the consequences of failing to deliver.

Technology and finance

Test capacity available to the workload, integration requirements, costs and power assumptions.

Record uncertainty rather than hiding it within a single forecast.

The assessment should distinguish measured performance, supplier estimates and planning assumptions. They should not carry the same evidential weight.

Risk and procurement

Require evidence of recovery, portability and workable alternatives to critical suppliers.

Identify which contractual rights have been tested operationally and which remain assumptions.

Document the residual exposure and who has authority to accept it.

Investment committee

Agree the review date, named decision owners and explicit scale, pause or stop criteria before committing further capital.

The committee should know what evidence would change its decision, not simply what evidence supported the initial approval.

For cryptographic transformation, our Cryptographic Agility Services address adaptability, cryptographic controls and readiness for algorithm and regulatory change.

These capabilities belong within a governed programme, with explicit responsibilities and evidence requirements.


Our assessment

The WEF Next-Generation Computing Framework deserves credit for connecting computing capability with sovereignty, energy, resilience and deployment.

Its diagnostic purpose is a strength. It supports a strategic conversation that would otherwise remain divided between technology, infrastructure, finance and risk teams.

Our contribution is the enterprise decision layer.

Before committing capital, add verified evidence, workload-level economics, named decision owners and clear scale, pause or stop criteria.

The question is not how impressive the proposed capability appears. It is which dependency could stop the organisation turning that capability into value.

For an evidence-led assessment of cryptographic risk, supplier claims and governance, explore SITG’s Quantum Trust & PQC Assurance Services.

 
 
 

Comments


bottom of page