The i · Lebanese AI Watch Issue LAW-001Legal AIBeirut23 October 2026

The legal AI built in Beirut that tests itself in public.

HAQQ Legal AI was founded in Beirut in 2020, raised three million dollars in February, and runs a research desk that scores its own competitors on a published rubric. In July it put an independent evaluation on its own site and printed the result, a 27.0 percent pass rate on a deliberately hard test, in a category where vendors usually print nineties. Both sides made mistakes in the making of this issue, and both are on the record.

HAQQ cleared publication 17 questions asked 15 answered 4 left open Our corrections: 3 No fee either direction
Review

HAQQ saw this before anyone else. The full piece was sent to HAQQ on 17 September 2026 for review, in the form it appears here. HAQQ gave its go ahead to publish. As with every issue, the subject corrects factual errors and does not approve the analysis, which is ours. Where HAQQ has corrected or added to something, the change is attributed to HAQQ and dated.

01 · Theirs

The answers

Antoine Kanaan, co-founder and CEO. Abbas Kabalan, co-founder and Chief Legal Officer. Returned through Mark Elian, Senior Communication Officer.

Seventeen questions, written for HAQQ and nobody else. Printed in their words, edited for length and nothing else. Where an answer did not come, the space is left empty and says so.

Q01

Describe HAQQ to a lawyer who has never used AI, in the way you would describe it to a colleague rather than to an investor.

HAQQ

HAQQ is a Legal AI and practice management platform built around how legal teams actually work. For a lawyer, the simplest way to think about it is this: you can use HAQQ for work such as legal research, drafting, document review and analysis, while eFirm manages the operational side of the practice: matters, clients, documents, tasks, deadlines, billing and history.

The point is to give one environment where the work itself and the management of that work connect. HAQQ reduces the time spent finding, structuring and processing information.

Q02

What was the specific moment that made you start it. Not the reason, the moment.

HAQQ

The clearest specific moment HAQQ has publicly documented was an afternoon when we tested leading general-purpose AI tools on regional legal matters. We saw them invent provisions and, in some cases, confidently apply the wrong jurisdiction. The conclusion was not that the models were bad. It was that a general model did not have the legal infrastructure around it to handle this work reliably.

Q03

Justinian produces jurisdiction specific output. What does jurisdiction specific actually mean inside the engine, as opposed to in the marketing.

HAQQ

It means jurisdiction is part of what happens before the answer is produced. Justinian sits between the user, organizational data and the underlying AI models. It applies context, jurisdiction, retrieval, permissions, controls and model selection before producing the output. The underlying foundation model is therefore one component of the system, rather than the entire Legal AI product.

Q04

What happens when the model is wrong about the law. Walk us through a real case rather than the policy.

HAQQ

One concrete example HAQQ has already made public comes from the internal testing that helped shape Justinian. We gave leading general-purpose AI tools regional legal matters and saw examples where they invented legal provisions, missed Sharia-specific rules or applied the wrong jurisdiction while presenting the answer confidently.

Q05

Where does professional liability sit when a lawyer relies on HAQQ and it costs their client. Has that conversation happened with a bar association yet.

HAQQ

HAQQ's position is that using AI does not remove professional accountability from the lawyer. The lawyer remains responsible for judgment, strategy and the final work product. HAQQ is designed to support that judgment, not replace it. That does not mean the technology provider can never have responsibilities of its own. The precise allocation of legal liability depends on the jurisdiction, the contract between the parties, the applicable professional rules, the nature of the error and the law governing the claim. We do not position HAQQ as transferring a lawyer's professional duty to a software provider. The system is built on the assumption that legal output remains subject to professional review.

On the bar association point specifically: HAQQ has relationships with bar associations and engages with professional bodies on Legal AI and institutional modernization.

Q06

Legal AI hallucination has already produced sanctioned lawyers in several countries. What do you do that a general model does not, specifically enough that somebody technical could evaluate it.

HAQQ

The fundamental difference is architectural. A foundation model is a component. Justinian is HAQQ's proprietary reasoning and orchestration engine around that component. The system can apply jurisdiction, retrieve relevant context and legal material, use organizational data, select models and tools, enforce controls and assemble the resulting output. It also supports source traceability, auditability, access controls, isolation and human review.

The technical test is not whether the system can produce fluent legal text. The test is whether you can inspect how the task was grounded, what jurisdiction and sources were used, what context entered the system, what controls were applied and whether a lawyer can review the work before it becomes final.

Q07

Abbas, as Chief Legal Officer: what have you overruled the engineering side on, and what did holding that line cost.

Abbas Kabalan · attribution confirmed 16 September

