GCC GPU-as-a-Service Platforms: Sovereign Demand and Third-Party Revenue Quality

Introduction

GPU-as-a-Service platforms convert accelerated-computing infrastructure into contracted or usage-based services. The operating proposition combines scarce computing hardware, high-density data-centre capacity, power, networking, orchestration software and customer support. In the GCC, the proposition also sits within national programmes for digital sovereignty, economic diversification and artificial-intelligence capability. This strategic setting can accelerate capital formation and customer access. It also creates a diligence question: which part of demand reflects enduring third-party willingness to pay, and which part depends on sponsorship, related-party procurement or policy allocation?

The distinction matters to valuation and financing. Sponsor-backed demand may be contractually strong, yet concentrated in one public-sector budget, one parent group or one policy programme. State-linked enterprise demand may be commercially negotiated while still sharing common ownership or procurement direction. Independent customers may provide stronger evidence of product-market fit, but their commitments can be shorter, more price-sensitive or exposed to workload migration. The revenue model must preserve these differences instead of treating every signed amount as equivalent.

The framework below follows the transaction from ownership and customer classification through contracts, capacity, utilisation, margin, cash conversion and valuation. Public disclosures provide context. Platform-specific conclusions require executed agreements, procurement files, acceptance records, invoices, bank receipts, telemetry, power documents, equipment records and financing agreements. The worked case supplies a transparent model for applying the framework; every figure is hypothetical.

1. Define the board or investment decision

Fix the decision before collecting data. A board may be approving expansion, an investor may be pricing equity, and a lender may be sizing debt. Each decision requires a valuation date, legal perimeter, currency, return threshold, financing assumptions and downside tolerance. The platform may span a holding company, national operating entities, equipment vehicles, data-centre leases and customer-contracting entities. The analysis should identify which entity owns hardware, controls power, employs operating staff, invoices customers and grants security.

Create a sources-and-uses schedule and legal-entity map. Classify leases, equipment finance, customer prepayments, restricted cash, shareholder funding and committed capital. The committee record should state which strategic benefits are inside the valuation and which remain sponsor objectives. This prevents announced ecosystem value from being counted as distributable cash flow.

2. Map ownership, sponsorship and procurement influence

Sovereign sponsorship can appear through ownership, guarantees, land, power, procurement direction, grants, tax support or access to international suppliers. Map each form separately. Common ultimate ownership across the operator and customer can create related-party or quasi-related exposure even when the contracts sit in different legal entities.

For every material customer, record the ultimate parent, government nexus, procurement authority, tender route, budget source and decision-maker. Review whether the service was competitively procured, mandated, directly awarded or bundled with a national programme. The purpose is commercial classification, not a judgement on public ownership. The valuation should show how revenue changes if a policy allocation, budget or sponsor instruction changes.

3. Classify customer independence

Use six customer groups: sovereign sponsor, government entity, state-linked enterprise, domestic private customer, regional third party and international third party. Classification should reflect economic decision-making and cash source, not the logo on the contract. A private reseller funded entirely by a sponsor allocation may remain sponsor-dependent; a listed state-linked enterprise with independent procurement and payment can carry different evidence.

Maintain both legal-customer and economic-customer identifiers. Measure revenue, committed value, receivables, usage, gross margin and renewal by group. Disclose judgement cases and the evidence used. Independent third-party adoption is strongest when procurement is arm's-length, the customer pays from its own budget, service is accepted, usage repeats and renewal is supported by workload economics.

Proposed framework unless stated otherwise.

4. Separate commercial document states

A press release, memorandum of understanding, reservation, order form, master agreement and accepted service are different states. Create a document ladder: announced opportunity, non-binding memorandum, reserved capacity, executed minimum commitment, deployed service, accepted service, billed service, collected cash and renewed service. Each state has distinct conditions and cancellation risk.

