Industries
for Giga-Projects
Systems That Exist Before the Buildings Do
A new city has no legacy systems and no IT department yet. It has thousands of contractors, a fixed deadline, and every process still to be defined. ifBash builds the operational platform while the asset is still under construction.
The problems we get called about.
Contractor Onboarding
Prequalification, insurance, permits, and induction as one workflow across thousands of vendors, so a contractor cannot reach site with an expired document nobody checked.
Permit to Work
Permits, isolations, and safety approvals as records with expiry and dependency, rather than paper in a site office — the difference matters most during handover between construction and operations.
Asset Data From Day One
Asset registers populated during construction instead of reconstructed after it. What gets captured at commissioning is what operations will have to run on for thirty years.
Programme Reporting
Package-level status rolled up without a reporting team rekeying it, so a delay is visible while there is still time to act on the critical path.
Local Content Tracking
Supplier and spend data structured so local content reporting is produced from records rather than assembled manually each cycle.
Greenfield Service Design
No legacy to migrate is an advantage only if the model is designed rather than inherited. We define the service catalogue and operating model before there is an organisation to argue about it.
Where AI actually helps here.
On a programme of this size the bottleneck is reading, not deciding. Agents work well on contractor submittal review — checking a document set against the required list and flagging what is missing before it reaches an engineer — and on drafting the first version of an RFI response from the specification it refers to. Anything with a safety or commercial consequence keeps a named human approver, because on a live construction site the cost of a confidently wrong answer is measured in more than money.
Where it does not help, we will say so. An agent added to a broken process just makes the same mistakes faster.
The questions procurement actually asks.
Giga-projects are a Gulf category with no real equivalent elsewhere: capital programmes large enough to have their own regulators, their own utilities, and eventually their own residents. NEOM, Qiddiya, Diriyah, the Red Sea developments and ROSHN are all Vision 2030 delivery vehicles, which means they are measured against national targets rather than only commercial ones. For a platform team the defining feature is greenfield — no legacy systems, no accumulated process, and no organisation yet to inherit either. That is an opportunity and a trap: whatever gets configured first becomes the operating model by default.
We map platform configuration to the control families below and hand over the mapping with the build. That is a description of how we work, not a certification claim — where a framework requires an accredited audit, that audit is yours or your assessor's, and we say so in writing.
- Local content / LCGPASaudi Arabia
- Local Content and Government Procurement Authority requirements shape supplier selection and reporting on programmes of this scale. The data that feeds it is supplier and spend data, which is a modelling decision.
- NCA ECCSaudi Arabia
- Applies where a programme operates critical infrastructure — which most eventually do, once utilities and transport come online. Easier to design to it than to retrofit at the point the classification lands.
- NDMO data standardsSaudi Arabia
- Classification and retention standards apply to the enormous volume of design, contractor, and resident data a programme accumulates. Deciding this early is materially cheaper.
- PDPLSaudi Arabia
- Relevant from the first contractor record onward, and again later for residents and visitors. Two very different populations under one law.
We won't name clients we can't name.
Sector pages usually carry logos and percentages. Ours don't, because most of that work sits under agreements that do not permit it — and inventing a number to fill the space is worse than leaving it empty.
If you want a reference in giga-projects, ask. Where a client has agreed, we will introduce you directly under NDA.
See what we can show youBecause the asset data and permit history created during construction is what operations inherits. Capturing it as it happens is cheaper than reconstructing it from contractor archives after handover, and handover is when the gaps become expensive.
Working in giga-projects?
Tell us the problem in your own words. Back inside two working days: an approach, a sequence, and who would do the work.