Legora

“If coding is a half a trillion dollar market, and you have two companies like Harvey and Legora, I don't see why there's not a half trillion dollar market in law.”

“And it's very similar and many people in this audio probably knows what, what's been going on in legal AI with Harvey and Legora. This is almost the exact same thing, but for an engineering workflow.”

“The round that just happened, you know, about six months ago. It was like it was kind of sub-fifty, but in that range.”

“I mean, look, Max, I guess maybe he hasn't been as public about it, but absolutely that's part of the strategy. You know, when we got to know each other and we were thinking about the round and justifying not only the current round and hopefully, you know, par…”

“We acquired four businesses so far this year. We did the diligence in house the with our own tool and the fastest transaction with it was 12 days. From LOI to closing.”

“We do the hard work of gathering All the cases, all the legislation, all the regulatory updates for every jurisdiction in the world.”

“Instead of having to call a lawyer who then knows a lawyer in that region who will respond to the query, they can get an 80% accurate response immediately that they can start working off out of.”

“They are not competing in our product category at all.”

“So it's actually a big pipeline generator for us.”

“There's a lot of legal AI companies and very few are making it through and not because it's hard to build stuff. It's actually quite easy to understand where you can build value, but getting it to the customer is very hard”

“We're hosting National Secrets, weapons manufacturers with their contracts on Legora, and we work with governments.”

“I don't want to say infinite, but for me, it's a question of opportunity cost. We're in a competitive environment. There's so many things that we can do, and the cost of not doing it is extremely high. It almost outweighs any sort of token cost.”

“They hit a hundred million in ARR in just 18 months.”

“So essentially I don't have any priors coming into how to build an engineering org.”

“It's Cloud Code, it's Cursor.”

“Each engineer can produce much more than they could previously and that just has a ton of ripple on effects throughout the org, basically, and how you structure it”

“We do AI code review today, and it's in its nascent phase.”

“I think the other thing that engineers are doing more and more, which is an explicit role with us soon, which is like kind of the meta engineering of making agents really effective.”

“Actually, I took a look recently, and it's Claude and Cursor on the top, and there's like, I think it's like two percent between them. So they are really, really close. And then it's, you know, miles above the next engineer. So they're way above 50%.”

“One of our vendors had a security incident just yesterday. We just rotated a lot. I mean, just, you know, to be clear, this was internally doesn't affect any of our clients or anything like that, but it's just, I think we're going to see more of them.”

“If you have an incident, now you just unleash an SRE agent, a sort of an incident agent, and it will just super quickly figure out what's going on, look at all the logs, look at all the metrics, metrics, sorry, Telemetry, and it's surprisingly good. It's reall…”

“PEMs can prototype super, super fast. Which is really, really great because that means you can front load a lot of the work. So like a PM can start hyper long before once he or she has the, you know, smallest inkling of an idea that we might want to do this. T…”

“We still use Figma, yes. I know where you're going with this. As soon as you start building a system that's larger than something very small, you want consistency, and you want to have a design language and all that kind of stuff, and so you need somewhere to …”

“We have this notion internally that there's the speed of AI, there's the speed of our product, and then there's the speed of humans, you know, and they're like, they're not the same necessarily.”

“It will be the future. I don't know when, but it will be the future.”

“Ryan, who joined from Canada, we have a team of people joining from Canada, they're all moving to Sweden, and he vibe coded an app to help everyone migrate. So like very specifically, if you're Canadian, these are like all the laws and all the steps you take, …”

“If it's a shallow app, and it requires a lot of customization from you, maybe you just build it. That's probably actually the right thing to do. If it's a very deep one, there's just too much stuff for you to build, and it's not viable for you to do.”

“Let's say you took away a model from LIGORA, people would still pick LIGORA. So they don't buy it based on the model.”

“We, not 15, but yeah, maybe 10.”

“Almost always performance. Performance is more important. Almost always. If you're a lawyer, you can wait two seconds more for the output if it's better. You can probably wait an hour more for the output if it's better.”

