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.

EVERY SPOKEN WORD

  1. 0:00 – 0:40

    Cold open

    1. SW

      People were asking us about Mythos and everything, even though I think realistically a lot of legal work does not require Mythos-level intelligence. Paralegals, gone.

    2. JL

      Yeah.

    3. SW

      Junior lawyers, gone. I don't need them. [laughs]

    4. JL

      Um, that's actually not what we're seeing. And we had one problem where, like, it wouldn't cite properly, and so we were like, "Next model release solved." It went from like [laughs] 70% to 99%. It's just like we did nothing, and, like, great.

    5. SW

      But if you're doing a, you know, $400 million M&A transaction, you're gonna want Legora.

    6. JL

      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. But it's something that I'm toying with is like how much of our product can just be the agent versus all the other stuff.

    7. SW

      [ on-hold music]

  2. 0:40 – 1:05

    Meet Jacob Lauritzen, CTO of Legora

    1. SW

      Okay, we're here in the studio with special guest, uh, Jacob Lauritzen, CTO of Legora. Did I get it right, Lauritzen?

    2. JL

      That's fine. Yeah.

    3. SW

      Lauritzen.

    4. JL

      That's okay.

    5. SW

      I'm not super sure that how-

    6. JL

      And it's Danish. It's Danish, yeah, exactly.

    7. SW

      Does it have a special history meaning?

    8. JL

      It just... No. Sen is like sun, son of.

    9. SW

      Son of Laurits.

    10. JL

      So it's like you have son, and yeah.

    11. SW

      [laughs]

    12. JL

      So son of Laurits. That's my name. [laughs]

    13. SW

      Nice. Uh, we've crossed paths here and there. You, you, you spoke at, uh, AI a few times, and obviously Legora is one of the fastest growing legal tech in history.

  3. 1:05 – 1:54

    Starting out as underdogs in a Stockholm basement

    1. JL

      Yep.

    2. SW

      And, uh, y- you said something at the start in our pre-show that I thought was really interesting. You said that your origin is very European-

    3. JL

      Mm-hmm

    4. SW

      ... uh, even though obviously you're expanding in New York and SF. What feels different about your culture?

    5. JL

      I think we are just at the core probably very, uh, humble about what we're doing because we've always been the underdog from the very beginning. 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. So I think we've always been underdogs, and so we've always been very humble. Um, we've always sort of had to fight for our, uh, existence. Um, I think something we've had to learn as we've also become more and more, um... as we've entered the US and been in the US a lot more, is to be a little bit more, uh, bold and, like, s-s-tell the world how great we are 'cause it, it doesn't come naturally to, I think, some of us.

  4. 1:54 – 4:12

    How Legora grew from ChatGPT with Swedish law into a legal agent

    1. SW

      I kinda wanna start by going over your guys' product 'cause I feel like with a lot of these, like, legal products, you know, they're kinda like under wraps. Like, you know-

    2. JL

      Yeah, sure

    3. SW

      ... you're not supposed to, like, show it. But, um, yeah, if you could just talk about, like, what does the product look like and maybe, like, how did you guys get there? Like, like, what have been the product iterations that got you-

    4. JL

      Hmm

    5. SW

      ... to where you are today? I think that would be really interesting.

    6. JL

      Yeah, absolutely. The way everything started was ChatGPT with a Swedish loss-

    7. SW

      Okay

    8. JL

      ... search tool in it. That was literally the entire everything. And so that's where we started. We started with legal research, which is, like, a huge market basically in the world where, um, lawyers spend a lot of time figuring out what are previous cases that look like this. What's the legal precedent? Like, is this, you know-- what have previous people done in these situations? That's extremely important. Um, and so that has always been part of our product. Basically, we started from, like, an, an agent you could ask questions, then it would query loss. That was the very simple beginning. Um, and then from that it's expanded, and so it's expanded in, like, what can the agent do? It, it will now, uh, you know, draft a lot of stuff really well. It will edit Word files. It will, you know, move your files away, organize everything, um, run really complex analyses. Um, and we've added just a bunch more features to it. So one of our features is called Tabular Review, which is, um, now a name that's being used in industry, [laughs] and we're very happy to see Claude for legal using-

    9. SW

      [laughs]

    10. JL

      ... our terminology for what they're building. [laughs]

    11. SW

      Ooh, we gotta talk about that. We gotta talk about that.

    12. JL

      Which is essentially, like, a way to just bulk extract and bulk review many, many, many, um, agreements, which you do in due diligence and when you raise money or whatever. So that's part of it. It's like we help lawyers just do their work much more efficiently, much, much better. And then outside of just doing the work, we're also now, um, helping orchestrate the work a lot more than we were just even a year ago. So we have different sort of-- We have a, a thing called Lists, which is s-sort of like Linear for us. And, um, we have Intake, which is a way to collaborate with, um, clients. And we have, um, Portal, which is also sort of a way to collaborate, you know, lawyer to lawyer, client to lawyer, lawyer to agent, agent to agent maybe. [laughs] We're, we're spending a lot of time there 'cause, um, there's just frankly the way that you work with a lawyer ten years ago or maybe even today is, is really painful, and there's loads of room to do that-

    13. SW

      [laughs]

    14. JL

      ... in a much better way, to be honest. And so those are, like, I think the two things. It's, it's doing the work, and it's also, like, orchestrating the work.

  5. 4:12 – 5:23

    The switch from assistant to agent

    1. SW

      When did you guys start doing or building the agent?

    2. JL

      So I mean, we've al-- We basically had this switch from the assistant to the agent-

    3. SW

      Yeah

    4. JL

      ... we call it, right? Um, I guess that the agent, I don't know, I wanna say a year ago probably.

    5. SW

      Yeah.

    6. JL

      Um, somewhere.

    7. SW

      So this is a rough timeline for people who are understanding. YC 2023.

    8. JL

      Yes.

    9. SW

      Uh, and then you were, you were a YC founder as well.

    10. JL

      It was YC '24.

    11. SW

      YC '24.

    12. JL

      Yeah, I was in YC '23.

    13. SW

      Yeah.

    14. JL

      Legora was '24.

    15. SW

      Okay. And then, uh, so, so there is-- this is like a little bit pre a- pre, like, agents really taking off.

    16. JL

      Exactly, yeah.

    17. SW

      And then, like, using models obviously changed everything.

    18. JL

      Yes.

    19. SW

      I mean, you know, in one, in one sense today, uh, you know, we had a preview of the products. Uh, it does look... Well, preview. We had a private, uh-

    20. JL

      [laughs]

    21. SW

      ... thing. Well, we will put up a video on the-

    22. JL

      Private screening, yeah

    23. SW

      ... on the YouTube. It's mostly like ChatGPT for lawyers.

    24. JL

      Yeah.

    25. SW

      Right? Like a very-

    26. JL

      Yeah

    27. SW

      ... like, very fair to say that. But then, like, uh, the sidebar has a lot of nice custom tools like the Tabular View, uh, like the in-intake, which I really liked, uh, and, you know, a bunch of other-

    28. JL

      Yeah

    29. SW

      ... things.

    30. JL

      Exactly. That, that's, that's exactly what it is. It's, it's CoWork or ChatGPT-

  6. 5:23 – 7:48

    Which models Legora uses and why it added a model picker

    1. SW

      Yeah. What models are you guys using underneath? Like, can you talk about that?

    2. JL

      I mean, we're using a, a bunch of different ones depending-

    3. SW

      Yeah

    4. JL

      ... on task, right? That's, um-

    5. SW

      Okay. And then that's not available to the lawyer to see. You guys picked yourselves.

    6. JL

      For the agent... Yeah. Well, we've been back and forth on this.

    7. SW

      Yeah, yeah. [laughs]

    8. JL

      Yeah, just like everyone else, I think. In the agent, there's a model selector for the primary model, but there are certain tools that we use different models in, and there's, like, Tabular View, and, like, we, we try. I think we found it most effective to subdivide the problem and, and, and route on, like, as we subdivide the task. But we do right now have a, a picker- In the agent.

    9. SW

      Mm-hmm.

    10. JL

      I'm not sure if that's gonna stay there always, to be honest.

    11. SW

      Ah.

    12. JL

      Um, so yeah.

    13. SW

      Yeah, I mean, so I bring a little bit of context to this because I'm advisor for cognition.

    14. JL

      Yeah.

    15. SW

      Uh, and when I joined, you know, part of my, my thesis for what an agent lab is, an agent lab is a, you know, uh, ideally a domain-specific GPT wrapper.

    16. JL

      Yeah.

    17. SW

      Right? Like we-

    18. JL

      Yeah

    19. SW

      ... we, we run the, uh... We are the domain experts. We'll pay attention to you. We'll, we'll serve your needs way, way more than the frontier labs, and we'll give you the best of the frontier labs-

    20. JL

      Yeah, we'll abstract away all the-

    21. SW

      ... according to our judgment.

    22. JL

      Yeah.

    23. SW

      See, our job is to decide for you because your not, your job is not to-

    24. JL

      Exactly

    25. SW

      ... use models.

    26. JL

      We'll always keep you on the Pareto frontier-

    27. SW

      Yes

    28. JL

      ... and make sure that it just is great all the time, and you don't have to dive into all the details. 'Cause like, one of the things that I've... Exactly to this point, if you go to a lawyer and you ask them, "Oh, you're gonna, you know, uh, draft this contract based on this precedent, do you think that's a Sonnet high or an Opus mid task?" [laughs]

    29. SW

      Like, you know, they, they won't know.

    30. JL

      Just give me the smartest model.

  7. 7:48 – 8:20

    Are today’s models good enough for lawyers?

    1. JL

      Yeah.

    2. BC

      So you think the models are already, like, as good as lawyers need? Like, there's no need for them to get better?

    3. JL

      It's a... I think it's a power distribution. So like, there's probably like 60% of the work-

    4. BC

      Yeah

    5. JL

      ... we can do really, uh, well right now, and the... You know, from now on, it's like a cost and latency thing. But then there's the rest of the, the thing where especially for, like, very complex analysis, we, we still need more intelligence. And then I think there's also just the work expanse kind of. It's like that's the work that we have right now, but also the work before the lawyer who thus probably expands with intelligence-

  8. 8:20 – 9:18

    What agents couldn’t do nine months ago

    1. BC

      Yeah

    2. JL

      ... I imagine.

    3. BC

      Early on, like, when you guys first started, I guess, transitioning to the agents-

    4. JL

      Mm

    5. BC

      ... or building the agents, like, what were... like, what models were you guys using? I guess it would've been, like, Opus 46 or something.

    6. JL

      That would've been, yeah, Sonnet 46, Opus 46 is probably right.

    7. BC

      What were the agents, like, not good at at that point-

    8. JL

      Mm

    9. BC

      ... that they're much better at now, even though it's only what, like-

    10. JL

      Yeah

    11. BC

      ... nine, nine months later?

    12. JL

      Sub agent delegation was one of them that we've gotten working really well now for, like, fan out type retrieval queries.

    13. BC

      Yeah.

    14. JL

      Works extremely well for us now. Um, that was difficult before. We basically track... So we have a team that's just doing evals, and so we track all of the models' performance in different practice areas, which is like subgroups of, of legal, and different tasks across all of those. So we basically have, like, a big heat map, and we're like-

    15. BC

      Hmm.

    16. JL

      And then we can see them move, and it's like usually they improve most stuff, but there's actually a lot of model releases where they improve some and, and regress in others.

    17. BC

      Okay.

    18. JL

      And that actually happens a lot more than you'd think.

  9. 9:18 – 10:07

    Testing the agent in simulated worlds and a 10,000-file data room

    1. BC

      Like, what are some of those tasks? Like, are you familiar with how you guys are running a lot of the evals?

    2. JL

      Mm. Yeah.

    3. BC

      Like, what, like, what are those different subsegments, I guess, that you look at?

    4. JL

      Yeah. So, like, there's, um, there's different just, like, framing stuff. So we have different basically, like, worlds, like RL environments essentially, which is like, "Here's a..." 'Cause, 'cause lawyers work in projects always, more or less. So it's like, "Here's 10,000-file data room. You're doing a due diligence. In the end, a great report looks like this. Like, it contains all these ri- red flags, and, like, it doesn't contain whatever weird, uh, stuff, and, like, we want it to be concise," et cetera, et cetera. That's kind of how we've built it. So there's different tasks, which is like part of it is drafting a report. Like, does the draft look good? Does it contain all the right stuff? Is the wording sound, the analysis sound? There's also the part of finding the red flags, like the analysis before that. So we can kind of like subdivide it a little bit, and then, and that's how we run the evals.

  10. 10:07 – 11:03

    The evals team and Legora’s 100 legal engineers

    1. BC

      Interesting. Like, what does your evals team look like? Like, do you hire lawyers to, like, do that?

    2. JL

      So yes. It's a mix. We have, uh, engineers, and then we have lawyers, and it's one team. So there's like three engineers and like three lawyers right now, and then we have a pool of what we call legal engineers, which is, um, people that have worked in Big Law for like three or four years. Typically, maybe they have a CS degree, and, like, they're very tech forward, and then they come to us and because they wanna, like, help change, uh, the industry.

    3. SW

      Are they IT in Big Law, or-

    4. JL

      No

    5. SW

      ... they're lawyers?

    6. JL

      They're lawyers in Big Law.

    7. SW

      They're lawyers in Big Law.

    8. JL

      Yeah.

    9. SW

      With CS degrees.

    10. JL

      Yes. [laughs]

    11. SW

      Oh my God.

    12. BC

      Must be really hard to find those.

    13. JL

      It's a Venn diagram that... Yeah, exactly.

    14. SW

      [laughs]

    15. JL

      That's like our hardest person to hire for. [laughs]

    16. SW

      [laughs]

    17. JL

      But they're also such a force multiplier 'cause we can pull on them for the eval stuff and for the product development. It's just like you have a pool of 100 experts that use the product every day and go and talk to clients every day, and also, like, they live this and have lived this, and we just pull on them to do evals and to, like, help us shape the product, and it is such a, such an advantage.

  11. 11:03 – 12:18

    When evals didn’t seem worth it and one release took citations from 70% to 99%

    1. BC

      And curious, like, when did you guys start that team?

    2. JL

      Evals, um, grew out of the assistant agent team at some point. I think there was a point up until recently where it was like, honestly, just not really worth it 'cause, like, all models just got better. So it was like, do we wanna spend a lot of our time doing really complex evals, or do we just, like, wanna build... 'Cause there was so much to be gained from building a better harness and, like, just sort of leaning into everything's gonna improve, and everything kind of just improved.

    3. BC

      Hmm.

    4. JL

      But-

    5. SW

      Yeah, like every two, three months you get a different tier model

    6. JL

      ... it just like solved. I'm-- Yeah, exactly. I mean-

    7. SW

      Just pass it through, right?

    8. JL

      Exactly.

    9. SW

      Yeah.

    10. JL

      I mean, we had one problem where, like, it wouldn't cite properly, and so it would be difficult to follow, and it was like next model release solved. It went from like [laughs] 70% to 99% [laughs] . It's just like we did nothing and, like, great.

    11. SW

      Yeah. Maybe the, the, the real work is, uh, you know, keeping all the data private, making it-

    12. JL

      Yeah

    13. SW

      ... taggable, sortable, ad- adding new features like the, the tabular view.

    14. JL

      Yep. Yep.

    15. SW

      Maybe is that the... You know, may- like-

    16. JL

      You mean over and above ChatGPT?

    17. SW

      Well, I mean, like, yes. But obviously now you're also doing evals.

    18. JL

      Sure.

    19. SW

      I assume your, your use of open models is also increasing.

    20. JL

      Yes. Yeah.

    21. SW

      We can talk about that. Uh, so yeah. I, I don't know what I'm saying here apart from like, you know, what is the job?

    22. JL

      The job is- Yeah ... uh, maybe not... Uh, in the early days, it was not so much to do, do evals- Mm ... because it was mostly exposed model capability-

  12. 12:18 – 14:18

    What legal practice could look like in five to ten years

    1. JL

      Yeah ... to lawyers. Yeah. The huge part of it is just, um, figuring out what does the legal profession look like in five years, 10 years with all of this stuff. Like, coding is maybe a year or two ahead, so, like, we can kinda look to that a little bit, but, like, what are the primitives? How do people work? How do you collaborate if it's not a 200-thread email with, like, V5 Word files back and forth? Like, what does that look like? And that's, like, not even necessarily purely AI. That's just, like, build [laughs] a much better product experience- Yeah ... and make sure you do it with, like, audit logs and data retention and all of those sort of really important things in regulated industry. And then there's the, the AI part, which is, like, make the work faster and better, and, and proactive agents that react to stuff when it comes in, so you don't have to, you know, uh, kick off everything. So I think a lot of the work is just figuring out what do we think it's gonna look like in five years. If, you know, model, um, capabilities keep increasing, if price keeps coming down, what could we do? Can you log in, and it's, like, command center, where it's just like, "You need to react to these five things that the agents have been doing lately, and, like, review and check and improve the system"? Maybe that's where we're going, or is where we're going. Yeah, yeah.

    2. BC

      Yeah, I was gonna ask, like, could you go into that in a little more depth? Like, yeah, what, what is the, like, law profession gonna look like in a few years?

    3. JL

      [laughs] I should preface this by saying I don't know.

    4. BC

      Yeah.

    5. JL

      I mean, who knows really? But, um, I think we can look to coding a lot. I think, um, all lawyers are gonna be way more, uh, productive than they were before. They're gonna be able to do a lot more stuff at a higher quality, uh, for, uh, lower cost. I think the profession itself, the work itself, is gonna improve a lot. It's gonna be a lot more... I think lawyers are gonna spend more of their time doing the stuff that they became lawyers to do, uh, you know, figuring out what's the right risk profile, which manageable risk, what's, like, the... all of their judgment, strategic judgment, and, like, working with clients. They're gonna do that a lot more, and much less of the, like, trawling through big documents to, like, find the smoking gun or, like, do all this menial, super annoying work that a lot of lawyers have been doing.

  13. 14:18 – 16:40

    Will the law firm partnership model survive?

    1. BC

      What do you think's gonna happen in the partnership model? Like, do you think that stays, or, like, what happens?

    2. JL

      I gave this... Uh, I actually gave this a lot of thought just, like, last week.

    3. BC

      Yeah.

    4. JL

      Yeah. 'Cause the, the partnership model, I don't wanna get, uh, into too much of the details, but, like, the partnership model kind of exists because the only type of capital that these companies have is human capital. So, like, it's not like, you know, us or, like, a software engineering firm or, like, a manufacturer or whatever. You h- you have physical assets or, like, some sort of intangible assets that, that you accrue over time, and, and they pay dividends to the shareholders. But if you work in an industry like professional services, and it's the same for, like, uh, consultancies and, and whatever else, all of your value is in your people, and you can't really own human capital. You know, you, you can't [laughs] you know, slavery's abolished. You can't own people, but you can rent them. You can pay them money. And so partnerships essentially is a structure where you make the human capital the owners of the company so that they stay.

    5. BC

      Yeah.

    6. JL

      Will that change? Like, I don't... It doesn't have to, but I think what we really wanna do with lawyers, we actually want lawyers to be able, law firms to be able to build some sort of intangible capital, some durable capital. And, like, you can build a system that learns of how you work. A lot of firms right now think about, like, well, there's the X law firm way of doing things, and we can codify that, I think. And we can build a system. And whether that's, like, a self-improving knowledge graph or whatever it is, and, like, precedent files and documents, where there's, like, a way of working that produces a really good out- output, and that can be their IP. So it's, like, a way to codify the human expertise and judgment into a system. That, I think, is... Now I'm just rambling completely, but, like, um, that's something that we want to help empower. Mm. And does that change the partnership model then? 'Cause the incentives are different in the partnership model. You just gotta bring more clients, and you don't wanna take away time from bringing in clients to codify your information, basically. Mm. 'Cause, like, you get rewarded from, you know, eat what you kill or- Yeah ... make this lockstep, whatever. Um, that needs to change a little. We need to figure out an incentive structure where partnerships, uh, partners are incentivized to codify things for, to build an asset for the company. But right now they aren't, 'cause as soon as they leave the partnership, they don't, um, get any dividends from the assets that they built. Yeah. So there's, like, a... Yeah. I think the, the, the whole business model is, is, uh... We'll, we'll see. [laughs]

    7. BC

      Yeah, yeah. It's all, it's all in question

  14. 16:40 – 18:00

    What happens to paralegals and junior lawyers?

    1. BC

      right now.

    2. JL

      Yeah. My, my actual other take, y- you know, so n- on the partnership level, that's, like, the top end of the- Mm ... the industry. Actually, my take is more on the bottom end, right? Yeah. What happened there? Uh, paralegals, gone. Yeah. Right? Like, junior lawyers, gone. Mm. I don't need them. Yeah. Like, it's, um- [laughs] That's actually not what we're seeing. Okay. So, yeah, there's a... I think it's... I don't know. Would you, would you say that we're seeing that in engineering? Uh, yeah. Yeah? So, uh, junior engineers are- Really kind of cooked ... kind of cooked. Yeah. Like, you kinda have to come out of, uh, drop out of university fully baked, or else you're [laughs] Or else you're not gonna make it. [laughs] Yeah. Um, I feel like I'm, I'm being a bit dramatic- Yeah ... for, for, uh, comedic purpose, but, like, uh, yeah, I know a lot of lawyers, they started as paralegal. They go through law school, all these things, right? Yeah. And now they don't, they're not needed. Yeah. They're seriously just not needed. Yeah, yeah. Yeah, it, it's interesting what happens to the partnership model, like, the pyramid. I think generally a lot of lawyers, um, you still need ju- you need the next generation. And at least for engineering, the way I think about it is you have a good engineer today, they're worth a lot more even than they were two years ago 'cause they can produce so much more stuff, like, if they're good. And I think it's the same thing in legal, where, like, they can actually do a lot of really good work if they're good. So I think it's more that, like, really good lawyers or junior lawyers are worth a lot more. Yeah. It's- And- It's always been the case, right? Yeah. Yeah. Exactly. But it's even more so. But it's like, it's, yeah, it's polarizing even more so.

  15. 18:00 – 19:39

    The billable hour and why earlier legal tech fell short

    1. JL

      Yeah.

    2. BC

      I'm actually curious about that. So, like, the whole, like, law business is basically, like, um, charging per hour.

    3. JL

      Mm.

    4. BC

      So-

    5. JL

      Yeah

    6. BC

      ... you know, if each project now can be done-

    7. JL

      Is faster

    8. BC

      ... a lot faster-

    9. JL

      Yeah

    10. BC

      ... is it going to be, like, way cheaper? Like-

    11. JL

      This was actually-

    12. BC

      Yeah

    13. JL

      ... so, um, fun story. I was- I was reading Max's YC application, uh, and, like, helping him getting into YC, uh, Leia as it was called back then in YC. And this was my one thing. I was like-

    14. SW

      And, and curious, Leia is a Danish thing for something?

    15. JL

      No, a Swedish.

    16. SW

      Swedish.

    17. JL

      Um, no. Also, it means nothing. [laughs]

    18. SW

      [laughs] Okay, okay.

    19. JL

      There's this really funny story in, um, I think it was a Spanish newspaper that wrote about us in the early days, Leia, and then they, they explained that the abbreviation was Legally Efficient Yoda Assistant. [laughs]

    20. SW

      [laughs] Why Yoda?

    21. JL

      Yeah, I don't know. [laughs] I'm just like, "Why, why is it-"

    22. SW

      See, hallucinations are not just from LLMs.

    23. JL

      No, I think journalists hallucinate. [laughs]

    24. SW

      [laughs]

    25. JL

      Um, but no, it, it doesn't mean anything.

    26. SW

      Mm-hmm.

    27. JL

      Uh, so he wrote the application. He, he wr- And my feedback to him was, um, you know, "People have tried this a million times. Legal tech has never been a thing 'cause, like, there's no incentive for lawyers to, to... Why would they be more efficient? They earn less money. Like, it doesn't make any sense." But I think the reason that lawyers do wanna adopt this is that they understand the gravity of the situation. They know that, like, the business model and everything is under pressure, and it's like they need to change 'cause the competitive pressure's so high. The billing model itself I think is also gonna change. We've, we're already seeing that, particularly in the US, that a bunch of stuff is actually being priced on, like, a project fee and not on an hours fee. Um, particularly the, like, sort of lower-end stuff on the spectrum, like, whatever it is, like small reviews and whatever. Some of it honestly is being done for free.

    28. SW

      Mm.

    29. JL

      And some of it is just being priced on a flat rate.

  16. 19:39 – 22:44

    Where the money goes now

    1. SW

      So where is the money being made then? Is it... 'Cause I, I-

    2. JL

      In the strategic work.

    3. SW

      Yeah, I feel like a l- lot of what you guys talk about is M&A specifically, like that's where all the money is made.

    4. JL

      That's just a, a very easy example.

    5. SW

      Oh, okay, okay.

    6. JL

      Yeah, yeah. Litigation's also. The big work still is there, and it's very valuable, and so they'll, they'll spend-- lawyers will spend more of their time there. Client relationship's also super important.

    7. SW

      Like a CRM?

    8. JL

      No, just like spending more time with the client.

    9. SW

      Oh.

    10. JL

      Like, a lot of law firms will or historically have basically done stuff for free just to have that relationship with the client.

    11. SW

      Yeah, yeah.

    12. JL

      Uh, and so now they can do that, but they don't have to lose a lot of money on doing it. [laughs]

    13. SW

      Wait, I thought, I thought I just-- I have to pay s- the lawyer money just to be my friend. Like, this, like-

    14. JL

      Yeah. [laughs]

    15. SW

      ... isn't that the retainer thing?

    16. JL

      Yeah. [laughs] Yeah. Yeah, that, that, that's, that's-

    17. SW

      You, you, you tell me I can do it for free? Like...

    18. JL

      Yeah, you just have to find the right lawyers, yeah.

    19. SW

      Oh, goddammit. [laughs]

    20. JL

      [laughs]

    21. SW

      Uh, okay, cool.

    22. JL

      Or Latent Space has to grow much bigger. I don't know.

    23. SW

      Yeah, yeah, we're trying. We're trying. [laughs]

    24. JL

      [laughs]

    25. SW

      Uh, you know. Yeah, so okay, so, so, uh, uh, so you're saying, um, you know, obviously the, the strategic work and all this high-value add is still there.

    26. JL

      Mm.

    27. SW

      But our legal fees are not going down. But you also said paralegals are not affected-

    28. JL

      Mm

    29. SW

      ... or, like, they're, they're just shifting. And, and this is something that, uh, we also did, we, uh, worry about with Cognition.

    30. JL

      Yeah.

  17. 22:44 – 23:59

    How Legora used its own product for acquisition diligence

    1. JL

      No. [laughs]

    2. SW

      I have a question. So you guys bought a company, Kira.

    3. JL

      Yes.

    4. SW

      Is, is that how you say it?

    5. JL

      Yeah. Yeah.

    6. SW

      And you, you guys used your own product to do the M&A?

    7. JL

      Yes, we do that all the time.

    8. SW

      So how did that work?

    9. JL

      Yeah.

    10. SW

      Like, can you talk a little bit about that?

    11. JL

      Ooh, dogfooding.

    12. SW

      Yeah.

    13. JL

      No, that works great. We're doing that a lot. Our legal team is, is... I mean, intake has been built with our legal team.

    14. SW

      Yeah.

    15. JL

      'Cause right now we have a Slack workflow where everyone floats their stuff in, and they're like-

    16. SW

      Yeah

    17. JL

      ... "This is annoying".

    18. SW

      Yeah, yeah.

    19. JL

      Right? And inefficient. So it's like, great. We should use Legora for that.

    20. SW

      Yeah, yeah. Uh, can you talk a little bit about that? Like, you know, what that process looked like?

    21. JL

      Yeah, absolutely. So it's, it's, um, we, uh, do a lot of the due diligence ourselves because we can do it, uh, with Tabular Review and other tools. We do still have counsel coming in-

    22. SW

      Mm

    23. JL

      ... um, to, like, assess certain risk or, like, you know, there's payroll. And so Kira was simple 'cause that was all in Sweden, but, you know, we've done one in Canada and one in Australia, and so there's, like, payroll in Australia. Okay, do we want someone to look at this, like, a bit more strategically? So there we will still use lawyers for the strategic part, where they can actually be sparring partners and help us a lot on, like, how to figure out how to structure this the right way. But a lot of the more menial stuff we could actually just do ourselves.

    24. SW

      Mm.

    25. JL

      So, like, a lot of, uh, yeah, a lot of the early things we would find, and we have had cases where we found something, uh, [laughs] that's been, like, a red flag, and then we've, we've pulled the brakes.

    26. SW

      Can you talk a little bit about any of those?

    27. JL

      No, I don't think so. [laughs]

    28. SW

      [laughs]

    29. JL

      Yeah.

  18. 23:59 – 26:12

    How Swedish and American law firms differ

    1. SW

      All right. Early on, you said you, your early customers were Swedish-

    2. JL

      Mm

    3. SW

      ... like Swedish law firms.

    4. JL

      Yeah.

    5. SW

      Have you seen a difference between working with, like, Swedish law versus, like-

    6. JL

      Yeah

    7. SW

      ... American law firms-

    8. JL

      Mm

    9. SW

      ... that sort of thing? And you guys are mostly working with, like, big, big law firms, right?

    10. JL

      Well, we're also g- smaller law firms also.

    11. SW

      Oh, okay.

    12. JL

      No, we st- we definitely started really, really big law firms, but 50 lawyers also. Use us and, and get a lot of value.

    13. BC

      Yeah. So have you seen differences between working with, like, the Swedish ones-

    14. JL

      Yeah

    15. BC

      ... versus American ones? Maybe, like, even-

    16. JL

      Mm

    17. BC

      ... I don't know, Asian ones? [chuckles]

    18. JL

      Yeah, yeah. I think the European ones, um, have been a bit slower to move. The American ones are very forward, um, move really quickly. I think, uh, it's also very high on their agenda of the American companies, more so than the, uh, European ones, I think. It's, like, a strategic, super important thing we need to just, like, do a lot here. The American companies generally, both corporates and law firms, also have a much higher appetite to, like, custom-build stuff. That's, like, a thing that they all want to do. Like, "Hey, we wanna build this, like, huge thing with you guys and, like, structure it in whatever way." Whereas Europeans-

    19. BC

      What-

    20. JL

      ... are much more like, "We'll just take the off-the-shelf and figure it out"

    21. BC

      What's an example of something they would wanna build themselves?

    22. JL

      Integrations into their own. Like, some of these customers build their own CRM and their own-

    23. BC

      Ah

    24. JL

      ... uh, document management system, and their own all sorts of stuff, and they want to build that, and then they want to build triggers that, like, you do a review in, in, in Salesforce and it goes to this one person for whatever reason, and they do something, and then it goes into Legora, and then it goes back in. And there's-- so that's, like, the simple end, and then there are some that are extremely ambitious, where it's, like, a whole new product that they want to build with us, and I-- you know, we can't really do that. [chuckles]

    25. BC

      Yeah, yeah.

    26. JL

      Um, but, but that's definitely a thing where, like, American companies really want, um, to build their own more than European ones do.

    27. BC

      And the European ones are like, "Hey," like, you know, they give you product suggestions or-

    28. JL

      Yeah, for sure. I mean, we have-

    29. BC

      Yeah

    30. JL

      ... great collaboration with all of them.

  19. 26:12 – 27:41

    Product metrics when you can’t read the traces

    1. JL

      to achieve it.

    2. BC

      Okay. Another question I think maybe y-you wanna bring this up is, like, product metrics. Like, how do you know-

    3. JL

      Mm

    4. BC

      ... that, like, you know, we're actually doing-

    5. JL

      Yeah

    6. BC

      ... something good here?

    7. JL

      Yeah. Yeah. Mm-hmm.

    8. BC

      How do you think about that? I'm assuming that's also related to evals.

    9. JL

      So we have the regular product metrics that we care a lot about. Are people spending a lot of time in our product? Uh, do they seem to get a lot of value out of it? Do they renew it? Do they come back a lot? We have really good numbers for an enterprise, uh, software of, like, our DAU over MAU and our, like, uh, you know, hours spent per month on the product are extremely high. And then we do some sort of-- we do online evals also, where it's like, try to figure out generally, like, do we solve the problem here? Just where-- with, like, a super cheap LLM message, just try to just, like, have an online metric, and then we can use that also when we do rollouts of new things. We can just, like, compare feature flag wise, okay. Does it-- did it impru-improve or, like, did it catastrophically decline? Because one thing actually that's might be interesting that's difficult for our business is 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. [chuckles] So it's like, here's an agent and it can do so many amazing things, and I have no idea what people are actually doing with it.

    10. BC

      I would've assumed you guys, like, signed some sort, sort of agreement with the-

    11. JL

      Yeah

    12. BC

      ... law firm, and they were like, "Oh, yeah, sure."

    13. JL

      I wish. Yeah, I wish. No, but the thing is, like, a lot of the data that they have is not even, even theirs, right? It's their clients.

    14. BC

      Oh.

    15. JL

      And it's super confidential, so we can't look at it. And so basically we have an evals team that's, like, trying to approximate-

    16. BC

      [chuckles]

    17. JL

      ... what we think everyone is doing and, like, build that into eval sets. Um-

    18. BC

      Wow

    19. JL

      ... so that's just, like, a super annoying kink of

  20. 27:41 – 28:42

    Paraphrasing traces and narrowing failures down to 10 or 20 types

    1. JL

      the business.

    2. SW

      Can you do paraphrase? So for example, ChatGPT has, like, a slash feedback thing-

    3. JL

      Mm

    4. SW

      ... uh, that directly fully says the full trajectory.

    5. JL

      Mm.

    6. SW

      But obviously that would-- that is not possible-

    7. JL

      Yeah

    8. SW

      ... for you guys.

    9. JL

      Mm.

    10. SW

      Uh, but you can use an LLM to paraphrase, like, from this real thing-

    11. JL

      Yeah

    12. SW

      ... make a synthetic thing that is, like, close enough, but change all the names, change all the details-

    13. JL

      Yeah

    14. SW

      ... but, like, still-

    15. JL

      Yeah.

    16. SW

      Yeah.

    17. JL

      We can't re-- There's, I mean, there's always a, a, a, a range, right, of, like, if you, if you paraphrase all the way down to, like, three values and you pick one of them, then obviously that's fine. If you, if you just remove the names, then that's may-maybe not fine.

    18. SW

      Yeah.

    19. JL

      And so, like, we are, um, generally pick the, the most safe way.

    20. SW

      Okay.

    21. JL

      So, like, we, we restrict ourselves as most possible 'cause we, you know, there should be-

    22. SW

      Yeah, that's fair enough

    23. JL

      ... no risk at, at all.

    24. SW

      Yeah.

    25. JL

      Um, but there are things where it's like, okay, we know that the failure modes are probably these ten or twenty, so we can, uh, classify it into one of those, and that's-

    26. SW

      Yeah

    27. JL

      ... a helpful signal. Uh, we can classify it into the ta-types of tasks and the practice areas also, and then, like, we have an idea. It's something that we're always trying to, to figure out how to do in a smart way.

  21. 28:42 – 30:04

    Why data privacy led Legora to run everything on Azure

    1. BC

      Also, like, on the privacy front, I guess, um, I'm assuming even two years ago it must have been, like, insanely difficult to get the law firms to be okay with this.

    2. JL

      Yes.

    3. BC

      But, like-

    4. JL

      Yeah

    5. BC

      ... how do they think about their data being sent over to Anthropic or-

    6. JL

      Yeah. Yeah, yeah

    7. BC

      ... you know?

    8. JL

      Yeah.

    9. BC

      It must be, like, a huge thing.

    10. JL

      This-- All of our infrastructure is on Azure-

    11. BC

      Yeah

    12. JL

      ... um, primarily for this reason. 'Cause, like, when we started, law firms were like, "AWS? No."

    13. BC

      Yeah. [chuckles]

    14. JL

      Like, "No way. We don't trust AWS."

    15. SW

      Law firms don't trust AWS?

    16. JL

      Yeah, yeah.

    17. SW

      Why?

    18. JL

      It's different now. No, but it-- they were like, "Amazon, Google-

    19. SW

      [chuckles]

    20. JL

      ... we can't trust them with any of our data." So we basically, we had to host everything on Microsoft 'cause they already have 365.

    21. BC

      Oh, so they're okay with Microsoft but not-

    22. JL

      Exactly, 'cause they've already done, like, whatever security review-

    23. BC

      Oh, oh

    24. JL

      ... et cetera, for all of their documents and all of their Word and whatever. So, like, Microsoft is an approved vendor in their mind, and so we had to host everything on, on Azure, and that's changed over the past few years.

    25. BC

      Mm.

    26. JL

      So, like, now people understand, okay, we need to get on cloud, we need to do all this kind of stuff. Um, there was also a lot more people talking about on-prem back then. That's also disappeared completely. People understand that, like, you should just do it in the cloud and it's, and it's safe, and it's probably safer than what you're doing.

    27. BC

      Yeah.

    28. JL

      Um, so that's changed a lot, but I think we can-

    29. SW

      Yeah, and by the way, it's only been three years, so, like, it's actually like-

    30. JL

      Yeah. [laughs]

  22. 30:04 – 30:55

    Open-weight models and model arbitrage

    1. BC

      So also then on, like, open source models now are getting really good.

    2. JL

      Mm.

    3. BC

      So yeah, how are you thinking about that with the-

    4. JL

      Yeah. The-- We're just thinking about, to, to your point, um, just bring our clients along on, like, the Pareto frontier.

    5. BC

      Yeah.

    6. JL

      And, like, the, on the, the map of all the models and what they're good at and their latency and their cost and their, their Governance and, and, and their, uh, regional availability, how do we just optimize across all of that? So some open-weights models are great for certain tasks, and then we'll use them there. Um, some we'll post-train, and, and some we'll just use the frontier models.

    7. SW

      Yeah. You call, uh- call it model arbitrage.

    8. JL

      Yeah.

    9. SW

      Uh, you have different, uh, favors. You did some research on this where you were firmly anthropic at the start of the year. Uh-

    10. JL

      Yeah

    11. SW

      ... Grok is improving a lot. Um, yeah, you wanna give an example of a model that wasn't ranked highly overall, but, like, you wanna shout it out as, uh, surprisingly good?

  23. 30:55 – 33:33

    Transcription models and why Legora doesn’t use ElevenLabs

    1. JL

      Yeah, I think not overall good. Gemini, one of the early Geminis is-

    2. SW

      Ooh

    3. JL

      ... uh, yeah, extremely good for certain types of, um, uh, transcription-

    4. SW

      Yeah

    5. JL

      ... and speaker attribution. So we use that for transla- um, transcription actually.

    6. SW

      Oh, so you have a, a-

    7. BC

      Yeah, were you guys transcribing?

    8. SW

      Like a Granola?

    9. JL

      We don't have... We actually probably will build, like, a meeting thing.

    10. SW

      Yeah.

    11. JL

      But this is just like talk-to-spe- speech-to-text-

    12. SW

      Ah

    13. JL

      ... text-to-speech, just like an- an, um, any wor- any other app [chuckles] that has this. And we do actually also transcribe files. If you upload hearings or whatever-

    14. SW

      Oh

    15. JL

      ... we'll, we'll then, like, transcribe them, put them into text, and so we can do all of our analysis on it.

    16. SW

      No ElevenLabs. [laughs]

    17. JL

      No ElevenLab for DPA reasons. Same thing as, like, yeah, data processing agreement, I should say. So, like, our data processing agreement has very few vendors on it-

    18. SW

      Yeah

    19. JL

      ... 'cause we just need to keep it-

    20. SW

      You just need to keep it for-

    21. JL

      Exactly. We need to keep it-

    22. SW

      Tight

    23. JL

      ... super tight-

    24. SW

      Yeah

    25. JL

      ... on where any data goes. And so, um-

    26. SW

      I think, no, that, that is one of the benefits of, like, a Gemini and OpenAI where they're like, you, you come to us, we have most of the things that you need.

    27. JL

      Yeah.

    28. SW

      And that is actually va- very valuable. Even if it's like it doesn't have to be, like, state-of-the-art. As long as it's, like, mostly good enough for all tasks-

    29. JL

      Yeah

    30. SW

      ... then who cares?

  24. 33:33 – 34:24

    The agent, Tabular Review, projects, and the Word add-in

    1. SW

      I do want to cover a little bit on the, the agent product side. Uh, so we've covered a few, like, of, of the top-level stuff, right? Uh, we've already name-dropped Tabular Review.

    2. JL

      Mm.

    3. SW

      Uh, we've name-dropped Intake.

    4. JL

      Yeah.

    5. SW

      And you've, you've got some other, uh, stuff that we haven't even, uh, touched on yet. But I just wanna cover the, the big two, let's call it.

    6. JL

      Yeah. Yeah. Sure.

    7. SW

      Is it- is that- is, is that fair to say that they're the big two, approximately?

    8. JL

      Agent and Tabular Review.

    9. SW

      Yeah.

    10. JL

      Uh, and our-

    11. SW

      And projects

    12. JL

      ... probably-

    13. SW

      Yeah

    14. JL

      ... yeah, and our Word add-in, um-

    15. SW

      Okay

    16. JL

      ... is also something 'cause that's p- a lot of people work, work inside of Word, and so our Word add-in-

    17. SW

      Yeah

    18. JL

      ... is, is a huge... And an Outlook add-in also.

    19. SW

      Yeah, so I just wanna cover, like, the, the big ones that everyone must know.

    20. JL

      Yeah.

    21. SW

      Uh, so Tabular Review is basically like fan-out of, like, uh, a lot across each document. You can ask the same question across all, all documents.

    22. JL

      Exactly.

    23. SW

      It's collected in a table-

    24. JL

      Yeah

    25. SW

      ... uh, and then work back and forth.

    26. JL

      And then you-

    27. SW

      You can-

    28. JL

      Yeah.

    29. SW

      A million is impressive. Uh, what's any other, like, engineering considerations or performance things? Like, what, what's hard about this?

  25. 34:24 – 35:51

    How a lawyer uses Tabular Review

    1. JL

      Uh-

    2. BC

      Wait, like, before we do that-

    3. JL

      Yeah

    4. BC

      ... can you just, like, walk through, like, what is a user experience for a lawyer and then, like, actually using-

    5. SW

      Okay. So you want, you want us to do a top-level flow?

    6. BC

      ... Tabular Review.

    7. SW

      Yeah.

    8. BC

      Yeah, yeah. Like-

    9. SW

      Okay

    10. BC

      ... so, like, what are they doing-

    11. SW

      Mm

    12. BC

      ... like, with Tabular Review?

    13. JL

      Yeah.

    14. BC

      And then we can go into that.

    15. JL

      Sure.

    16. SW

      Yeah.

    17. BC

      Yeah.

    18. JL

      Um, so they... It's typically... I mean, a good example is just a due diligence, right? Where it's like we need to review all employment contracts, all the supply contracts, all of whatever. And so employment contracts, you put 10,000 employment contracts in there, and then you, um-

    19. SW

      Like, each cell is one employment contract.

    20. JL

      Each row-

    21. SW

      Okay

    22. JL

      ... is one employment contract. And then for cells, you ask questions, basically. So, like, the first question, the first, uh, no, sorry, per column. So the first column might be what's the termination, uh, period. And then it's gonna q- like, fill out for everyone. It's 30 days or whatever it is. And the next question is like, uh, is there an IP assignment clause or whatever. Next one is like, uh, how much, you know, how much do we have to pay them if we fire them or whatever it is. Like, how much are they getting paid? And then it's gonna fill out the entire thing. You can also just ask the agent to do this. Like, if you just drop 10,000 files into the agent and say, like, "Do a due diligence on this," it will spin up a Tabular Review and run all of them and wait for it to be done and then analyze the results, and it can then highlight, like, red flags. Okay, this, the CEO is getting paid an outrageous amount, or there's, like, this weird bonus structure. Okay, then, like, obviously we need to look at that. And then the agent from that can draft a memo to send to the client, or, uh, it can just do the review and then have, you know, a lawyer they use will just be like, "Okay, let's, let's look at this. Here are the red flags." It's also collaborative so that you can comment on it, um, for other people to look at, et cetera.

  26. 35:51 – 37:53

    Why a spreadsheet works and what you learn from the first 10 rows

    1. BC

      And why'd you choose that, like, uh, spreadsheet format?

    2. JL

      Yeah. It's just a lot better to... It's, it's super easy to work with, work in. Uh, it's really easy to get an overview super quickly of what's going on, uh, and to review it. So all of the stuff that we produce also has citations back to source documents, and so you can basically review it super easily. If you wanna just make sure that everything's right, you can also, like, highlight cells. These are reviewed or whatever. These are the ones that are flagged, and you can comment and collaborate. That's much easier than any other form factor that we've tried.

    3. SW

      Yeah.

    4. BC

      Mm.

    5. SW

      I would say that the spreadsheet form factor has S- has a lot of pull in some areas, but somehow hasn't really spread.

    6. JL

      Mm.

    7. SW

      I, uh, I fi- I find it very weird. Like Clay-

    8. JL

      Yeah

    9. SW

      ... is another one on the GTM side-

    10. JL

      Yeah

    11. SW

      ... that, uh, you know, very known for the spreadsheets.

    12. JL

      Yeah.

    13. SW

      You guys. Uh, I don't really know if anyone else does a, a large spreadsheet AI thing.

    14. JL

      No, no.

    15. SW

      There, there was like V7 that like tried to launch. There, like there's like Sheets, there's... Uh, even in finance domain, I don't really have like a, a top name that like-

    16. JL

      Mm

    17. SW

      ... does spreadsheets.

    18. JL

      Does this really well. Yeah.

    19. SW

      [laughs]

    20. JL

      No, I, I agree. I think it's like a great... If you, if you have fan-out and you do the exact same thing, and you- you're extracting stuff, it's, it's such a great-

    21. SW

      Yeah

    22. JL

      ... form factor to like understand-

    23. SW

      Yeah

    24. JL

      ... what's going on.

    25. SW

      Do you find like you must export to Excel, or like people are happy to live in your spreadsheet?

    26. JL

      People are happy to live there. Uh-

    27. SW

      Do you use ag-Grid or your own?

    28. JL

      We do use ag-Grid.

    29. SW

      ag-Grid.

    30. JL

      Yeah.

  27. 37:53 – 39:11

    How the legal intake bot works in Slack

    1. SW

      Yeah. I am happy to move on to the next thing.

    2. JL

      Mm.

    3. SW

      Intake, uh, which is your Slack bot.

    4. JL

      Yeah, yeah.

    5. SW

      Um, everyone has a Slack bot. Uh-

    6. JL

      Of course

    7. SW

      ... what's different about yours?

    8. JL

      So ours is just legal specific. Uh, and what, what happens with ours is it's not actually... It might also... We, we'll probably also build one that's just an interface to the agent, but it's actually specifically to basically, uh, kick off an agent that then adds a task to our list. So we have this lists thing, which is like Linear, for ex- for, you know, that's the closest, uh, equivalent. And so it will add it to a specific intake list, and then lawyers and agents can go into Legora and just be like, "Okay, these are the things that, you know, people are sending to us as our law firm or as our, um, legal team in a big corporate." We can kick off agents for them, we can collaborate on them, and then we can just like mark them as done, and then it gets sent back in Slack. So it's more of a... It's not just like kicking off an agent. It's more of a like, um, I don't know, storefront thing where it's like, "Hey, here's the ticket. I want this thing reviewed. Okay, now it's, now here it is, it's back. No one needs to change anything," and the legal team just sits in Legora and like manages the agents and everything there.

    9. SW

      I think the, the data structure for this kind of thing is really interesting 'cause it's like basically the inbox, right-

    10. JL

      Yeah

    11. SW

      ... for all these kinds of queries that can potentially translate into a thing, into something else-

    12. JL

      Yeah

    13. SW

      ... into something else. Um, and like, I, I don't know. Is it hard to integrate all these with all the other features, or do you just not worry

  28. 39:11 – 40:15

    How agents create lists and lists start agents

    1. SW

      about it? [laughs]

    2. JL

      It's... No, it's not. I think we have some primitives that work really well. So like Lists is a great primitive 'cause it's essentially... It's like extremely flexible. It's almost like a Notion database.

    3. SW

      You could treat it as, yeah, a Notion database.

    4. JL

      It's like a Notion database, and so you can basically configure it for whatever you want, and we, of course, invest a lot into making this super scalable and work really well, and you can have triggers on them, automations on them, and it's like a great glue to glue everything together 'cause then you can kick off an agent run based on a list if something happens, and then that comes back and populates a field or whatever, adds new documents or whatever it is. And so it's like, just like you might coordinate a bunch of coding agents with Linear or some sort of task management tool, we can do it similarly with lists. And so like agents can create lists, and lists can create agents, and-

    5. SW

      Wow

    6. JL

      ... agents can read lists, and so it's like the agent swarm comes alive. [laughs]

    7. SW

      Yeah. Do people get excited or overwhelmed by that? You know, like I, I feel like, uh-

    8. JL

      Yeah

    9. SW

      ... this is basically end user programming.

    10. JL

      Yeah.

    11. SW

      Uh, you're, you know, you can let people set up crazy automations. Some people get super obsessed by it-

    12. JL

      Mm

    13. SW

      ... and they become like influ- like, you know-

    14. JL

      Yeah

    15. SW

      ... it'd be cool to have like Legora influencer.

    16. JL

      Yeah, right, Legora has influencers. Yeah, yeah.

    17. SW

      Um, is that worth it?

    18. JL

      Um-

    19. SW

      Too overcomplicated?

  29. 40:15 – 42:37

    Building products on those same pieces and acquiring Wexler

    1. JL

      We need the, the flexibility, even if we don't actually expose it to the end user. Let's say this was just all internal. Then it's a really fast way for us to utilize people like, people like our legal engineers to basically build a lot of products extremely fast. So like you can build custom like fund management dashboards. You can basically build that on List with like your own, uh, generative UI, and then you basically have a new product that some people are gonna love, and we can have a marketplace of just like a bunch of sp- specialized products that we can scale super quickly 'cause all of our legal engineers can just build new ones. If they're out with a client, "Oh, you want your own? Easy. Like we'll just fix one for you." So it's like a lovable inside Legora a little bit, and if we don't wanna expose it, that's also how we build our own custom features. So we, we made another acquisition in the UK called Wexler, and they're doing fact intelligence, which is for litigation mostly, which is like you upload a million documents, uh, for a lawsuit or whatever, and then we extract facts from those with like named entities and dates and whatever. And then when you have all the facts, you can basically hold them up against each other and see which ones are corroborated and which ones are, um, what do you call? Disagreement. They-

    2. SW

      Yeah

    3. JL

      ... you know. And that's extremely powerful 'cause then you can also transcribe a court hearing, and you'd be like, "Oh, he said this thing, but actually the email over here says that he was not there." Uh, and it's like if you see it live, it's like so fucking cool.

    4. SW

      Yeah.

    5. JL

      And that we can also build on this primitive, and so like we can build a lot of really cool things on this one primitive, basically. That's how we think about it, 'cause like we have to be-- as we scale the company, we just have to solve so many things, and like so, so I think a lot about how do we build a core primitive that we can scale to, to many different end products and create very customizable-

    6. SW

      Mm

    7. JL

      ... experiences.

    8. SW

      Okay, so you have, uh, what, what core primitives do you have? Let's just restate for, for people.

    9. JL

      Lists is a core one.

    10. SW

      Lists.

    11. JL

      Yeah.

    12. SW

      Projects.

    13. JL

      It's a core one. Yeah, projects.

    14. SW

      Yeah.

    15. JL

      It's basically containers of files, file systems.

    16. SW

      Yeah.

    17. JL

      Um, the agent, of course. You can kick that off and run that in very different configurations.

    18. SW

      Do you have a name for the agent, by the way?

    19. JL

      No, we don't. No.

    20. SW

      Okay. Just intake.

    21. JL

      No.

    22. SW

      Okay.

    23. JL

      Yeah. No, you mean-

    24. SW

      That's okay

    25. JL

      ... like we called it-

    26. SW

      Yeah

    27. JL

      ... like, uh, Leia or-

    28. SW

      Yeah

    29. JL

      ... like we gave it a name?

    30. SW

      [laughs]

  30. 42:37 – 43:52

    What forward-deployed engineers do at Legora

    1. BC

      Yeah. So I actually wanted to talk a little bit about, like, FTEs, 'cause this sounds-

    2. JL

      Yeah

    3. BC

      ... kinda like that. And I think Max has talked about that a little bit. That, like, okay, when you onboard a new, like, big customer-

    4. JL

      Yeah

    5. BC

      ... you wanna get them value, like, ASAP-

    6. JL

      Yeah

    7. BC

      ... so that, you know, they stay on-

    8. JL

      Exactly

    9. BC

      ... stay on Legora.

    10. JL

      Yep.

    11. BC

      Yeah. How has that evolved? Like, when did you guys start that forward-deployed team?

    12. JL

      So we hired our first forward deployed engineer, that was our first hire in New York, also YC, uh, founder, nine months ago maybe. I'm not actually sure. Um-

    13. BC

      Are they considered-

    14. JL

      Just talking about

    15. BC

      ... legal engineers, or no?

    16. JL

      No, no.

    17. BC

      Okay. All right.

    18. JL

      True engineers. But we do... It, it is something that I think about, is like how do we exactly enable that at scale? Um, and I think a, a really core thing is, like, how can we empower our legal engineers? Like, how can we empower our power users and our legal engineers to customize the product in a powerful way? And then of course, we, we will still have forward deployed engineers, like, help out, you know, do all the custom integrations and the, the, the scoping and figuring out what's possible, and feed all of that back into core product development. So that's kind of how I think about it, is like almost a first-line, second-line defense. [laughs]

    19. BC

      Yeah.

    20. JL

      Where it's like legal engineers should be able to customize a lot of stuff and build a great experience, and then where they can't or we need to make core product changes or custom integrations or whatever, we have forward deployed engineers who also then cycle in a little bit behind, like, sometimes they'll just work on the product and sometimes they'll work-

    21. BC

      Yeah

    22. JL

      ... with clients.

  31. 43:52 – 46:43

    How legal engineers and forward-deployed engineers onboard a big client

    1. BC

      Can you walk through, like, an example? Like, okay, so you-

    2. JL

      Mm

    3. BC

      ... just got, you just got this new client. Like, what's step number one? Like, are you guys like, "Okay, hey, we have a forward deployed engineer for you guys. They're gonna go build-"

    4. JL

      Yeah

    5. BC

      ... you know, some kind of product for you." Like, how does that work?

    6. JL

      Yeah. So it's very different client to client, right?

    7. BC

      Yeah.

    8. JL

      But, um, if it's a big client and they're super engaged and they, like, want... They have all these dreams of things that they would wanna do, or they already have. Typically, they have already tried to build something and it's failed, and they're like, "This is what we... This is a problem that we'd like to solve." Um, then we'll, we'll basically staff them with legal engineers and a forward deployed engineer potentially, depending on what, you know, their thing is, and then we'll just be like, "Hey, these guys will come. They'll make you successful. They will sit with all your lawyers and teach them how to use it, and, like, figure out all the workflows that you have right now and, and build them into Legora." And some of that will just be legal engineer, and some of that will require a forward deployed engineer.

    9. BC

      What is that separation, I guess? Uh, if you could like talk about that a little bit.

    10. JL

      Legal engineers configure the product as a power user would.

    11. BC

      Okay.

    12. JL

      They don't write code.

    13. BC

      Yeah, yeah.

    14. JL

      And a forward deployed engineer writes code into production-

    15. BC

      Mm

    16. JL

      ... basically. I guess that's the, that's the, the-

    17. BC

      Yeah. What kind of background do the forward deployed engineers normally have?

    18. JL

      Regular engineers.

    19. BC

      You said YC founder.

    20. JL

      Yeah. Founders, regular engineers. They're all-

    21. BC

      Your, like-

    22. JL

      Yeah

    23. BC

      ... yeah, Dee was your-

    24. JL

      Yeah, exactly.

    25. BC

      Was the guy-

    26. JL

      Dee was our first, yeah

    27. BC

      ... two YC companies and worked on Search at Meta.

    28. JL

      Yeah. She's awesome. Yeah.

    29. BC

      [laughs]

    30. JL

      Yeah.

  32. 46:43 – 47:24

    What’s next for the forward-deployed team over the coming year

    1. BC

      Oh.

    2. JL

      Is there a rule, like, uh, I guess, does, uh, every, like... You know, so Palantir famously had, like, you know, four days you spend on site.

    3. BC

      Mm.

    4. JL

      One day you come back and, uh-

    5. BC

      Yeah

    6. JL

      ... contribute back to products. Anything like that?

    7. BC

      No. We, we don't-

    8. JL

      Uh, nothing like that?

    9. BC

      Uh, [laughs] I, um, to be fully honest with you guys, it's still, it's still, uh, you know, still early days in a lot of this. Yeah.

    10. JL

      I mean, where do you see it headed maybe over the next year?

    11. BC

      I do think that it's gonna be more, maybe not exactly like Palantir, but, like, we... I think we will have a larger in-constant circulation group of FDs that maybe sit with a client for, like, two months or whatever to build out this one thing, and then they go to the next one, et cetera, et cetera.

    12. JL

      Yeah.

    13. BC

      But I, I do imagine us rolling in with legal engineers and forward deployed engineers to, like, work on specific projects.

  33. 47:24 – 49:26

    Why Legora resisted building APIs

    1. JL

      Mm. Okay.

    2. BC

      Yeah. The API business is actually, uh, interesting, like, like you said.

    3. JL

      Mm.

    4. BC

      Um, because, uh, you know, that's another rule that you can have, where you are the CTO maintainer of the Legora platform.

    5. JL

      Yeah.

    6. BC

      Right?

    7. JL

      Yeah.

    8. BC

      Like, we will offer everything that we have in the Legora web app-

    9. JL

      Yep

    10. BC

      ... as an API, and then you guys can use whatever. Is, is that, is that a, a promise that you make, or?

    11. JL

      That's not something we're promising now.

    12. BC

      Yeah.

    13. JL

      Um, we do have APIs that you can build against-

    14. BC

      Yeah

    15. JL

      ... but not the entire surface of the product.

    16. BC

      That's the curious thing, like, is that the strategy?

    17. JL

      Mm.

    18. BC

      Or... And obviously, you know, some people will love it because-

    19. JL

      Yeah

    20. BC

      ... uh, I don't have to learn a new tool. I can just use the, the existing tool I have.

    21. JL

      Yeah.

    22. BC

      Right? And then I just like-

    23. JL

      Yeah

    24. BC

      ... uh, install Legora, the-

    25. JL

      Yeah

    26. BC

      ... for example, with the, the Word document stuff.

    27. JL

      Mm.

    28. BC

      Other than that, you know, I, I do think, like, then you have to maintain it.

    29. JL

      Exactly. That, that's, so that's been my thing. That's why we've tried not to do it. Uh-

    30. BC

      Okay

  34. 49:26 – 50:12

    Can the agent be the API?

    1. SW

      get it."

    2. JL

      Yeah. I think, I think that's also changing a little bit. A lot of, um, a lot of APIs now, like one thing that we're toying with is like can the agent be the API? I know it sounds weird, but like for some of this stuff, what they actually want to do is they wanna trigger certain things to happen. For some part of this, it could-- you could just be... I'm not saying that we're doing this, but it's like a thing that I'm toying with in my head is could that just be like, okay, you trigger the agent and ask it to do this thing? Like, obviously, it's way less efficient than if you just had like an API that you always hit, and it's like, you know. But it's something that I'm toying with is like how much of our product can just be the agent versus all the other stuff?

    3. SW

      Well, you know, unbounded execution and costs and latency-

    4. JL

      Yeah. That's the-

    5. SW

      That's-- Is that the only holdbacks?

    6. JL

      That's... Yeah, and then I think, uh, deterministic, like im-

    7. SW

      Yeah

    8. JL

      ... maybe, you know, 100 out of-- or in, in two out of 100 times, it's gonna do something whack that we

  35. 50:12 – 51:32

    The 300 Spartans slide and the plan to stay at 20 engineers

    1. JL

      didn't want it to do.

    2. SW

      We're gonna go into, like harness and, and model, uh, fine-tuning in a bit, but I think there's a, there's a product question about restraint-

    3. JL

      Mm

    4. SW

      ... about what you don't do.

    5. JL

      Yep.

    6. SW

      Because you could do all that, and obviously there's a prioritization issue.

    7. JL

      Mm.

    8. SW

      Like it-

    9. JL

      Mm.

    10. SW

      Are, are you at, uh, more at a point of let's, uh, say no to most things-

    11. JL

      Mm

    12. SW

      ... and then only do a short number of stuff? Or no, actually we wanna do more things, and we need... just need to hire like 100 people? [laughing]

    13. JL

      [laughing] I was, I was very strongly the first thing for a very long time.

    14. SW

      Yeah.

    15. JL

      Let's just say no to everything, like keep the eng team. I, I think, um, I've said this before, but like one of our presentations that I... like after I've been at Legora for half a year, I, I put up this slide of, um, you know, the 300 Spartans and, and, and-

    16. SW

      Yeah, yeah

    17. JL

      ... 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. I wanted to do that, but I think the... in the real world, we're in like fierce competition. People want so much stuff. It's like, uh, I could be a puritan and just be like, "No, we have to stay 20 people, and we can only build, you know, whatever," uh, but then we just lose, uh, and like people would go elsewhere. So we have to build more, and so I think my job is to figure out how do I build a system where we can build a lot, but actually only... like where we can... the, the customer feels like we've built so much stuff, but we've actually only built a few things. That's, that's how I think about my job right now.

    18. SW

      Yeah. I mean, primitives is right, you know?

    19. JL

      Yeah, exactly. I think that's gonna be... that's really powerful.

  36. 51:32 – 53:05

    The bets nobody asked Legora to make

    1. BC

      Do testing new products, just seeing if like, hey, there's like any pull here, and then you just kinda like, you're like, "No, let's just focus on our main thing," or...

    2. JL

      Ooh. We haven't made... I mean, we've made certain strategic bets-

    3. BC

      Yeah

    4. JL

      ... but we've not tried anything that we don't have a lot of confidence in already. Mostly because we just have like a mountain of demand-

    5. BC

      Yeah

    6. JL

      ... that's like, "We want all of these things," and so it's does- hasn't really made sense for us to try to be like, "Hey, what... maybe this thing could work," 'cause like, there's so many people screaming for the other things.

    7. BC

      Yeah.

    8. JL

      And so we mostly, uh, build those, and then sometimes we'll disagree with clients, and we'll be like, "Actually, I think this thing over here will make a lot of sense strategically," and then we'll try to build that anyway.

    9. BC

      Like strategically for you?

    10. JL

      Yeah, exactly.

    11. BC

      So what are those things?

    12. JL

      Or the industry. So one of those things, um, was, uh, the agent actually. So like no one was actually asking for like, "I want us to be, uh... I want the assistant that I'm using to have more agency and do things without me asking it."

    13. BC

      Yeah.

    14. JL

      Like no one, no one ever... but we're just like, "This def-definitely where the industry is going. This is gonna empower you to do so much cool stuff." Um, collaboration was another one where we're like, we think the industry is going in a place where you can collaborate inside of where you're working, which is Legora, and not in like emails and text messages. So yeah, there, there are, there are a few of those.

    15. BC

      And then how... like once you say, "Okay, yeah, we want you guys to use agents," I'm assuming like internally at the law firm, you know, it's gonna take a lot for them to actually-

    16. JL

      Mm

    17. BC

      ... learn how to do that.

    18. JL

      Yep.

    19. BC

      And so that's-

    20. JL

      Yeah

    21. BC

      ... where you kinda like say, "Hey, FDEs, go in there and teach them what they can do."

    22. JL

      Yeah, legal engineers w- mostly-

    23. BC

      Oh, legal engineers

    24. JL

      ... they'll be, yeah. Yeah.

    25. BC

      Okay, that makes sense.

    26. JL

      But they're like some people call them forward-deployed legal engineers-

    27. BC

      Yeah, yeah

    28. JL

      ... if you want, but that's essentially what they are. [laughing] Um, then they go in, yeah, and help, and help them structure their workflows around, uh, the capabilities of the agent.

  37. 53:05 – 54:05

    Post-training open-weight models for legal research

    1. BC

      You guys said previously, I think Max said this-

    2. JL

      Mm

    3. BC

      ... but that early on specifically, you guys weren't fine-tuning your own models. Is that still the case?

    4. JL

      Yeah. So we haven't fine-tuned any models up until now.

    5. BC

      Yeah.

    6. JL

      I think now in the past few months, open-weight models have become extremely capable, and so we will do it for certain tasks where we think there's a huge delta between what a frontier model can do at the cost and latency versus what we think a, a, a post-trained model can do. Legal research is a great example. It's like, uh, you have to make... it's a, it's a fan-out retrieval problem, and you can make a really effective, uh, model to tho-those queries super quickly and super cheaply at low latency.

    7. BC

      So specifically, you're post-training them to be better at-

    8. JL

      Very specific bounded tasks

    9. BC

      ... searching.

    10. JL

      Yeah, exactly.

    11. BC

      Okay.

    12. JL

      Yep. Yep. We're not trying to like train our own Fable-

    13. BC

      Yeah

    14. JL

      ... to like be the main agent. I, I don't think that's like a... We won't win that, you know-

    15. BC

      Yeah, yeah

    16. JL

      ... versus Anthropic most likely.

    17. BC

      Yeah. There's still a lot of, uh, s- let's say, search and retrieval research or RAG research-

    18. JL

      Mm

    19. BC

      ... to

  38. 54:05 – 54:51

    Search, retrieval, and late interaction

    1. BC

      do-

    2. JL

      Yeah

    3. BC

      ... uh, that is like maybe less glamorous. It's not actually even model training sometimes. It's just like-

    4. JL

      Yeah

    5. BC

      ... architecture and pipelines. You, you, you did a case study with, uh, TurboParpher, but like, you know, there's also like, uh... do you do late interaction of-

    6. JL

      Yes, absolutely. Yeah.

    7. BC

      You, you do that?

    8. JL

      Yeah. Uh, we actually don't do that.

    9. BC

      Right.

    10. JL

      But it's, uh... you're completely right that this is... Uh, so there's one guy on the team, Sung, who's, uh- He just really cares about search, and he c- he basically comes to me all the time, and he's like, "Oh, we should do these things," and like, "There's these new embedding models," and like, "We can do this lid and late interaction." He actually talked to Turbo teams to get them to build multi-vector so that we could do these types of things. But no, there's loads of, uh, low-hanging fruit generally even before models. And even in the harness honestly, like, if you just wanna create a better output for our clients, there's like so much stuff that we can do that has immediate impact before training models.

  39. 54:51 – 56:25

    What makes a good legal agent harness and why drafting depends on search

    1. SW

      Yeah.

    2. BC

      Like, what makes a good harness for, like, the law industry, I guess? Like, you guys are making, I'm assuming-

    3. JL

      Mm

    4. BC

      ... like, your own custom harness.

    5. JL

      Yeah.

    6. SW

      Yeah, of course.

    7. JL

      Yeah. Yep. The way that we edit files is important. The way that we do an analysis is important. Uh, the way you do legal research is all baked into it. So it's like you might have a problem that comes up, or you see something, then it knows how to go and do the legal research to figure out what the answer is-

    8. BC

      Mm

    9. JL

      ... what the precedent is. That's all very important, and then of course there's all the governance stuff around it as well.

    10. BC

      Yeah. It seems like the search is probably, like, would you say the most important tool that you guys are really customizing? 'Cause-

    11. JL

      It's-

    12. BC

      ... if you can't pull down-

    13. JL

      Yeah

    14. BC

      ... the right information-

    15. JL

      Yeah, and then you're-

    16. BC

      Yeah, yeah

    17. JL

      ... screwed.

    18. BC

      You're screwed. [chuckles]

    19. JL

      It's, uh ... Yeah, I think it's, it's, it's, um-

    20. BC

      You guys are searching-

    21. JL

      ... search-

    22. BC

      ... like a lot of documents

    23. JL

      ... and analysis.

    24. BC

      Yeah.

    25. JL

      Yeah. It's search, it's analysis, and it's drafting probably.

    26. BC

      Okay.

    27. JL

      'Cause, like, drafting word, drafting huge contracts is actually also not super trivial.

    28. BC

      Like, what about it is not trivial?

    29. JL

      'Cause you have to ... Let's say you're drafting a huge, uh, contract from scratch, then you have to find precedents of like, well, how did we do this previously? Do we need this type of clause or not?

    30. BC

      A specific law firm, how did they do it previously?

  40. 56:25 – 57:03

    Which model writes the best draft?

    1. JL

      problem.

    2. SW

      Which model's best at drafting?

    3. JL

      [laughs] So I'll say, I was told I was far from this yesterday, uh, definitely Fable and Opus are extremely chatty. I'm sure you guys have known this. Uh, they're very verbose.

    4. SW

      So that's not good.

    5. JL

      That's generally not good, no.

    6. SW

      Okay.

    7. JL

      So this is super important-

    8. BC

      I've noticed Astra is pr- pretty good at writing

    9. JL

      ... Astra is, uh-

    10. BC

      Yeah

    11. JL

      ... yeah, pretty good at writing.

    12. SW

      And is it promptable?

    13. JL

      Much less more concise.

    14. SW

      Um, are you running-

    15. JL

      For, for-

    16. SW

      ... like, 100 different prompts to, like-

    17. JL

      Yeah

    18. SW

      ... be sure?

    19. JL

      We, we can ... Yeah, we can-

    20. SW

      Okay

    21. JL

      ... we can do, we can do certain things, but I think the chattiness verbosity is actually a little bit difficult for us to do.

    22. SW

      Wow.

    23. JL

      So this is ... I think, you know, let's see, but probably the next model from Anthropic is gonna be much better at this. Astra is actually very concise.

    24. SW

      Yeah, yeah.

    25. JL

      And I, I assume they, they all have a Slack channel with

  41. 57:03 – 57:41

    Hallucinations and Legora’s citation system

    1. JL

      you, and you're telling them this, right?

    2. SW

      Yeah, yeah, yeah, exactly.

    3. JL

      Like, it's just-

    4. SW

      Yeah, we talk to them about it

    5. JL

      ... this is not news to them. No, no, no, they know this.

    6. BC

      All right.

    7. JL

      Then the other thing that I really care about is hallucination.

    8. SW

      Mm-hmm.

    9. JL

      Do they make stuff up? So, uh, we have a system of a citation system where we basically check what they're writing has a link. So the user has a link they can click, and it highlights with a bounding box like in the PDF or whatever where, where this information was taken from, and we can sort of make sure that what it says always is citable somewhere even multiple layers down. So, like, if the agent writes something based on a tabular review, you know, c- it can cite the cell in the tabular view or the row in the tabular view. So you can actually, like, click multiple layers down and find, you know, sort of validate it

  42. 57:41 – 58:19

    Do lawyers check the citations?

    1. JL

      all the way up.

    2. SW

      Yeah.

    3. BC

      Are you finding that lawyers are, like, verifying that these citations are correct-

    4. JL

      They-

    5. BC

      ... or not?

    6. JL

      No. In-

    7. SW

      [laughs]

    8. JL

      ... init- initially-

    9. BC

      It's kinda like code review

    10. JL

      ... some of them were but now ... Yeah, exactly. Same thing

    11. BC

      ... are you actually, are you actually doing it?

    12. JL

      It's the same thing.

    13. SW

      People ship, like, hallucinated links to Supreme Court. They don't care.

    14. JL

      That happens, yeah.

    15. SW

      [laughs]

    16. JL

      Exactly. That happens. Uh, yeah. I, I think it's like coding. You know, you have engineers that just don't give a shit and just, like, send agents, and you have people that, like, sit and read every comma. Same distribution at all.

    17. BC

      There's just, like, so much that, like, how can one human do that, right?

    18. JL

      Yeah, but I think they probably just like we know in code review what to look for-

    19. BC

      Yeah

    20. JL

      ... like, what is the system or whatever. I think they also know, okay, this is the, the thing. These are the red ... Like, this is the thing that's important. Let me just, like, double-check these things.

    21. BC

      Yeah.

    22. JL

      Then, like, these sound reasonable, so it's probably fine.

  43. 58:19 – 1:00:16

    MapReduce or one big context window for a million-token contract?

    1. BC

      Okay. Interesting.

    2. SW

      Mm. Just like if you, if you receive something from a junior lawyer, it's the same thing you do, right? Just like, eh, I should double-check this, and like-

    3. BC

      Yeah

    4. SW

      ... this probably is fine. Any other elements of let's call it legal reasoning or what's the, the, the legal frontier that-

    5. JL

      Mm

    6. SW

      ... uh, models are not good enough yet that you want from the next generation of models?

    7. JL

      Nothing I can think of specifically right now. I think long document reasoning is still difficult. Um-

    8. SW

      Long, like, million-token, token contracts or something?

    9. JL

      Yeah, exactly. You have a huge contract-

    10. SW

      Yeah

    11. JL

      ... um, and, like, you're making edits across it. It's a difficult thing to do for a model today even.

    12. SW

      Mm.

    13. JL

      Uh, and, like, remember that you changed all these things up here, and, like, the definition's changed and that you ... the ordering changed and whatever else.

    14. SW

      Mm.

    15. JL

      Um, so the simplest would be one shot. You put- feed everything in and then one-shot output.

    16. SW

      Yes.

    17. JL

      You don't do that. You break it up into chunks-

    18. SW

      Yeah

    19. JL

      ... and then you orchestrate edits.

    20. SW

      Yeah. Exactly. Exactly.

    21. JL

      And this is, like, one of those things that are funny, like, that are fun to be part of in this industry, right? So our Word add-in was like we, we've done, you know, we've done MapReduce, and we've changed, and there was one big one, and there was, like, one big one and multiple times. It's like we keep changing-

    22. SW

      Yes

    23. JL

      ... the, the scaffolding that we build around as models change.

    24. SW

      Yes. I, I, I would say I, I, um, I've ... Recently I do a lot of, like, news reporting-

    25. JL

      Mm-hmm

    26. SW

      ... uh, obviously because of what I do, and I've recently shifted from MapReduce to throw everything into context.

    27. JL

      The entire thing. Yeah. Yeah.

    28. SW

      And it's-

    29. JL

      'Cause now they're-

    30. SW

      ... it's better. [laughs]

  44. 1:00:16 – 1:01:53

    Getting anonymized examples and the idea of buying a law firm for its data

    1. BC

      be hard-

    2. JL

      ... non-trivial

    3. BC

      ... like you said earlier, to actually make the models better at that 'cause you can't even look at the contracts, right?

    4. JL

      Exactly.

    5. BC

      These are real contracts.

    6. JL

      Yeah, yeah.

    7. BC

      So do you guys ever ask them for, like, "Hey, can you-

    8. JL

      Yes

    9. BC

      ... make example contracts-

    10. JL

      Yes

    11. BC

      ... that are similar to your real ones?"

    12. JL

      We do. Yeah, yeah.

    13. BC

      Okay.

    14. JL

      So we have, we have feedback, and we can receive feedback from them-

    15. SW

      Yeah

    16. JL

      ... and if they are willing to engage-

    17. SW

      Send to the company

    18. JL

      ... yeah, exactly, or they're just like, "Hey, this is, like, super important to us and it's not working well." And then we'll be like, "Okay, great. Can you, like, anonymize the documents?"

    19. BC

      Yeah.

    20. JL

      And, like- The problem, then whatever, and we'll re- we- if we can recreate it, then we can fix it.

    21. BC

      Yeah.

    22. SW

      I mean, so one version of this is you buy a law firm-

    23. JL

      Yeah

    24. SW

      ... which some people are considering.

    25. JL

      Yes, but, uh, there's some... we... There's some stuff there on whether-

    26. SW

      [laughs]

    27. JL

      ... uh, their data is actually their data or if it's the client's data.

    28. SW

      Hmm.

    29. JL

      So if the clients are all gone, then maybe it's fine. I actually don't know.

    30. SW

      Interesting.

  45. 1:01:53 – 1:02:44

    Why Jacob advises against default embeddings

    1. SW

      We're gonna wrap up soon. Uh, the last thing I'll point people to is also there's a lot of alpha left on embeddings. If you're-

    2. JL

      Yeah

    3. SW

      ... if you're a rag-heavy work, workload, uh, you're, you're just looking at like MTEB and you're taking like top model, uh, you're leaving a lot on the table. You should look at like, uh, Voyage or like some of the em-

    4. JL

      Yeah

    5. SW

      ... uh, custom embeddings. You-

    6. JL

      Yeah, yeah

    7. SW

      ... you've looked into this.

    8. JL

      We've... Yeah, yeah. Absolutely.

    9. SW

      Yeah. So basically, don't take default embeddings even like OpenAI embeddings, Gemini embeddings. Doesn't matter. Customize your embeddings.

    10. JL

      Yeah.

    11. SW

      Right?

    12. JL

      Yes.

    13. SW

      You, you, you support that?

    14. JL

      Yes. Ev- I think that's right.

    15. SW

      Okay.

    16. JL

      I think that's right. We... The only thing is, uh, need to make sure that you're multi, uh, language. So for us, we, we serve so many languages, so that's been one of the problems.

    17. SW

      I mean, Europe is like king of this.

    18. JL

      [laughs] Yeah, yeah. Exactly.

    19. SW

      Uh, Mistral helpful there?

    20. JL

      Um, no. [laughs]

    21. SW

      [laughs] Ooh.

    22. BC

      Until-

    23. JL

      That's-

    24. BC

      Until now. They just raised a ton of money, right? So maybe.

    25. SW

      Yeah.

    26. JL

      Let's see.

    27. SW

      I mean, you guys basically-

    28. JL

      They also raised a ton of money a year ago.

    29. SW

      Yeah. I don't know

    30. JL

      ... champions like-

  46. 1:02:44 – 1:03:26

    Will lawyers work in Legora or through Claude?

    1. JL

      Yes.

    2. BC

      [laughs] I just wanted to ask you, like, what predictions do you have maybe like over the next year for like the law industry?

    3. SW

      Uh, ex- uh, we, we asked a little bit of that earlier.

    4. BC

      Yeah.

    5. SW

      I'll modify it to your second question, which is, uh, in two years, will lawyers do their work inside Legora or will they use, uh, other tools like-

    6. JL

      Hmm

    7. SW

      ... Claude or ChatGPT-

    8. JL

      Yeah

    9. SW

      ... and call Legora? Like, you know, the API function.

    10. JL

      Yeah, yeah, yeah, yeah, yeah. I think both. It really depends. I think if you're an, an big enterprise, you might have Claude Copilot and then you'll... It's... I think it's similar to like how I use Linear through Claude, but I still go to Linear. I think enterprise will do that. I think law firms will just use Legora-

    11. SW

      Yeah

    12. JL

      ... because that's simpler and better.

    13. BC

      Yeah.

    14. JL

      Um-

    15. BC

      It kind of reminds me of like open evidence for like medicine.

    16. JL

      Yeah.

    17. BC

      Like you're, you're basically that for law.

    18. JL

      Yeah.

    19. BC

      Yeah.

  47. 1:03:26 – 1:04:24

    Will the model labs cut Legora off?

    1. JL

      Exactly.

    2. SW

      In coding as well until a point where people, the labs will cut you off for competing with them.

    3. JL

      Mm.

    4. SW

      And this has happened twice.

    5. JL

      Yeah.

    6. SW

      Do, do you think that will happen to law?

    7. JL

      No, I don't think so.

    8. SW

      Yeah.

    9. JL

      I think-

    10. SW

      Because like, you know, they are re- releasing legal services things.

    11. JL

      Yeah, yeah.

    12. SW

      Right?

    13. JL

      Yeah, yeah. They are. I don't... I mean, we obviously talk to them a lot, but it's also... it's like, "Hey, are you gonna [laughs] what's-"

    14. SW

      Your sales reps will say no.

    15. JL

      Exactly.

    16. SW

      They don't make the call.

    17. JL

      Exactly. That's not their call to make.

    18. SW

      [laughs]

    19. JL

      Right? And they don't even know of- like often what's actually going on. I don't thi- I don't think that's the case. They have so much stuff to capture in knowledge work or in, in, in sort of enterprises knowledge work generally that like legal has to be part of that, just like data analytics has to-

    20. SW

      Yeah

    21. JL

      ... and sales and marketing and finance. So like they have to do things that are good there, but uh, they're never gonna go as deep as we are. And I think if, if Claude takes a small client, small, uh, you know, corporate clients and they do some of their legal via Claude, like that's, that's great. That's fine. But if you're doing a, you know, $400 million M&A transaction, you're gonna want Legora.

    22. BC

      I had kind of

  48. 1:04:24 – 1:05:28

    Law schools and scholarships for computer science majors

    1. BC

      an unrelated question, but I'm curious, are you guys going to law schools and kinda like getting them-

    2. JL

      Mm.

    3. BC

      ... to like teach-

    4. JL

      Yeah

    5. BC

      ... Legora-

    6. JL

      Yeah, yeah

    7. BC

      ... like in classes? Like how does that work?

    8. JL

      It-

    9. BC

      Are you guys thinking about that?

    10. SW

      Yeah. It's, it's, uh, it's definitely a program that we are... uh, I think we've started.

    11. BC

      Oh, cool.

    12. SW

      I actually don't know exactly where we're at, but we, we do want people in law school to-

    13. BC

      Yeah

    14. SW

      ... learn to use Legora. Um-

    15. BC

      Ha- like are you seeing that, like law schools are changing their curriculums a lot or not really?

    16. SW

      I don't know. I, I, I, I-

    17. BC

      Yeah

    18. SW

      ... wouldn't know actually.

    19. BC

      Interesting.

    20. SW

      I would actually do it a different way. Uh, you should do scholarships for l- for law school for CS majors, for engineers. We will cover your-

    21. JL

      After you've done CS-

    22. SW

      Yes

    23. JL

      ... we'll, we'll put you in law school?

    24. SW

      We'll co- Yeah. CS plus some software experience-

    25. JL

      Yeah

    26. SW

      ... we'll put you in law school.

    27. JL

      Yeah.

    28. SW

      We'll cover it.

    29. BC

      Or you do like the MA like, like masters plus JD programs.

    30. JL

      Yeah. We'll-

  49. 1:05:28 – 1:06:09

    Hiring in New York, Stockholm, and London

    1. SW

      Yeah. Yeah. Uh, okay, look, uh, overall, uh, you know, super impressive progress. I mean, congrats on all your success. Like, uh, are you still gonna keep up the pace like, uh-

    2. JL

      Absolutely.

    3. SW

      Yeah, you know, uh, and I think you're hiring in SF, New York-

    4. JL

      We're hiring in-

    5. SW

      ... Sweden

    6. JL

      ... yeah, engineering, we're hiring in New York, um, Stockholm and London.

    7. SW

      Yeah.

    8. JL

      Uh, and all other roles we're hiring everywhere, almost.

    9. SW

      How many people do you have in New York right now?

    10. JL

      100. About 100.

    11. BC

      Okay. And you guys are planning on how many in New York?

    12. JL

      In New York?

    13. BC

      Yeah.

    14. JL

      For just like generally?

    15. BC

      Let's just say, yeah, generally engineering.

    16. JL

      Um, a lot.

    17. BC

      As many as you can.

    18. JL

      I don't... Yeah.

    19. BC

      [laughs]

    20. JL

      It's, it's, it's aggressive. [laughs]

    21. SW

      [laughs]

    22. BC

      Cool.

    23. SW

      Yeah. I mean, like that, that's the home of corporate law, right? As far as like-

    24. JL

      It i- yeah,

  50. 1:06:09 – 1:07:21

    Why most work eventually becomes legal work

    1. JL

      it is

    2. SW

      ... Mid-America is concerned.

    3. JL

      New York is, uh-

    4. SW

      So like-

    5. JL

      Yeah

    6. SW

      ... yeah, I mean, I'm looking forward to you buying a law firm and like-

    7. JL

      Yes

    8. SW

      ... you know, becoming-

    9. JL

      Yeah.

    10. SW

      Yeah. It, it, it's, it's super exciting to, to... I think like, you know, every industry, especially like the top like doctors, lawyers, coders, you know, th- they all have to have like, you know-

    11. JL

      Yes. I agree

    12. SW

      ... two or three agent labs that like just-

    13. JL

      Yeah

    14. SW

      ... sort of dominate the space.

    15. JL

      I agree.

    16. SW

      So you guys have like a great market. Yeah. Good.

    17. JL

      Yeah, I think so. And I think it's only gonna get much bigger as like law changes and get- becomes more, um, available to more people.

    18. SW

      Yeah. Also, I, I think like, I mean, we're already like super over, but like, uh, the problems that you work on are very like the frontier knowledge work, you know?

    19. JL

      Yes. Yeah.

    20. SW

      They're... Okay. Like un- unless you're literally like doing like science-

    21. JL

      Navier-Stokes

    22. SW

      ... Navier-Stokes and science. Other than that, like most work is like basically c- uh, converges to legal.

    23. JL

      Yeah.

    24. SW

      Like [laughs]

    25. JL

      [laughs]

    26. SW

      Yeah.

    27. JL

      Uh, yeah.

    28. SW

      It's all legal in the end. [laughs]

    29. JL

      Yeah.

    30. SW

      Hiring, finance, everything, like I just have to consult my lawyer, so.

Episode duration: 1:07:21

In the uListen app, the transcript lights up word by word as you listen. Get uListen

Transcript of episode bJBEFzlKPoQ

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.