The line I keep holding is that statistical performance is not enough for legal work. Engineers can quite reasonably say, this works in 97 out of 100 cases. My response is: tell me what happens in the other three, because one of those three could be the matter that costs somebody their case or their money.

I have pushed back against presenting generated legal conclusions as more final than they really are, and I have pushed for professional review to remain part of the workflow even where automation would make a cleaner demo or a faster product experience.

Q08

What have you refused to build, even though customers asked for it.

HAQQ · complete as written, confirmed 16 September

We have a very clear boundary around the idea of the fully autonomous AI lawyer that makes the professional disappear.

We will automate research, drafting, review, extraction and administrative work very aggressively. But we do not want to design a product whose selling point is that professional accountability no longer matters. In serious legal work, there are decisions that require a professional to take responsibility for the consequence. We are happy to automate the work around that decision; we are not interested in pretending that the decision itself no longer needs an accountable human.

Q09

What is the actual pipeline from a question to an answer. How much is retrieval, how much is the model, and where does a person sit in it.

HAQQ

At the level HAQQ can discuss publicly, the chain is: user question, context and jurisdiction, retrieval and relevant organisational knowledge, model and tool selection and orchestration, generated legal work, controls and review.

Justinian controls the reasoning and orchestration layer. The underlying foundation models are selected components, not the entire system. Retrieval matters because legal work is only as useful as the legal and factual context it is grounded in. The model matters because it performs reasoning, drafting and synthesis.

The person sits at the points where professional judgment is required: defining the task, reviewing the sources and output, and deciding what is actually relied on or sent to a client.

Q10

What breaks most often, and what is the failure you have not solved yet.

HAQQ

Left open.

Q11

Give us one number nobody outside HAQQ knows. Cost per query, accuracy on an internal benchmark, how long a contract review actually takes.

HAQQ · answered 16 September

One example is the 27.0% overall pass rate from that independent evaluation. It covered 61 real legal tasks across 21 jurisdictions, with every task run twice. A task counted as a pass only if every applicable binary criterion written by lawyers in advance was satisfied; any judging disagreement capable of changing the result was escalated to a qualified lawyer for blind review.

Q12

eFirm is practice management, a different product from legal AI with different buyers and a different sales cycle. Why build both rather than one properly.

HAQQ

Because the two products solve different parts of the same legal workflow. eFirm contains operational context: matters, clients, documents, tasks, deadlines, billing and history. Legal AI works better when it can operate with that context rather than beginning from an isolated prompt every time. That is why HAQQ's own product logic connects the two: the AI should understand the matter it is working on, not just the sentence typed into a chat box. Building only the AI would leave that context fragmented across other systems. Building only practice management would organize the work without helping lawyers do more of the substantive work. We built both because the long-term value is in connecting legal intelligence with the operational reality of the practice.

Q13

The February round was three million dollars, led by Sowlutions Ventures. What did that money actually change, and what did you turn down.

HAQQ

The money changed our ability to move from proving the product to hardening and deploying the system. We put capital into the Legal AI and agent architecture, engineering, security and data residency foundations, and the teams required to deploy with enterprises and institutions. It also gave us more room to expand across markets and invest in the operational side of scaling the company, not just the prototype.

Q14

Your mission line says around five billion people never benefit from the justice system because they cannot afford it. How does a paid product sold to law firms reach any of them, honestly.

HAQQ

HAQQ actually started with professionals, but the consumer strategy is separate. The mobile product is free to start and is designed to provide the first step: help someone understand a document, understand their position, review something or know whether professional legal assistance is needed. AI helps someone reach the lawyer better informed and better prepared. For people who do need a lawyer, the product can shorten the distance between confusion and professional help. For people whose problem is simpler, it can make useful legal information more accessible. The enterprise side and the consumer side therefore solve different parts of the same access problem: one makes lawyers more productive, while the other lowers the friction for people trying to understand their position and what they should do next.

Q15

You built this in Beirut through some of the worst years the country has had. What did that cost, and what did it teach you that building it anywhere else would not have.

HAQQ

It was one of the challenges of building the company; the importance of self-reliance, discipline, speed and responsibility. Instead of continually exporting talented people, keep and finance more of that talent at home and export the products, values and companies they build.

Q16

What does the Lebanese tech scene get wrong about itself.

HAQQ

One assumption HAQQ very clearly challenges is that Lebanese talent has to leave Lebanon in order to build something globally relevant. The idea is to build a company that the world respects, keep talent in the country and export the product rather than exporting the people.

Q17

Who else should we be featuring. Name somebody building something real that nobody is writing about.

