Why a General CRM for Law Firms Fails PI Practice
The data model behind most CRMs was designed for quarterly sales quotas, and injury cases refuse to fit.
A general CRM for law firms fails a personal-injury practice because its core record, the deal, was built to model a sale that closes in weeks. A contingency case runs on medical treatment, records requests, liens, and court deadlines, often for a year or more before a dollar arrives. You can rename the pipeline stages and bolt on custom fields, and the mismatch survives, because the assumptions live in the data model itself.
Nimbus Marlowe is the AI operations layer for personal-injury law firms, starting with intake. We spend our days inside the operational plumbing of solo and small plaintiff firms, and this argument comes from watching what happens when contingency work gets poured into software designed for quota-carrying sales teams.
What is a general CRM built to model?
The center of every general-purpose CRM is the deal, sometimes labeled an opportunity. A deal has an amount, a close date, an owner, and a stage. The stage advances when the owner does something, like sending the proposal or getting the signature. Multiply each deal's amount by a stage probability, add the results up, and you have a forecast, which is the report this whole software category was invented to produce.
That design is honest about its purpose. It assumes the seller controls the tempo and that the deal's value is known up front. The record is also allowed to go quiet after the close, since the sale was the whole story.
Then a plaintiff firm signs up. The stages get renamed to Signed, Treating, Demand, Negotiation, and Settled, and for a week the thing resembles a personal injury case management system. The demo always looks right. The trouble starts when a real caseload arrives.
Why is a matter different from a deal?
A deal connects two parties. A matter carries a roster. One motor-vehicle case can involve the client, a spouse, two insurance adjusters on separate policies, defense counsel, four treating providers, and a health-plan lienholder. Each of those people has a role and a document trail, and a moment will come when someone at the firm needs to reach them fast. A general CRM attaches contacts to a deal as a flat list with no concept of role, so the paralegal hunting for the records custodian at the second imaging center is scrolling nine unlabeled names.
Records are the deeper problem. Moving an injury case means knowing which medical records requests went out, when they went out, to whom, what came back, and what is still missing. The deal object has no shelf for any of that. Firms compensate with a spreadsheet running next to the CRM, and once the spreadsheet exists, the CRM has stopped being the source of truth.
The stage field carries its own hidden assumption, which is that somebody inside the company moves the record forward. In a PI file, months can pass in treatment because a human body heals on its own schedule, and the judgment about when treatment is complete belongs to the client's doctors and the supervising attorney. Software that reads a long-running stage as a rep problem will nag the wrong person about the wrong thing, forever.
Why does PI intake break lead-nurture logic?
A general CRM treats a new lead as the opening move in a nurture sequence. Score the lead and drop it into a drip campaign, with a follow-up task set for next week. That cadence fits a buyer researching software over a quarter.
The 9pm car-accident caller is running a different clock. She is hurt, she is dialing down a search results page, and she signs with the first firm that answers and sounds competent. By the time a Monday follow-up task fires, the case has been signed for two days at somebody else's office. The metric that decides whether she becomes a client is minutes to a live answer, followed by qualification against the firm's own criteria and a consult on the calendar. Most general systems have no field for that number, because in their home market a lead that waits until Tuesday is still a lead.
What does a 14-month case do to a quarterly dashboard?
The forecast is where the mismatch turns into bad decisions. Weighted pipeline value multiplies deal amounts by stage probabilities to project the quarter's revenue. On a contingency caseload that arithmetic fails twice. Nobody knows at intake what a case will resolve for, and an attorney should distrust any dashboard that pretends otherwise. And the fee, whatever it turns out to be, may arrive in month 14, long after the quarter the software assigned it to. A firm that staffs or borrows against that projection is planning around a fiction.
Resolution exposes one more difference. A sales record has nothing left to do after the close. Resolution in a contingency practice opens its own workstream, with lien balances to clear and post-resolution follow-up that quietly becomes nobody's job. A record designed to die at the close goes dark at the exact moment the file still needs motion.
The numbers a small plaintiff firm can operate on look nothing like a forecast. Signed cases per month is one. So are days from signup to demand sent, files still waiting on outstanding records, and matters where the client has heard nothing in three weeks, because quiet clients go find new lawyers mid-case. A general CRM can be bent into reporting some of these with enough admin work, and at a five-person firm the admin doing that work is usually the owner, at night.
What does a PI-specific system have to track instead?
- •The matter as the core record, with every person attached in a role: client, adjuster, defense counsel, provider, lienholder.
- •Treatment and records status: which requests are still out, and which records came back with gaps.
- •The statute of limitations date as a first-class field the supervising attorney sets, visible to everyone who touches the file.
- •Demand milestones, from draft started through sent to response received.
- •Lien balances that follow the file all the way through resolution.
- •Client-contact aging, so a frustrated client surfaces in a report before surfacing in a bar complaint.
- •Fee events recorded at resolution, because that is the moment contingency revenue exists.
This list is the real substance behind the legal CRM vs general CRM question. It has little to do with feature counts. Two products can both advertise pipelines and automation, and only one of them can answer which records requests are still open on the Herrera file without a workaround.
Where does an ops layer fit?
A matter-shaped record is half the fix. Somebody still has to answer the 9pm call, chase the records, draft the demand, and keep post-resolution outreach alive. Nimbus builds that as an operations layer sitting in front of whatever practice-management system a firm already runs, so nothing gets ripped out. The intake coordinator answers every call 24/7 by voice, qualifies the caller against the firm's criteria, and books the consult, with a transcript waiting in the CRM. The demand letter drafter turns the file into a complete draft. The contract analyst flags the terms in an agreement that deserve attention, case preparation assembles what the team needs to move the matter, and collections follow-up keeps post-resolution outreach running on schedule.
Every one of those outputs lands as a draft that a licensed attorney reviews and adopts. That supervision chain is the design, since agents handle operations and attorneys practice law. Pricing is flat and published, per completed unit of work: a qualified intake runs about $18 and a demand letter draft is $170, against the $3,000 to $4,000 a month a part-time intake specialist costs. No Nimbus fee is ever a percentage of a recovery, and the company never holds or transmits client funds.
Frequently asked questions
Can a general CRM be customized for a personal-injury firm?
Partway, and plenty of firms have tried it with custom objects and renamed stages. The cost surfaces later as side spreadsheets and an admin workload that a firm of five has nobody to absorb. Renaming a stage changes the label without touching the assumptions underneath it.
What is the difference between a legal CRM and a general CRM?
A general CRM organizes its records around a sale with a close date and an owner who advances the stage. A legal CRM built for personal injury centers on the matter, holding parties in roles, treatment and records status, attorney-set limitation dates, and liens through resolution.
Does Nimbus replace my practice management system?
Nimbus sits in front of the system you already run. The agents handle intake, document work, and follow-up, and everything they produce arrives as a draft for attorney review. Keep what you have.
Does Nimbus take a percentage of settlements?
Never. Every rate is flat and published, identical whatever the outcome, and the company never holds, transmits, or takes custody of client funds.
The CRM underneath the Nimbus agents was built matter-first, and it costs $0, never invoiced. Sign up now to start free, or book a call and watch the intake coordinator take a live one.
Put your firm's operations on autopilot. Reviewed by you.
Nimbus Marlowe is the AI operations layer for personal-injury firms. The CRM is free, pricing is flat and per-unit, and every output is a draft your attorneys review and adopt.