Services

Know what applies. Prove what you run.

Four lines, licensed separately, because you may only need one. Every engagement starts from what your regulators actually require of your organisation — and what they do not.

The four lines

What we do, in the order it has to happen.

AinoTeq consultants deliver Determine, Discover and Assess; you keep working in the Control Room afterwards. A partner can deliver Assess and Discover under its own mark instead.

01 — Determine

Which obligations reach you

Jurisdiction, sector, role and system risk class go in. A signed applicability determination comes out, with the predicate behind every line shown and cited to the clause. No language model participates in deciding what applies to you.

DeliverableA signed, versioned applicability determination, generated at a named corpus version.
02 — Discover

Every AI system you are actually running

Declared by owners in the register, extracted from the documents you already hold, detected through read-only connectors into your cloud accounts, through an agent you run inside your own network, and by reading your own dependency manifests and published endpoints. The detected layer routinely contradicts the declared one, and both are kept.

DeliverableAn AI estate with owners, criticality, status and change history — and the contradictions surfaced, not smoothed over.

Start with the free Readiness Quick Scan → — ten minutes, anonymous, an indication from your own answers.

03 — Assess

Where you are short, against law and standard alike

ISO 42001 readiness and the Statement of Applicability, NIST and EU AI Act coverage, control assurance tested against the evidence you actually hold, and an architecture assessment against the target enterprise AI architecture.

DeliverableA released Statement of Applicability, with every accepted control tied to a named piece of evidence.
04 — Govern

Keeping it true after the report is filed

The Control Room holds continuous posture — what you run, what applies, what is proven, what has drifted. It also ingests the decisions your own AI gateway makes, so what your AI actually did is evidence rather than an assertion. AinoTeq does not today sell a gateway that enforces policy or inspects content in your traffic; when we do, this line will say so.

DeliverableA live Control Room, plus the gateway if you take it — Protect and Monitor live inside this line, not beside it.
Licensing is per line. A client or a partner can take assurance without the gateway, or the gateway without assurance.
Start here

Applicability Determination

Two weeks from a completed profile, fixed fee.

What you get

Four answers, every line cited

We establish which obligations apply to your entity, in your jurisdictions, for your AI use cases — and, just as usefully, which do not.

  • Applicable — with the clause that triggers it
  • Conditionally applicable — with the condition stated
  • Not applicable — with the reason
  • Watchlist — proposed and consultation instruments
Why it matters

Scope down before you spend

Most organisations begin an AI governance programme without knowing which rules bind them. They over-build in some areas and miss others entirely.

Telling you that CBUAE requirements do not reach your entity is worth as much as telling you that Regulation 10 does. Both shrink the problem to its real size.

DeliverableAn applicability matrix, cited clause by clause, plus a short executive note.
The ladder

Engagements

Each rung stands alone. Each one earns the next.

2 weeks · fixed fee

Applicability Determination

Which obligations apply to you, which do not, and why.

OutcomeA cited applicability matrix and a scoped programme.
4–6 weeks

AI Regulatory Readiness Assessment

Your full AI estate — declared, detected and embedded — classified by risk, mapped to your obligations, with the control gaps named.

  • Enterprise AI inventory
  • Risk classification per system
  • Regulatory applicability matrix
  • Gap assessment
  • Executive risk report
  • Target governance framework
  • Remediation roadmap
OutcomeA board-ready picture of where you stand and what to fix first.
8–16 weeks

AI Governance Implementation

Closing the gaps the assessment found — the operating model, the frameworks, the registers, the controls and the evidence.

  • AI governance operating model
  • AI policy and risk frameworks
  • AI register implementation
  • Control implementation and evidence framework
  • Vendor and third-party AI assessment
  • Model and agent governance
  • Monitoring architecture and board reporting
OutcomeControls that operate, with evidence that proves it.
Recurring

Continuous AI Governance

Governance decays without attention. New systems appear, models change, vendors change, and regulations move.

  • AI inventory monitoring
  • Regulatory change alerts, mapped to your systems
  • Risk reassessment and evidence tracking
  • Control monitoring with expiry
  • Quarterly management reporting
OutcomeA picture that stays true between assessments.
Annual retainer · DIFC

Outsourced Autonomous Systems Officer

DIFC Regulation 10 names the role. Most firms are too small to appoint one internally.

  • Registers of use cases, processing and automated decisions
  • High Risk Processing assessments
  • Transparency notice review
  • Annual report to the board
OutcomeThe named officer, held externally, with the records kept.
Per filing

Regulatory filing preparation

Where a regulator sets the cadence, the work repeats whether you are ready or not.

  • QCB pre-approval submissions
  • QCB annual disclosures
  • CBUAE remediation updates
  • Oman compliance reports
OutcomeA filing prepared, evidenced and ready to sign.
Independence

What we will not do.

The refusals are part of the service, not a limitation of it.

No vendor commissions

No referral fees, no reseller margin, no marketing funds — from any AI platform or model provider. You pay us; nobody else does.

No licence resale

We do not sell software. The tooling we use to run an engagement is ours, and it is not on your invoice.

No opinion on our own work

We do not provide an independent validation opinion on any model we have built or remediated. Regulators require validators to be independent of development, and so do we.

Check what applies to you →