Skip to content

By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.

Latent SpaceLatent Space

Building Legal Agents When You Can't See the Data — Jacob Lauritzen, CTO of Legora

Legora can’t read a single trace of what its agent does for a lawyer. The data belongs to the law firm’s clients. How do you build and test an agent when you can’t see its work? Jacob Lauritzen is the CTO of Legora, one of the fastest-growing companies in legal tech history. The team started in a Stockholm basement with ChatGPT, Swedish law, and a search tool. Today, a lawyer can use Legora to draft and edit Word documents, review 10,000 contracts in a single table, or run due diligence. The agent also coordinates work between lawyers, clients, and other agents. When Legora made its own acquisitions, the team used it for diligence. What we talked about • Why Legora resisted adding a model picker for years, and why it finally added one • Jacob’s estimate that models already do about 60% of legal work well, and why the rest takes a smarter model • How three engineers and three lawyers build test environments modeled on customers’ work, much like the “worlds” used in reinforcement learning • A citation problem where the model got it right 70% of the time, then 99% after one release. Legora didn’t have to change anything. • Why Legora runs everything on Azure and why it doesn’t use ElevenLabs • Tabular Review, the million-cell spreadsheet the industry copied down to the name • How intake works, how agents create lists, and how a list can start another agent • What legal engineers and forward-deployed engineers each do, and who gets to write code • The 300 Spartans slide Jacob used to argue that 20 engineers would be enough forever. Now there are 100, and he still feels short-handed. • Why Jacob finds Fable and Opus too chatty for drafting and likes Astra’s concise writing • Why drafting a long contract is a search problem • Whether model labs will cut off legal tools the way they cut off coding tools • What happens to law firm partnerships, the billable hour, and jobs for junior lawyers Legora is hiring engineers in New York, Stockholm, and London. Chapters 0:00 Cold open 0:40 Meet Jacob Lauritzen, CTO of Legora 1:05 Starting out as underdogs in a Stockholm basement 1:54 How Legora grew from ChatGPT with Swedish law into a legal agent 4:12 The switch from assistant to agent 5:23 Which models Legora uses and why it added a model picker 7:48 Are today’s models good enough for lawyers? 8:20 What agents couldn’t do nine months ago 9:18 Testing the agent in simulated worlds and a 10,000-file data room 10:07 The evals team and Legora’s 100 legal engineers 11:03 When evals didn’t seem worth it and one release took citations from 70% to 99% 12:18 What legal practice could look like in five to ten years 14:18 Will the law firm partnership model survive? 16:40 What happens to paralegals and junior lawyers? 18:00 The billable hour and why earlier legal tech fell short 19:39 Where the money goes now 22:44 How Legora used its own product for acquisition diligence 23:59 How Swedish and American law firms differ 26:12 Product metrics when you can’t read the traces 27:41 Paraphrasing traces and narrowing failures down to 10 or 20 types 28:42 Why data privacy led Legora to run everything on Azure 30:04 Open-weight models and model arbitrage 30:55 Transcription models and why Legora doesn’t use ElevenLabs 33:33 The agent, Tabular Review, projects, and the Word add-in 34:24 How a lawyer uses Tabular Review 35:51 Why a spreadsheet works and what you learn from the first 10 rows 37:53 How the legal intake bot works in Slack 39:11 How agents create lists and lists start agents 40:15 Building products on those same pieces and acquiring Wexler 42:37 What forward-deployed engineers do at Legora 43:52 How legal engineers and forward-deployed engineers onboard a big client 46:43 What’s next for the forward-deployed team over the coming year 47:24 Why Legora resisted building APIs 49:26 Can the agent be the API? 50:12 The 300 Spartans slide and the plan to stay at 20 engineers 51:32 The bets nobody asked Legora to make 53:05 Post-training open-weight models for legal research 54:05 Search, retrieval, and late interaction 54:51 What makes a good legal agent harness and why drafting depends on search 56:25 Which model writes the best draft? 57:03 Hallucinations and Legora’s citation system 57:41 Do lawyers check the citations? 58:19 MapReduce or one big context window for a million-token contract? 1:00:16 Getting anonymized examples and the idea of buying a law firm for its data 1:01:53 Why Jacob advises against default embeddings 1:02:44 Will lawyers work in Legora or through Claude? 1:03:26 Will the model labs cut Legora off? 1:04:24 Law schools and scholarships for computer science majors 1:05:28 Hiring in New York, Stockholm, and London 1:06:09 Why most work eventually becomes legal work Guest — Jacob Lauritzen, CTO of Legora https://legora.com Co-host — swyx, Latent Space Host — Basil Chatha, Forward Deployed https://forwardeployed.com

