Europe and the GCC
European expertise. GCC execution.
Our roots are European; our work is in the GCC. This page explains what that combination means in practice: the engineering discipline we bring, how we deliver in Arabic and English, and how we organise time and presence across both regions.
01European roots
What we bring from Europe
01
Engineering discipline
Documented architecture decisions, work in reviewable increments and validation before anything reaches production.
02
Privacy by design
Data minimisation, clear purposes and named accountability, built into systems from the first sketch.
03
An applied research ecosystem
We take part in the Vision for Robotfusion collaborative project in the Dutch Brabant AI ecosystem, on shared image data for robotic vision.
04
A Dutch training partner
We have designed and delivered training with the Dutch institute Educational Mastar Central (EMC).
02GCC execution
How we deliver in the GCC
01
Bilingual by default
Workshops, documents and interfaces in Arabic and English, written for the people who will use them.
02
Shared working hours
Riyadh and Central Europe share most of the working day, so reviews and decisions never wait for another time zone.
03
On-site when it matters
Discovery workshops, go-live and training where the work happens; build and reviews remotely in between.
04
Local rules and processes
We design within the regulations that apply to you and involve your procurement and compliance teams from the start.
03Working hours
Two time zones, one working day
Riyadh and Central Europe share most of the working day and most of the working week. We plan workshops, reviews and releases inside that shared window.
Winter: Riyadh UTC+3, Amsterdam UTC+1
Riyadh09:00–17:00 local time
Amsterdam09:00–17:00 local time, 11:00–19:00 Riyadh time
Shared window11:00–17:00 Riyadh time, 6 hours
Summer: Riyadh UTC+3, Amsterdam UTC+2
Riyadh09:00–17:00 local time
Amsterdam09:00–17:00 local time, 10:00–18:00 Riyadh time
Shared window10:00–17:00 Riyadh time, 7 hours
All bars are drawn on Riyadh time.
Working week
| Sunday | Monday | Tuesday | Wednesday | Thursday | Friday | Saturday | |
|---|---|---|---|---|---|---|---|
| Riyadh | Working day | Working day | Working day | Working day | Working day | Weekend | Weekend |
| Amsterdam | Weekend | Working day | Working day | Working day | Working day | Working day | Weekend |
| Shared window | Weekend | Working day | Working day | Working day | Working day | Weekend | Weekend |
Shared working days: Monday to Thursday
Assumes a typical 09:00–17:00 working day in each city, the Sunday-to-Thursday working week in Saudi Arabia and the Monday-to-Friday working week in the Netherlands. Clock changes follow the official time-zone rules.
04Bilingual delivery
Arabic and English, by design
من الاستراتيجية إلى أنظمة تعمل.
From strategy to systems that work.
- 01
Working documents in your language
Executive summaries, workshop materials and user guides in the language your teams use; technical artefacts in English, with Arabic summaries where they are needed.
- 02
Arabic-first interfaces
Right-to-left layouts and Arabic typography designed properly, not mirrored as an afterthought.
- 03
Terminology agreed early
A shared glossary, so business and technical terms mean the same thing in both languages.
05Engagement modes
On-site where it matters, remote where it works
01
On-site
Discovery workshops, key design reviews, go-live and training, where the work happens.
02
Remote
Build, reviews and support between on-site moments, inside the shared working window.
03
Hybrid
Our usual pattern: on-site at the decision points, remote in between.
A note on company details
This page describes how we deliver, not an office network. Registration and office details are published only once they are verified. If you need them for procurement, ask us directly.
Plan an engagement that works across both regions.
Before the engagement starts, we propose the mix of on-site and remote work, the working language of each deliverable and the review rhythm.