Abstract legal customer, term, committed quantity, price, delivery condition, acceptance, service levels, credits, termination, change of control, renewal and payment. Reconcile contract values to the revenue ledger and bank. An executed order should enter the committed case according to its conditions. Optional consumption and unsigned expansion belong in separately labelled scenarios.

Proposed framework unless stated otherwise.

5. Reconcile announced demand to enforceable revenue

Public announcements can combine infrastructure investment, potential capacity, partner sales and national demand. Rebuild the operator's stated number from contract-level records. Remove duplicates between framework agreements, customer reservations and channel forecasts. Identify amounts conditional on capacity, export approval, customer funding or performance acceptance.

Produce a waterfall from announced value to enforceable minimum, accepted value, billed value and collected cash. Keep currency translation, tax, credits and pass-through items separate. The hypothetical case reduces USD 1.80 billion of stated value to USD 1.28 billion after contract, delivery, acceptance, credit and collection adjustments. This is a modelling example, not an observation about an identified operator.

6. Test sovereign offtake quality

Sovereign offtake can provide long tenor and strategic support. Its value depends on the contracting authority, appropriation, termination rights, payment process, service acceptance and remedies. A policy objective does not replace an enforceable payment obligation. A ministry, procurement body, sovereign fund and state-owned enterprise can have different legal and budget characteristics.

Review authority, approvals, budget coverage, governing law, dispute process, assignment, set-off and payment history with qualified advisers. Test whether volume is take-or-pay, reserved, consumption-based or subject to annual work orders. Model delayed acceptance and delayed payment. Treat guarantees and support letters according to their actual wording, cap, term and enforceability.

Proposed framework unless stated otherwise.

7. Test state-linked enterprise demand

State-linked enterprises can be commercially sophisticated anchor customers. They can also create correlated exposure when ownership, sector budgets or national programmes align. Aggregate customers by ultimate parent and common funding source. Review whether the enterprise selected the platform through competitive procurement and whether its workload can migrate.

Analyse unit price, service levels, payment, credit and usage against comparable private customers. Identify cross-default, group-negotiated pricing and common renewal dates. A state-linked customer that repeatedly expands paid workloads after acceptance provides stronger evidence than a one-time allocation. The model should show this progression explicitly.

8. Test independent third-party adoption

Independent demand should be demonstrated through customer-controlled procurement, arm's-length pricing, accepted service, recurring usage and collection. Segment customers by enterprise, startup, research, hyperscaler, channel and international origin. New-customer count alone can mislead when trial credits, reseller aggregation or one workload drives activity.

Build cohorts by first billable month. Track conversion from trial to paid, expansion, contraction, churn, gross retention, net retention, contribution margin and cash collection. Identify the workload and replacement alternatives. A repeat purchase after the initial project, made without sponsor subsidy, is valuable evidence of commercial adoption.

9. Measure concentration and common-cause risk

Calculate top-one, top-three and top-five shares for committed value, recognised revenue, gross margin, receivables, capacity and renewal timing. Aggregate by government nexus, ultimate parent, sector, workload, channel, site and currency. Several legal customers can share one budget or programme and therefore one economic risk.

Map correlated events: budget revision, export restriction, power delay, model migration, channel failure or common renewal. Estimate replacement time, sales cost, reconfiguration and idle capacity if a major cohort leaves. Concentration can support initial financing, while equity value remains sensitive to the cost and timing of replacement.

10. Build the contract-quality ladder

Score contracts on enforceable minimum, duration, credit, delivery conditions, acceptance, service remedies, price adjustment, termination, renewal and security. The output should remain a transparent evidence ladder rather than a single opaque score. Contract quality also changes over time as delivery, acceptance, billing and collection occur.

Create a monthly movement schedule between document states. A contract moves upward only when evidence is complete; disputes, credits or termination notices can move it downward. Debt sizing may use a narrower eligible-contract definition than equity valuation. The committee should approve both definitions and the haircuts between them.

11. Test pricing and arm's-length economics