HAQQ

Jad Jabbour, Principal Engineer at HAQQ. Jad is the kind of human who imagined the whole thing and knows where every wire goes. On a system this tightly coupled, it is the advantage.

02 · Ours

The analysis

This is The i's reading. HAQQ has no approval over it.

Where a claim can be checked we checked it and say how. Where it cannot, it is printed as HAQQ's statement with HAQQ's name on it. Two facts set the register. HAQQ was founded in 2020 and reported its first round seven months ago. Club Cedro is a few weeks old. Everything we found is here, read on two tracks: how HAQQ measures against the category as it stands, and where it has come from and can go. Where we have a view it is offered as a suggestion, not a verdict.

Track one · Against the benchmark

They put an independent test on their own site, and printed the result

On 23 July HAQQ put an independent evaluation on its own site. Sixty one tasks contributed by practising lawyers, across 21 jurisdictions including the United States, the United Kingdom, India, Singapore, the Netherlands and Oman. Every task run twice. Binary criteria fixed by lawyers before testing, and a task passes only when every criterion is met. HAQQ passed 27.0 percent. On the hardest subset it passed 5.9 percent, against 1.1 percent for the average legal AI on the same set. Their own summary: on roughly three out of four hard tasks, at least one lawyer authored criterion was still missed.

Read that against the category. Vendors in legal AI publish scores in the nineties, on tests they design. HAQQ published its result on a test somebody else designed, and wrote the caveat themselves. The evaluator is not named, because that evaluator keeps its reports private by default, so a reader cannot rerun it. That is a real limit, and a smaller one than anything else in the category offers.

The forty nine is theirs, and they say so

The other figure on the homepage, 49 out of 50, comes from HAQQ's own rubric. Fifty points across eleven categories, criteria published, nineteen tools scored on the same sheet. The top five on that sheet are in the table below. Topping your own rubric proves less than publishing the rubric does. Putting the criteria out and scoring named competitors on them is something we have not found elsewhere in the category, and the two figures together, the 27 and the 49, tell a reader more than either alone: this is what we get on our own terms, and this is what we get on someone else's.

HAQQ's 50 point rubric, top five of nineteen, as published on haqq.ai
ToolAverage
HAQQ, Justinian46.8
Claude Fable 542.7
Claude Opus 4.740.8
Mike OS39.1
Harvey37.9

They named the right test, and they are the ones closest to passing it

The most useful sentence in the questionnaire is in Q06. The technical test, HAQQ says, is not whether the system can produce fluent legal text but whether an outsider can inspect how the task was grounded, which jurisdiction and sources were used, what controls were applied, and whether a lawyer reviewed the work before it became final. That is a governance argument in a category that mostly sells fluency, and fluency is the property that has put lawyers in front of judges.

The first draft of this piece argued that HAQQ had set that test and then published figures that could not pass it. That was wrong. MINZÂR, still in development, overlooked the research pages on haqq.ai where the figures and their methods are published. Corrected below. What survives is narrower: until a legal AI benchmark exists that a reader can rerun, no vendor fully passes the Q06 test, HAQQ included. HAQQ is the nearest.

The research desk

Since February HAQQ has published around twenty studies on its site. A country by country tracker on whether lawyers may use AI, 17 jurisdictions, one restricting. A grading of 3,000 answers from ten frontier models across 300 legal tasks. Head to head reviews of Harvey, Legora, CoCounsel and Lexis on the same rubric. On 11 September, three models run against 41 real legal questions, all failing on Saudi and Egyptian law despite correct looking citations.

The most useful is the hallucination audit: 1,598 verified court cases involving AI fabricated material as of 9 June, built on Damien Charlotin's public database at HEC Paris, which lists a case only where a court explicitly found or clearly implied reliance on hallucinated material. HAQQ did not build that count. It reads it, checks it and publishes it, which is a public service the category needed and did not have, and the strongest argument for HAQQ's own product.

The result is theirs. So is the decision to print it.

Track two · Where it came from, and where it can go

They stayed, and built it here

HAQQ was founded in Beirut in 2020 and is run from Beirut today. On our own record that is the exception. Anghami, founded in Beirut, moved its headquarters to Abu Dhabi in 2021. Integral AI, Bounty, Ramp and Medicus AI were built by Lebanese founders somewhere else. Each of those was a rational choice and the register says so. HAQQ made the other choice, through the years it describes in Q15 without naming them, and its answer to Q16 says why: keep the talent, export the product. That is major, and it is the thing Club Cedro, as part of Lubnan Online, exists to put on the record first. Everything else in this issue is read in that light.

