Build the budget legal AI for small firms

What to build

A narrow, affordable legal-AI SaaS for solo attorneys and small firms — fork the open-sourced Harvey clone and ship a focused tool for one practice area (e.g., immigration intake Q&A, residential lease review, or personal injury demand-letter drafting), priced per-seat at a fraction of enterprise legal AI.

Harvey's $500M raise proves big demand for legal AI, but its enterprise pricing locks out solo attorneys and small firms; a freshly open-sourced clone lets a solo builder repackage that same tech into a cheap, practice-area-specific tool for the segment Harvey ignores.

Demand

Solo attorneys and small firms handling high-volume, repetitive document work (immigration intake, lease review, demand letters) want AI assistance but are priced out of enterprise tools like Harvey, and the open-sourcing of a comparable clone just removed the biggest technical barrier to serving them cheaply.

• Hacker News (thomasunise/casecite)News

  "Harvey raised 500M for legal AI, I built the same and open sourced it" — 69 points, 37 comments on HN, indicating high engagement with the idea of an accessible legal AI alternative.

• Signal cluster (arbitrage opportunity report)News

  Harvey raised $500M targeting large law firms with enterprise pricing, signaling strong institutional demand for legal AI but leaving smaller firms unaddressed.

Stack

• casecite (open-source Harvey clone, forked)
• OpenAI API or Anthropic Claude API
• Postgres + pgvector for document retrieval
• Supabase (auth, storage, per-seat billing data)
• Stripe (per-seat subscription billing)
• Vercel or Render for hosting

Solo + AI difficulty

Easy part: forking an already-working open-source codebase and narrowing its scope to one practice area and one document workflow. Hard part: legal-domain accuracy tuning, prompt/retrieval quality for a specific practice area, and navigating bar association ethics rules around AI-assisted legal work (disclaimers, human review steps). Rough time-to-MVP: 3-6 weeks for a single-workflow version with one solo builder using AI coding tools.

Entry threshold

Technically low barrier since an open-source base and LLM APIs already exist, but legal accuracy and liability concerns plus slow, trust-based sales cycles mean traction takes longer than the build itself; picking a narrow underserved niche is essential to avoid the crowded enterprise legal AI space.

Window

6-12 months

Where to find first users

• r/LawFirm and r/Lawyertalk on Reddit
• Solo practitioner Facebook groups and bar association listservs
• Product Hunt launch targeting legal tech
• Cold outreach to immigration or PI solo practitioners via LinkedIn

Competitors

• Harvey
• Spellbook
• Clio

Counter-signals & risks

• An open-source clone of Harvey may lack production-grade accuracy, legal-domain fine-tuning, compliance safeguards, or support, making it unsuitable for direct repurposing without significant additional engineering investment.

• Solo attorneys and small firms may be price-sensitive but also risk-averse around AI tools due to malpractice liability and bar association ethics rules on AI-generated legal work, potentially limiting adoption regardless of price point.

• Harvey or well-funded competitors could downmarket their own pricing or launch a lightweight tier to capture the small-firm segment before a new entrant gains traction, eroding the arbitrage window.