20Product: Inside Legora's Tech Stack: Why Token Maxing is Failing Enterprise Startups with Jacob Lauritzen, CTO @ Legora
Jacob Lauritzen, CTO of Legora, discusses how AI tooling has transformed software development, the evolution of engineering roles, and lessons learned scaling Legora to 100M ARR in 18 months. He covers topics ranging from AI model selection and developer experience teams to hiring philosophy and the future of legal tech.
Summary
Jacob Lauritzen, CTO of Legora (a legal tech company that hit 100M ARR in 18 months), joins Harry Stabbings to discuss how building an engineering organization in 2026 differs fundamentally from prior years. Jacob argues that AI tooling—primarily Claude Code and Cursor—has compressed the code-writing bottleneck so dramatically that the new constraints are product discovery and code review. He describes a three-phase model of software development (product work, coding, review) where coding is no longer the rate limiter, shifting attention to the other two phases.
On AI tooling and infrastructure, Jacob explains that Legora uses approximately 10 different models simultaneously, routing tasks by latency and performance requirements rather than cost. He notes that Cloud Code and Cursor collectively account for the top two contributors to their codebase—well above any individual engineer. He expresses concern about AI-generated code creating new security vulnerabilities and confirms Legora still manually reviews every human-authored PR as a precaution.
Jacob discusses the evolving role of engineers, predicting they will move from writing code to managing systems architecture and configuring guardrails for AI agents. He envisions a new internal role at enterprises—an 'AI systems enablement' function—that sets boundaries within which agents can autonomously operate. He also argues that developer experience teams are critically underinvested, sharing that Legora's three-person DX team builds background coding agents, custom review bots, and CI automation that dramatically accelerates engineer productivity and onboarding.
On hiring and org design, Jacob reflects on consistently underestimating Legora's growth—he once capped the team at 20 engineers; they now have 80 and are still understaffed. He emphasizes hiring for low ego and high adaptability over seniority or title-consciousness, noting that senior candidates with ego problems reveal themselves during salary and title negotiations. He discusses acquihires as an efficient way to bring in clusters of trusted A-players quickly.
Jacob addresses the PM role, arguing that while PMs can now prototype faster than ever, the opportunity cost of having them code extensively is too high—the real bottleneck is product synthesis and customer insight work. He predicts that in enterprise environments, in-office co-location dramatically reduces handover costs between PM, design, and engineering. He also shares that Legora deliberately avoids token-maxing incentives (like leaderboards) in favor of rewarding tangible output and efficiency demonstrated through demos and hack days.
Finally, Jacob shares his views on the legal industry's future: lawyers will eventually operate at a strategic level above contract language, setting negotiation stances rather than editing Word documents, analogous to how engineers are moving above source code. He also discusses Legora's competitive strategy—focusing on depth of value rather than reacting to fast-copying competitors—and attributes Legora's success partly to working harder and faster than the larger incumbents whose employees lack founder-level motivation.
About this episode
<p><span><span class="citation-19">Jacob Lauritzen</span> <span class="citation-19">serves as the CTO at</span> <span class="citation-19">Legora</span><span class="citation-19 citation-end-19">, the fastest growing B2B enterprise company in history; hitting $100 million in ARR in just 18 months<sup class="superscript"> <!----></sup></span></span><span><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span><span>.</span> <span><span class="citation-17">Legora boasts a valuation of</span> <span class="citation-17 citation-end-17">$5.6BN<sup class="superscript"><!----></sup></span> and has raised a total of $866 million in funding. <span class="citation-16">Legora's investors include the likes of</span> <span class="citation-16">Accel, Benchmark, and Bessemer Venture Partners</span><span class="citation-16">, alongside strategic tech giants</span> <span class="citation-16 citation-end-16">NVIDIA (NVentures) and Salesforce Ventures<sup class="superscript"><!----></sup></span>.</span></p> <p><strong>AGENDA: </strong></p> <ul> <li> <p id="p-rc_55d945fb6cf44468-114"> <span><strong>05:01</strong> - How to Hire the Best Product Talent in 2026</span><span><!----><!----><!----><!----><!----><!----><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span> <!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-115"> <span><strong>06:21</strong> - The New Product Bottleneck: Shifting Beyond Code Creation</span><span><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span> <!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-116"> <span><strong>09:24</strong> - System Design vs. Code Creation: The Future Role of the Engineer</span><span><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span> <!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-117"> <span><strong>14:04</strong> - The Evolving Software Development Lifecycle & The Death of the Design Phase</span></p> </li> <li> <p id="p-rc_55d945fb6cf44468-119"> <span><strong>22:23</strong> - Will Product and Engineering Fully Converge?</span><span><!----><!----><!----><!----><!----><!----><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span> <!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-120"> <span><strong>29:16</strong> - Scalability and UX: Designing for 10x vs. 100x Spikes</span><span><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span> <!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-121"> <span><strong>38:15</strong> - Scaling the Organization: What Breaks with a 250 Person Product Team</span><span><!----><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span><!----><!----><!----><!----><!----><!----><!----><!----></p> </li> <li> <p id="p-rc_55d945fb6cf44468-122"> <span><strong>47:05</strong> - Quick-Fire Round: Hyper-Growth Tactics & Out-Working the Giants</span><span><!----><!----> <!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><sup class="superscript"><!----></sup><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----><!----></span></p> </li> </ul> <p><span> </span></p>
Key Insights
- Jacob argues that the coding bottleneck has been eliminated by AI, shifting the rate limiters in software development to product discovery work and code review—not implementation.
- Jacob claims Legora uses approximately 10 AI models simultaneously, routing tasks based on latency and performance rather than cost, with performance almost always winning over speed.
- Jacob states that Claude Code and Cursor together collectively outcode every individual engineer at Legora by a wide margin, effectively becoming the top two 'contributors' to the codebase.
- Jacob argues that token-maxing incentives like leaderboards are counterproductive—they reward token burn rather than output—and recommends hack days and demos that reward demonstrated efficiency instead.
- Jacob believes that having PMs spend significant time coding is inefficient at Legora's stage because the product synthesis and customer insight work is now the primary bottleneck, making PM coding time costly in opportunity terms.
- Jacob argues that enterprises should build an internal 'AI systems enablement' team—an evolution of IT—that sets guardrails and data boundaries allowing agents to run autonomously within defined limits.
- Jacob predicts that the current IDE form factor (reading lines of code) will die and be replaced by something graphical focused on systems architecture, where engineers review plans and agents execute them.
- Jacob claims that acquihires are strategically valuable not primarily for their code but for the ability to onboard clusters of pre-trusted A-players at once, with integration being surprisingly smooth when hires have low ego.
Topics
Transcript
What percent of developer salary would you be willing to spend on AI tooling for them? I don't want to say infinite, but for me, it's a question of opportunity cost. We're in a competitive environment. So many things that we can do. The cost of not doing it is extremely high, and it almost outweighs any sort of token cost. Honestly, just work harder than the £800 gorilla. People underestimate this. Like, no one in the £800 gorilla is extremely excited to be there. This is 20 Product with me, Harry Stabbings. Now, I'm so excited to welcome Jacob Luritson, CTO at Legora to the show today. Legora is the fastest growing enterprise company in history. They hit 100…
Full transcript available for MurmurCast members
Sign Up to AccessMore from The Twenty Minute VC (20VC): Venture Capital | Startup Funding | The Pitch
20VC: Are OpenAI and Anthropic Overvalued? The Open-Source AI Reality | How Token Costs Will Fall 10x And Usage Will Explode 100x | The Future Is Not One AGI; It's Millions of Specialised Models with Lin Qiao, Founder and CEO @ Fireworks
Lin Qiao, CEO of Fireworks, discusses how specialized AI models will dominate over single AGI systems, predicting 10x token cost reductions and 100x usage increases over three years. He argues that companies should own their own customized intelligence rather than relying on frontier models, positioning Fireworks as the infrastructure layer enabling this shift.
20VC: $5BN in Revenue, 7 to 7,000 Employees in 9 Months, 206,000 Tests in a Single Day: The Craziest Story in Startups: Curative with Fred Turner
Fred Turner, CEO of Curative, discusses scaling a COVID testing business to $5B in revenue in 9 months, then pivoting to health insurance where he's now deploying AI agents to transform back-office workflows, replacing legacy SaaS with custom solutions, and achieving 10x productivity gains across contract negotiation, claims processing, and credentialing.
20VC: Apple Sues OpenAI | Zuckerberg Back on X and Challenging Codex and Claude Code | SK Hynix's $26BN IPO | Is Seed Investing Dead: Jason Calacanis Departs Seed for Growth | Greylock Raises New $1.5BN Fund
A weekly tech news roundup covering Apple's lawsuit against OpenAI for trade secret theft, Meta's aggressive pricing for Llama 3.1 models, SK Hynix's $26.5B NASDAQ IPO, the shift toward growth-stage investing, and analysis of AI token consumption, pricing dynamics, and the sustainability of AI spending growth.
20VC: Wix's Founder on What Wall St Gets Wrong About AI and Wix | Will Base44 Win the Vibe Coding Wars | The Truth About the Economics of Vibe-Coding | The Buyback Disaster: Lessons Learned with Avishai Abrahami
Wix founder Avishai Abrahami discusses the company's $2.8B market cap undervaluation despite $2.1B in revenue, the strategic acquisition and growth of Base44 (vibe coding product at $150M+ ARR), and his perspective on AI's limitations in replacing human workers despite market hype.
20VC: Why OpenAI and Anthropic Won't Win the App Layer | Why Teams Will Get Bigger Not Smaller in a World of AI | Why AI Removes Incumbents Advantage of Bundling | China vs America: Who Wins the AI War with Arvind Jain, Co-Founder @ Glean
Arvind Jain, co-founder of Glean, argues that 90% of enterprise AI use cases are now commoditized across multiple models including open source, reducing frontier model providers' bundling advantage. He contends that teams will grow larger rather than shrink in an AI world because companies choosing not to reduce headcount will outcompete those that do, and that AI companies should view model providers as assets rather than threats.