Law Firm Software Features: Cases, Billing, Documents and AI
Core, plan-gated, credential-dependent, and paused capabilities are not interchangeable. Confirm the exact Starter trial scope during approval before relying on a workflow.
Availability notice
This page maps product direction as well as implemented workflows. AI, e-signatures, online payments, email, bulk messaging, storage scanning, calendar connections, and third-party integrations may require production credentials, a higher plan, or release approval. A feature shown here is not a promise that it is enabled in every trial.
147
Total Features
10 modules
62
MVP Core
Ship first
66
Growth Stage
Scale next
19
Enterprise
Premium tier
Feature modules
Explore the AttorneyCore architecture
Open each module to review the workflows, security controls, AI tools, billing features, and growth-stage capabilities.
Case-Centric Architecture
Every module connects through the Matter, the central entity. This ensures lawyers never leave their case context to find related information.
Why This Structure Is Better
Workflow-centric, not tech-centric
Modules mirror how lawyers actually work: clients -> matters -> documents -> billing. Not database tables.
Calendar belongs with Matters
Hearings and deadlines are case events. Moving Calendar into the practice core eliminates context switching.
Billing is not Accounting
Attorneys track time and send invoices (Billing). Admins manage trust funds and run reports (Accounting). Different users, different modules.
AI is dual-mode
Dedicated AI workspace for deep work + embedded AI actions inside every module. No orphaned 'AI tab' problem.
Intake is a pipeline, not a form
Lead tracking -> conflict check -> conversion -> onboarding. This mirrors real firm operations.
Permissions-ready structure
Each module maps cleanly to permission scopes. Role-based access can be configured per module, per action.