A firm buys software, imports its contacts, runs training, and then watches the system quietly become a place where nobody looks. Six months later the intake coordinator is back in a spreadsheet, the attorneys are back in email, and the reports the managing partner wanted still do not exist. The problem is almost never the product. It is that the firm bought a law firm crm to solve a records problem when the actual problem was that intake had no defined process to record.
This matters more than it sounds. Intake is the only part of a law firm where the work is fully controllable, fully repeatable, and directly tied to revenue. If a law firm crm cannot get traction there, it will not get traction anywhere else, because every downstream feature depends on data that intake was supposed to create.
What firms are actually trying to solve
When a managing partner starts searching for software, the stated goal is usually something like "we need better tracking of leads." The real goals underneath are narrower and more specific, and they are worth naming out loud before you look at a single demo.
Most firms want to know how many people contacted them last month and what happened to each one. They want to stop losing prospective clients who called on a Friday afternoon. They want conflicts checked before someone spends an hour on a consultation. They want to know which referral sources produce matters that actually convert and pay, not just calls. And they want to stop the situation where a partner asks about a specific prospect and three people give three different answers.
None of these are software problems in the first instance. They are process problems. A firm that cannot answer "who is responsible for responding to a new enquiry within four business hours" will not be able to answer it after buying a product either. The software will simply make the absence of an answer more visible, which is genuinely useful, but only if someone acts on it.
Where rollouts actually break
The common failure pattern is predictable. The firm configures the system around its ideal process rather than its real one. Intake staff find that logging a call properly takes four minutes when the old way took forty seconds. So they log the ones they remember, skip the ones they do not, and within a quarter the data is unreliable enough that nobody trusts the reports. Once the reports are untrusted, the discipline collapses entirely.
The second failure is treating intake as one process when it is several. A personal injury firm running a motor vehicle case, a premises liability case, and a workers compensation referral has three different qualification paths, three different sets of statutory deadlines, and three different reasons to decline. A family law firm's intake for a contested custody matter looks nothing like an uncontested dissolution. Building one generic pipeline to cover all of them produces a pipeline that fits none of them, and staff route around it.
The third is ownership. Software rollouts that succeed have a named person whose actual job includes the system. Not a committee, not "the office manager when she has time." Someone with authority to change the process when it does not work and enough proximity to intake to notice within days rather than months.
Judging the options honestly
The market splits into categories that are easy to confuse.
Practice management platforms such as Clio Manage, MyCase, and Filevine handle matters, time, billing, and documents, with intake and lead tracking as an adjacent capability. Clio Grow and MyCase's intake features sit in this family. The advantage is a single system of record from enquiry through to closed matter. The tradeoff is that the intake and marketing automation side is usually less flexible than a dedicated tool.
Dedicated legal intake and marketing platforms such as Lawmatics are built specifically around the pre-engagement stage. They tend to be stronger on drip campaigns, form building, e-signature on engagement letters, and conversion reporting. The tradeoff is another system to integrate and another set of data to keep in sync with wherever matters actually live.
General purpose CRM tools such as HubSpot or Salesforce can be configured for legal work and offer more raw flexibility. The tradeoff is that legal-specific concepts like conflicts, matter numbers, trust accounting boundaries, and statutory deadlines have to be built by hand, which means real configuration cost and ongoing maintenance.
A few honest questions to ask any vendor:
- Can I see the actual click path an intake coordinator takes to log an unqualified enquiry, timed, not the polished demo version?
- What happens to my data if I leave, and in what format?
- How does the system handle a conflicts check, and is that check a real search across matters and parties or just a text field?
- Which of the features you just showed me require the higher tier?
- Who at your company will still be reachable in month seven?
A worked example
Consider a five-attorney employment law firm in Sacramento handling wrongful termination and wage and hour matters. Enquiries arrive by phone, web form, and referral from two staffing agencies.
The workable configuration looks like this. A web form captures name, contact details, employer, employment dates, a short description, and how they heard about the firm. On submission, the record is created and a conflicts search runs against existing party names, returning a flag rather than a decision. An unflagged enquiry triggers an automatic acknowledgement email with a scheduling link and an internal task assigned to the intake coordinator with a four hour due time. Flagged enquiries route to an attorney for review before any substantive contact.
Qualification is a short structured set of fields, not free text: employment end date, whether a right to sue letter exists, whether the client has filed with the Civil Rights Department or the Labor Commissioner, and approximate wage figures. The employment end date drives a calculated reference date on the record so that anything approaching a limitations concern surfaces on a review list rather than sitting in someone's memory. The system flags it. An attorney decides what it means. That distinction is not negotiable, and any configuration that blurs it is a professional responsibility problem, not a workflow preference.
Consultations that convert generate an engagement letter from a template with client and fee terms populated, sent for signature. Declines get a written non-engagement letter, logged, with the record retained. That declined-file record is worth more than most firms realise, both for conflicts purposes later and because the pattern of what you decline tells you something about your marketing.
What the software will not do for you
It will not decide whether a matter is viable. It will not compute a limitations period you can rely on. Statute calculations involve tolling, discovery rules, government claim requirements, and continuing violation questions that no field configuration handles. Treat any date the system produces as a prompt to look, never as an answer.
It will not fix a conflicts problem. Automated checks catch exact and near-name matches. They miss corporate relationships, former clients under prior names, and the positional conflicts contemplated by the California Rules of Professional Conduct. An attorney reviews the output.
It will not make your data compliant on its own. If your firm falls within CCPA thresholds, intake data collection creates notice and deletion obligations that sit with the firm regardless of what your vendor's marketing materials say about security. Read the data processing terms before you import anything.
And it will not produce good numbers from bad input. Conversion reporting from a law firm crm is only as honest as the discipline of the people logging enquiries.
What to do first
Before you evaluate a single law firm crm, spend two weeks logging every inbound enquiry in a spreadsheet with five columns: date, source, practice area, who handled it, and outcome. Do not change anything else. At the end, you will know your real volume, your real response times, and where enquiries actually die. That spreadsheet is your specification. Firms that skip this step buy features. Firms that do it buy a fit.
Then pick one practice area, configure the process for that alone, and run it for a quarter before expanding. If you want help mapping the process before you commit to a platform, that mapping and automation work is what Alphovia does.