Ruli AI

Ruli AI is an AI-native legal intelligence platform built specifically for in-house legal teams, founded in 2024 by Bryan Lee (ex-Google, ex-Meta). $8.2M total funding across pre-seed ($2.2M) and seed ($6M, November 2025) led by Album VC with SignalFire, PJC, Foothill Ventures, and Genius Ventures. Former Pinterest GC Michele Lee joined the advisory board; John Lee (ex-Alphabet lawyer) hired as GC and head of strategy. HQ in Austin, Texas. Product suite: Ruli Assistant (AI research and drafting grounded in company playbooks and precedents), DataGrid (bulk contract analysis — input disclosure docs, foreign law docs and get structured extraction), Word Extension (contract review and redlining directly in Microsoft Word), and Legal Hub (intake automation and business unit FAQ self-service — described by co-founder as ‘a Zendesk copilot for in-house legal teams’). Positioned as ‘Continuous Legal Intelligence’ — AI that learns from the team’s playbooks, policies, and prior agreements. SOC 2 Type II compliant per security page — notably ahead of peers at seed stage. TechFundingNews positions Ruli as a ‘Harvey rival’ targeting in-house teams specifically (Harvey primarily targets law firms). Active Reddit presence on r/legaltech — Donna Scaffidi (Head of Legal Innovation) engages transparently with practitioners (‘Full disclosure: I work at Ruli’). One r/legaltech user describes Ruli as ‘like an In-House Harvey.’ Another notes Ruli offers ‘similar features and equal output quality for half the price’ of a competitor. FeaturedCustomers lists 10 customer references. No published case studies with specific outcome metrics yet — expected given 2024 founding. John Lee (GC) spoke at California Lawyers Association Solo and Small Firm Summit, suggesting interest beyond enterprise in-house. Early-stage but well-funded with strong legal tech advisory pedigree.

Company Info

• Founded: 2024
• Team size: 1-10 employees
• Funding: $2.2M
• HQ: United Kingdom
• Sector: In-House Automation

What We Haven’t Verified

This page was assembled from publicly available information. Feature claims and workflow mappings are based on what the vendor and third-party listings publish — not hands-on testing or practitioner feedback.