Compare unit pricing by GPU type, reservation structure, term, geography, service bundle, support level and customer group. Separate compute price from storage, networking, orchestration, support, power and taxes. Sponsor pricing below full economic cost can accelerate adoption while weakening stand-alone value; sponsor pricing above market can impair renewal.

Reconcile list price, contracted price, invoiced price and collected price. Adjust for credits, free periods, channel rebates and minimum-volume shortfalls. Use external quotations only when product, availability and service are comparable. The forecast should show margin at the contracted price and the price required for replacement demand.

12. Reconcile usage, billing and collection

Telemetry, scheduler records, customer portals, invoices and bank receipts should tell one story. Define available, reserved, delivered, accepted, billable and paid GPU hours. Maintenance, failed jobs, internal use, free trials and service credits reduce conversion. Validate a sample from job record through meter and invoice to bank.

Analyse days to acceptance, invoice timing, disputes, days sales outstanding and cash application by cohort. A customer with high reservation and low paid use may generate minimum revenue today but face renewal risk. A customer with rising paid utilisation and timely cash provides stronger evidence of value.

13. Build the GPU cohort ledger

Record each material cohort's architecture, configuration, quantity, serial evidence, acquisition cost, delivery, commissioning, warranty, workload fit, financing, utilisation and refresh plan. Supporting networking, storage and cooling can constrain usable service before nominal GPU count does. Record failed, idle, reserved and billable units separately.

Link every cohort to sites and customers. Reconcile title and liens to invoices and security documents. Model maintenance, replacement and residual recovery by cohort. The commercial case should fund enough refresh capital to perform contracts through their terms; accounting carrying value and economic recoverability should remain separate schedules.

Proposed framework unless stated otherwise.

14. Map capacity and power states

Separate announced, planned, permitted, power-contracted, energised, commissioned, customer-usable and accepted-billable capacity. Public programmes can describe ultimate scale while current revenue depends on a smaller operating base. Each state should have evidence, remaining capital, earliest date and responsible counterparty.

Review connection agreements, supplier contracts, data-centre capacity, cooling, network, construction milestones, securities and curtailment. Link customer delivery dates to the relevant capacity state. In the hypothetical case, 92 MW announced becomes 31 MW accepted and billable; the difference retains option value only after cost, timing and delivery probability are recognised.

15. Test chip supply and export dependencies

Advanced accelerators can require supplier allocation and government authorisation. Record orders, deposits, cancellation rights, delivery schedules, destination, end-use conditions, warranties and software dependencies. Review current export and import requirements with qualified counsel and update the model when rules or licences change.

A purchase announcement is not installed capacity. Model delayed approval, partial delivery, configuration change and higher integration cost. Customer remedies should be linked to the affected cohort. Avoid assuming substitute hardware has identical performance, software compatibility, power density or customer acceptance.

16. Model utilisation by customer cohort

Build monthly cohorts using the first accepted billable month. Show reserved, minimum, variable and actual use. Separate training, inference, fine-tuning, research and internal workloads because cluster size, network intensity, duration and price can differ. Preserve operating headroom and redundancy.

The utilisation curve should show ramp, steady state, contraction, renewal and redeployment. Do not allow the same spare capacity to support multiple independent opportunities. Reconcile the weighted curve to physical capacity and billing. The hypothetical central case reaches 72 per cent billable utilisation; the downside reaches 52 per cent.

17. Calculate customer-level contribution margin

Revenue quality includes margin after the costs required to serve the customer. Allocate power, facility, network, orchestration, support, service credits, sales commissions and directly attributable maintenance. Show depreciation, leases, refresh capital and financing below the contribution measure so that users understand each layer.

Compare sponsor, state-linked and independent cohorts on consistent definitions. A high-volume anchor can have lower unit economics but support capacity delivery. A smaller international customer can provide price discovery and diversification. The portfolio decision should reflect both roles and the cash required to sustain them.

18. Build the contract-to-cash schedule