Six years, read in order

Founded in Beirut in 2020, which means built through the years HAQQ describes in Q15 without naming them. In February 2026 Sowlutions Ventures led a three million dollar round, reported by Wamda and L'Orient Today, with the platform above 7,000 clients at the time. That is somebody looking at the same company we are looking at, from closer, and putting money behind it. It is the largest confirmed round on the Lebanon tier of our record, where the next reported figure is around 150,000 dollars, and it is a plus on any reading. In July they published the 27. By September they were running a research desk that scores their own competitors in public and a site that now says 15,000 or more legal teams. Both client figures stay on the record with their dates, one reported and one stated, because that is how a figure keeps its standing. Read as a line rather than a snapshot, the direction is a company that keeps publishing more about itself, not less.

The strongest thing here is a boundary, because a boundary can be watched

Abbas Kabalan on the engineering conversation: this works in 97 out of 100, so tell me what happens in the other three, because one of them is somebody's case or somebody's money. And a refusal to build the fully autonomous AI lawyer, stated as a line the company will lose demos over. A published boundary is the one claim in this questionnaire that anybody can audit, by watching what HAQQ ships over the next two years.

The figures on the record, and what stands behind each
ClaimFigureWhere it comes fromStanding
Pass rate, independent evaluation27.0%haqq.ai, 23 Jul 2026. Evaluator unnamed, reports private by defaultIndependent
Hardest subset, HAQQ vs category average5.9% vs 1.1%Same evaluationIndependent
Average across HAQQ's 11 category rubric46.8 / 50haqq.ai. HAQQ's rubric, criteria published, 19 tools scoredOwn rubric, open
Flagship 10 dimension test49 / 50Same rubricOwn rubric, open
Round size and lead$3mWamda and L'Orient Today, Feb 2026. Sowlutions VenturesReported
Clients at the time of the round7,000+Wamda and L'Orient Today, Feb 2026Reported
Legal teams on the platform15,000+haqq.ai, read 15 Sep 2026Company statement
Use cases covered, review pass rate, drafting time, hallucination reduction70 to 85%, 95%, 70%, 85%haqq.ai home page. Not traced by us to a published studyCompany statement
Verified court cases involving AI fabricated material1,598Charlotin database, HEC Paris, as read and published by HAQQ, 9 Jun 2026Third party

03 · The context

A category with no referee, and one company that keeps publishing anyway

Entirely ours. The related piece published with every issue.

Nobody marks the exam

We have not found an independent benchmark for legal AI that buyers treat as authoritative, a regulator publishing comparative accuracy, or a bar association running its own tests and printing the results. The nearest is the Vals Legal AI Report, a private evaluator whose results are public when vendors opt in. In that vacuum every vendor scores itself, and every vendor scores well. A buyer comparing three products is comparing three private exams with three syllabuses, each marked by the people who sat it.

The one independent evaluation we have found a Lebanese company submitting to is the one HAQQ published in July, and its evaluator keeps the reports private. That is the state of the art. It is not good, and HAQQ is not the reason it is not good.

Why the stakes are different here

In a region where a good deal of what looks like coverage was paid for, self reported figures travel further and get checked less. The nine times error is the case study: one page of funding numbers, wrong by an order of magnitude, copied into roundups, decks and research reports until it became the thing everybody knew. Nobody in that chain was lying. Nobody opened the source either.

Legal AI raises the cost of that habit, because the downstream reader is a lawyer deciding what to rely on, and past them, a client. Which is why a company that publishes a 27 is worth more to this category than one that publishes a 95, whatever either number turns out to mean.

How this issue was made

The procedure

How we score

The i is for builders. That is why every gap comes with a suggestion and why the subject sees everything first.

Three things, held together. Being fair. Improving the industry and its players. Being credible. None of the three survives without the others, so a line that is accurate but unfair does not run, a line that is fair but helps nobody is cut, and a line that is fair and useful but cannot yet be shown to be true waits until it can. The reader is owed what the builder is owed. A lawyer deciding whether to rely on this product gets every fact that decision needs, in the same register. Crediting a company for its stage is about tone. It never means the reader is told less.

Every figure carries a standing, and the standing is printed next to it. Independent: measured by a party the company does not control. Reported: carried by named outlets. Third party: a public dataset the company reads and republishes. Own rubric, open: scored by the company on criteria it has published. Company statement: said by the company, not traced by us to anything else. A figure never moves up that ladder by being repeated.

Every question carries a status. Answered. Left open. Nothing is inferred from a left open.

Two tracks, always. Track one reads the company against the category as it stands. Track two reads it against where it started and where it can go. A company is not marked down on track one for something it is credited for on track two.

