How to Choose a CRM for a Law Firm: A Practical Selection Guide

Before the steps, it helps to know the usual failure points:

• Buying features, not outcomes. Every system can do more than the firm will use. The question is whether it does the few things that matter, easily.
• Letting one function choose. A CRM chosen only by IT may not suit marketing. One chosen only by marketing may not suit partners or fit the firm's systems.
• Trusting the demonstration. Vendors show their product at its best, using their own data and their own scenarios.
• Underestimating the cost. Licences are usually the smallest part of the total.
• Ignoring adoption. If partners do not record relationships and activity, the system cannot tell you anything useful.
• Migrating a mess. Moving years of duplicated, outdated and unconsented contacts into a new system simply moves the problem.

The most important question is not "which CRM?" but "how do we get instructions?" The answer shapes almost every requirement.

Many firms are a mix: a commercial practice that wins through relationships alongside a private client team that depends on enquiries. If so, decide which needs come first, and make sure the system handles both without forcing one team into the other's process.

Our overview of the main types of law firm CRM explains which kinds of system tend to suit each model.

Write down the three to five problems the CRM must fix, in the firm's own words. For example:

• "When a partner leaves, we lose track of their relationships."
• "We don't know how many website enquiries we lose, or why."
• "We can't produce a list of everyone who attended our events this year."
• "We can't tell which referrers send us work."
• "Our mailing lists are out of date and we're not sure what consent we hold."

Then separate must-haves from nice-to-haves. A short list of must-haves keeps the selection focused and stops vendors winning on features the firm will never use.

If referrers and enquiry follow-up are the main drivers, our guide to how to get new clients for a law firm explains how to manage both systematically.

A CRM touches most of the firm. Involve, from the start:

• A partner sponsor, respected by other partners, who will champion its use
• Business development and marketing, who will use it most
• IT, for integrations, security and support
• Whoever handles enquiries, such as reception, intake or new business teams
• The person responsible for data protection, for consent, retention and vendor checks
• Two or three fee earners, including a sceptic, to test whether it is genuinely easy to use

Keep the selection group small enough to make decisions, but broad enough that nobody can say the system was chosen without them.

A few pages is enough. It should cover:

1. How the firm wins work, and which practices matter most
2. The problems the CRM must solve, with must-haves and nice-to-haves
3. Who will use it, and for what
4. What it must connect to
5. Reporting the firm needs (for example enquiries by source, conversion to instruction, relationship coverage for key clients)
6. Data protection and security requirements
7. Budget range and timescale

Send the same document to every shortlisted vendor. It makes their responses comparable and forces them to address your needs rather than their standard pitch.

A CRM that does not connect to the systems people already use becomes a separate place to type things, and quickly gets ignored. List what matters:

• Email and calendar, usually Microsoft 365, so contacts and activity can be captured without retyping
• Website enquiry forms, so enquiries go straight into the system
• Practice or case management, so the CRM knows who is already a client and which matters followed an enquiry
• Email marketing and event tools, if they are separate
• Finance, if you want to report on the value of work by client, referrer or source

For each one, ask vendors whether the connection is built in, needs a third-party tool or needs custom development. The answer has a large effect on cost and reliability.

Three systems is usually enough. More than that makes demonstrations hard to compare and the decision slower. It is often worth including more than one type of system, for example a legal-specific product and an adapted general platform, so the firm can see the trade-offs for itself.

Do not let vendors run their standard demonstration. Give each one the same scenarios in advance, based on how your firm actually works, and ask them to show each one live. For example:

• A new relationship. "A partner meets a potential referrer at an event. Show us how that contact, the conversation and a follow-up reminder are recorded, on a phone, in under two minutes."
• An enquiry out of hours. "A website enquiry arrives at 6pm on a Friday. Show us how it is acknowledged, who is notified, and how we see on Monday whether it was followed up."
• A targeted mailing. "Marketing wants to invite HR directors at existing clients who attended a webinar in the last year. Show us how that list is built, and how people who have opted out are excluded."
• A partner leaving. "Show us everything the firm knows about the relationships of a partner who is about to retire."
• A report for partners. "Show us last quarter's enquiries by practice and source, and how many became instructions."

Then ask the questions demonstrations tend to skip:

• What would we need to configure to do this, and who does it?
• What does a fee earner have to do manually, and how often?
• How does it work on mobile and inside Outlook?
• What happens to our data if we leave, and in what format do we get it back?
• Which features shown today cost extra?

Score each system against the same scenarios immediately after each demonstration, while the differences are fresh.

The licence price is usually only part of the cost. Compare every shortlisted system across the same elements:

Look at the cost over three to five years, not just the first year. A cheaper licence can become the more expensive choice once configuration and administration are included.

A CRM holds some of the firm's most sensitive information, so the checks matter as much as the features:

• Data location and security. Where is the data stored, who at the vendor can access it and what security certifications does the vendor hold?
• Access controls. Can access be restricted where confidentiality or conflicts require it, so sensitive client relationships are visible only to the right people?
• Consent and marketing rules. Can the system record the lawful basis for marketing, consent and opt-outs for each contact? Under PECR, marketing emails to companies and LLPs are treated differently from emails to sole traders and some partnerships, which are treated as individuals and generally need consent. The system should let you tell them apart.
• Retention. Can it apply retention rules and support data subject requests?
• AI features. If the system includes AI tools, what data do they use, where is it processed and is it used to train the vendor's models?
• Contract terms. Check the data processing terms, sub-processors and what happens to your data at the end of the contract.

These checks also support the firm's professional duty to keep client affairs confidential.

Ask each vendor for references from UK firms of a similar size, practice mix and way of winning work, ideally ones that have used the system for more than a year. Ask them:

• How long did implementation really take, and what did it really cost?
• Do partners use it? What made the difference?
• What would you do differently?
• How responsive is the vendor when something goes wrong?

Speaking to firms that are a year or two in will tell you more than one that has just launched.

Adoption decides whether a CRM is worth the investment, so plan it during selection, not after go-live:

• Make it easy. Capture as much as possible automatically from email and calendar, and keep the information fee earners must add to a minimum.
• Give partners something back. Reports and briefings partners actually want, such as a relationship summary before a client meeting, give them a reason to use it.
• Clean the data first. Remove duplicates and outdated contacts, and record consent before migration, so the system is trusted from the first day.
• Launch in phases. Start with the problems that matter most, show results, then extend.
• Train by role. Short sessions for partners, fee earners, BD and support staff, each focused on what they need.
• Measure use. Agree how adoption will be tracked, and what the partner sponsor will do if it lags.

Many firms already own a capable system that nobody uses. Before replacing it, ask whether the problem is the software or the way it was set up and introduced. Cleaning the data, simplifying the configuration, adding useful reports and retraining users often costs less than a new system and avoids a second difficult migration.

Replacement makes more sense when the system cannot connect to the tools the firm relies on, cannot meet data protection requirements or no longer suits how the firm wins work.

Score each shortlisted system against the same criteria after demonstrations and reference calls:

Agree the relative importance of each criterion before the first demonstration, so the decision reflects the firm's priorities rather than whichever system presented best.