Forecast each executed tranche monthly from delivery and acceptance through billing and collection. Include minimums, variable use, escalation, credits, taxes, currency and payment lag. Unsigned expansion and renewal remain separate cases. Reconcile forecast opening balances to contract, receivable and deferred-revenue ledgers.

The cash schedule should identify the first month when liquidity, covenant or supplier payment becomes tight. Link delays to working capital rather than moving revenue alone. This schedule becomes the common operating case for valuation, debt sizing and transaction protections.

19. Build the capacity-to-cash schedule

Connect each customer tranche to site, power, GPU, network, commissioning and acceptance. Record remaining capital and supplier payments. A megawatt should not support cash until the relevant equipment and service have passed customer conditions. Apply delivery probability to pre-operational capacity.

The schedule should reveal circular dependencies: supplier deposits require financing, financing requires offtake, and offtake starts after delivery. Resolve the circle through committed equity, sponsor support, customer prepayment, milestone debt or staged procurement. Model refund and restriction terms for every prepayment.

20. Map financing, leases and prepayments

GPU platforms can use equipment finance, project debt, leases, shareholder facilities, vendor credit and customer prepayments. Capture borrower, security, amortisation, covenants, guarantees, cash sweeps, reserves and change-of-control. Link each claim to its assets and cash flows.

Compare debt tenor with contract term and equipment life. Identify cross-collateralisation and trapped cash. Customer prepayments can fund equipment while creating delivery or refund obligations. The enterprise-to-equity bridge should deduct claims according to legal priority and economic substance.

Proposed framework unless stated otherwise.

21. Apply revenue and asset accounting evidence

IFRS 15 supports analysis of enforceable contracts, performance obligations, transaction price and revenue recognition. IAS 16, IAS 36 and IFRS 16 inform equipment, impairment and lease evidence. IFRS 13 informs fair-value methods. Accounting does not replace commercial diligence, but reconciliations can expose differences between stated backlog, recognised revenue and asset recoverability. ^{[15][16][17][18][19]}

Obtain policy papers, contract assessments, impairment models, lease schedules and audit differences. Reconcile management metrics to statutory accounts. Keep accounting remaining performance obligations distinct from wider sales backlog. Adjusted measures should have a bridge to reported figures and stable definitions.

22. Assess data sovereignty, cyber and operating control

Customers can require local data processing, access control, encryption, audit, incident response and personnel restrictions. Map each obligation to architecture, site and subcontractor. A sovereign platform can still depend on foreign software, hardware, support or control planes; identify these dependencies.

Use current national requirements, contracts and recognised cyber frameworks. Test identity, privileged access, logging, isolation, backup, recovery and incident evidence. Price required remediation and service interruption. Commercial quality includes the operator's ability to perform its promises securely and repeatedly.

23. Test channel and hyperscaler dependence

A platform may reach customers through cloud marketplaces, resellers, systems integrators or global technology partners. Channels can accelerate distribution while concentrating economics and customer ownership. Record who controls pricing, billing, support, data, renewal and termination.

Separate end-customer demand from channel commitment. Measure gross-to-net revenue, receivable risk, customer visibility and churn by route. Ooredoo's disclosed hyperscaler concentration illustrates why infrastructure operators should report both operating scale and customer mix. Company disclosures require transaction-specific verification. ^[6]

24. Triangulate enterprise value

Use discounted cash flow, billable-capacity references and relevant market references on consistent definitions. The DCF should use the contract-to-cash and capacity-to-cash schedules. Capacity references should value accepted billable service differently from planned megawatts. Market references require adjustments for customer independence, utilisation, power, hardware age, geography and claims.

Reconcile methods rather than averaging them. Show how value changes with billable utilisation, contribution margin, renewal, delivery and refresh capital. Strategic sponsorship may support delivery probability; it should not create a premium twice through both cash flows and a separate strategic uplift.

25. Build the enterprise-to-equity bridge

