IKTVA, Saudi-Made and AI Vendors: A 2026 Procurement Reality Check

Why local content scoring matters more for AI than for hardware

A construction project buying steel rebar already has a mature local-content market. Buying enterprise AI is different. The talent, the cloud infrastructure, the model-training pipeline, and the support function can all be foreign by default — and a vendor that ships a great product without a Saudi delivery footprint can quietly drop your local-content score by points that cost you contracts elsewhere.

For Saudi owners running multi-vendor AI procurement, three programmes shape the scorecard:

1. IKTVA — Aramco’s In-Kingdom Total Value Add scoring
2. Saudi-Made — Ministry of Industry product certification
3. Nitaqat — Ministry of Human Resources localisation tiering

Each has a different scope. Together they shape contract eligibility and pricing on Aramco, NEOM, Royal Commission, and other major Saudi tenders.

For broader context see the Vision 2030 digitisation reading, the PDPL compliance checklist, and the edge vs cloud architecture decision tree.

IKTVA — what it actually measures

IKTVA is Aramco’s framework for scoring suppliers on the percentage of value retained in-Kingdom. As of public programme materials May 2026, the scoring covers:

• Goods sourced in-Kingdom
• Services performed in-Kingdom
• Saudisation in the supplier workforce
• Training spent in-Kingdom
• R&D spent in-Kingdom
• Supplier development spent in-Kingdom

Each component is reported annually with audit. Aramco uses the score in tender evaluation, prequalification, and long-term framework agreements. A higher score does not mechanically win a tender, but a low score increasingly disqualifies a vendor from serious consideration on long-term work.

For an AI vendor, the IKTVA exposures most often missed:

Component	Frequent vendor gap
Software and services in-Kingdom	Engineering team based abroad
Saudisation	Few or no Saudi engineers / analysts
Training in-Kingdom	All training events held abroad
R&D in-Kingdom	No locally-funded research activity
Supplier development	No local SME pipeline

Owners reviewing AI proposals in 2026 are increasingly asking for the latest filed IKTVA score, with audit attestation, before shortlisting.

Saudi-Made — product-level certification

Saudi-Made is a Ministry of Industry initiative recognising products manufactured or substantively produced in the Kingdom. As of May 2026 the programme covers a wide range of physical and software products under defined value-add criteria.

For AI vendors, Saudi-Made registration of the platform — when the underlying engineering and IP work occur substantively in the Kingdom — confers two practical benefits:

1. Eligibility for procurement preferences in government and quasi-government tenders
2. Marketing and brand alignment with the Made-in-Saudi initiative

Crucially, Saudi-Made registration is product-by-product, not company-by-company. An AI vendor with a Saudi-Made platform but a non-registered hardware accessory line ships a partial story. Verify which product lines hold the certification.

Nitaqat — workforce localisation tiering

Nitaqat is the Ministry of Human Resources programme tiering employers by Saudi national share of workforce relative to industry size. As of May 2026 the tier names (Platinum, Green, Yellow, Red) and the underlying calculation continue to apply.

The procurement-relevant facts:

• Tier directly affects the employer’s ability to hire and retain non-Saudi staff, renew work permits, and participate in some tenders
• Tier is a forward-looking capacity signal — an AI vendor in a low Nitaqat tier may struggle to scale local operations even if the IKTVA score is acceptable
• Owners increasingly request both IKTVA score and Nitaqat tier in prequalification

How to translate the three programmes into a vendor scorecard

A 2026-ready procurement scorecard for an AI tender should include:

1. IKTVA score for the most recent reporting year, with audit attestation
2. Saudi-Made registration status for the specific product line being procured
3. Nitaqat tier with the date of the tier
4. Local engineering team headcount with Saudisation %
5. Local R&D footprint — research projects funded locally
6. Local supplier ecosystem — SMEs developed under the vendor
7. Saudi data centre / cloud residency — see the PDPL checklist
8. Local training programme — operator and analyst training in-Kingdom

Weighting depends on the tender. Aramco contractor work weights IKTVA heavily; Royal Commission and NEOM tenders weight Saudi-Made and Nitaqat alongside IKTVA. Build the weights into the RFP, not into a side conversation.

Where AI vendors commonly misrepresent

Three patterns we see in 2026:

1. Re-badging foreign engineering as local. A Saudi sales subsidiary with no engineering staff is not a local engineering team. Ask for engineering headcount by location and Saudi national share.
2. Saudi-Made halo on uncertified products. A vendor may have a Saudi-Made registration on one product and pitch it as a company-wide attribute. Verify product-by-product.
3. Inflated Saudisation by counting partners. Some vendors include partner staff in the Saudisation percentage. The Nitaqat tier of the contracting entity is what counts.

The mitigation is straightforward: make the prequalification request specific — not “are you Saudi-Made?” but “list the products carrying current Saudi-Made certification with registration numbers”.

Why local vendor choice impacts your supply chain

Even a major project’s sourcing strategy can over-rotate to global brands and find that:

• Operator training has to be conducted abroad, at significant cost and schedule risk
• Support response times are bound by foreign time zones and visa-dependent on-site visits
• IKTVA reporting is harder when foreign-vendor share of total spend is high
• Procurement preferences for Saudi-Made are forfeited
• Knowledge transfer to the owner’s local team is slow

For a comparison anchored in product capability rather than national content, see the Pix4D vs DroneDeploy vs FI Tech comparison.

A simple owner playbook for 2026

1. Make IKTVA, Saudi-Made and Nitaqat explicit RFP fields, not optional addenda.
2. Ask for evidence: scores, registration numbers, tier dates.
3. Weight each programme appropriately for the tendering authority.
4. Verify product-line specificity for Saudi-Made.
5. Cross-check against PDPL — local content and data residency are usually correlated but not always.
6. Reserve room in the scorecard for technology fit — local content is necessary, not sufficient.

For the technology fit dimensions see the Vision 2030 digitisation reading, the edge vs cloud decision tree, and the PPE detection field guide.

Common owner mistakes

Three patterns in Saudi AI procurement in 2026:

1. Treating local content as a tiebreaker. It is increasingly a gate item. Vendors who ignore IKTVA and Saudi-Made get screened out before the technical review.
2. Skipping the technical review on a high-IKTVA vendor. Local content is not a substitute for product fit. The five CFO KPIs must still move.
3. Single-vendor strategies on long programmes. Vision 2030 is a decade-long story. Building a portfolio of qualified vendors — with at least one strong Saudi-Made provider — protects against single-vendor risk.

Next steps

If you are scoping a Saudi AI procurement in 2026, start with the solution catalogue, the trust and certifications page, and the PDPL compliance checklist. For programme-level context see the Vision 2030 digitisation reading.

Request an IKTVA-aligned vendor evaluation for your tender and we will produce a scorecard against the criteria above within 10 working days.

React to this article

🔥...💡...🤔...👏...❤️...