Intake CRM vs. Case Management Software: Does Your PI Firm Need Both?

We decide from the workflow gap, not the software category.

Gadient Consulting helps PI firms decide whether to improve their existing platform or add a dedicated intake CRM. The firm needs pre-retention and matter-management capabilities, but it does not necessarily need two separate products. We begin with the work that currently fails.

We map source capture, contact, screening, follow-up, scheduling, acceptance, and transfer into ongoing matter work. We inspect where staff rely on memory, disconnected lists, or repeated data entry. The deliverable is a requirements and ownership map tied to real operating decisions.

Product descriptions below come from vendor documentation, not a hands-on ranking. Our role is workflow design, selection support, implementation coordination, testing, and adoption. We do not claim a partnership with every platform discussed.

We distinguish the person, inquiry, and matter.

We define identity and duplicate rules before field mapping. One person may make several inquiries, and several people may be connected to one incident. A shared phone number cannot automatically mean one matter; every repeat call should not automatically create a new acquisition record.

We assign intake responsibilities and matter responsibilities to the appropriate teams, then identify the shared information. The table below is the starting responsibility map. We adapt it to the firm’s approved acceptance process and access requirements.

We include declined and unresolved inquiries in reporting requirements. A system that reports only matters cannot explain everything marketing generated or where pre-retention work stopped.

Swipe or scroll the table sideways to view every column.

We translate vendor capabilities into demonstration requirements.

Clio describes Grow as intake and CRM and Manage as practice management, with transfer of intake information into the matter workflow. We require a demonstration of the specific fields, documents, ownership, and updates the proposed configuration transfers.

Lead Docket describes intake workflows and a native connection to Filevine. We test the trigger, field mapping, repeat transfer, failed transfer, and later correction. A native connector still needs operating ownership.

Litify describes intake and matter-management capabilities within its platform. We use that as a basis to test a single-platform approach, not proof that every workflow is included or configured in a quoted package.

We classify each requirement as native, separately licensed, integrated, custom, or manual. We carry that classification into the implementation scope so the firm knows what it is buying and who maintains it.

Source: Clio Grow: intake, CRM, and transfer to Manage

Source: Lead Docket: intake workflow and native Filevine transfer

Source: Litify: intake and matter-management capabilities

Compare the broader platforms in our Clio, Filevine, and Litify evaluation.

We run an inquiry-to-matter acceptance test.

We prepare a synthetic PI inquiry with original source, a second contact channel, missing screening information, and a callback request. The intended intake role progresses it; the firm’s approved legal process controls acceptance. We then inspect the receiving matter and assigned team.

We record the link between inquiry and matter identifiers, transferred documents, timestamps, source fields, contact restrictions, owner, and next action. A successful connector response is insufficient if the receiving person cannot find the work.

We repeat the transfer, correct a contact detail, and simulate a connection failure. We verify duplicate handling, exception routing, and recovery with the administrator. The test ends when staff can resolve the scenario in their actual permission level.

We assign authority field by field.

We document which system controls each value, who may update it, and what happens when values disagree. Original source may belong to intake while active legal status belongs to case management. The reporting layer can combine them without letting every tool overwrite both.

We preserve original source separately from later interactions and maintain the connection to the acquisition cohort after a matter closes. Contact restrictions require a defined process across affected systems, not two independently maintained preferences.

The field map includes direction, trigger, error owner, and acceptance evidence. We use it for implementation, testing, staff guidance, and subsequent integration maintenance.

Swipe or scroll the table sideways to view every column.

Connect the field map to law-firm marketing attribution.

We model the complete operating commitment.

Clio’s U.S. pricing page lists a starting price of $49 per user per month as checked September 30, 2026. That entry price is not a complete intake-plus-PI configuration. Lead Docket requests a custom quote. We obtain written scope for the actual products, modules, services, and usage the firm needs.

Our cost worksheet includes seats, minimum commitment, implementation, cleanup, migration, communication usage, signatures, integrations, reporting, training, internal administration, and exit. We separate recurring, one-time, and variable costs and compare the same horizon.

For the cost worksheet, add monthly software, implementation cost allocated across the selected period, and administration hours multiplied by loaded hourly cost. Entering $900, $6,000 over 12 months and eight hours at $60 calculates to $1,880 per month before usage and tax. Replace those inputs with the actual proposal. Released staff time creates value when the firm avoids a cost or uses the capacity productively.

We show the lower-utilization case as well as expected use. A capability that solves a problem can still be a poor purchase if the firm cannot staff or use the workflow.

Source: Clio U.S. pricing: products, tiers, and add-ons

Source: Lead Docket: custom pricing request

We recommend configuration, a connected pair, or one platform.

We favor improving the existing configuration when the required function is already available but ownership, fields, training, or reporting are inconsistent. We consider a dedicated intake layer when a demonstrated pre-retention gap remains and the firm can own the integration.

We recommend a single platform when it performs both groups of work reliably and preserves the necessary acquisition history. We do not use login count as a substitute for operational fit.

The objection to two systems is real: another bill, handoff, and failure point. The objection to one is also real: shallow intake controls may conceal unfinished work. Our recommendation weighs demonstrated failures and management effort, not feature totals.

We manage the boundary through pilot and adoption.

We coordinate a bounded rollout with the field map, permissions, test scenarios, training, and acceptance criteria. The assigned technical team performs authorized configuration and migration work; we track dependencies and verify the operating result with staff.

Before cutover, we check critical records, identifiers, documents, open tasks, dates, and access. We require a continuity and rollback plan and inspect declined and unresolved inquiries as well as successful matters.

We use Clio’s conversion documentation as a checklist and ask the vendor to demonstrate which information transfers in the proposed configuration. We explicitly test task ownership, pending work, and receiving-team access rather than assuming that a transfer function completes the client handoff.

Source: Clio Help: convert matters and field-transfer limitations

Explore implementation and ongoing ownership through AI agents and automation for law firms.

We keep ownership after the software goes live.

We review failed transfers, duplicate creation, missing fields, staff adoption, and report reconciliation. We update the operating documentation and coordinate changes as the firm’s process evolves. Launch is the beginning of management, not the end of the engagement.

If an AI assistant is added, we define its permitted reads, writes, human approval points, and failure queue against the same authoritative records. Automation should fit the architecture rather than silently introducing another competing source of truth.

Bring one broken workflow and the current system map to a consultation. Our software and fractional CMO work connects the implementation decision to intake execution, attribution, capacity, and the next investment the firm needs to make.

Discuss the work with Gadient Consulting in a consultation about this workflow.