Start from enterprise value and deduct debt, leases, equipment claims, restricted amounts, refund exposures, unpaid capex and other debt-like items; add unrestricted excess cash only after availability is confirmed. Allocate claims by legal entity and security. Include transaction costs and working-capital mechanics where relevant.

The hypothetical central case uses USD 1.15 billion of enterprise value and USD 0.49 billion of claims, producing USD 0.66 billion of equity. The downside uses USD 0.48 billion of enterprise value and USD 0.52 billion of claims, producing no equity recovery. These assumptions illustrate claim sensitivity and describe no identified business.

Proposed framework unless stated otherwise.

26. Run a combined downside

Combine risks that share causes. A delayed export approval can delay equipment, acceptance, billing and customer renewal. A power delay can strand hardware and increase financing cost. Lower independent adoption can increase sponsor concentration and weaken price discovery. Model these interactions together.

The hypothetical downside assumes delayed approvals, a ten-month commissioning delay, sponsor-volume reset, 52 per cent utilisation, weaker renewal and higher financing claims. Report minimum liquidity, covenant headroom, required equity and recoveries. The decision should state the maximum tolerable downside and the evidence that would change it.

27. Convert findings into transaction protections

Translate evidence gaps into conditions, price mechanics, escrow, earn-outs, covenants, capital commitments, customer consents, supplier milestones and walk-away criteria. Every protection needs a measurable trigger, data source, calculation agent, dispute process and long-stop date.

Possible protections include consideration linked to accepted billable capacity, an earn-out based on independently collected third-party revenue, committed sponsor equity for remaining infrastructure, customer-consent conditions and reserves for refunds or service credits. Counsel should align the mechanism with local law and transaction structure.

28. Establish the first-one-hundred-day revenue-control system

The operating dashboard should reconcile contract state, customer independence, accepted capacity, billable utilisation, contribution margin, receivables, cash, power, incidents and financing weekly or monthly. Name data owners and exception thresholds. Require signed evidence for movements between states.

Priorities are to close ledger gaps, stabilise billing, resolve acceptance, secure power and supplier milestones, build independent pipeline and govern capital. The board should review sponsor and independent cohorts separately. A platform earns a stronger valuation when strategic support and repeatable third-party economics are both visible in the same controlled system.

Proposed framework unless stated otherwise.

Appendix A. Integrated revenue-quality model

The framework has three deliberate limitations. First, public announcements and company releases establish strategic context; they do not prove the terms, utilisation or collection performance of a specific platform. Second, customer independence is a commercial classification that requires transaction records and governance evidence; ownership alone does not determine contract quality. Third, accelerator markets, export rules, power arrangements and software economics can change rapidly. Valuation inputs therefore require a stated date, source and update trigger. Qualified legal, accounting, technical, cyber and tax advisers should review the matters within their disciplines.

The evidence hierarchy gives precedence to executed contracts, regulatory approvals, acceptance records, invoices, bank receipts, telemetry, title and financing documents. Audited financial statements and controlled management reports provide reconciliation. Public statements and third-party market information provide context. Where sources conflict, the model records the difference and avoids forcing an unsupported resolution. This hierarchy keeps strategic narrative connected to evidence that can support a financing or investment decision.

The model should run monthly and use stable identifiers for customer group, contract, order, site, GPU cohort, power allocation, invoice, receipt and financing claim. Each customer receives both a legal-entity identifier and an economic-independence classification. Each commercial document receives a state from announcement through renewal. Changes require an evidence link, owner and date. This design allows management, investors and lenders to reproduce the bridge from public or management statements to cash.

The contract schedule records minimum and optional volume separately. It captures delivery conditions, acceptance, service levels, credits, price, escalation, termination, renewal, invoice and collection. The capacity schedule records planned, power-contracted, energised, commissioned, usable and accepted megawatts. The equipment schedule records cohort configuration, commissioning, utilisation, title, security, maintenance, refresh and residual. Total customer allocation cannot exceed tested service capacity after redundancy and operating headroom.