“We currently do, yeah. But I think that's just, that's an education thing. In five years, maybe we don't at all, to be honest.”

“I think they've been more aggressive with hiring, which I actually think I have not been aggressive enough with hiring because I've always tried to have a very, very small, very lean team, which I believed a lot in.”

“Today we are about 80.”

“We have a developer experience team. Relatively new. Again, a mistake I made. I should have staffed that earlier.”

“We have our own background coding agent that they built. That allows each engineer to have, like, 10 different agents running concurrently with, like, all of our local development, a browser, all the iteration stuff.”

“Now, now I make sure everything we build will scale to 100 X the usage. I used to say 10 X, but then that was not enough, so now everything needs to scale to a hundred X.”

“If you're running a 100,000 cells, you're probably okay waiting a bit. You can go grab a coffee and that's fine, but if you run 10 cells at the same time, those should be really fast.”

“No, I don't buy that. I think It's, to me, it's a question of how quickly can I solve problems? Am I the person that can solve the problems that we have right now the fastest, or can someone else solve them faster than me?”

“And I only, most of the people that we hire, we don't even talk about their title. We talk about the difficult problems that they're going to work on.”

“If you have a PM and a designer and an engineer, and they just sit together, You can almost not even have the handover. You can just be like, run at this problem and do it together, the three of you know, next week, and then it's done. But if you have them sil…”

“Well, we're very opinionated about who we are and who we aren't. We, if you're a great engineer and you want to be remote, then you probably also want to work on very isolated problems, and that's, that can be fine. We'll, we'll, we probably have those, and we…”

“If I have to put my, I want to say the lower number let's say two 70.”

“If they'worked on adjacent things or think it's in a similar field or even, you know, unrelated but similar technology, we'll take all their learnings and we might rebuild it into Lagora. I think that's what happens in most cases, but they become, you know, fu…”

“It's surprisingly easy if you hire people with low ego. That's the thing. If you get five great engineers that don't care about their titles or where they sit in the org chart that just want to solve problems, it's surprisingly easy to integrate.”

“I give really strong feedback after two weeks. What does really strong feedback mean, Jay? Really strong means you're not gonna stay if you don't change this. And feedback is feedback.”

“No. But they need to get the chance. And if they do, they stay.”

“I think senior management is extremely difficult to hire for. No yeah, or like engineering directors, engineering managers within, yeah, within product and engineering, yeah. Maybe that's always been difficult, but I think it's because we only have really tech…”

“The way that we have engineering teams is relatively small teams, let's say six people, a PM and an engineering manager. The engineering manager is super technical, you know, spends most of their time coding.”

“When I started, we were at 40 people. Today, we're over 500.”

“When we get into a deal, when we get into a pilot, we convert pilots, 78% of the time, into a close one opportunity.”

“We have both forward deploy engineers, but we also have forward deploy legal engineers who are typically, you know, big law attorneys who understand how individual practice areas work within a law firm, as well as how corporate legal departments work within th…”

“We can afford to take, you know, to take this sort of human, this very human-centric approach right now, but we do it for, you know, pretty much anything in, in, in six figures and above.”

“At Braze, we never ran pilots in Lagora. We just, we run pilots all the time as an example.”

“So for example, we just did a big brand campaign with Jude Law.”

“One of the companies I really admire and try to model after his ramp, like you said, and we talk a lot about them internally in terms of how they've built the execution layer from a go to market perspective.”

“We have one big competitor, and they come up on every, it's a, you know, death match on every deal. It's super competitive. We have a ton of respect for them.”

“Getting on site is super critical because people don't pay attention on Zoom.”

“We don't give Legora away for free. So we try and have price integrity.”

“If a company's not spending any money on a product, does it matter? Then they're not going to put the resources and attention into it that they need to.”

“If you're selling to a corporate, they're going to ask all their law firm panel, what tools are they using? If you're selling to a law firm, they're going to ask their big corporate clients and the tools they're using.”