20Product: Inside Legora's Tech Stack: Why Token Maxing is Failing Enterprise Startups with Jacob Lauritzen, CTO @ Legora

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.