Contact

a reply within one working day, from the engineer who would do the work

Tell us where you are

About a minute. No scheduling link and no sales sequence.

The more concrete the middle field, the more useful the reply. Name the documents, the systems they sit in, and roughly how much arrives each month - that is enough for a specific answer rather than a brochure, and it is the same information a discovery call would open with.

You get a reply within one working day, from the engineer who would do the work - not a sales sequence.

Four fields are needed, and two more help if you have them. About a minute.

Your name

Organisation

Work email

Phone (optional)

With country code. The reply is often quicker as a conversation, but an email reply is the default if you would rather.

Country (optional)

Which working week to answer against. The Gulf weekend is not the Egyptian one.

Where you are, and what is slowing you down

The documents, the systems they sit in, and roughly how much arrives each month. Detail here is what makes the reply useful.

Timeline

Worth writing about: paperwork that has grown past the people handling it, a pilot that worked and then stopped, a diagnostic you want a second read on, or a system already in production that nobody is reviewing. Also worth writing if you are not sure whether this is an AI problem at all - that is a question we answer for a living.

The form is the route in. A direct address goes live with the domain and will be published here then - an address that bounces is worse than no address.

Compliance and data posture

Only what is actually true. An aspirational badge row is worse than none, and a badge nobody granted is the worst failure possible on a page like this.

Sovereignty is table stakes in this market rather than a differentiator, so it is stated here rather than featured on the home page. What is deliberately absent is any partner badge or certification we do not hold, and any claim about which foundation models we have worked with - nothing in the delivery record documents which underlying model sat behind any engagement, so that line has no basis and is not made.

Where the data sits: On-premises, in a sovereign cloud region, or in your own tenancy. Stated because it is table stakes here, not because it is a differentiator.
Language: Arabic and English, in the same document and the same process. Not translated first.
Your material: Documents shared for a diagnostic are used for that diagnostic and returned or destroyed on request. They do not train anything.
What we deliver, and what we keep: You own every deliverable. We keep our own audit frameworks and evaluation methods, which is what makes the next engagement better than the last.
Certification: None claimed yet. ISO/IEC 42001 is the one this market has started citing and it is on the list; until it is held, it is not on this page.