There is a shortcut every legal-AI product is tempted by. Build the thing once — usually for the biggest market you can reach — and then run it through translation for every other market. One engine, one set of templates, one body of legal reasoning, rendered into as many languages as you like.

It reads plausibly. That is exactly the problem.

Translation gets the words right and the law wrong

A lawyer in one country does not practise another country's law in translation. The differences are not vocabulary — they are structural, and they go all the way down.

The duty of confidentiality is the clearest example. In England and Wales, legal professional privilege is a strong protection you can nonetheless discuss in terms of best practice and reasonable steps. In some other jurisdictions the equivalent duty is closer to an absolute prohibition — criminally backed, and one the lawyer cannot waive at will. Translate an English privacy notice into another market's language and you get a document that describes the wrong duty, fluently. It will not survive contact with that market's supervisory body, and it should not.

The same holds for the statutes a matter cites, the registers a firm files into, the form a court expects, and the tone a client reads as competent. A calque — literal machine translation from one legal frame into another — reproduces the surface and drops the substance.

What we do instead

Each jurisdiction is built natively. In England and Wales, content is authored to UK statutes, UK regulator language, and the way an England-and-Wales solicitor actually writes. Every other market is authored the same way — to that market's own statutes anchored verbatim, its own professional voice, and its duties as that market's law defines them. Never an English draft rendered into another language.

There is no translation surface on any customer-facing page. If a feature exists in one market and not another, we build it native in the second market or we don't ship it there. A feature that only exists as a translation does not exist.

What that costs

It costs duplication, honestly. Each market means its own body of legal drafting, its own compliance pack, its own set of templates, its own voice to get right. A translation-first competitor can claim more markets faster than we can, and on a spreadsheet their coverage looks broader.

We think that breadth is a liability, not an asset. A firm that trusts a document because it reads well, and then discovers it cited the wrong duty, has been let down in the one place a legal tool cannot afford to fail.

What that buys

It buys a product a lawyer in each market can actually rely on. The privilege gate knows which duty applies — soft-warn where the law allows judgement, hard-block where the duty is absolute. The templates cite the right statutes. The voice reads as though it came from inside the profession, because the drafting did.

This is the through-line for the whole product: built by solicitors, for solicitors, not a generic tool with a legal skin. Native-per-jurisdiction is that principle applied to the map. You cannot translate your way to trust. You have to build to the frame — every market on its own terms.

← All posts