LegalDesk
Intake, matters, clauses, e-sign — a lean platform for solo attorneys.
Prospective-client intake, conflict scanning, template clauses, e-signature and time-tracking — without buying five SaaS tools.
WHY IT WORKS
LegalDesk turns a solo practice into a boutique operation. Prospective clients file through a guided intake, a conflict-scan service checks against the firm's matter history, and qualified inquiries flow to the calendar with a polite disqualification for the rest. Matters are first-class objects: documents, events, time entries and clauses live together, with an editable timeline attorneys can read in five seconds.
Drafting shortens dramatically. ClauseBank hosts the firm's own clauses with smart variables; the agent composes first drafts from the matter record; SignatureGate takes care of signing. FeeMeter runs in the background — every minute in the workspace turns into a billable line you can dispute, not hunt.
Every bit of PHI-adjacent data — client identities, engagement letters, matter notes — lives in the same PHIVault pattern TriageDesk uses, with per-matter access controls and a consent ledger for every document exchange.
ARCHITECTURE · LAYERED BLUEPRINT
How the microservices wire up.
Read top to bottom. Channels are where people arrive, orchestration is how the AI thinks, domain is the startup-specific logic, data & identity keeps the source of truth, and platform is the invisible glue.
Scroll horizontally to see the full architecture.
INVENTORY
Every block in LegalDesk.
Each block is a microservice with a clear role — grouped by layer so you can see what belongs to channels, orchestration, domain, data and platform at a glance.
HOW TO SHIP IT
Quick-start checklist.
- 01 Load ConflictScan with the firm's existing matter list.
- 02 Seed ClauseBank with the firm's top 30 clauses; tag variables.
- 03 Turn on FeeMeter background timer; every desktop session logs.
- 04 Publish the IntakeRouter form on the firm's site.
WHAT'S NEXT
Compose LegalDesk in a visual workspace.
Log into AIM Engine 2.0, drop the blueprint on a canvas, fork the domain microservices you need, and deploy to your own domain. Everything shown here is already a real component.