The customer schedule calculates cohort conversion, paid utilisation, gross retention, net retention, contribution margin and cash collection. Sponsor, state-linked and independent cohorts remain visible. Channel customers are analysed using both intermediary and end-customer information where available. The financing schedule links every debt, lease, prepayment, reserve and guarantee to the relevant legal entity and operating cash flow.

The valuation uses the same schedules. Discounted cash flow follows contract and capacity delivery. Billable-capacity references apply only to comparable accepted capacity. Market references use consistent customer, power, equipment and claims definitions. The enterprise-to-equity bridge deducts claims by legal priority. The combined downside changes related assumptions together and identifies liquidity, covenant and equity requirements.

Appendix B. Minimum confirmatory evidence

The commercial room should include executed customer documents, procurement records, approvals, acceptance, service reports, invoices, credits, receivables and bank receipts. The operating room should include site agreements, power rights, construction milestones, capacity tests, GPU serials, telemetry, incidents, maintenance and refresh plans. The financing room should include facilities, leases, guarantees, reserves, security and prepayment terms. The regulatory room should include licences, authorisations, data-sovereignty controls, cybersecurity evidence and current counsel advice.

Sample tests should follow high-value customer periods from executed order to service allocation, telemetry, invoice and cash. Exceptions should state the financial effect, owner, remedy and deadline. Evidence is sufficient when value-moving differences are resolved, priced, protected or explicitly accepted by the decision-maker.

Appendix C. Hypothetical worked case

The case begins with USD 1.80 billion of stated committed revenue. Sovereign sponsor and directly controlled customers represent USD 1.044 billion, state-linked enterprises USD 0.396 billion and independent third parties USD 0.360 billion. Contract-condition review removes USD 0.12 billion; delivery risk removes USD 0.16 billion; acceptance and service exposure removes USD 0.10 billion; credit and collection adjustments remove USD 0.08 billion; and optional or duplicated amounts remove USD 0.06 billion. The resulting risk-adjusted schedule is USD 1.28 billion.

Independent third-party revenue requires a further quality test. Of the USD 0.360 billion stated, USD 0.26 billion is supported by accepted recurring service and evidence of collection or contracted minimums. The remaining USD 0.10 billion consists of expansion, trial conversion or delivery-dependent value. The central case includes the evidence-supported amount and places the remainder in a separate upside scenario.

Capacity is reconciled independently. The platform describes 92 MW of announced capacity. Executed documents support 68 MW of power rights; 51 MW is energised; 44 MW is customer-usable after commissioning, network, cooling and redundancy; and 31 MW is accepted and billable. The valuation gives each state a different probability, remaining-capital requirement and start date. It does not apply an operating multiple to planned megawatts.

Four GPU cohorts serve different workloads. Cohort A is mature and carries the highest refresh need. Cohort B serves sponsor training workloads. Cohort C serves state-linked inference. Cohort D supports independent regional and international customers. The model records customer allocation, accepted hours, contribution margin and financing by cohort. Refresh capital is funded before contractual performance degrades.

The central case reaches 72 per cent billable utilisation and a 31 per cent steady-state EBITDA margin. It incorporates power, facility, network, service, maintenance, working capital and refresh. Discounted cash flow, billable-capacity references and market references support a USD 1.15 billion enterprise-value conclusion. Adjusted claims total USD 0.49 billion, comprising debt, leases, prepayment exposure, restricted amounts and unpaid committed capital net of available cash. Illustrative equity value is USD 0.66 billion.

The combined downside delays an approval and equipment delivery, extends commissioning by ten months, reduces sponsor volume, reaches only 52 per cent utilisation, weakens renewal pricing and increases financing cost. Enterprise value falls to USD 0.48 billion. Claims rise to USD 0.52 billion because cash absorption and capital commitments increase. Equity recovery is nil. The scenario shows how delivery, concentration and funding risks can interact.

