Best CRM for Law Firms: Intake, Conflict Checks, Referral Sources and an Evaluation Method

Choosing the best CRM for law firms from a ranking can produce a system that works on its own terms and still fails the firm in two places no feature list mentions. In the first, a person consulted the firm last spring, did not retain it, and exists only in the intake tool. This spring's conflict check runs in the practice management system and returns nothing for a name the firm still owes duties to. In the second, the partners ask which referrers produced last year's fees, and the source sits in one system while the fees sit in another.

This article sets out how a firm chooses between the products sold under that heading. It starts with the four categories, then the conflict check, which constrains the choice more than any feature, and the difference between a matter and a relationship. Referral reporting, two sample firms, a comparison table and costs follow, then an evaluation method, symptoms, limits and questions by practice type.

A practice management system holds matters, time, billing and documents: Clio Manage, MyCase and PracticePanther here. A legal intake CRM manages a prospective client from enquiry to engagement and hands the hired matter to practice management: Clio Grow and Lawmatics here. A general CRM such as HubSpot or Salesforce models contacts, companies and a pipeline, and a relationship CRM such as LexisNexis InterAction+ serves relationship development in professional services. A prospective client, under ABA Model Rule of Professional Conduct 1.18, is a person who consults a lawyer about possibly forming a client-lawyer relationship, and the rule's confidentiality duty applies even when no relationship follows.

Legal CRM Software Categories

Practice management systems are built around the matter. Clio Manage runs conflict checks against existing contacts and matters (Clio help centre, "Run Conflict Checks in Clio Manage and Clio Grow"). MyCase adds Leads, with a default pipeline of New, Contacted, Consult Scheduled and Pending and a referral source captured as a default field (MyCase leads). PracticePanther's conflict check searches notes, tasks, events, emails, contacts, matters and custom fields, on every plan (PracticePanther conflict checks).

Legal intake CRMs are built around the prospective client. Clio Grow turns a lead into a contact, or through Quick Intake into a contact and a matter, and each Grow matter is either intake or hired (Clio help centre, "Manage Leads in Clio Grow" and "Clio Grow Matters Overview"). Lawmatics records every prospect as a matter with the status PNC, for potential new client, then Hired or Lost (Lawmatics matter statuses); conversion marks it Hired and syncs it to an integrated practice management system (Lawmatics Clio Manage integration).

Relationship CRMs are built around the relationship. LexisNexis describes InterAction+ as capturing emails, calendar invitations and other interactions automatically from Outlook, and states that it "does not follow a sales pipeline like other CRMs" (InterAction+).

General CRMs are built around contacts, companies and deals, so a matter becomes a custom object. HubSpot restricts custom objects to Enterprise subscriptions (HubSpot custom objects); Salesforce Professional Edition allows 50 (Salesforce Professional Edition allocations). Litify, which sells practice management built on Salesforce, sits across the boundary (Litify platform).

A firm asking which CRM to buy is making four decisions at once: which system holds and bills the matter, which runs intake to engagement, which holds relationships spanning matters, and which holds the party list the conflict check searches. A feature comparison cannot show the fourth, and it constrains the other three.

Conflict Checks and the Prospective Client Record

Every conflict check these vendors document searches records held in that vendor's own products, and the default route into practice management, conversion, runs at hire. A declined prospective client therefore sits outside the practice management system's conflict search unless the firm has put that person inside it, and that is the record Model Rule 1.18 continues to govern.

Clio's check searches Clio Grow, Clio Manage or both, and a check run in one product is available in the other, so an intake matter that never converted stays inside the same search. Up to ten searches, such as spelling variants and each known adverse party, combine into one report (Clio help centre, "Customize Conflict Check Search Settings"). Intake and matter records therefore share one searchable estate.

Lawmatics scans all matters held in Lawmatics, can run the check as an automation action, and requires a new lead to exist as a matter before it can be checked (Lawmatics conflict checking). A PNC synced to Clio Manage before hire arrives as Pending and joins Clio's search; without that step, a Lost matter stays in Lawmatics alone. MyCase checks from global search across cases, people and documents (MyCase conflict checking), without saying whether unconverted leads are included; the planted test below settles it for an account.

