Overview

NEOM is Saudi Arabia’s $500B flagship giga-project — a 26,500 km² development in the Tabuk region comprising multiple sub-projects including The Line (linear smart city), Sindalah (yacht island), Aqaba (mountain resort), and Oxagon (industrial complex). Tonomus, the technology and digital arm of NEOM, manages all AI, cloud, smart city, and digital infrastructure procurement. For technology vendors and AI companies, a NEOM/Tonomus contract is among the most valuable and complex procurement processes in the global AI market. This guide explains the procurement structure, vendor registration, typical contract sizes, and what Tonomus actually prioritizes.

Understanding the NEOM Procurement Structure

NEOM Co. vs. Tonomus

NEOM operates through two distinct procurement channels that vendors frequently confuse:

NEOM Co. handles all physical development: civil construction, master planning, real estate, hospitality infrastructure. If you are building physical structures, roads, water systems, or building management systems, you deal with NEOM Co. Procurement via NEOM’s Vendor Portal (vendors.neom.com).

Tonomus is the technology, digital, and AI operating company. Tonomus handles: cloud infrastructure, AI platforms, smart city operating systems, data platforms, cybersecurity, telecommunications (with stc as a partner), digital twin platforms, autonomous mobility systems, and all software applications that run NEOM’s digital spine. If your product is AI, cloud, SaaS, or tech infrastructure, your counterparty is Tonomus.

Both share a parent (NEOM Company, 100% PIF-owned) but have separate procurement organizations, separate vendor panels, and separate budget authorities. Winning a NEOM Co. facilities management contract does not create a pathway to Tonomus technology contracts.

Tonomus Organizational Structure

The Tonomus leadership team relevant to AI and compute procurement:

  • CEO: Joseph Bradley (former Cisco). Sets strategic priorities for Tonomus’s technology stack.
  • Chief AI Officer: Position held by rotating leadership; reports to CEO. Oversees AI platform decisions.
  • Chief Procurement Officer (CPO): Manages the vendor panel and RFP process. Direct contact for large contract negotiations.
  • Business Development: bizdev@tonomus.com — the initial contact point for vendors not yet on the approved panel.

Tonomus maintains a Vendor Advisory Council that meets quarterly and includes selected strategic vendors for early sight of procurement roadmaps. Membership requires: active engagement on at least one Tonomus project, a minimum of SAR 50M ($13M) in cumulative Tonomus procurement, and nomination by a Tonomus C-level sponsor.

Step 1: Vendor Registration

NEOM Vendor Portal

Register at vendors.neom.com. The registration process takes 2–4 weeks for basic approval and 60–90 days for full qualification. Required documents:

  1. Commercial registration (Saudi CR or equivalent foreign business registration)
  2. Financial statements for the last 2 fiscal years (audited)
  3. Quality Management System certification (ISO 9001:2015 minimum; ISO 27001 required for technology vendors)
  4. List of comparable projects (reference projects of similar size and scope)
  5. Bank guarantee capability letter (from a Saudi or GCC-licensed bank)
  6. Nitaqat compliance certificate (for Saudi-registered entities)
  7. ZATCA (Zakat, Tax and Customs Authority) tax registration certificate

For technology and AI vendors specifically, Tonomus’s procurement team also requires:

  • Data security and privacy policy (PDPL-aligned, reviewed by Saudi-licensed privacy counsel)
  • Cloud security architecture overview for SaaS/cloud products
  • SOC 2 Type II report or equivalent (IASME Cyber Assurance Level 2 as a minimum)
  • Product roadmap for the next 18 months

Panel Approval Tiers

