Arabic-first products
Right-to-left interfaces designed that way from the first screen, not mirrored afterwards.
Gulf & KSA
Arabic first. Not Arabic afterwards.
Products designed right-to-left from the first screen, not mirrored once the English version works. Delivered with the trail Gulf enterprise and government procurement actually ask for: ZATCA clearing in production, ECC controls, data resident in the Kingdom, and Daleenda already registered on Etimad.
The gate: ZATCA / Fatoora
Invoices clear Fatoora in production, rather than merely being generated in the right shape. For anything that bills inside the Kingdom, this is the gate a system passes before anything else about it matters.
- Saudi ZATCA
- Saudi PDPL
- NCA ECC
- Data residency
- Etimad
- Saudi PDPL
- The Kingdom's personal data protection law, under SDAIA, applied to storage and access.
- NCA ECC
- The National Cybersecurity Authority's Essential Cybersecurity Controls: the bar public-sector vendors are held to, and the one that decides procurement long before features do.
- Data residency
- Data kept inside the Kingdom where the rules require it, rather than wherever the cheapest region happens to be.
Etimad
Daleenda is registered on the government's e-procurement platform, so a public-sector buyer can find and qualify us without a separate onboarding round.
The work itself
What we build here
Enterprise platforms
Systems built to be reviewed, procured and handed over, with the architecture notes and access model an enterprise committee asks for before it approves anything.
Billing and compliance
Invoicing that satisfies ZATCA without a separate reconciliation step.
The arrangement
How the work runs
- Hours
- Gulf working hours, with a working week that matches yours rather than Europe's.
- Language
- Arabic first, and right-to-left by default rather than as a later translation pass.
- Delivery
- Remote, with the documentation trail enterprise and government procurement require.
- Ownership
- Code, repository and cloud account are yours from day one.
Getting started
How the work begins
30-minute meeting
You talk to an engineer. We listen, ask, and tell you honestly if we're the right fit.
A proposal scoped to the work
Fixed scope and price for a defined build; a phased plan for a larger programme. In writing, without obligation, and small asks come back in days.
Delivery in the rhythm the work needs
Short cycles with a demo at each for product work; staged milestones for large programmes. Either way you own the code and the repo from day one.
Launch, run, improve
Monitoring, support and a roadmap. We stay after go-live.
Questions
What companies here usually ask
- Are you ready for government procurement?
- Yes. The three things a public-sector buyer checks first are covered: the Essential Cybersecurity Controls, data residency inside the Kingdom, and registration on Etimad.
- Is Arabic really first, or a translation pass?
- First. Interfaces are designed right-to-left from the first screen; English is the mirror, not the original.
- Whose working week do you keep?
- Yours. The team works Gulf hours, with a working week that matches yours rather than Europe's calendar.
The other markets
Thirty minutes, before the tender goes out.
With a senior engineer who would do the work, not a sales call.