HubSpot's knowledge base, searched in September 2026, describes no conflict-check tool, so a firm running intake in a general CRM builds the check. One published migration designed it as an iPaaS scenario that searched the firm's existing client database whenever a lead arrived (a regional law firm's migration to HubSpot). A check of that shape finds clients, and a declined prospective client is not a client, so intake has to write that person into the searched database as well. HubSpot's data sync runs on all plans and updates records within ten minutes of a change, but maps custom properties only with a Data Hub subscription (HubSpot data sync). The Clio Manage app in HubSpot's marketplace is built by HubSpot, syncs two ways, and pairs Clio matters with HubSpot deals (Clio Manage listing).

The design rule holds for every product named here: the intake system must either be the searched system, or write each declined prospective client, with the adverse parties that person named, into the searched system before the intake record closes. A legal-native stack meets the rule inside one vendor, and a general CRM only through an integration or a written procedure that has to be tested.

Matter Records and Client Relationships

A matter opens, runs and closes, while a client relationship outlives every matter inside it, and the categories differ on which is the primary record.

The legal-native products carry the relationship on the contact, and their documentation shows where that model strains. In Clio Grow a contact carries one marketing source, "representing the initial outreach", while each matter may carry several (Clio help centre, "Clio Grow Marketing Sources"). In MyCase, converting a lead from a returning client creates a new contact marked "duplicate" beside the existing one (MyCase leads). Clio's conversion from Grow to Manage carries contacts, custom fields, tags, notes, submitted documents and attached files, but not the matter type, status, assignee, estimated case value, emails or tasks (Clio help centre, "Filter, Export, and Convert Matters").

A general CRM holds the relationship as a record in its own right. HubSpot associates one company with many contacts and deals, and association labels on Professional and Enterprise name each relationship, up to 50 per object pair, including contact-to-contact pairs such as referrer and referred client (HubSpot association labels). The matter object for a firm running HubSpot beside practice management is set out in HubSpot for law firms.

The difference bites where one client opens many matters, such as an employer sponsoring several employees for visas: in a matter-first system that relationship is whatever the matters share, and in a relationship-first system it has its own owner, history and pipeline.

Referral Source Reporting Across Systems

The white paper on law firm CRM adoption sets out why a contacts folder cannot hold a referral source. The reporting problem is separate: the source is captured at intake and fees are recorded in billing, so fees by source need both values in one place.

Clio Grow's lead source revenue report counts intake, hired and not-hired matters per source. Its matter revenue report lists source and referring contact beside billed time, collected time and revenue from Clio Manage, provided contacts are synced and matters converted (Clio help centre, "Clio Grow Reports"). The same-vendor stack wins this axis because the vendor maintains the join. Lawmatics documents one value returning from Clio Manage, the closed status. In a general CRM a fee arrives only when an integration writes it back, which makes the report an integration deliverable.

Relationship Share and Conflict Load on Sample Data

Two numbers from records a firm already holds decide the category. Relationship share is the fraction of new matters opened for existing or former clients or for people introduced by a named referrer. Conflict load is the number of people a year who consulted the firm and did not retain it, each of whom must stay searchable. The two firms below are sample data built to make the arithmetic checkable; they describe no client.

Firm A's relationship share is (12 + 40) ÷ 264 = 19.7%, and its conflict load is 700 − 252 = 448 people a year; Firm B's share is (96 + 54) ÷ 180 = 83.3%, and its load 118 − 84 = 34.

Two further ratios come from the same rows. Firm A converts 252 of 700 consultations, 36.0%, and adds 448 ÷ 264 = 1.70 declined prospective clients to its conflict estate for every new matter it opens. Firm B converts 84 of 118, 71.2%, and adds 34 ÷ 180 = 0.19. At the sample fees, Firm A's open-market matters bill 212 × $6,500 = $1,378,000 against 52 × $6,500 = $338,000 from relationships, 4.1 times as much. Firm B's relationship matters bill 150 × $11,500 = $1,725,000 against 30 × $11,500 = $345,000 from the open market, 5.0 times the other way.

Those ratios show where a system's attention belongs, not what any system will return, because no source consulted here measures conversion or fees by CRM category. Firm A's work is intake: time to consultation, attribution for 212 open-market matters, and 448 declined prospective clients a year routed into the conflict search. Firm B's work is relationship development across 150 matters, with a conflict load small enough for a documented manual step to carry.

Comparison of CRM Software for Law Firms

InterAction+ sits outside both columns: it suits a partnership whose business development runs through relationships partners hold individually, and LexisNexis does not describe it as an intake system.

Costs and Returns by Firm Profile

The firm writing this article is a HubSpot Solutions Partner, and a general CRM beside practice management is the arrangement that produces partner work; that interest should be weighed here. Licence prices are left out because every arrangement is priced by seat and edition, and a quote settles that line.

The legal-native stack wins on two specific axes. It keeps declined prospective clients inside the conflict search without an integration, and in Clio's pairing it reports fees by referral source from the billing ledger. It costs a relationship model that lives on the contact, so a client with many matters is reconstructed from matters rather than held as a record. Its case is strongest at a consumer practice with high enquiry volume, and weakest at a business practice growing through existing clients.

A standalone legal CRM beside practice management buys intake automation outside the billing system, at the cost of a second system, a sync running one way apart from the closed status, and two searchable estates unless PNCs are synced to Clio as Pending.

A general CRM beside practice management wins on two other axes. It holds relationships spanning matters and companies as records with owners and labelled associations, and it automates with triggers the designer chooses. It costs a conflict route the firm designs and tests, fees written back from billing, Data Hub for custom mappings, and HubSpot Enterprise wherever a matter must be a custom object. Its case is strongest at a business practice with high relationship share, and weakest at a high-volume consumer practice, where it rebuilds intake a legal CRM already has. A multi-office family law practice runs consumer intake in a HubSpot deal pipeline (family law Service Hub case study), which shows the arrangement is possible, not that it is the default.

Evaluation Method for a Law Firm CRM

1. Export twelve months of new matters from practice management and classify each by origin: existing or former client, named referrer, or open-market enquiry. Compute the relationship share; a system that cannot supply the origin has produced the first finding.
2. Count consultations with people not yet clients and subtract the matters they produced, which gives the annual conflict load.
3. Name the system of record for the matter and its billing, the prospective client, the relationship across matters, and the party list the conflict check searches.
4. Shortlist by the two numbers: high conflict load with low relationship share points to a legal intake CRM inside or paired with practice management, and high relationship share to a general or relationship CRM beside it. No published threshold exists, so a firm between the samples tests both.
5. For each arrangement, write down how a declined prospective client becomes searchable: a check spanning both products, a sync before hire, a contact sync, or a manual step with a named owner.
6. Write down where the referral source is captured and what writes collected fees back beside it.
7. Verify with a planted record. Create a test prospective client with a distinctive name and one named adverse party, mark it declined, lost or not hired, and run the firm's standard conflict check; the arrangement passes only if both names return. Then confirm one closed matter's collected fees appear against its known referrer, and remove the test record under the firm's retention policy.

Symptoms of a Misplaced Intake Record

A conflict check clears a name a lawyer remembers from a consultation. The consultation lives in the intake system, the check ran in practice management, and conversion moved only hired matters across. The repair belongs at intake: search both products, sync prospects before hire, or widen the contact sync.

The referral report counts matters by source but shows no fees. The source was captured in the CRM, fees sit in billing, and the integration returns status rather than money. The report belongs in the product holding both values, or the integration must write fees back.

A returning client appears twice. The intake product created a new person from the lead, as MyCase conversion does by design: it warns that a contact with that email exists, links both contacts to the new case and marks the new one "duplicate". The fix is a post-conversion step with a named owner that resolves the duplicate against the existing contact, so every matter sits on one record.

An estimated case value disappears after conversion. Clio does not convert that field from Grow to Manage, so it stays on the Grow matter, and estimated-against-collected reports read both products.

Scope, Dates and Limits of the Evidence

Every product fact here is as documented in September 2026, read from vendor help centres and product pages on 27 September 2026 rather than from testing. Clio's help centre refuses automated requests, so its articles are cited by title rather than linked. Its conversion, marketing-source and report articles were read in archived copies dated April and May 2026, and its conflict-check articles through Clio's own published excerpts, so a Clio customer should confirm those details in the current help centre. Ethical screens, trust accounting and document management are outside the comparison.

The evidence has three limits. Model Rule 1.18 is a model that each state adopts in its own version, the conflict duty turns on whether information received could be significantly harmful, and nothing here is advice on a particular conflict. The sample firms are invented to make the arithmetic checkable, and no frequency of any symptom has been measured. No source consulted measures outcomes by category, so the method shows where a firm's records need to live without showing that any arrangement raises revenue.

Law Firm CRM Questions by Practice Type

What is the best CRM for law firms? No single product: the phrase covers four categories doing different jobs, and relationship share and conflict load, computed from the firm's own matters, select between them.

What is the best CRM for small law firms? A small firm pays for every system in licences and administration, which favours the fewest systems keeping declined prospects searchable: practice management whose own conflict check is shown by a planted record to cover its leads, or Clio Grow with Clio Manage.

Is there a best free CRM for law firms? HubSpot offers a free CRM with data sync, but workflows start at Professional, and a free general CRM runs no conflict check, so the check stays in practice management.

What is the best CRM for immigration law firms? A practice serving individuals has the consumer profile, while a practice filing for employers may open a matter for each sponsored employee under one client relationship, the relationship-first profile.

What are the best CRM solutions for personal injury law firms? Personal injury intake is high-volume and a contingency fee is known only at resolution: PracticePanther records a contingency rate on the matter and pays the fee from settlement funds in trust (PracticePanther contingency billing), so fees by source depend on the practice management join.

What is the best legal CRM software for law firms, as distinct from a general CRM? Clio Grow, Lawmatics and InterAction+ hold prospective-client statuses, conflict checks or partner relationships natively; a general CRM holds them once designed.

In Summary

The products sold as the best CRM for law firms fall into four categories, built around the matter, the prospective client, the partner's relationship, and the contact, company and deal. Each vendor's conflict check searches its own products, and conversion carries matters into practice management at hire. A person who consulted and did not retain the firm stays searchable only where intake and search share a product or a route joins them.

The legal-native stack wins on conflict coverage and fees by referral source; a general CRM wins on relationships spanning matters and on automation. Relationship share and conflict load say which axes carry a firm's money: 448 declined consultations and a 19.7% share in one sample, 34 and 83.3% in the other. Whatever reaches the shortlist is accepted only when a planted prospective client, marked declined, comes back in the firm's own conflict check.