The proposed transaction response uses accepted billable capacity as a consideration milestone, independently collected third-party revenue as an earn-out measure, committed sponsor equity for remaining infrastructure, consent conditions for key customers and reserves for service or refund exposure. Each mechanism has a defined source, calculation and long-stop date. The figures are assumptions and describe no identified company, security or transaction.

Appendix D. Board and lender diligence questions

Ownership and customer classification: Which entities provide capital, land, power, guarantees, procurement direction and customer budgets? Which customer decisions are made independently, and what records support that conclusion? Has the operator aggregated legal entities that share one parent, budget or national programme? Which revenues require related-party disclosure or a separate arm's-length test?

Contract evidence: What proportion of the stated book is supported by an executed minimum payment obligation? Which amounts remain memoranda, reservations, options or expected expansions? What delivery, acceptance, service and termination conditions can reduce value? Have change-of-control requirements and customer consents been identified? Can every material amount be traced to an order, invoice and collection record?

Commercial adoption: How many customers progressed from trial to paid service, and how many purchased again? What are gross retention, net retention and contribution margin by cohort? Which independent customers pay without sponsor credit, subsidy or mandatory allocation? How long does acquisition take, what does it cost, and how quickly can churned capacity be redeployed?

Capacity delivery: Which megawatts are power-contracted, energised, commissioned, customer-usable and accepted? What capital remains at every stage? Which milestones depend on a utility, landlord, supplier or regulatory authorisation? Does the customer delivery schedule use the same dates as the engineering and funding schedules? What penalties or refunds arise if those dates slip?

Equipment and software: Which GPU cohorts serve each customer and workload? Who holds title, and which lender or lessor has security? Are networking, storage, cooling or software constraints limiting service? What maintenance and refresh capital is required through the contract term? Have replacement hardware, integration, downtime and customer acceptance been modelled?

Pricing and margin: Are sponsor and independent customers charged on comparable terms after service differences? Which discounts, credits, free periods, rebates, taxes and pass-through items separate contracted price from cash? Does the operator earn positive customer-level contribution after power, facility, network, support and incidents? Which contracts become loss-making under the downside?

Cash and financing: Do billed amounts reconcile to receivables and bank statements? Which customer prepayments are refundable or restricted? When do equipment, lease and debt payments fall due relative to acceptance and collection? Where is cash trapped? Which covenants, guarantees or change-of-control clauses can accelerate claims?

Regulation and resilience: Which current licences and authorisations govern equipment, end use, data, cyber and operation? Which foreign dependencies remain inside the service architecture? Has counsel reviewed the specific transaction and customer perimeter? What incidents occurred, how were they resolved, and what service credits or customer rights resulted?

Valuation and decision: Does every method use the same accepted capacity, customer classification, utilisation, margin, refresh and claims assumptions? Which strategic benefits already appear in cash flow? What evidence would move a contract or capacity tranche upward in value? What evidence would trigger a reduction, reserve or exit? Who owns each update before signing and after closing?

Governance: Can management reproduce the board dashboard from controlled systems without manual narrative adjustments? Are metric definitions stable and documented? Does internal audit sample contract-to-cash and capacity-to-cash pathways? Are sponsor objectives and stand-alone commercial performance reviewed separately? These questions turn revenue quality into an operating discipline rather than a one-time transaction exercise.

Appendix E. Scenario governance and update protocol

The central case should represent the decision-maker's evidence-supported expectation at the valuation date. It should not contain unsigned customer expansion, unapproved capacity, uncommitted financing or unsupported operating improvement. Each material assumption needs a source, owner, review frequency and threshold for change. The model archive should preserve the input set used for every approval so later performance can be compared with the original decision.

The upside case may include identified commercial options, but every option should state the event required before value is recognised. Examples include an executed customer order, regulatory approval, energisation, supplier delivery, acceptance or funded expansion. The model should avoid treating several mutually competing customers as though each can use the same available capacity. Probability, timing and capital should be internally consistent.