Tonomus’s vendor panel has three tiers:

  • Tier 3 (Preferred Vendor): Eligible for contracts up to SAR 2M ($530K). Limited to pre-qualified catalog items. Easiest to attain.
  • Tier 2 (Approved Vendor): Eligible for contracts up to SAR 50M ($13M). Requires the full registration documentation above plus a Tonomus reference from an existing approved vendor.
  • Tier 1 (Strategic Partner): Eligible for contracts above SAR 50M. Requires demonstrated delivery on at least one prior Tonomus project, a dedicated Saudi team of at least 10 FTEs, and a technology partnership agreement with Tonomus outlining IP rights and data governance.

Most AI vendors should target Tier 2 as a starting point and build to Tier 1 status through initial contract performance.

Step 2: Typical Contract Sizes and Types

Based on publicly available procurement notices and industry sources, Tonomus AI and compute contract ranges:

  • Proof-of-Concept / Pilot: SAR 1M–10M ($270K–$2.7M). 90–180 day duration. High conversion rate to Phase 2 if KPIs met. Often structured as a Time and Materials engagement. Accessible to Tier 2 vendors.
  • Platform License + Implementation: SAR 10M–75M ($2.7M–$20M). 12–24 month implementation. Requires Tier 2 panel status and a Saudi-registered implementation partner if vendor is a foreign entity.
  • Managed Services / Long-Term Contracts: SAR 75M–500M ($20M–$133M). 5–10 year terms. Tier 1 panel status required. Often structured as performance-based contracts with KPIs linked to city operational metrics (uptime, response time, user adoption).
  • Infrastructure / Hyperscale Deals: SAR 500M+ ($133M+). AWS, Google Cloud, Microsoft Azure, STC Cloud tier. Direct negotiation with NEOM CEO office; not accessible via standard procurement process.

For AI-specific work, the sweet spot for mid-market technology companies is the SAR 10M–75M managed services contract, typically covering: AI platform deployment, Arabic NLP configuration, data pipeline setup, and ongoing model monitoring. These are typically 3-year initial terms with 2-year renewal options.

Step 3: RFP Format and Response Requirements

How Tonomus Issues RFPs

Tonomus uses three procurement mechanisms:

  1. Open Tender: Published on vendors.neom.com and sometimes on the Saudi Government Procurement Portal (etimad.sa). Open to all Tier 2+ registered vendors. 4–6 week response window.
  2. Selective Tender: Invitation-only RFP sent to a shortlist of 4–8 pre-qualified vendors. Access requires being on the Tier 2+ panel and having engaged Tonomus’s procurement team in advance.
  3. Direct Award: For contracts below SAR 500K or for urgent requirements. Not a viable path for strategic AI vendors.

The majority of valuable AI contracts use Selective Tender. This means that being on the panel is a necessary but not sufficient condition — you also need to have built a relationship with Tonomus’s procurement and technical teams so you are included on the shortlist.

Mandatory RFP Response Sections

Tonomus RFPs for AI/technology work follow a standard format:

Section 1 — Technical Response (40–50% of evaluation weight):

  • Solution architecture diagram (must show data flows within Saudi Arabia)
  • Arabic language support details (model, dialect coverage, benchmark scores)
  • Integration approach with Tonomus’s existing platforms (typically Palantir Foundry for data operations, and Azure/AWS for cloud infrastructure)
  • Implementation plan with milestones and acceptance criteria
  • Cybersecurity approach (aligned to NCSA ECC framework)

Section 2 — Commercial Response (25–35% of evaluation weight):

  • Fixed-price or time-and-materials pricing with rate cards
  • Total cost of ownership model (3-year and 5-year)
  • Payment milestone schedule (Tonomus prefers milestone-based payments, not monthly retainers)
  • Bank guarantee: typically 5% of contract value, held for the duration of the contract plus 12 months defect liability period

Section 3 — Local Content and Sustainability (15–25% of evaluation weight):

  • Saudi headcount plan: minimum 30% Saudi nationals for contracts above SAR 10M
  • In-Kingdom spend: what percentage of your contract value will be spent with Saudi suppliers
  • Technology transfer: training programs for Saudi staff, university partnerships
  • Vision 2030 alignment narrative

