The leak happens between the web form and the engagement letter
When you choose or replace a law firm CRM, the best-looking dashboard isn't the thing to judge. Judge whether the system can move a prospect from first contact to a cleared conflict to a booked consultation. Nobody should have to retype data, lose a consent record or guess where the lead came from along the way.
Most lost prospects aren't lost in the consultation. They're lost before it. The callback comes the next afternoon. The conflict check stalls while a paralegal waits on an email. The intake form wants a full matter summary typed on a phone screen. By the time the firm is ready, the prospect has signed with whoever answered first.
The eight red flags below are the gaps that most often separate intake software that works from intake software that just looks good in a demo. Each comes with what to insist on instead. They apply to a 12-lawyer firm in Manchester, a 200-lawyer firm in Mumbai and a regional practice in São Paulo alike. In-house teams that use intake tools to triage internal requests can skip the marketing points. The conflicts and privacy sections still apply to them.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Conflict checks that start after the prospect has told you everything
Red flag: the conflict check is a manual handoff
Ask the vendor to show you exactly what happens when a new inquiry arrives. If the answer is "intake staff export the names and email them to conflicts" or "you can download a CSV," you've found the most expensive gap in the process. Manual handoffs add hours or days. They also invite a worse problem: the firm keeps collecting detailed facts from a prospect it may not be able to represent.
In many jurisdictions, information from a prospective client creates duties of its own, and those duties can get in the way of other matters. ABA Model Rule 1.18 is the best-known example in the US. Professional conduct rules in the UK, India and elsewhere raise similar confidentiality concerns, though the details differ.
What to do instead: require a native or API-based conflict check integration. It should send the prospect, adverse parties and related entities to your conflicts system as soon as limited intake is complete. The result should come back to the intake record as a status (clear, potential hit, needs review), not as an attachment. Until that status arrives, collect only names and a one-line matter description. Intapp's intake and conflicts products, and several practice management suites with built-in conflict search, support versions of this workflow. How far each one goes varies, so test it with your own data during the trial.
Red flag: the CRM can't tell that two records are the same party
"Mohammed Al-Rashid," "Mohamed Alrashid" and "M. Al Rashid" are three records in a weak system and one person in reality. The same goes for a subsidiary that trades under a different name from its parent. Exact-match search misses these. A missed match is a conflict you only discover after engagement.
What to do instead: ask for fuzzy matching and corporate-family linking. If your client base needs it, ask for transliteration handling for non-Latin scripts too. Bring ten real near-duplicate names from your own files to the demo and watch what the search returns.
Consent capture that wouldn't survive a regulator's question
Red flag: one checkbox covers everything
A single "I agree to the privacy policy" box that also signs the prospect up for newsletters fails on several counts. Under the EU and UK GDPR, consent must be specific, informed and unambiguous, and you must be able to show it was given. Bundling marketing consent with a service inquiry undermines all of that.
India's Digital Personal Data Protection Act, 2023 sets a high bar as well. It requires a notice describing the data collected and why, consent that is free, specific and unconditional, and a way to withdraw consent that is as easy as giving it. Its implementing rules were notified in 2025, and most obligations phase in over a transition period. Check the current commencement dates with counsel. Brazil's LGPD, South Africa's POPIA, Singapore's PDPA and the UAE's federal PDPL each add their own requirements. Electronic marketing rules, such as the EU ePrivacy regime and the UK's PECR, apply on top of these laws.
Consent also isn't always the right legal basis for handling an inquiry. Under GDPR, firms often answer requests on the basis of steps taken before a contract, or legitimate interests. Marketing is where consent usually comes in. A good system records which basis applies to which purpose.
What to do instead: require a separate, unticked consent field for each purpose. Each consent should be stored with a timestamp, the exact wording shown, the form version and the channel. Prospects should be able to withdraw on their own, and withdrawal should update the record automatically. Have your privacy counsel or data protection officer approve the notice wording for every jurisdiction you take inquiries from.
Red flag: nobody knows where intake data lives or when it's deleted
Prospects who never become clients still leave sensitive facts behind. Ask the vendor:
- Where is the data hosted, and which regions can you choose (for example the EU, UK, India, Australia or the Middle East)?
- Are sub-processors published?
- Can you set automatic retention rules for inquiries that were declined or didn't show up?
A vague answer to any of these is a reason to walk away.
Lead-source data nobody in the partner meeting trusts
Red flag: attribution is a free-text field staff fill in later
When staff type the source by hand after the call, the same report ends up with "Google," "google ads," "internet" and "referral – maybe Priya?" Partners stop believing the numbers, and legal marketing software budgets go to whoever argues loudest. Most systems also stop tracking once the inquiry arrives, so nobody can see which channels produce matters that actually pay.
What to do instead: capture the source in layers and tie it to outcomes. A workable minimum:
| Field | Populated by | Why it matters |
|---|---|---|
| First-touch channel | Automatically, from tracking parameters or a call-tracking number | Shows which channels start relationships |
| Self-reported source | The prospect, from a locked picklist | Catches word-of-mouth and offline referrals that tracking misses |
| Referrer name | Intake staff, linked to an existing contact record | Lets you thank and track referral partners properly |
| Matter opened (yes/no) and practice area | Sync from the practice management system | Separates inquiries from actual work |
| Fees billed in the first 12 months | Sync from billing | Turns cost per lead into cost per profitable matter |
Hypothetical example: a 25-lawyer firm spends USD 4,000 a month on paid search and gets 60 inquiries. That works out to about USD 67 per lead, which looks cheap. Now say only four become matters. The cost is USD 1,000 per matter opened. If two of those four are low-fee, it's USD 2,000 per matter worth having. The marketing budget discussion should start from that number, not the cost per lead.
Looking to streamline vendor RFP selection?
Access pre-negotiated tier discounts through our independent institutional network.
Routing and forms built for the firm's convenience, not the prospect's
Red flag: no response-time rules or routing
If every inquiry lands in one shared inbox, response speed depends on who happens to be at their desk. Prospects with urgent matters, such as a dismissal, a detention or a regulatory deadline, tend to contact several firms and hire the first one that gives a credible reply.
What to do instead: look for client intake software for law firms that routes inquiries by practice area, language and office. It should start a response clock and escalate when a target is missed. One business hour for a reply from a person is a reasonable target. If you take cross-border work, it has to handle time zones correctly. An instant automated acknowledgment helps, but only if it's honest about when a person will respond.
Red flag: the intake form asks for everything up front
A 30-field form with a required matter narrative shows how the firm likes to work. It tells you very little about the prospect. Fewer people finish long forms, especially on mobile. Long narratives also bring back the over-collection problem from the conflicts section.
What to do instead: keep the first stage short: name, contact details, practice area, other parties, and preferred language and contact method. Collect the detail in a second stage once conflicts clear. If you serve Arabic or Hebrew speakers, check that forms display right-to-left scripts properly. Also check that the e-signature step for engagement letters supports the signature methods recognized where your clients are, because e-signature rules differ by country and by type of document.
Pricing and contract terms that make every fix expensive
Red flag: the integrations you need are add-ons, or can't be bought at all
The demo showed conflicts integration, two-way practice management sync and a choice of data region. The quote includes none of them. Or the vendor only exports data in a format your next system can't read. Either way, the problems above become permanent because fixing them costs too much.
Below are typical 2026 market ranges. They vary by contract, region and firm size, and local pricing often differs, so confirm current figures with each vendor.
| Segment | Examples | Indicative cost | Watch for |
|---|---|---|---|
| Small-firm intake and CRM | Clio Grow, Lawmatics, intake features in suites such as LEAP, Smokeball or Actionstep | Roughly USD 50–150 per user per month; some vendors sell flat or bundled plans instead | Caps on contacts, automations or e-signature envelopes |
| Mid-size, configurable platforms | Litify, or Salesforce or HubSpot with a legal configuration | Roughly USD 100–300 per user per month, plus implementation that can run from the low five figures to the high five figures | Setup that depends on a partner, and ongoing admin cost |
| Large-firm and enterprise | Intapp Intake and DealCloud, LexisNexis InterAction | Usually custom quotes, often tens of thousands to several hundred thousand USD a year | Multi-year terms and separately priced modules |
What to do instead: make the quote list every integration, data region and automation limit you saw in the demo. Negotiate a documented export that includes full records and consent history, plus a cap on renewal price increases. Vendors expect to negotiate both, and both get much harder to win after you've migrated.
A two-week check before you sign or renew
- Days 1–3: Map your current intake from first contact to signed engagement letter. Time each handoff on five recent inquiries.
- Days 4–7: Run those five scenarios in each shortlisted system. Include one cross-border prospect and one near-duplicate party name.
- Days 8–10: Have privacy counsel review consent wording, hosting region and retention settings for every jurisdiction you take inquiries from.
- Days 11–14: Get written confirmation that conflicts integration, attribution fields and data export are included in the quoted price.
The decision rule: if a system can't send a new inquiry to conflicts and return a status to the intake record without a manual export, don't buy it, however good its marketing features are. You can fix every other red flag on this list through configuration or negotiation. This one shapes the whole workflow.