FAQ
Frequently asked questions
What types of companies do you work with?
Banks, insurers, investment houses and public-sector bodies, mostly in Saudi Arabia and the wider GCC. About 95% of our revenue comes from regulated industries, which is where our domain depth and regulatory experience sit.
How do engagements typically start?
With a discovery call, then a short assessment of the estate you already run, the obligations you carry and the risk posture your regulators expect. Direction comes out of that assessment rather than out of a template.
How long does a typical engagement last?
It depends on the engagement model. Advisory and architecture work is measured in weeks, project delivery runs to a defined scope and milestones, and managed services continue for as long as the platform does. The teams that build your systems stay to run them.
Where do you deliver from?
Riyadh and Dubai for client-facing work, with offshore engineering centres in Chennai and Hyderabad and a presence in London. Most engagements use more than one location, and capacity scales with the programme phase rather than the contract.
Can you deploy inside our perimeter?
For most of our clients that is the starting assumption rather than an option. Data platforms, AI and our own products are designed to run on-premises or air-gapped, so data, models and intellectual property stay inside your perimeter. The honest trade-off is that air-gapped delivery takes more effort and moves more slowly than a managed cloud service. What it buys is the ability to use AI where it otherwise could not be used at all.
How do you handle data residency and regulatory requirements?
Residency, classification and auditability are decided in the first architecture session rather than retrofitted before go-live. We design against the SAMA cybersecurity and cloud frameworks, the NCA Essential Cybersecurity Controls, NDMO data governance rules and PDPL, and align to ISO 27001, PCI-DSS and SWIFT CSP where they apply. Compliance is designed into the controls rather than evidenced afterwards.
How are engagements priced?
Three models, chosen to fit the work rather than the other way round. Advisory and architecture runs to a fixed scope with a defined deliverable. Project delivery is priced against agreed milestones. Managed services and Architecture as a Service run as a monthly capacity commitment. Scope changes are agreed before the work starts, not invoiced after it.
What happens once a platform is live?
The same engineers stay on it. We build systems to be operated, so observability, runbooks, access certification and a handover path are part of the build rather than a closing phase. Where you would rather run the platform yourself, the skills handover is a deliverable in its own right.