Section 4 — References (10% of evaluation weight):

  • Three comparable project references with client contact details
  • Willingness to provide client site visits during evaluation

Step 4: What Tonomus Actually Prioritizes

Based on procurement patterns and vendor feedback from the 2022–2025 period:

Arabic Language is Non-Negotiable

Any AI product interfacing with NEOM residents, visitors, or government staff must handle Arabic input natively — not via translation to English. Tonomus has explicitly rejected internationally recognized AI platforms whose Arabic capability was described as “dialect agnostic.” Provide ArabiGen and ORCA-Arabic benchmark scores in your technical response. If your product relies on translation as a workaround, do not submit.

Data Sovereignty Architecture

Tonomus requires that all data generated within NEOM is processed within Saudi Arabia and, where possible, within NEOM’s own infrastructure. Your solution must be deployable on Tonomus’s on-premise or sovereign cloud infrastructure. Architectures that require sending NEOM resident data to US or European cloud endpoints will not pass technical evaluation.

Vision 2030 Alignment Language

The RFP evaluation committee includes NEOM’s strategy team, and they score Vision 2030 alignment explicitly. Use specific Vision 2030 KPI language: reference the Digital Economy 19.9% GDP target, the National AI Strategy ranking goal (top 15 globally), and NEOM’s own sustainability targets. Generic statements about “digital transformation” score poorly; specific alignment to NEOM’s stated 2030 milestones scores well.

Joint Venture Preference

For contracts above SAR 50M, Tonomus strongly prefers a Saudi-JV structure where the prime contractor is a Saudi-registered entity with at least 30% Saudi ownership. Foreign vendors typically partner with: STC Solutions (the IT services arm of STC), Elm Company (a PIF-owned IT services company), or ITC (Information Technology Company, a Saudi Aramco subsidiary). Negotiate JV terms before the RFP closes — adding a JV partner after award is prohibited.

Step 5: Submitting an Expression of Interest

For contracts above SAR 50M that are not yet at RFP stage, the standard first step is an Expression of Interest (EOI):

  1. Address to: Tonomus Business Development at bizdev@tonomus.com
  2. Include: 2-page executive summary of your solution, your team’s relevant experience, an indication of deal size you can handle, and your proposed Saudi-entity structure
  3. Reference: The specific NEOM sub-project your solution applies to (The Line smart systems, Sindalah hospitality tech, NEOM airport, etc.). Generic NEOM EOIs receive low priority.
  4. Follow up: 7 days after submission, request a 30-minute call with the relevant Tonomus vertical lead (Smart City Operations, AI Platform, Cybersecurity, etc.). The EOI alone will rarely generate a response — the follow-up call is the actual first meeting.

EOIs are reviewed quarterly by Tonomus’s Vendor Advisory team. Submissions received before the quarterly review date (typically the last Friday of March, June, September, December) are included in the next review cycle.

Step 6: Navigating the Evaluation Timeline

Tonomus procurement timelines for technology contracts:

  • EOI to Selective Tender invitation: 3–9 months
  • RFP response window: 3–6 weeks
  • Evaluation period: 4–8 weeks
  • Contract negotiation: 4–12 weeks (longer for Tier 1 contracts with complex IP terms)
  • Contract execution to mobilization: 4–8 weeks

Total: 10–24 months from initial EOI to first billable day. Vendors that accelerate this timeline do so by: securing a Tonomus C-level sponsor early, delivering a compelling proof-of-concept during the evaluation phase (often unfunded — treat it as a sales cost), and having their Saudi entity and bank guarantee documentation in order before the RFP drops.

Budget for pre-sales costs of SAR 500K–2M ($130K–$530K) for a serious pursuit of a SAR 50M+ Tonomus contract. This covers: travel to Riyadh, Saudi entity setup, legal costs for JV negotiations, proof-of-concept development, and local business development support.

The NEOM Compute Context

