The Problem With Plugging a Generic CRM Into a Law Firm

I had a conversation with a managing partner at a mid-size personal injury firm who had just spent eight months trying to get HubSpot to work as their intake and matter management system. They built out pipelines, connected their web form, and set up automated emails. What they could not do: run a conflict check before moving a new client into their database, isolate matter data so that associates could only see files they were assigned to, or prevent the marketing sync from pulling client names into their email campaign tool. They scrapped the implementation and went back to spreadsheets.

That is not a story about HubSpot being a bad product. It is a story about using the wrong category of tool for a regulated industry with specific data obligations.

Client Intake: The First Four Steps

A proper law firm intake flow has a specific sequence that most CRMs cannot enforce natively. It goes roughly like this: a prospective client submits a web form or calls in; that inquiry triggers a conflict check against the firm existing and former client database; if no conflict is found, a retainer or engagement letter is generated and sent for signature; upon signature, a matter is opened and the contact transitions from prospect to active client.

Each of those steps has a dependency on the one before it. You cannot open a matter before the conflict check clears. You cannot send the engagement letter before the conflict check clears. A CRM that treats all pipeline stages as equal and does not enforce gate logic cannot model this without manual intervention at every step.

The conflict check itself is the piece most generic tools skip entirely. It requires querying a database of all current and former clients, opposing parties, related entities, and sometimes witnesses — and comparing new intake names against that database before proceeding. This is not a feature. It is an ethical and professional responsibility obligation.

Matter Management vs. CRM: What Is Different

A CRM tracks relationships and business development activity. A practice management system — Clio, MyCase, Filevine, Smokeball — tracks matters, deadlines, time entries, billing, and documents. These are different jobs.

The distinction matters because firms often try to collapse both into one tool and end up with a system that does neither well. The CRM side needs to track referral sources, business development conversations, potential client relationships, and marketing attribution. The matter side needs to track case milestones, court dates, statute of limitations deadlines, assigned timekeepers, and billed hours. Those data structures are different enough that merging them into a single pipeline view creates confusion rather than clarity.

The firms that have this working well almost always have two systems with a deliberate integration between them, not one system trying to do everything.

Confidentiality and Data Isolation

Role-based access in a law firm CRM is not optional. A client intake coordinator should be able to see prospective client records and move them through intake stages, but should not have access to financial terms, matter strategy notes, or case documents. Associates should see only the matters they are assigned to. Partners may need cross-matter visibility for conflict checking and business development purposes.

The data isolation problem becomes acute when the firm also runs marketing. Client names, matter types, and case outcomes are confidential. A system that syncs all contacts to a marketing email platform without filtering — something that many off-the-shelf CRM and marketing tool integrations do by default — creates a confidentiality problem. The marketing sync needs to be scoped to business development contacts and prospective clients, not active or former clients, and it needs to exclude any matter-specific data.

Statute of Limitations and Deadline Tracking

This one is specific to law and it is not something most CRM vendors think about at all. Statute of limitations deadlines are tied to matter type, jurisdiction, and sometimes the discovery date of the harm rather than the date of the incident. Missing one is malpractice.

A CRM or intake tool that captures the incident date, matter type, and jurisdiction should be able to calculate and surface the applicable deadline automatically. It should also flag cases that are within 90 days of that deadline so someone can escalate or confirm that filing is on track. This is not complex logic, but it requires that someone build it deliberately. Off-the-shelf CRMs do not include it because they are not built for law.

Referral Source Tracking for Business Development

Law firms, particularly those that generate business through referral networks — other attorneys, accountants, financial advisors, past clients — need a clean way to track where new matters originate. This is the part of a law firm operation that looks most like traditional CRM: relationship management with people who send you business, tracking which referral sources are most productive, and staying appropriately in touch without being transactional about it.

This business development CRM layer should live separately from the matter management system. It can sync selectively — for example, pulling in matter open dates to update a referral source record with their most recent referral — but it should not expose matter details to whatever marketing or outreach tool the business development team uses.

The Honest Answer: You Probably Need Both Systems

Most firms I have worked with that are trying to solve this with a single tool end up building workarounds that create more manual work than having two systems with a clean integration would. The practice management platform handles matters, billing, and deadlines. A CRM — potentially a custom one — handles intake workflow, conflict check logic, referral tracking, and business development activity.

The integration between them needs to be explicit and scoped. When a prospect converts to a client, a record is created in the practice management system and the CRM record is updated to reflect active client status. That is a handoff, not a merge. The two systems do not share all their data — they share the specific fields that need to flow between them.

Where to Go From Here

If the intake or conflict check gaps resonate, the custom CRM page covers how I approach building systems for regulated industries where off-the-shelf tools cannot satisfy data isolation or workflow enforcement requirements. It is also worth looking at the integrations piece if you already have a practice management tool and need to connect it to something cleaner on the business development side.