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

What It Covers

Legora CTO Jacob Lauritzen details how the legal AI company reached $100M ARR in 18 months by rethinking engineering org structure, AI tooling strategy, and product velocity — arguing that coding is no longer the bottleneck and that token maxing is a counterproductive metric for enterprise teams.

Key Questions Answered

• •Engineering bottleneck shift: Coding is no longer the rate-limiting step in software development — AI handles that. The two new bottlenecks are product work (customer synthesis, scoping) and code review. Structure your org accordingly: protect PM time for customer-facing discovery and invest in AI-assisted review tooling rather than raw engineering headcount.
• •Developer experience ROI: Legora built a dedicated 3-person developer experience team that creates custom background coding agents, automated CI review bots, and onboarding tooling. Lauritzen says he should have staffed this team earlier — each engineer gains roughly 20% efficiency, compounding across 80 engineers and making new-hire ramp dramatically faster.
• •Token maxing backfires: Leaderboards tracking raw token consumption push engineers to burn tokens for optics, not output. Instead, run hack days and demo sessions where engineers show measurable efficiency gains. Reward output and effectiveness — AI usage follows naturally — rather than incentivizing token volume as a standalone performance review metric.
• •Vibe coding internal tools: Legora's internal AI enablement team evaluates building vs. buying software using two axes — surface area breadth and depth of complexity. Shallow apps requiring heavy customization (HR tools, migration apps, onboarding systems) are now cheaper to build in-house via vibe coding than to license and configure off-the-shelf products.
• •Hiring for low-ego scales faster: Acquihires of 5-8 person teams deliver A-player density faster than individual recruiting. Integration succeeds when engineers have no title attachment — Lauritzen tells engineering directors directly that roles can swap if someone else executes better. Ego signals surface clearly during salary and title negotiations, making screening straightforward.