swyxhostJacob LauritzenguestBasil Chathahost
Nov 2, 20261h 7mWatch on YouTube ↗

Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.

At a glance

WHAT IT’S REALLY ABOUT

How Legora builds privacy-first legal agents with evals and workflow primitives

  1. Jacob Lauritzen explains Legora’s progression from a Swedish-law research assistant into an agentic legal workspace that drafts, edits, analyzes, and organizes legal work.
  2. He describes core product primitives—Agent, Projects, Lists, Intake, and Tabular Review—that aim to replace email-heavy collaboration with in-product orchestration.
  3. He outlines how Legora evaluates models using simulated legal “worlds” like a 10,000-file due diligence data room, while acknowledging frequent model regressions across tasks.
  4. He emphasizes the operational reality of legal confidentiality: Legora can’t inspect user traces, so it relies on privacy-preserving signals, failure-mode classification, and anonymized customer examples.
  5. He argues AI will raise lawyer productivity and shift monetization toward strategic judgment and client relationships, while changing (not eliminating) junior roles and billing norms.

IDEAS WORTH REMEMBERING

5 ideas

Legora’s product evolved from simple legal research into a broader “legal agent” that can both do and orchestrate work.

He describes the earliest version as essentially ChatGPT paired with a Swedish law search tool, and says it expanded from question-answering into drafting, editing Word files, organizing files, and running more complex analyses.

Legora is building workflow primitives (not just AI outputs) to reshape how legal teams collaborate.

He says the product now emphasizes not only producing work (research, drafting, analysis) but also “orchestrating” it via collaboration features like Lists, Intake, and Portal, aiming to replace painful email-and-versioned-Word workflows.

Model choice is treated as an internal routing problem, with limited user-facing control.

He says they route different models by task, offer a primary-model picker in the agent (though he’s unsure it will remain), and use specialized models inside certain tools; the discussion frames this as keeping users on the “Pareto frontier” without forcing lawyers to understand model tradeoffs.

Evaluation is structured around realistic project simulations, not isolated benchmarks—and regressions are common.

He says they built evals as simulated “worlds” (e.g., a 10,000-file data room due diligence) and track performance across practice areas/tasks, noting model releases can improve some tasks while regressing others.

Privacy constraints force Legora to learn from approximations and structured feedback rather than raw traces.

He says Legora can’t look at user traces because the documents are highly confidential (often belonging to the law firm’s clients), so they rely on safer paraphrasing, coarse failure-mode classification (e.g., 10–20 types), and customer-provided anonymized examples when available.

WORDS WORTH SAVING

5 quotes

No one believed the smallest startup in a basement in Stockholm was gonna, you know, out-compete this huge behemoth that was, like, way ahead of us in the US.

— Jacob Lauritzen

The way everything started was ChatGPT with a Swedish loss- search tool in it. That was literally the entire everything.

— Jacob Lauritzen

You can't own people, but you can rent them.

— Jacob Lauritzen

We can't look at any traces, basically. We can't look at any data 'cause it's all super confidential, and that's, like, extremely frustrating to work with 'cause you, you basically don't know what people are doing.

— Jacob Lauritzen

I put up this slide of, um, you know, the 300 Spartans and, and, and- for the movie, and I was like, "We're just gonna be 20 engineers for the rest of the company's history, and like we're gonna beat everyone who's much bigger." And we're 100 engineers now, and it feels like we're way too small.

— Jacob Lauritzen

Assistant-to-agent transitionLegal research and precedent searchTabular Review spreadsheet workflowLists/Intake as orchestration primitivesModel routing and model pickerEvals via simulated legal projectsOperating without access to user traces due to confidentiality

High quality AI-generated summary created from speaker-labeled transcript.

Get more out of YouTube videos.

Read along on your phone, search it beside the video, or ask your favorite AI app what was said.