Vendors position better when they understand the infrastructure NEOM itself is building, because Tonomus procurement increasingly assumes vendors will deploy onto NEOM-controlled capacity rather than bring their own. The anchor development is DataVolt’s AI factory at Oxagon: $5B, 1.5 GW of net-zero, renewable-powered capacity planned for 2028 — the benchmark for green AI infrastructure in the Kingdom and the physical substrate for NEOM’s AI ambitions. Two procurement consequences follow. First, sustainability scoring at NEOM has teeth in a way it does not yet have in Riyadh-based procurement: solutions that can articulate energy-per-inference metrics, workload scheduling against renewable availability, and net-zero-compatible cooling assumptions score materially better in the Local Content and Sustainability section, which already carries 15-25% of evaluation weight. Second, deployment timelines should be phased against NEOM’s own capacity milestones — a 2026 contract award may run its pilot on interim capacity with production deployment sequenced to the Oxagon build-out, and proposals that acknowledge this phasing read as more credible than those assuming day-one hyperscale availability inside NEOM.

Worked Example — a Mid-Market Arabic AI Vendor Pursuit

Compressing the six steps into a single pursuit timeline shows how the pieces sequence. A mid-market vendor with an Arabic-native AI platform targets a SAR 10M-75M platform-and-implementation contract:

Months 0-3: Vendor portal registration filed with the full documentation stack (ISO 27001, SOC 2 Type II, PDPL-aligned privacy policy, 18-month product roadmap). Tier 2 is the target. In parallel, JV conversations open with STC Solutions and Elm — before any RFP exists, because adding a JV partner after award is prohibited.

Month 3: EOI submitted to Tonomus business development, referencing a specific sub-project (Oxagon industrial AI, not generic NEOM), timed ahead of the quarterly review date — the last Friday of March, June, September, or December. The follow-up call with the relevant vertical lead is requested at day 7, because the EOI alone rarely generates a response.

Months 4-9: Relationship cadence with the procurement and technical teams. ArabiGen and ORCA-Arabic benchmark results prepared; the solution architecture redrawn to show all data flows within Saudi Arabia and deployability on Tonomus sovereign infrastructure; NCA ECC cybersecurity alignment documented.

Months 9-12: The Selective Tender invitation arrives. The response allocates effort by evaluation weight: the technical response with the Palantir Foundry integration approach (40-50% of scoring), a milestone-based commercial model with the 5% bank guarantee capacity confirmed (25-35%), a Saudi headcount plan at 30%+ nationals with named training commitments (15-25%), and three references pre-briefed for site visits (10%).

Months 12-18: Evaluation, negotiation, execution, and mobilization — with pre-sales spend tracking against the SAR 500K-2M budget the pursuit was costed at on day zero.

The vendors that fail this sequence usually fail it in months 0-3: entering at RFP time without panel status, without a JV partner, and without the Arabic benchmarks means the selective-tender shortlist was set before they arrived.

Bid/No-Bid Decision Checklist

Before committing pursuit budget, answer honestly: Does the product handle Arabic natively rather than via translation? Can the architecture run entirely in-Kingdom on Tonomus infrastructure? Is Tier 2 panel status achievable with current certifications, or is there a six-month remediation project first? Is a credible Saudi JV partner (STC Solutions, Elm, ITC) genuinely available for this deal size? Can the balance sheet carry a 5% bank guarantee for the contract duration plus the 12-month defect liability period? Does the pipeline justify SAR 500K-2M of pre-sales cost against a 10-24 month conversion timeline? And does the offer map to a specific NEOM sub-project with a named budget line? Two or more noes is a no-bid this cycle — build the missing capability and enter at the next quarterly EOI review instead. NEOM procurement rewards preparation compounded across cycles, and punishes opportunistic entries priced as if this were a conventional enterprise sale.

For deeper reading: How to build a Saudi data center · How to win a Humain contract · How to JV with PIF · NEOM entity profile.