Client intake software for law firms - SMB guide

Client intake software for law firms handles four compliance-bound steps: conflict checks, engagement letter signing, identity verification, and secure document collection. Most small and mid-size firms can run all four for $40-150 per month. They do not need the $5,000+ annual enterprise platforms aimed at AmLaw firms, provided they understand which intake steps are genuinely regulated and which are just operational habit.

I am writing this for solo practitioners and 2-20 attorney shops who have outgrown the email-plus-DocuSign-plus-shared-drive setup but balked at the price tag on Litify or top-tier Lawmatics plans. The middle ground exists. You just need to know which corners of intake to solve with general-purpose SaaS and which corners need a legal-specific tool.

What law firm intake actually requires

The ABA Model Rules and your state bar's rules of professional conduct govern what intake must accomplish. Most of the rest is firm-by-firm preference.

The non-negotiables for nearly every U.S. firm:

1. Conflict check before the engagement starts. ABA Model Rule 1.7 covers concurrent conflicts; Rule 1.18 protects prospective clients whose information you collected even if you never took the case. The check has to happen before you receive confidential information from a new matter.
2. A written engagement letter. Required by Rule 1.5(b) when you have not previously represented the client, and required in writing for contingent fees under Rule 1.5(c). Most state bars now treat written engagement letters as the standard for all matters, not a courtesy.
3. Identity verification appropriate to the matter. For most U.S. firms this is light: enough to know who you are representing. For firms in regulated practice areas, including immigration, real estate closings covered by FinCEN's residential transfer reporting rule, or non-U.S. firms subject to AML regulations, it gets heavier. UK firms under the SRA face full Client Due Diligence requirements.
4. Trust accounting separation. Retainer funds belong in an IOLTA or equivalent trust account, not your operating account. Your intake software does not need to manage the trust account itself, but it should connect cleanly to whatever does (LawPay, Clio Payments, your bank).
5. A confidentiality-appropriate channel for documents. Email attachments are not categorically prohibited, but multiple state bars (California's Formal Opinion 2010-179, for example) have advised that attorneys consider encryption based on the sensitivity of the matter.

Everything else (branded portals, automated welcome sequences, intake CRMs that score leads) is operational, not regulatory. You can run a compliant intake process from a notebook if you want. The question is whether you should.

The build-vs-buy decision: where you actually need a legal tool

Most articles in this space conflate "law firm intake software" with "law firm practice management software" and recommend Clio, MyCase, or PracticePanther. Those are case management systems that happen to include intake features. They are not the cheapest or simplest way to handle intake alone.

Here is the honest breakdown of which intake steps require legal-specific tooling and which do not:

The pattern: you need legal-specific tools for trust accounting, KYC where required, and integration into case management. Everything else is solved by general-purpose SaaS.

For the underlying form mechanics that apply to any vertical, see the client intake form guide.

Engagement letters and e-signature

The federal ESIGN Act of 2000 and the Uniform Electronic Transactions Act (adopted by 49 states; New York adopted the similar ESRA) make electronic signatures on engagement letters legally enforceable in all U.S. jurisdictions for the kinds of contracts law firms typically use. There is no "lawyer-only" e-signature standard. DocuSign and Dropbox Sign are used for engagement letters every day.

What you actually need to get right in the engagement letter itself:

• Scope of representation (what you are and are not doing)
• Fee structure with specific dollar amounts or rate schedules
• Trust account handling for retainers
• Costs and disbursements policy
• Termination conditions
• Conflict-of-interest disclosure and waiver if applicable
• For contingency cases, the contingency percentage and how costs are deducted

These are content requirements set by your state bar. The tool you sign them in is your choice. I would not pay extra for a "legal e-signature" product; it does the same thing as DocuSign at a markup.

The one feature worth paying for is template-based document generation that lets non-attorney staff send the correct engagement letter for the correct matter type without rewriting it each time. Clio Grow, Lawmatics, and most modern intake platforms offer this. Documate (now Gavel) handles more complex document assembly if your engagement terms vary heavily by matter.

Conflict checks: the step that resists automation

This is where small-firm intake usually breaks down. A conflict check is not a feature you can buy off the shelf. It is a search across every party you have ever represented or been adverse to, plus their related entities, opposing counsel, witnesses, and anyone whose interest could create a positional conflict.

For solo practitioners with fewer than 100 historical matters, a maintained spreadsheet with party names, related entities, and matter status meets the standard. Search it before opening any new file. Document that you did the search.

Above 100 matters or with multiple attorneys, you want:

• A central client and party database that everyone updates when a matter opens or closes
• Searchable by name, alias, related entity, and matter
• A logged search result attached to each new matter file

Most case management systems (Clio Manage, MyCase, PracticePanther, Smokeball) include this. If you are running intake through a separate tool, you still need the conflict check to happen against your case management system's party database. The intake tool collects the prospective client's information; the case management system checks it. Get the integration working before you take on volume.

ID verification, AML/KYC, and trust accounting

ID verification for most U.S. law firms means seeing a driver's license or passport and matching it to the person sitting across the table or on the Zoom call. A request through an encrypted intake form is sufficient. Content Snare, Clio Grow, and most encrypted intake tools can collect ID documents with encryption at rest.

ID verification becomes a regulated process when:

• You are a UK or EU firm subject to AML regulations
• You are handling residential real estate transfers in a U.S. jurisdiction covered by FinCEN's residential beneficial ownership reporting rule
• Your matter involves anti-money-laundering checks for compliance reasons

For these, you want a dedicated KYC vendor: Persona, Veriff, Jumio, or Onfido. These verify the document itself (is the ID real?) and run biometric matching (does the face match the ID?). A general intake tool that collects a JPG of a driver's license does not satisfy AML requirements.

For retainer collection, LawPay and Clio Payments handle IOLTA segregation automatically. Stripe and Square will accept payment but require you to manually route trust funds to the correct account, which is where most bar grievance complaints originate. The $20-40 per month for LawPay is cheap insurance.

Three intake stacks by budget

Here are the stacks I would actually recommend at three budget points for a U.S. firm in a non-AML practice area. Prices are monthly per firm unless noted as per-user.

Two notes on the table. First, the per-user pricing for Clio Grow and Lawmatics is approximate and changes with tier and contract length. At solo or small-firm volume you are paying for client-facing CRM features (lead scoring, email sequences, marketing automation) that small firms rarely use. Second, the lean stack is not a step down in compliance; every step still meets the ABA Model Rules. It is a step down in convenience.

For a practical look at the same problem in adjacent verticals, client portals for financial advisors and client portals for accountants handle similar trade-offs in regulated industries.

A practical 10-step intake sequence

The sequence below is what I would set up for a 1-5 attorney firm running on the mid-tier stack. Adapt the tool names to whatever stack you actually run.

1. Inquiry capture. Prospective client fills out a web form on your site. Capture: name, contact, matter type, opposing parties, jurisdiction, and a free-text description. Tag the matter type so it routes to the right attorney.
2. Conflict check. Run the prospective client's name and any disclosed opposing parties against your case management system's party database. Log the search result with a date and the name of whoever ran it.
3. Intake call scheduling. If no conflict surfaces, send a Calendly or Cal.com link. Block 30 minutes.
4. Initial consultation. Discuss scope, fee structure, and likely engagement terms. Take notes that map to the engagement letter template you will send.
5. Engagement letter generation. Pull the right template, fill in the client name, scope, fee, and any matter-specific terms. Send for e-signature.
6. Retainer collection. Once the engagement letter is signed, send a LawPay payment request for the retainer. Funds route to the IOLTA. Send the receipt and a trust account ledger entry.
7. ID and document request. Send an intake form for the documents you need: ID, prior counsel records, contracts, correspondence, and anything matter-specific. Use an encrypted portal, not email.
8. Matter creation. Once intake documents are returned, open the matter in your case management system and link the intake record.
9. Welcome and next-steps email. Tell the client what to expect: who is on the matter, how to reach you, expected timelines, and how to use the portal for ongoing document exchange.
10. Internal handoff. Notify the attorney and paralegal that the matter is active. Schedule the first work task.

A general client onboarding checklist covers the structural pieces of any service-business onboarding without the legal-specific compliance layer if you want to compare.

When to pay for a legal-specific intake platform

Three signals tell you that you have outgrown a general-purpose intake stack:

• Volume. Above roughly 200 inquiries per month, manual routing and conflict-checking starts to bottleneck a single intake coordinator. Tools like Lawmatics, Clio Grow, and Captorra exist because they automate the routing, status tracking, and reporting at that volume.
• Multi-attorney conflict surface. Once you have more than five attorneys taking unrelated matters, a spreadsheet conflict log is no longer defensible. You need a real database with role-based access.
• Marketing intake. If a meaningful share of your matters come from paid ads or referral partners that need attribution tracking, the marketing-CRM features in Lawmatics or Clio Grow start to pay for themselves.

If none of the three applies, paying $100+ per user per month for a legal-specific intake CRM is hard to justify. Content Snare or a self-built combination of Typeform, DocuSign, and LawPay will run a compliant intake at one-third the cost.

A note on the tool behind this blog: it sits in the middle tier above. Its e-signature support handles engagement letters, and its encrypted document storage covers the document-collection step in one workflow, which is two of the four compliance-bound intake steps. It does not handle KYC verification or trust accounting; for those you still need a dedicated tool. That limitation applies to every general-purpose intake platform, not just Portico.

A note on what counts as "compliance" in legal intake

Most of what gets sold as "law firm compliance" is operational hygiene with a compliance label. A branded portal is not required by any rule. Lead routing is not required by any rule. Automated welcome sequences are not required by any rule. These are useful operational features that individual firms benefit from, but they are sold as compliance because compliance commands higher prices than convenience.

The actual compliance surface in intake is narrow:

• Conflict check before receiving confidential information (Rule 1.18)
• Written engagement letter with required content (Rule 1.5)
• Trust account segregation for retainers (state IOLTA rules)
• Document confidentiality appropriate to the matter (state confidentiality rules; sometimes encryption advisories)
• Where applicable, AML/KYC and FinCEN-specific verification

A stack that covers those five points compliantly is enough. Anything beyond is a productivity decision, not a regulatory one. Knowing the difference is what lets a small firm spend $100/month where a peer spends $1,000/month for the same compliance posture.