First I wrote about it. Then I built it.
It wasn't easy. A lawyer wrote an article about the future of law. Realized he couldn't wait. Started building it himself.
Where the hours actually go
A moment in every litigator's career. Not about a specific case. About the system itself.
Clauses drafted a thousand times before. Evidence mapped manually into Excel. Statement structures rebuilt that already exist in dozens of variations. Not legal work - assembly work. And clients who pay dearly for it, because there's no alternative.
Not legal work. Assembly work. And those hours cost dearly - for lawyers and their clients.
15 years of international litigation. Arbitrations. Complex lawsuits. The accumulation of thousands of hours - and a moment every litigator knows: The best lawyers in the country wasting time on work a machine could do. I saw it from the inside.
The problem runs deeper than time. The system creates built-in inequality. Budget - perfect statement of claim from a large firm. No budget - mediocre document, or don't file at all. Access to justice depends on what you can pay for technical work.
I wrote that it was years away. I was wrong.
August 2025. Before a single line of code. Sat down and wrote an article. Not a business plan. Not a pitch deck. A professional article on AI and international arbitration. The premise: international arbitration is the natural laboratory for integrating AI into law.
Described a scenario for 2032: AI conducting interviews. Scanning thousands of documents. Identifying contradictions. Preparing witnesses. Generating reports. Wrote that it was far off. Years of development. Conceptual shift needed.
Finished writing. Read what I'd written. Realized I was wrong. Not the analysis - the timeline. Technology is already here. Not 2032. Now.
If I know what needs to be built, and if the technology is already here - then writing about it isn't enough. It needs to be built.
The decision to leave and build
Let's be honest: partner at a large firm, a litigator - not a programmer. The decision to build this myself was not a given.
Something I learned in 15 years: if you see the case clearly, you must act. What I saw was clear. No tech company has 15 years of litigation experience to know what "correct" means in a legal document. Almost no lawyer understands enough tech to build the system.
That gap isn't a bug. It's the opportunity.
What I saw: a product large firms need - but don't yet know they need.
What it took: ten months, full focus, building what a whole team builds - alone. The result: dozens of domains scaffolded, thousands of legal elements, and a checking layer that takes facts to a review-ready draft end-to-end on a real archetype. Production-depth proven on one; the rest is scaffold.
Rebuilt. Not code - approach. Quality checks for legal content, not just structure. Fabrication prevention at the core. Quality control by an uncompromising quality reviewer - no mercy, no discounts.
The principle: Facts in, Law out. Facts only go in. System does everything - causes, arguments, evidence, relief. Doesn't fabricate. Not a fact. Not a document. Not a date. Not an amount. Every word traces to input. Not a technical limitation. An ethical decision from courtrooms.
Built a system that produced documents that looked perfect and contained lies. Broke it down and rebuilt it. This time with quality checks that show no mercy.
"Process passes" doesn't mean "document is valid." Machine producing a document with one wrong fact - professional liability, not a tool. Legal experience becomes the advantage: I know what's broken because I know what's correct.
ORCA is not a document generator. It is a legal reasoning system that renders its conclusions as prose. The five structural moves behind every document: read the full methodology.
What's really different here
ORCA - not "another AI tool for law". Dozens of those exist. Most built by programmers who read about contracts. ORCA was built by someone who wrote briefs. Examined witnesses. Stood before judges.
Programmer builds legal system - "document generator". Litigator builds legal system - decision system.
The difference isn't marketing - structural. Programmer builds legal system = "document generator". Litigator builds legal system = decision system. Facts establish cause? Which is stronger? What will defendant argue? Where are gaps? What's the risk? Not questions for a text generator. Questions that require years in the field.
Let's not fake a story. ORCA isn't finished. But it works - and improves every day. Built from a belief: Lawyers focus on what only humans can - judgment, empathy, strategy, presence. The rest - the machine does. Faster. More precise. With consistency humans can't maintain across 40 pages.
Working with AI is like working with a brilliant junior associate. The speed is astonishing, the knowledge broad, the deliverables look ready to file. Until you actually check.
You discover he cut corners in places an experienced lawyer knows not to cut. That he invents sections when he can't remember the right ones. That he doesn't distinguish between "this could be true" and "this is true".
The rules are the discipline that turns a junior associate into a system you can file with in court.
ORCA's code will be replaced. Similar knowledge bases will be assembled. But three things compound and are harder to copy as a set: cause models built from practice and anchored to a verified statute registry, a deterministic validation apparatus that refuses to ship a document while a hard check is failing, and a replicable encoding methodology. That combination is hard to copy.
We built a jurisdiction-agnostic encoding methodology and ran it end-to-end on a complex non-English legal system - 500+ cause models scaffolded, with production-depth proven on one demanding archetype (a Hebrew defamation statement of claim) behind a deterministic validation apparatus.
ORCA was built exactly the way it works: one expert, with the right system, producing the output of a team.
Every legal rule, every quality check, every template - written from 15 years of litigation experience. Not from research - from the field.
ORCA is a product of ORCA Legal Labs Ltd. (HP 517334603) - a separate corporate entity from Moran's law practice. This story explains the product's origin - it does not constitute legal advice or solicitation of legal services.
I built the tool I wish I had when I started.
ORCA isn't perfect. But it already absorbs the drafting cycle that used to consume my afternoons - without compromising the standard you sign off on. Early access, free.
Try it on your next case See pricing →