Case study

Graysen

Service: AI Development & Integration
Year: 2026
Live: www.graysen.ai

01The work

Overview

An AI contract analyser built for the UAE, working in Arabic and English. You give it a contract and it hands back the clauses that carry risk — an auto-renewal buried in the fine print, a financial penalty out of all proportion to the breach it punishes, a responsibility left vague enough that it will land on you — each one flagged with the reasoning beside it. It is aimed at the person about to sign rather than the lawyer paid to review, and it is careful about the difference: the page states plainly that Graysen provides analysis, not legal advice, and tells you to consult a lawyer before signing.

Challenges

Jurisdiction is the entire problem. A contract analyser reasoning from general legal training produces answers that are fluent, confident, and wrong in the Emirates, where employment sits under Federal Decree-Law No. 33/2021, tenancy runs through Ejari and RERA, and the DIFC and ADGM operate their own common-law frameworks alongside the UAE Civil Code. On top of that the product has to work in two languages where neither is a translation of the other — an Arabic contract is the binding document, not a copy of the English one — and it has to stay useful to someone with no legal training while staying on the right side of a line that, once crossed, is unlicensed legal practice.

Solution

Scope the model to named instruments instead of to law in general. The site advertises which frameworks it reasons against — Federal Decree-Law 33/2021, the UAE Civil Code, DIFC Courts, ADGM, MOHRE, the Dubai Land Department, PDPL, Ejari, RERA — which is both the product's substance and its honesty: it tells you the ground it stands on, so you can judge when you are standing off it. Findings come back as discrete flagged clauses rather than a wall of prose, each with a plain-language explanation of why it matters, so the output is scannable by someone who has never read a contract closely. The analysis-not-advice disclaimer sits in the hero rather than in a footer. Behind the product sit a separate content system on its own subdomain, an independent API, Postgres and Redis.

Conclusion

The interesting decision here is the narrowing. A contract analyser that works everywhere is a demo; one that knows which UAE instrument governs the clause in front of it is a product. Naming the frameworks on the marketing page rather than hiding them is the same decision made twice — it is what makes the tool credible to a sceptical reader, and it is what keeps the promise small enough to keep.

02More work3 projects