Lebanon and diaspora are read differently, on purpose. A company run from Lebanon is read with the conditions it chose to build in taken into account, and the choice to stay is a credit in its own right. A company built abroad by a Lebanese founder is read against the market it chose. Both are Lebanese. They are not the same fact, and the register does not pretend they are.

Where a standard is not met, the subject hears it from us first, privately, with the evidence. Nothing of that is published unless the subject asks. What the subject does about it, if anything, is published as their own update, in their words.

A subject's answers are kept separate from anything we collect and compared only afterwards. Nothing publishes one company at a time. The subject sees everything first, our reading included, and corrects facts but does not approve the analysis. Our mistakes are recorded in the same register as theirs. Where we think a subject could go further, we say so to them, privately, with the evidence. Those notes are not published. If the subject acts on any of them, the change goes into the piece as their update, in their words, with its date.

Part of the collection and first drafting is done by MINZÂR, the assistant Club Cedro is building. The name is the Arabic منظار, the instrument an eye looks through, and it is still in development. A person reads, checks and rewrites everything before it reaches a subject. Some of the procedural changes on this issue came out of the exchange with HAQQ: answers now come by email rather than on the PDF, a question is asked once and then left, and a subject's whole site is read before anything is said about what they have not published. Those are standard now, and HAQQ is credited for them.

Corrections

What we got wrong, in the same register as what they left out

A register that only records the subject's gaps tells you nothing about the publication. These are ours, dated, with what changed.

14 Sep

We sent a reading document as a form. The questionnaire had no fields. HAQQ filled it with an annotation tool and nine answers were clipped at the box edge, invisibly to them. We asked for all nine again by email and got them the same day. Every questionnaire since carries an instruction to answer in the email body.

15 Sep

The first draft argued HAQQ's figures could not be checked from outside. MINZÂR, still in development, overlooked the research pages on haqq.ai where the independent evaluation, the published rubric and the hallucination audit sit, and built the claim on the homepage. The draft was withdrawn and this one replaces it.

15 Sep

We told HAQQ they need not answer, then asked again. Seven follow up questions, five of them repeats in softer words, after an email saying their answers could stand. Mark Elian named it: the exchange felt automated. Part of our analysis is produced by MINZÂR, our assistant, which is still in development, and it showed. A question asked once and left open is now recorded as asked and left open.

Left open

Asked, and left as asked

Listed so a reader knows they were put. If any is answered later, the answer goes in as HAQQ's update, in their words, with its date.

Q10

What breaks most often. Not answered.

Q04

A case where HAQQ itself was wrong. Not answered.

Q13

What was turned down after the round. Not answered.

Q05

Whether the liability conversation has happened with a bar association. Not answered.

Sources

Everything checked, and when

  • 16 Sep 2026Mark Elian, by email. The 27.0 percent with its methodology, the liability position restated, Abbas Kabalan's attribution confirmed, Q08 confirmed complete.
  • 16 Sep 2026Legal AI Benchmark 2026, haqq.ai, published 23 July. Read in full. Source for the 61 tasks, 21 jurisdictions, two runs, 27.0 percent, 5.9 against 1.1, and the unnamed evaluator.
  • 16 Sep 2026The 19 Best Legal AI Tools, Ranked by Benchmark, haqq.ai. Source for the 50 point rubric, its eleven categories and published criteria, and the scores of HAQQ, Claude Fable 5, Claude Opus 4.7, Mike OS and Harvey.
  • 16 Sep 2026AI Hallucination Cases, haqq.ai. Source for the 1,598 figure, its 9 June date, and its basis in Damien Charlotin's database at HEC Paris.
  • 16 Sep 2026AI and Legal Tech, haqq.ai. The research listing, read for the count and dates of published studies.
  • 16 Sep 2026Vals Legal AI Report, 27 February 2025, and LawSites on it. Source for which vendors opted in and that LexisNexis withdrew.
  • 15 Sep 2026Mark Elian, by email. The nine answers clipped on the 14 September form, returned in full.
  • 15 Sep 2026haqq.ai, home page. Source for the 15,000 plus figure, the four percentage claims, product names and founders' titles.
  • 14 Sep 2026HAQQ's completed questionnaire, returned as a PDF. Source for Q02, Q03, Q04, Q15, Q16 and Q17, which arrived intact.
  • Feb 2026Wamda and L'Orient Today, on the three million dollar round and the 7,000 plus client figure at the time.
  • 7 Sep 2026The i, letter and questionnaire LAW-001, sent to HAQQ from eye@cedro.club.