Legal Practice Playbook: Running Client Intake and Case Pipeline in a CRM
A practical playbook for law firms running client intake, matter status, and referral tracking through a CRM instead of spreadsheets and inbox threads.
Last updated July 18, 2026
Why a legal practice needs a CRM separate from case management
A CRM and a practice/case management system solve different problems: the CRM tracks prospective clients before a matter opens, and case management tracks the matter itself once it's live. Most firms already have one and are missing the other.
Case management software is built around an open matter — documents, deadlines, billing, court dates. It's not built to answer "how many personal injury inquiries came in this month and what happened to them" or "which referral sources actually convert." That's intake data, and it lives and dies in a partner's inbox or a paralegal's notebook unless it's captured in a CRM.
Example
Imagine a small personal injury firm that gets inquiries from three channels: a web form, a referral network of local doctors, and walk-ins. Without a CRM, each intake coordinator tracks their own leads in a personal spreadsheet. When a partner asks how many car-accident inquiries converted to signed clients last quarter, nobody can answer without emailing three people and reconciling three spreadsheets.
How to structure intake as a pipeline, not a to-do list
The answer: model intake as deal stages — Inquiry Received, Conflict Check, Consultation Scheduled, Consultation Held, Retainer Sent, Signed Client, Declined — rather than a flat task list, so a coordinator can see exactly where every prospective client sits at a glance.
A to-do list tells you what's left to do; a pipeline tells you where things are stuck. If forty inquiries are sitting in "Consultation Scheduled" and only three ever move to "Retainer Sent," that's a signal the consultation itself isn't converting — a fact a spreadsheet of tasks won't surface, but a pipeline view will show as an obvious bottleneck the moment someone looks at the board.
Example
A typical Legal team might set up a kanban board with those seven stages and review it every Monday. Seeing eighteen cards stuck in "Conflict Check" for more than five business days tells the office manager the conflict-check process itself is the bottleneck, not attorney availability.
How to track referral sources without losing attribution
The answer: tag every contact with its referral source as a custom field at the moment of intake, not after the matter is won, because attribution entered retroactively is unreliable.
Law firms depend heavily on referrals — other attorneys, past clients, medical providers, community contacts — and knowing which sources produce clients that actually sign (versus ones that produce a lot of inquiries that go nowhere) changes where a firm spends its relationship-building time. This only works if the source field is a required part of intake, filled in by whoever takes the call, rather than something reconstructed later from memory.
Example
A firm might discover, after a year of consistent tagging, that a single referring physician's inquiries convert to signed retainers at twice the rate of web-form leads, even though the web form produces five times the volume — a finding that reshapes where the managing partner spends time each month.
How to handle conflict checks and confidentiality inside a CRM
The answer: run the conflict check as an explicit, gated pipeline stage that blocks progress until cleared, and restrict visibility on sensitive matters using field- and record-level permissions rather than keeping them out of the system entirely.
Some firms hesitate to put prospective client information in a CRM at all, worried about confidentiality. The more reliable practice is controlling access inside the system — restricting a sensitive intake record to the handling attorney and one staff member — rather than falling back to an unsearchable paper file that nobody else can reference either. A conflict check that's a required, visible stage (not a verbal "did anyone check?") also prevents a case from proceeding informally before clearance.
Example
A firm might configure their pipeline so a case cannot move past "Conflict Check" until a specific field is marked cleared by a designated reviewer, closing the gap where an eager associate schedules a consultation before conflicts are actually resolved.
How to automate follow-up without sounding like a form letter
The answer: use templated but personalized follow-up sequences tied to pipeline stage — a consultation-scheduled confirmation, a no-show re-engagement, a post-consultation nudge if the retainer hasn't been signed within a set number of days — rather than either manual one-off emails or an obviously generic mass sequence.
Prospective clients contacting a law firm are often in a stressful situation and notice when correspondence feels canned. Automation should reduce the coordinator's manual workload without making the client feel like a number; stage-triggered, lightly personalized templates achieve both, since the trigger is invisible to the recipient but the time savings is real for staff.
Example
A typical setup might auto-send a consultation confirmation with the assigned attorney's name and a case-type-specific document checklist the moment a "Consultation Scheduled" stage is entered, saving the coordinator a manual email on every single inquiry.