Featured · Operations
Choosing the best CRM for a law firm: requirements first
Every shortlist of legal CRMs looks convincing, which is the problem. Read three comparison articles and you will find the same dozen products described in the same approving terms, and be no closer to knowing which suits your firm — because none of them knows what your firm needs it to do.
The decision is much easier from the other end. Write down what the system has to do, in your own firm's terms, and most of the market eliminates itself before you have booked a single demonstration.
CRM is not case management, and firms conflate them
A great deal of wasted evaluation comes from the two being discussed as though they were one purchase. They serve different halves of the business and are frequently best bought separately.
A CRM handles everything before the matter exists: enquiries, their source, follow-up, and whether a prospect became a client.
Case or practice management handles everything after: the matter file, documents, deadlines, time recording and billing.
Some products do both, usually doing one of them well and the other adequately. Which half is the strong one is the question worth asking in a demonstration.
The overlap is the handover — a signed prospect becoming a matter — and that handover is where an integration either works or quietly becomes manual retyping.
If your firm already has case management it is happy with, you are shopping for a CRM that integrates with it, which is a much narrower search than shopping for a platform.
This distinction also explains a common disappointment. Firms buy a well-regarded practice management system, expect it to tell them which marketing produced which client, and find it was never designed to answer that question.
Marketing attribution lives on the CRM side. If nobody has bought that half, the reporting gap will not close whatever else is installed.
The requirements that actually decide it
Write these down and score every candidate against them. The list is deliberately short, because a long requirements document mostly measures how many features a vendor can claim.
Capturing enquiries from every route, including the telephone. A CRM that records web forms and nothing else will misrepresent your best channel as your worst.
Recording the source of each enquiry automatically, and keeping it attached through to instruction. This is the single feature most firms actually need and least often specify.
Follow-up that prompts a human rather than replacing one — reminders and sequences that a fee-earner can see and take over.
Reporting you can read without a consultant: enquiries by source, conversion by practice area, and what a client cost to acquire.
Integration with whatever holds the matter afterwards, tested with your own data rather than demonstrated on the vendor's.
Conflict checking and data handling appropriate to client confidentiality, including where the data is hosted and who at the vendor can see it.
And an honest look at whether your team will actually use it, because a system nobody updates is worse than a spreadsheet somebody does.
Running the evaluation, and surviving the rollout
Most CRM disappointments are implementation failures rather than product failures. The order below is arranged to surface that risk early, while changing your mind is still cheap.
Write the requirements before looking at any product, and circulate them internally to find the ones you missed.
Map your current enquiry process exactly as it happens, including the parts that live in somebody's inbox. Automating a process nobody has written down is how rollouts fail.
Shortlist on the requirements, not on reputation, and keep the list to three.
Demand a demonstration using your own enquiry types and your own data, not the vendor's tidy example.
Ask directly what it does badly. A vendor who cannot name a weakness has not been asked often enough by serious buyers.
Establish what leaving costs: can you export everything, in what format, and how quickly.
Pilot with one practice area for a quarter before rolling out to the firm, and appoint one person who owns it.
Budget more time for data migration and training than the vendor suggests, because that is the step that determines whether anyone uses it in month four.
The best CRM for a law firm is, unhelpfully but truthfully, the one your people will actually keep up to date. A modest system used properly produces better reporting than an excellent one used sporadically, and the second failure is far more common than the first.
FAQs
What is the difference between a legal CRM and case management?
A CRM handles everything before the matter exists — enquiries, their source, follow-up and conversion. Case management handles everything after: the file, documents, deadlines and billing. Some products do both, usually one well and the other adequately.
Why can't our practice management system tell us what marketing works?
Because it was designed for matters, not enquiries. Marketing attribution lives on the CRM side of the split, so if nobody has bought that half the reporting gap stays open no matter what else is installed.
What is the most important CRM feature for a law firm?
Recording the source of every enquiry automatically — including telephone enquiries — and keeping it attached through to instruction. It is the feature firms most need and least often put in their requirements.
How should we evaluate CRM products?
Write requirements before looking at anything, shortlist three against them, and insist on a demonstration using your own enquiry types and data rather than the vendor's example. Ask each vendor directly what their product does badly.
Why do CRM rollouts fail at law firms?
Almost always implementation rather than product: an enquiry process nobody had written down, underestimated data migration, no single owner, and insufficient training. Pilot with one practice area for a quarter before rolling out firm-wide.
End Note
There is no single best CRM for law firms, and any article confident enough to name one has substituted its own requirements for yours. What exists is a shortlist that becomes obvious once you have written down what the system must do and how your enquiries actually arrive.
Do that part first. It takes an afternoon, it eliminates most of the market, and it converts a comparison exercise into a decision.
Key Takeaways
CRM covers before the matter; case management covers after. Do not conflate them.
Marketing attribution lives on the CRM side — practice management will not supply it.
Capturing telephone enquiries with their source is the requirement that matters most.
Demand a demo on your own data, and ask each vendor what their product does badly.
Most failures are rollout failures: pilot one practice area, appoint one owner.
