The problem
What is usually behind this search
We do not have an office in NEOM
We serve organisations there from our Riyadh office and our engineering hubs in Lahore and Karachi, travelling for the parts of an engagement that need to happen in person.
The complaint is almost always the same: two reports disagree, and the meeting spends its time deciding which number to believe rather than deciding what to do. That is not a dashboard problem. It happens because the same concept — a customer, an order, a site, a shift — is defined differently in each source system, and nobody has ever reconciled the definitions.
Buying a visualisation tool on top of that produces prettier disagreement. The work that fixes it is unglamorous: agreeing definitions, building a pipeline that applies them consistently, and making the resulting record the one everyone uses. Once that exists, reporting and AI both become straightforward.
Capabilities
What we actually deliver
Data platform engineering
Ingestion, transformation and storage designed for the queries the business actually asks, with lineage from every figure back to its source.
Definition and model alignment
Getting agreement on what a customer, an order or a unit of production means across systems — the step that makes everything after it work.
Operational reporting
Reporting that reaches the people making the decision, at the point they make it, rather than a monthly pack nobody opens.
Forecasting and prediction
Demand, maintenance and risk models built on the operating history, with honest reporting of how accurate they are in practice.
Data quality and governance
Automated checks at ingestion, ownership for each domain, and a record of what was changed, when and by whom.
Industrial and operational data
Bringing plant historians, sensor streams and maintenance records into the same analytical surface as commercial data.
Local context
Why this is different in NEOM
NEOM is unusual in this market because it has no legacy estate. There is no thirty-year-old core system to integrate with, no accumulated technical debt, and no established operating convention to work around. That removes the constraint most Saudi programmes spend their effort on — and replaces it with a harder one.
The harder constraint is that everything is decided at once. Identity, data architecture, network design, operating model and vendor strategy all have to be settled before there is operational experience to inform them. Decisions made early become expensive to reverse once dependent systems accumulate on top.
Work in this environment tends to be architectural rather than remedial: setting the standard that later systems will inherit, and building the first implementations that prove the standard works. The value is in getting the foundations right, because the cost of a wrong foundation compounds with every system built on it.
What buyers in NEOM run into
- 01
Architecture decisions are made before operational evidence exists
Without a running operation to learn from, foundational choices rest on assumption. The defensible approach is to design for reversibility where the evidence is thin — open interfaces, portable data formats, no single-vendor lock on a core function — rather than to pick confidently and hope.
- 02
Many contractors, one architecture
Greenfield programmes run dozens of delivery partners in parallel, each with its own preferred stack. Without an enforced integration and data standard, the result is a set of islands that has to be re-integrated later at far higher cost than specifying it up front.
- 03
Security has to be designed in, because there is nothing to retrofit onto
A greenfield environment is the one chance to build identity, segmentation and monitoring correctly from the start. Once dependent systems are live, changing the identity model or the network boundary becomes a programme in itself.
How an engagement runs
The stages, and what happens in each
Define
Agree the questions the platform has to answer and the definitions behind them.
Profile
Examine the source data as it really is, not as the documentation describes it.
Build
Pipelines and models, delivered domain by domain so value arrives before the platform is complete.
Validate
Reconcile against the systems of record until the numbers agree and the differences are explained.
Adopt
Move reporting onto the new record and retire the parallel spreadsheets, which is the step most programmes skip.
Regulatory frame
What governs this work
References for buyers. Techbanq does not issue certifications, approvals or compliance determinations — those rest with the authority and its assessors.
The full frame in Saudi Arabia- NCA ECC
The Essential Cybersecurity Controls — the national minimum baseline for government entities and for private operators of critical national infrastructure. The 2024 revision expanded both scope and control depth.
- NCA CCC
Cloud Cybersecurity Controls — the requirements applied to cloud service providers and to the entities consuming their services.
- Aramco SACS-002 / CCC
Saudi Aramco's third-party cybersecurity standard. Vendors are classified into CCC or the on-site CCC+ tier, with audits carried out by firms Aramco authorises.
- PDPL
The Personal Data Protection Law, enforced by SDAIA. Sets lawful basis, transfer, retention and breach-notification duties for anyone processing personal data in the Kingdom.
- SAMA Cyber Security Framework
The mandatory framework for SAMA-regulated entities, organised across governance, risk, operations, third-party security, resilience and compliance.
Technologies
What we work with
Cost
What moves the price
We do not publish fixed prices, because any figure quoted before the scope is known is a guess. These are the variables that actually determine it.
Number of source systems
Each source adds connection, mapping, reconciliation and ongoing maintenance work.
Source data quality
Where the same entity is recorded differently across systems, resolving it is the largest single item of work.
Latency requirement
Daily batch is straightforward. Near-real-time streaming is a different architecture with a different operating cost.
History depth
Loading years of history, particularly where the source schema changed over time, adds meaningful effort.
Common questions
What buyers usually ask
Why do our two reports disagree?+
Almost always because they define something differently — a different date basis, a different treatment of cancellations, a different set of entities included. The fix is agreeing the definition once and applying it in one place, rather than reconciling the two reports each month.
Do we need a data platform before we can do anything with AI?+
Not a complete one, but you need the specific data the AI use case depends on to be reliable and accessible. Building an entire platform before any use case is a common way to spend a large budget with nothing to show at the end of year one. Build the domain the use case needs, prove it, then extend.
Other services in NEOM
Related
Data and analytics services in other cities
Discuss data and analytics in NEOM
Send us the scope as you understand it today, even if it is incomplete, and we will tell you what we need to know before giving an estimate.
What happens next
- 1We reply within one business day.
- 2A 30-minute scoping call with a senior consultant.
- 3A written proposal with scope, team, and timeline.
Or reach us directly

