A legal CRM is the system that holds everything about a client before, during and after the matter: the first enquiry, the conflict check, the engagement letter, every call and note, the fee arrangement, the invoices and what is still outstanding. In most firms that information lives in five places — an inbox, a spreadsheet, a practice management tool, an accounting package and somebody’s memory — and the gaps between them are where clients get dropped.
This guide covers what a legal CRM actually does, why generic sales CRMs consistently fail in law firms, the handoff problem that breaks most legal-specific ones, and an eight-point checklist for evaluating any system you are considering. It also explains how ModulawAI approaches the problem, because we built the client record and the matter record as the same object rather than two systems joined by an integration.
What is a legal CRM?
Client relationship management in a law firm covers a different lifecycle than it does in a sales organisation. A sales CRM is built around a pipeline that ends at a closed deal. A legal CRM has to keep working long after the client signs, because in legal work the relationship starts at signature and the obligations that follow — deadlines, privilege, trust money, conflicts, retention periods — are regulated.
A legal CRM should handle at minimum:
- Intake capture — structured information from a prospective client, not a free-text email
- Conflict and KYC screening — before work begins, with a record of who checked and when
- Conversion to a matter — the enquiry becomes a file without anyone retyping it
- The client record — contact details, custom attributes, notes, documents, related matters
- Communication history — what was said, by whom, on what date
- Time, fees and disbursements — captured against the matter as the work happens
- Billing and collection — invoices out, payments in, balances visible
- Client-facing access — a portal where the client can see their own matter without emailing to ask
Systems that do only the first two or three are intake tools. Systems that do only the last three are billing tools. A legal CRM is the thing that carries one client identity across all of it.
Legal CRM vs generic CRM: why Salesforce and HubSpot fail in law firms
Firms regularly try a general-purpose CRM first, because it is cheap, familiar and the marketing team already knows it. It usually survives about two quarters. The failures are structural, not cosmetic.
| What a law firm needs | What a sales CRM does |
|---|---|
| A matter that cannot exist without a client | Opportunities and contacts are loosely linked; orphaned records are normal |
| Conflict checks before engagement | No concept of a conflict; duplicate contacts are tolerated by design |
| Privilege and confidentiality boundaries | Open visibility across the sales team is the default and the selling point |
| Time recorded in six-minute increments against a file | Activity logging for pipeline reporting, not billable capture |
| Trust and client money held separately from firm money | No ledger concept at all |
| Retention and destruction schedules | Records kept indefinitely unless manually purged |
| Deadlines that carry legal consequence | Reminders you can dismiss |
The deeper problem is that a sales CRM treats the closed deal as the end state. Everything a law firm is regulated on happens after that point.
The handoff problem: where most legal CRMs break
Legal-specific CRMs solve the vocabulary problem — they know what a matter is — but many still stop at the signature. The intake tool captures the enquiry, and then the client is re-created in the practice management system, and then again in the accounting package. Each boundary is a retyping, and each retyping is a place where the name is spelled differently, the fee arrangement is remembered wrongly, or the file simply never gets opened.
The symptoms are familiar:
- An enquiry that was qualified, quoted and then never followed up, because it lived in an inbox rather than a queue
- Work billed months late because time was recorded on paper and entered at month end
- A client asking for a status update that takes a fee earner twenty minutes to assemble
- Two versions of the same client, one with the current address and one with the current matter
- A KYC check everyone assumes was done, with no record of who did it
None of these are training problems. They are what happens when one relationship is represented by several disconnected records.
How ModulawAI handles the client lifecycle
ModulawAI is an AI operating system for legal practice across eight jurisdictions. The client record, the matter, the time ledger and the invoice are parts of one system rather than four products joined by integrations. Here is what that means in practice.
Intake: structured forms, not an email inbox
Intake runs on a forms engine rather than a contact box. Templates are built from sections and typed fields — short and long text, rich text, numbers, currency, dates and date ranges, times and time ranges, select and multi-select, booleans, person references, file and file-list uploads, links, computed fields, repeating groups and matrices. That range matters because legal intake is rarely flat: a probate enquiry has a variable number of beneficiaries, a corporate instruction has a variable number of directors, and a repeating group captures that properly instead of forcing it into a comment box.
Templates are versioned and published, so amending your intake questions does not invalidate submissions already made against the previous version. Assignments control who must complete a form and by when. A submission can be rendered directly to a document, which means the intake questionnaire and the engagement paperwork draw on the same answers.
For firms currently relying on phone capture, it is worth reading our assessment of legal answering services and the intake problems they do not solve — an answering service takes the message, but the structured record still has to exist somewhere.
Conversion: one action from enquiry to matter
An intake submission can be reviewed, commented on internally, and then converted into a case as a single action. Nobody retypes the client’s details. The enquiry and the matter are continuous, and the intake record remains attached as the origin of the file.
This is also where the data model does real work. A case cannot exist without a client. Attempting to delete a client who has matters attached is refused outright rather than silently cascading — the correct action is to archive the client, which preserves the record and its full history. Deleting a case does not delete the client behind it. These are deliberately strict rules, because the alternative is a file with no one responsible for it.
The client record: custom fields and a genuine portal
Beyond standard contact details, workspaces define their own custom field definitions — text, number, date, boolean or select with defined options — each optionally grouped, ordered, marked required, and flagged as visible in the client portal. An immigration practice tracks visa category and priority date; a corporate team tracks incorporation number and financial year end. Same system, different schema, without either firm carrying the other’s clutter.
Clients can be sent a login link giving them direct access to their own matter, which removes a meaningful share of status-update calls. Notes attach to the client record. Clients can be imported in bulk and searched across the workspace, and bulk operations report partial results explicitly — a list of what succeeded and what failed, with reasons — rather than reporting a clean success over a half-finished job.
Time, billing and payment in the same record
This is where a CRM either becomes the system of record or becomes another place to check. ModulawAI captures time with live timers you start and stop against a matter, synced across devices, as well as manually entered time at both case and workspace level. Expenses are recorded with receipt uploads, approval statuses and summaries.
Invoices are then generated automatically from recorded hours or from expenses, using your own invoice templates with a configurable default. Each invoice carries a status, can be downloaded, and can issue a payment link so the client can settle without an exchange of bank details. Every matter exposes a financial summary and a timeline, so the question “where are we on this file, and what is outstanding?” is a single view rather than a small research project.
Firms handling client money should treat trust accounting as a separate discipline with its own controls; general ledger software is not a substitute for a compliant client account, and neither is a CRM on its own. For the billing and collection layer specifically, see our guide to legal accounting software.
KYC, onboarding and repeatable processes
Client onboarding, KYC, conflict checks and internal appraisals are handled as defined processes — published, versioned SOPs with steps assigned to named people. Each person sees the steps waiting on them. Instances can be tracked or cancelled, and a campaign launches the same process across an entire segment at once and reports completion, which is how you run a policy attestation or a re-verification sweep across the whole client base without chasing individuals.
Read-and-acknowledge steps use a dedicated documentAck field that records who confirmed, when, and which specific documents they were shown. That distinction matters under audit: a tick box proves someone clicked, whereas this stands as evidence of what was actually put in front of them. For an example of recurring compliance obligations handled this way, see our piece on building a CAMA 2020 compliance calendar that holds.
The AI layer, and where we are honest about its limits
Research, drafting and review run on Claude, with jurisdiction-aware citation checking across eight jurisdictions rather than a single body of law. Our Microsoft Word add-in produces native track-changes redlines and posts findings as comments, because most legal drafting happens in Word and asking people to leave it is how tools go unused.
We are direct about what a raw model cannot do. Our write-up on Claude for legal work covers where it genuinely performs and where it fails, and multi-jurisdiction research explains how we keep the citation trail intact when a matter crosses borders. If you are comparing the wider market, our honest comparison of legal AI tools covers Harvey, CoCounsel, Legora, Spellbook, Clio Duo and others, including where they beat us.
Programmable, so it fits the stack you already have
ModulawAI exposes a scoped REST API and runs as an MCP server, so Claude or another AI assistant can operate against your workspace directly, and your workspace can in turn call out to other MCP servers. Clients, intakes, matters, documents, calendars, tasks, notes, forms and financial records are all reachable programmatically. The developer platform update has the detail.
Legal CRM vs case management vs practice management software
These three terms are used interchangeably by vendors and mean different things in practice. The distinction is worth holding onto during a procurement conversation.
| Category | Primary job | Typically covers | Usually missing |
|---|---|---|---|
| Legal CRM | Win and keep the client | Intake, conflict screening, pipeline, communication history, client portal | Deep matter workflow, trust accounting |
| Case management | Run the matter | Files, documents, deadlines, tasks, court dates | Pre-engagement intake, marketing attribution |
| Practice management | Run the firm | Matters plus time, billing, reporting, sometimes accounting | Structured intake, AI-assisted legal work |
Most firms end up buying two of the three and building a bridge. Our position on why that bridge is the problem is set out in built for practice, not bolted on.
How to choose a legal CRM: an eight-point checklist
- Does an enquiry become a matter without retyping? Ask for a live demonstration of the conversion, not a description of it.
- Can you model your own intake? If the form builder cannot handle a variable number of beneficiaries or directors, it will not survive contact with real files.
- Is time capture in the same system as the client record? Separate time tracking means month-end reconstruction and written-off hours.
- Can a client see their own matter? A portal reduces status calls more than any internal efficiency measure.
- What happens when you delete a client? The correct answer is a refusal when matters exist, and archiving that preserves history. A silent cascade is disqualifying.
- Is there an audit trail of who did what, when? Particularly for KYC and read-and-acknowledge steps.
- Does it have an API? Without one, you own a silo, and every future workflow becomes a manual export.
- Does it cover your jurisdictions? Tools built for one legal system quietly assume its rules about citation, privilege and limitation.
Whatever you choose, run it against one real, live matter before rolling it out. A demo dataset never reveals the friction.
Frequently asked questions
What is the difference between a legal CRM and a legal case management system?
A legal CRM manages the relationship — enquiry, qualification, onboarding, communication history and billing relationship. Case management runs the work itself: documents, deadlines, tasks and court dates. They overlap at the point of engagement, which is exactly where most firms lose information, because that is where the two systems usually meet.
Can a small firm justify a legal CRM?
The economics usually turn on unbilled time and lost enquiries rather than headcount. A sole practitioner who recovers an hour a week of otherwise unrecorded time, or converts one additional enquiry a month that would previously have gone unanswered, has covered the cost several times over. Small firms often benefit more than large ones, because they have no operations team absorbing the gaps manually.
Does a legal CRM replace accounting software?
Not entirely. It should own time capture, disbursements, invoicing and collection, which is where most of the leakage happens. Statutory accounts and client-account reconciliation remain a separate discipline with their own regulatory requirements. The practical test is whether you are re-entering invoice data into your accounting package by hand.
How long does migration take?
Client and matter data with a clean export typically moves in days. The real timeline is set by how much history lives in individual inboxes and personal spreadsheets rather than in a system. Bulk import handles the structured part; the unstructured part is a decision about how far back you genuinely need to go.
Is client data kept confidential between matters and teams?
Access is scoped to the workspace and controlled by permissions, with read and write treated separately. This is a structural difference from general-purpose CRMs, where broad internal visibility is a design goal rather than a risk.
Which jurisdictions does ModulawAI support?
Eight, with jurisdiction-aware research and citation checking rather than a single legal system with others appended. Our note on research that crosses borders explains how the citation trail is preserved when a matter spans more than one.
See it against one of your own matters
The fastest way to evaluate a legal CRM is to put a live file through it — intake to matter to invoice — and see where it makes you retype something. Start a workspace at app.modulaw.ai, or read where we are taking the platform.