The short answer
Choose the operating model, then prove the handoff.
Lawmatics is the more obvious candidate for a CRM-led intake and marketing stack with a broad published case-management integration marketplace. Lead Docket is the more obvious candidate for a Filevine-centered intake stack with product-family handoff paths and PI-oriented lead operations.
That is a fit hypothesis, not a winner. Both base platforms require a quote. Both have capabilities whose price or entitlement depends on add-ons, usage, purchase date, or a related product. The selection should turn on a written requirements matrix, a complete cost model, and the same fictional-data acceptance test in both systems.
Evidence rules
Read every capability with its current status attached
A demo can place shipped, paid, beta, and future features on the same screen. This guide does not. “Live” means an official current source supports availability; it does not mean every plan includes it.
Described as currently available in a dated official product page, help article, release note, or contract specification.
Available now, but the official source says it carries an additional fee, separate package, seat, outcome allowance, or usage charge.
The vendor publishes packaging but asks the firm to obtain a tailored price. A public list price is not assumed.
Sources leave an entitlement unclear, differ by purchase date, or conflict. Treat the signed order form and current demo tenant as authoritative.
The vendor explicitly describes it as in development or future. It is not counted as a present capability in this comparison.
Excluded from a must-have unless the vendor proves the exact feature is enabled, supported, and contractually available for the firm.
Status ledger
What is live, separately priced, uncertain, or still future
Lawmatics
Core CRM and intake platformEssential, Premium, and Enterprise are current plans. Public materials describe intake, lead management, forms, calendaring, e-signature, tasking, and higher-tier automation and marketing capabilities.
Lawmatics
Merlin Qualify and EngageCurrent help articles describe lead evaluation and AI-led SMS/email data collection, qualification, and booking. Lawmatics prices these through monthly AI Outcome allowances and overages.
Lawmatics
Merlin CopilotA current Copilot article lists Lite at $29/seat/month and Pro at $49/seat/month, and a Q3 update says it is available. The Merlin suite overview still contains “Coming Soon” language. Confirm entitlement and production status in writing.
Lead Docket
Core intake and lead trackingFilevine currently markets Lead Docket for lead capture, follow-up, qualification, source visibility, forms, e-signature workflows, document collection, referral tracking, and payments.
Lead Docket
Expanded Lead Docket AutomationsCurrent product specifications say the automation package must be purchased for all existing Lead Docket users and carries action allowances and overage terms. Base entitlements also vary by contract date and package.
Lead Docket
LeadsAI, OCR, and Ask LOISLeadsAI is described as included on newer Lead Docket subscriptions, with older-contract exceptions. Dated release notes show Ask LOIS, call-transcript access, OCR, and document summaries live; confirm the purchased package and usage limits.
Lead Docket
Lead ViabilityFilevine’s August 2026 product article says Lead Viability is in development. This page does not treat it as available today.
Requirement-by-requirement comparison
Compare proof your intake operation needs—not abstract feature scores
Each row begins with a testable PI operating requirement. Official links and the verification date sit beside the claim so procurement can re-check the evidence when the proposal arrives.
Published buying model
Proof question: Can finance calculate the first-year and steady-state cost without guessing?
Lawmatics
Lawmatics says pricing is tailored. Its public comparison identifies Essential, Premium, and Enterprise, plus user minimums, contact allowances, usage limits, and separately priced add-ons—but not a public base subscription total.
Lead Docket
Filevine says packages are custom built and asks firms to contact sales. The current product specifications publish some allowances and overage mechanics, but the base Lead Docket price remains quote-based.
Intake record and daily queue
Proof question: Can every channel create a traceable lead with a named owner, next action, status, and visible exception?
Lawmatics
The core plans list client intake, lead management, custom forms, calendaring, pipelines, task management, two-way SMS, and e-signatures. Premium adds round-robin scheduling and more advanced workflow/reporting tools.
Lead Docket
The current product page describes capturing leads from web forms, live chat, and after-hours calls, then using immediate SMS/email follow-up, intake forms, document collection, lead tracking, and source visibility.
Workflow automation
Proof question: Can the firm automate its actual steps and still see failures, retries, ownership, and usage consumption?
Lawmatics
The public comparison lists 10 automations on Essential and unlimited automations on Premium and Enterprise. Exact triggers, actions, messaging usage, and services should be proven in the proposed plan.
Lead Docket
Current specifications describe up to 100 automation actions per user/month in Lead Docket, while the separately purchased automation package must cover all Lead Docket users and includes up to 500 actions per user/month, with published overage mechanics.
Marketing attribution and intake reporting
Proof question: Can the firm trace source, spend, response, consultation, signed-case outcome, and corrections to the underlying lead?
Lawmatics
Premium and Enterprise list source reporting, ROI tracking, UTM tracking, custom reports, custom dashboards, email marketing, and large email-send allowances. Validate the exact definitions and source connectors used by the firm.
Lead Docket
Lead Docket’s current product page emphasizes seeing which sources produce strong leads and following each lead through conversion; Filevine’s pricing page also lists referral fee tracking. Require a report using the firm’s own source taxonomy.
PI qualification and AI-assisted intake
Proof question: Can the firm define its criteria, inspect source evidence, override results, and keep the attorney in control of the decision?
Lawmatics
Merlin Qualify applies firm-defined criteria and shows confidence and reasoning; Engage can collect missing information and book consultations over SMS or email. Qualify’s current documentation says file uploads are not evaluated and notes are optional with stated limits.
Lead Docket
LeadsAI summarizes lead details, messages, and notes and provides sentiment/timeline functions. Ask LOIS, call-transcript access, OCR, and document summaries are documented as live. Lead Viability remains explicitly “coming soon” and is excluded from present fit.
AI price and consumption model
Proof question: Can operations predict how one lead may consume multiple billable events, seats, summaries, or overages?
Lawmatics
Merlin Qualify and Engage share monthly AI Outcome plans: 50/$149, 100/$249, 200/$399, 500/$749, 1,000/$999, and 2,000/$1,999, plus tier-specific overages. One lead can create multiple outcomes. Copilot documentation separately lists Lite and Pro seat prices.
Lead Docket
Current specifications describe 100 LeadsAI summarizations per user/month on newer Lead Docket subscriptions, exceptions for pre-2026 subscriptions, and contracted or then-current overages. Filevine does not publish the base package total.
Filevine handoff
Proof question: Does a retained lead arrive with required fields, files, people, notes, ownership, and an acknowledged failure path?
Lawmatics
Lawmatics documents a one-way sync into Filevine through conversion or a separate sync action, with configurable matter, document, note, relationship, and compatible custom-field mapping. Filevine changes do not sync back; company matters are not supported.
Lead Docket
Official materials document pushing case details to Filevine, Filevine field mapping, a pending-Filevine queue, and current transfer of phone-call activity and related documents. Prove the exact objects, retries, duplicate handling, and receiving project template.
Broader integration strategy
Proof question: Will the intake CRM work with the firm’s present case system, communications stack, lead sources, calendar, and export process?
Lawmatics
Lawmatics lists case-management connections including Filevine, Clio, 8am MyCase, CARET Legal, DocketWise, LEAP, PracticePanther, Rocket Matter, SmartAdvocate, and Smokeball, plus lead, calendar, communications, file, connector, and billing categories.
Lead Docket
Filevine’s specifications define a Lead Docket CMS Integration for third-party systems but do not promise universal compatibility or responsibility for the third-party system. Ask for the named connector, direction, fields, files, retry path, and support owner.
Messaging, call context, and payments
Proof question: Which channels are native, what usage is included, and which records follow the lead into the matter?
Lawmatics
The plan table lists two-way SMS with plan allowances, MMS as an add-on on higher tiers, and a separate Time & Billing add-on. Marketplace listings include communications and call-tracking tools. Native voice and intake-payment workflow should be demonstrated, not inferred.
Lead Docket
Current specifications price Lead Docket text/tracking lines at $20/month per number with 1,000 texts and 300 voice minutes, then published overages. Product pages list online payments; October release notes show phone-call items and documents transferring to Filevine.
Best-fit operating models
The architecture is the decision—not the logo
Use these as shortlisting hypotheses. A vendor earns the fit only after it proves the firm’s actual roles, data, exceptions, integration, and economics.
Lawmatics may fit better
A CRM-led growth and intake stack
- ✓The firm wants intake, CRM, marketing automation, campaign attribution, events, and nurture in one pre-retention platform.
- ✓The downstream case system may be Filevine—or one of several other systems in a broader published integration marketplace.
- ✓A one-way, intake-to-case handoff is acceptable and the firm is prepared to govern the source of truth after conversion.
- ✓The firm is willing to separately model Merlin outcomes, Copilot seats, messaging, contacts, onboarding, and other add-ons.
Lead Docket may fit better
A Filevine-centered PI intake stack
- ✓Filevine is already, or is intended to become, the authoritative retained-matter platform.
- ✓The firm values a documented path for pushing leads, mapped information, files, calls, payments, and referral context into Filevine.
- ✓Intake operations need lead-source visibility, rapid follow-up, forms, document collection, and PI-oriented lead workflows.
- ✓The firm is comfortable negotiating a package whose automation, AI, phone-line, e-signature, payment, and case-system entitlements must be confirmed in the order form.
Keep evaluating
Neither vendor has yet passed the proof test
- ✓A hard requirement depends on a roadmap, beta, early-access interface, undocumented connector, or verbal promise.
- ✓The firm requires reliable two-way Filevine synchronization rather than a controlled one-way handoff.
- ✓Finance cannot reconcile base licenses, implementation, migration, usage, overages, support, and renewal terms into a complete cost model.
- ✓The demo cannot reproduce the firm’s real PI roles, intake fields, exception paths, exports, permissions, and downstream acceptance evidence with fictional data.
Fictional-data acceptance test
Make both vendors run the same PI matter
Use a sandbox and unmistakably fictional people, incidents, numbers, documents, and signatures. Do not enter a real prospect, client, medical record, opposing party, claim number, or other live identifier. Save screenshots, exports, and usage logs as evidence.
- 1
Capture the same fictional inquiry
Run
Submit “Jordan Example,” a fictional rear-end collision lead, through a tagged web source after hours. Include a preferred contact channel, one adverse party, a referral source, one attachment, and two deliberately unknown facts.
Pass evidence
The system preserves source, consent context, earliest receipt, supplied facts, unknowns, attachment, and a durable lead ID without inventing missing details.
- 2
Prove ownership and response
Run
Route by practice area and location, trigger the approved acknowledgement, assign a primary and backup owner, record one failed delivery, and then log meaningful two-way contact.
Pass evidence
The queue distinguishes acknowledgement from human response and exposes assignment history, delivery status, overdue work, and escalation.
- 3
Collect and correct facts
Run
Send a fictional intake form and document request. Correct the incident date after submission, add a duplicate contact, and ask the AI tool to summarize or evaluate the lead if included in the proposed package.
Pass evidence
The source answer, correction, duplicate path, file, summary, reasoning, human override, and any AI usage event remain reviewable. The AI does not silently replace the source record.
- 4
Schedule and sign
Run
Book a consultation, reschedule it once, send the vendor’s proposed e-signature workflow, let the first delivery fail, and complete the second send using a fictional signature.
Pass evidence
Availability, owner, reminders, reschedule history, document version, delivery failure, signature status, and final artifact are visible in the agreed systems.
- 5
Handoff into a Filevine sandbox
Run
Convert the fictional lead into the designated Filevine project template with mapped people, incident facts, source, note history, document, phone-call context if promised, open task, and responsible attorney.
Pass evidence
Filevine returns a project identifier; every required object arrives in the correct place; unsupported fields are listed; and the intake record shows accepted, partial, failed, or retrying status.
- 6
Break and reconcile the handoff
Run
Disable the receiving connection, attempt a duplicate transfer, reject one file, then restore service and correct one field after conversion. Export the resulting audit evidence.
Pass evidence
No failure disappears. A named owner can retry or resolve it, the duplicate does not silently create a second matter, corrections follow the documented authority rule, and usable data can be exported.
Procurement script
Questions that turn a demo into an auditable proposal
Commercial terms
- ?What is the complete first-year price for required users, implementation, migration, contacts, phone numbers, messages, forms, signatures, payments, integrations, AI, and support?
- ?Which usage pools are firm-wide, per user, per seat, per lead, per outcome, per action, per summary, or per phone number?
- ?What happens at the limit: hard stop, throttling, automatic overage, tier upgrade, or loss of functionality?
- ?Which prices, discounts, minimums, renewal increases, and cancellation or export services appear in the binding order form?
Current product status
- ?For every must-have, is it generally available, add-on, contract-limited, beta, early access, or roadmap?
- ?Can the vendor show the feature in the same production version and plan being quoted—not a preview tenant or conference demo?
- ?Where current help articles conflict, which document controls and who will confirm the answer in writing?
- ?Which AI capabilities require a Filevine, Lawmatics, Merlin, LOIS, LeadsAI, Vinesign, Payments, or other separate entitlement?
Operations and control
- ?Can permissions separate intake staff, attorneys, marketers, referral staff, administrators, and integration accounts?
- ?Can the firm see original submissions, changes, AI-generated content, approvals, delivery failures, automation runs, and exports in an audit history?
- ?How are duplicates, conflicts, urgency flags, opt-outs, wrong numbers, missing consent, and after-hours inquiries handled?
- ?Can automation pause for attorney review without losing the owner, next action, response target, or source evidence?
Connection and exit
- ?Is each connector one-way or two-way, real-time or queued, and which fields, files, notes, calls, tasks, payments, relationships, and IDs cross?
- ?What acknowledgement, retry, duplicate prevention, reconciliation report, and support escalation exists when the receiving system rejects data?
- ?Who owns every field after conversion, and what happens when intake staff correct a record after the Filevine project opens?
- ?Can the firm export leads, custom fields, activities, messages, source data, documents, signatures, audit history, and identifiers in usable formats without vendor services?
Migration and handoff controls
Preserve the record, prove acceptance, plan the exit
Inventory before mapping
Count lead records, contacts, custom fields, statuses, sub-statuses, sources, referrals, notes, tasks, messages, calls, forms, signatures, files, and disposition history. Do not call a contacts-only import a complete migration.
Write field authority
For identity, consent, incident facts, source, assigned staff, conflict status, engagement, documents, and matter ID, state which system can originate, update, and correct the value before and after handoff.
Preserve provenance
Keep the original submission, source/campaign values, timestamps, author, correction history, file names, and external IDs. A polished summary is not a substitute for the source record.
Map Filevine deliberately
Choose the receiving organization, project type, sections, contact roles, custom fields, document folders, activity destinations, tasks, and team roles. Test incompatible types and intentionally unmapped fields.
Define accepted handoff
Require a downstream project ID, accepted timestamp, receiving owner, required objects, and visible exception state. “Sent,” “converted,” or “automation completed” is insufficient by itself.
Reconcile every batch
Compare source counts, destination counts, rejected rows, duplicates, missing files, field-level samples, and aggregate totals. Keep a signed exception register and a rollback or repair decision.
Secure the integration identity
Use the least privilege that actually works, document token ownership and rotation, restrict administrators, and verify that offboarding a user does not silently break the connector.
Plan the exit before launch
Obtain a sample full export, file archive, schema/data dictionary, identifiers, deletion process, retention timeline, and priced assistance before signing—not after notice of termination.
Professional-responsibility context
Intake software does not make the professional decision
ABA Model Rule 1.18 and its comments explain that a person may become a prospective client through communications about possible representation, that information learned can carry duties even when no engagement follows, and that initial collection should be limited to what is reasonably necessary. Firms must apply the rules in their own jurisdictions.
ABA Formal Opinion 512 identifies competence, confidentiality, communication, supervision, candor, and reasonable fees among the duties implicated by lawyers’ use of generative AI. In procurement, that means understanding what the tool reads, checking outputs, controlling disclosures, supervising automated work, and preserving a human review path.
Transparent alternative: ClaimVela
Consider ClaimVela only if its narrower boundaries fit
ClaimVela authored this comparison and sells competing PI intake software. It should therefore be evaluated with the same fictional scenario, cost model, security review, export test, and handoff proof as Lawmatics and Lead Docket—not treated as a neutral recommendation embedded in the article.
ClaimVela is positioned around structured PI inquiry capture, response ownership, firm-configured follow-up, fact and document collection, attorney-controlled review, consultation and engagement coordination, a practical retained-case workspace, and deliberate handoff. Firms needing a large marketing-automation suite, a mature Filevine-native ecosystem, or broad practice-management depth may prefer one of the compared vendors or a different product.
ClaimVela’s explicit current limitations
ClaimVela does not claim SOC 2 certification, HIPAA compliance, a full case-management replacement, rules-based legal deadline calculation, billing or trust accounting, native telephony, or universal integrations. It does not clear conflicts, determine case merit or value, calculate legal deadlines, give legal or medical advice, or accept or reject representation. AI-assisted output requires human review. Confirm the current security and integration scope before using regulated, contractually restricted, or live client data.
Disclosure last verified October 22, 2026. Product boundaries can change; the linked pages should be treated as the current ClaimVela source of truth.
Scope and limitations
What this comparison can—and cannot—establish
This is an operational comparison, not legal advice, a security assessment, a contract interpretation, or a recommendation for every firm.
Only publicly accessible official vendor and ABA sources were used for product and ethics facts. Private proposals, customer-specific configurations, implementation partners, uptime history, support quality, and negotiated terms were not independently tested.
Feature names do not prove inclusion. Availability can depend on plan, purchase date, user count, geography, message registration, another Filevine or Lawmatics product, configuration, usage allowance, or a signed amendment.
A release note proves that a capability shipped in some form; it does not prove that it is enabled, suitable, or included for a particular organization.
Security, privacy, residency, retention, model-training, subprocessors, backups, incident response, and regulated-data commitments must be reviewed in the current contract and assurance materials.
ABA Model Rules and opinions are general professional-responsibility context. Firms must use the rules, opinions, laws, court requirements, and bar guidance that apply in their jurisdictions.
Official source register
Re-open the evidence before the contract is signed
Every product fact on this page is tied to a vendor-controlled source. Pages can change after publication, so save the version relied on during procurement and make disputed entitlements part of the order form.
Lawmatics
- Lawmatics pricing and plan comparison
- Lawmatics integration marketplace
- Lawmatics: Filevine integration
- Lawmatics: Merlin pricing
- Lawmatics: Merlin Qualify overview
- Lawmatics: Merlin Engage overview
- Lawmatics: Merlin Copilot and seat pricing
- Lawmatics: Q3 2026 product updates
- Lawmatics: Merlin AI Suite overview
Verified October 22, 2026.
Lead Docket / Filevine
- Filevine pricing and Intake package
- Filevine: Lead Docket intake and lead tracking
- Filevine product specifications
- Filevine: Lead Docket forms and automation release
- Filevine: June 2026 release notes
- Filevine: July 2026 release notes
- Filevine: October 2026 release notes
- Filevine: Lead Docket AI status update
Verified October 22, 2026.
Professional responsibility
Verified October 22, 2026.
Frequently asked questions
Lawmatics and Lead Docket for PI intake
Is Lawmatics or Lead Docket better for a personal injury firm?
Neither is universally better. Lawmatics may fit a CRM-led growth stack that values broad marketing automation and multiple case-management integrations. Lead Docket may fit a Filevine-centered PI operating model that values a tightly documented intake-to-Filevine path. The right answer is the product that passes the firm’s fictional-data workflow, handoff, permission, export, and cost tests.
How much do Lawmatics and Lead Docket cost?
Both base products use custom quote pricing on their current official pages. Lawmatics separately publishes Merlin AI Outcome plans from $149/month for 50 outcomes through $1,999/month for 2,000 outcomes, plus overages, and publishes Copilot seat prices in its help center. Filevine publishes selected Lead Docket usage and overage terms but not the base subscription total. Obtain a complete written cost model for the exact configuration.
Is Lawmatics Merlin included in the base plan?
Lawmatics presents Merlin AI capabilities as add-ons for an additional fee. Qualify and Engage use outcome-based pricing. Copilot documentation lists separate Lite and Pro seat prices. Because Lawmatics pages currently contain inconsistent availability wording for Copilot, confirm the entitlement and production status in the order form.
Does Lead Docket include AI?
Current Filevine specifications say LeadsAI is included with Lead Docket, with an exception for subscriptions purchased before January 1, 2026 unless the customer bought Lead Docket Pro or LeadsAI separately. Dated release notes document Ask LOIS, call-transcript access, OCR, and document summaries. Lead Viability was still described as coming soon in August 2026, so it should not be treated as a current requirement without newer written proof.
Is the Lawmatics–Filevine integration two-way?
No. Lawmatics’ current help article expressly describes the Filevine integration as one-way from Lawmatics to Filevine. It documents conversion, manual or automated sync, resync, and optional transfer of documents, notes, and related contacts, but says Filevine data does not flow back to Lawmatics.
Does either intake CRM replace Filevine case management?
Not on the evidence reviewed here. Lawmatics and Lead Docket are evaluated as intake and CRM systems. Filevine matter management is separately packaged. A firm should prove its requirements for litigation, legal calendaring, document management, client communication, billing, trust accounting, and settlement operations rather than assuming an intake feature list replaces the retained-matter system.
How should a PI firm evaluate AI lead qualification?
Use fictional matters with known expected outcomes, missing facts, contradictory documents, duplicate parties, and edge cases. Inspect what sources the tool can and cannot read, its reasoning, confidence, usage charge, audit trail, override path, and failure state. Keep conflicts, deadlines, legal analysis, case acceptance, and representation decisions with authorized people.
What is the safest way to test the Filevine handoff?
Use a sandbox or approved test organization and plainly fictional data. Transfer the same mapped record, files, notes, contact roles, open work, and owner; then simulate an outage, duplicate, rejected file, and post-handoff correction. Require a Filevine project ID and visible acceptance or exception state before calling the handoff complete.
Related resources
Continue the intake-system review
Architecture
PI CRM vs. case management
Assign lifecycle ownership and test the retained-matter handoff.
Workflow
PI intake automation guide
Automate operational work while preserving human decision gates.
Implementation
Integrations and migration
Review connector direction, data scope, migration boundaries, and exports.
Keep the test vendor-neutral
Bring the same fictional PI inquiry to every finalist.
Require current production behavior, a complete order form, and exported proof of ordinary and failed paths. If ClaimVela remains on the shortlist, hold it to exactly the same standard.