The combined downside should connect risks that can occur together. It should calculate liquidity and claims as well as revenue and enterprise value. Monthly cash, covenant headroom, supplier deposits, refunds, service credits and required equity should remain visible. Management actions need credible timing, authority and cost. A proposed capital reduction or capacity deferral should identify which contracts and customer relationships it affects.

Updates should be evidence driven. Contract execution changes the document state; acceptance changes billable capacity; invoice and bank records change cash conversion; telemetry changes utilisation; supplier and utility records change delivery. The board should receive a reconciliation of prior and current cases, separating actual performance, approved scope change, external conditions and management assumption. This discipline allows strategic sponsorship and independent commercial adoption to be evaluated consistently through the investment period.

The protocol should also retain rejected assumptions and the reason for rejection. This audit trail helps directors, lenders and future investors understand how the case evolved, where judgement was applied and whether subsequent outcomes reflect execution, market movement or an original evidence gap. Material exceptions should reach the board before they are absorbed into an updated forecast.

Sources

1. Public Investment Fund, HRH Crown Prince launches HUMAIN as global AI powerhouse, 12 May 2025. Read the primary source
2. Public Investment Fund, HUMAIN portfolio company profile. Read the primary source
3. NVIDIA, HUMAIN and NVIDIA announce strategic partnership to build AI factories of the future in Saudi Arabia, 13 May 2025. Read the primary source
4. Amazon, AWS and HUMAIN announce more than USD 5 billion strategic investment, 13 May 2025. Read the primary source
5. Amazon, AWS and HUMAIN expand partnership with NVIDIA infrastructure and AWS AI chips, 19 November 2025. Read the primary source
6. Ooredoo, Q3 2025 Results Presentation. Read the primary source
7. Core42, Core42 unveils self-service on-demand AI Cloud platform, 13 October 2025. Read the primary source
8. Core42, Core42 expands AI Cloud offering using NVIDIA accelerated computing, 2024. Read the primary source
9. G42, G42 introduces Digital Embassies and Greenshield, 2025. Read the primary source
10. G42, G42 and iGenius join forces to deploy European AI compute cluster, 2025. Read the primary source
11. Groq, Aramco Digital and Groq announce progress on inferencing data centre, 2024. Read the primary source
12. Groq, Groq announces new global deployment with HUMAIN, 2025. Read the primary source
13. International Energy Agency, Energy and AI. Read the primary source
14. National Institute of Standards and Technology, Cybersecurity Framework 2.0. Read the primary source
15. IFRS Foundation, IFRS 15 Revenue from Contracts with Customers. Read the primary source
16. IFRS Foundation, IAS 16 Property, Plant and Equipment. Read the primary source
17. IFRS Foundation, IAS 36 Impairment of Assets. Read the primary source
18. IFRS Foundation, IFRS 16 Leases. Read the primary source
19. IFRS Foundation, IFRS 13 Fair Value Measurement. Read the primary source
20. IFRS Foundation, IFRS 8 Operating Segments. Read the primary source
21. International Valuation Standards Council, International Valuation Standards. Read the primary source
22. CoreWeave, Inc., Annual Report on Form 10-K for the year ended 31 December 2025. Read the primary source
23. CoreWeave, Inc., 2025 Annual Report. Read the primary source
24. Amazon, AWS Cloud Region in Saudi Arabia remains on track to launch in December 2026, 2026. Read the primary source
25. Public Investment Fund, PIF and Google Cloud to create advanced AI hub in Saudi Arabia, 30 October 2024. Read the primary source
26. Public Investment Fund, Annual Report 2024. Read the primary source
27. Ooredoo, Annual Report 2025. Read the primary source
28. Ooredoo, ESG Report 2025. Read the primary source
29. NVIDIA Corporation, Annual Report for fiscal 2026. Read the primary source
30. Public Investment Fund, PIF and Aramco agree proposed significant minority investment in HUMAIN, 28 October 2025. Read the primary source