A new matter arrives as a form submission, a voicemail, or a referral email with a scanned document attached. Building the form is rarely the hard part. The hard part starts ninety seconds later, when somebody has to decide who is looking at this one, whether the firm can take it, and what the person who sent it hears back. Most firms shopping for client intake software are not short of ways to collect answers. They are short of a place where the answers sit with an owner, a status, and a record of what was said before anyone decided.
That distinction matters because the pages ranking for this search mostly describe the same bundle: forms, e-signature, document assembly, a pipeline, automated follow-up. What they rarely separate is which part of that bundle solves a legal problem and which part solves a clerical one. The clerical part is available cheaply and from many directions. The legal part is not.
The part of intake that software is actually for
Intake fails in a small number of recognisable ways, and none of them are form design.
The first is ownership. A submission lands in a shared mailbox that three people can see, which in practice means nobody is responsible for it. Everyone assumes the person who usually handles new enquiries has it. That person is at a deposition.
The second is status. A paralegal knows a matter is waiting on a medical record, an associate knows a conflict check has not come back, and neither fact is written anywhere a third person can read. Status lives in memory, so it evaporates when anyone is out.
The third is the decline. Firms are usually careful about matters they accept and careless about the ones they turn away. The declined enquiry generates no file, no note, and no searchable record, which is precisely the enquiry most likely to reappear eighteen months later on the other side of a dispute.
The fourth is the reply. The prospective client gets no acknowledgement, or gets two, or gets one that promises a call that nobody has scheduled. Every one of those is a trust problem before it is an efficiency problem.
Notice that all four sit after the submission. A form tool that stops at collection leaves all four in place. That is the shape of the problem, and it is the right lens for reading any product page in this category.
Three different products sell under one phrase
"Client intake software for law firms" is used to describe at least three kinds of purchase. They are not interchangeable, and confusing them is how firms end up paying twice.
| What it is | What it gives you | What stays manual | How it tends to be priced |
|---|---|---|---|
| Legal intake and CRM platforms built for firms | Intake forms, a lead pipeline, conflict checking against the firm's own records, document assembly, e-signature, drip follow-up | Deciding the matter, drafting the substance, the phone call | Per user, often quote only |
| Staffed intake and answering services | A human answering the phone at 2am, qualifying to a script, handing over a summary | Everything after the handover | Per call or per minute, plus a monthly base |
| General form tools with response management | The form, an owner and a status on each response, a reply sent from the same screen, an export | Conflict database, document assembly, trust accounting | Per user, published |
The pricing column is worth checking yourself rather than taking from a comparison article. As of this writing, Gavel publishes its tiers with prices directly on its pricing page. Lawmatics publishes no plan price at all and asks visitors to book a personalised demo. Neither approach is wrong, but they produce very different buying processes. A published price can be compared in an afternoon. A quote-only price means a sales cycle, a discovery call, and a number that depends on who is asking.
Staffed services deserve a separate line because they solve a problem software cannot. If matters arrive by phone at midnight and the firm competes on being the one that answers, no form fixes that. What a staffed service does not give is a durable internal record with an owner, which is why firms that use one still need somewhere for the handover to land.
The duty starts before the engagement letter
This is the part general business software is not built to respect, and it is the strongest argument for treating intake records as regulated records rather than marketing leads.
Under California's Rule of Professional Conduct 1.18, a prospective client is a person who consults a lawyer for the purpose of retaining the lawyer or securing legal service or advice. Paragraph (b) is the one that changes how intake data should be stored: even when no lawyer-client relationship ensues, a lawyer who has communicated with a prospective client must not use or reveal the protected information learned as a result of the consultation. Paragraph (c) goes further and bars representing a client with materially adverse interests in the same or a substantially related matter when material protected information was received. Other states word their versions differently, so the firm's own jurisdiction is the one that governs, but the structure is widely shared.
Three practical consequences follow.
The conflict check has to happen before the substantive conversation, not after. An intake process that collects a detailed description of the dispute and then checks for conflicts has already created the problem it was trying to avoid.
Declined enquiries have to stay searchable. If the only record of a consultation is a deleted email thread, the firm cannot later demonstrate what it knew or when. Retention is a decision to make deliberately, not a side effect of whatever the software does by default.
Access has to be limited by role. Intake data is not general staff-wide material, and a system where everyone sees everything is a poor fit. Look for view-only roles and per-workspace separation rather than a single shared inbox.
Phone intake and web intake have to land in the same place
Most firms have two front doors and one of them is a telephone. The web form produces structured answers. The call produces a handwritten note, a voicemail, or a summary typed by an answering service. Intake software that only knows about the web door quietly creates a second queue, and the second queue is the one that gets forgotten.
The practical fix is unglamorous: whoever takes the call opens the same intake form and fills it in on the caller's behalf. That sounds like duplicated effort and it is, by about two minutes. What it buys is one list, with one set of owners and statuses, and a single answer to the question of what is outstanding. A firm running two lists cannot answer that question at all, because the answer requires somebody to merge them in their head.
Referrals are the third door and behave the same way. A referral arriving as an email from a colleague has no structure, no owner and no status until somebody creates one. Firms that handle referrals well usually have a rule that the referring email gets converted into an intake record on the day it arrives, even when the matter is obviously being taken.
Two details make this workable. The form has to be fast to complete by staff rather than by the client, which usually means a short internal version with the fields a caller can supply. And the record has to accept internal fields that the client never sees, such as which partner was asked for, the source of the referral, and whether the conflict check has cleared.
What a general form tool covers, and what it does not
Firms with a simple practice mix often find that the expensive part of a legal platform is the part they do not use. It is worth being blunt about the line.
| Requirement | Form tool with response management | Legal intake platform |
|---|---|---|
| Intake form with document upload | Yes | Yes |
| Owner and status on every submission | Yes | Yes |
| Reply sent from the same screen, kept on the record | Yes | Yes |
| History of stage changes, notes and emails | Yes | Yes |
| Conflict check against the firm's matter database | No | Yes |
| Retainer assembly and e-signature | No | Usually |
| Trust accounting and billing | No | Often |
| Court deadline calendaring | No | Sometimes |
| Breach timers against a response target | No | Sometimes |
The honest reading of that table is that a form tool with response management is a good fit when intake is a coordination problem and a poor fit when it is a document-production problem. A firm that needs a retainer generated, signed and filed without human retyping should buy the platform built for that. A firm whose real pain is that eleven enquiries are sitting somewhere with nobody's name on them is about to pay several thousand a year for document assembly it will not switch on. The features list of any candidate is worth reading with that split in mind, and the use cases page usually reveals what a vendor actually optimises for.
Pricing models decide more than feature lists
Two pricing shapes dominate this category, and they fail in opposite directions.
Per-lead or per-matter pricing looks attractive to a small firm because the first month is cheap. It becomes unpredictable exactly when the firm succeeds. A single advertising campaign, a referral spike, or a mass tort filing multiplies volume, and the bill follows. Worse, it creates a quiet incentive to keep enquiries out of the system, which destroys the record the firm needs most.
Per-user pricing is predictable and has the opposite failure mode: it charges for the receptionist who logs in twice a week. That is usually the cheaper mistake, because the number of people at the firm changes slowly and is known in advance.
A third variable hides inside both. Ask what happens to stored responses and uploaded documents when the subscription ends, and ask for the export format in writing. A CSV export of every response, with uploaded files retrievable, is the difference between changing vendors and starting over. Check the pricing page of any candidate for a published number and a stated response limit, and treat a quote-only route as a signal about the sales process rather than about quality.
Five questions that separate the candidates
Ask these before a demo, because the answers are usually in writing already.
Does every submission carry an owner and a status that a second person can read without asking? If the answer involves assigning a tag by hand after the fact, that is a workaround.
Can the reply be sent from inside the record, with the sent message kept on the record? A tool that pushes replies into a personal mailbox loses the thread the moment somebody replies from their phone.
Is there a history of who changed what and when? For declined enquiries, that history is the audit trail.
Are there roles below full administrator? A view-only role for a bookkeeper or a contract paralegal is not a luxury in a system holding prospective client information.
What is the export, and is it self-serve? Vendor lock-in in this category is measured in months of retyping.
What to change first
Pick the single form that produces the most enquiries and give every response an owner and a status this week, before evaluating anything else. If that alone clears the backlog, the firm has a coordination problem and a general tool will hold it, which Halict shows on a live example; if the pain that remains is retainers and signatures, buy the legal platform and stop comparing.
Q1. Is a general form tool enough for a small law firm, or is a legal-specific platform necessary?
It depends on which part of intake hurts. If enquiries are getting lost because nobody owns them, a form tool with owners, statuses and a reply screen solves that directly. If the bottleneck is producing a retainer, collecting a signature and syncing to billing, a platform built for firms will pay for itself faster.
Q2. When in the intake process should a conflict check happen?
Before any substantive discussion of the matter, not after the form is reviewed. Under rules modelled on Rule 1.18, protected information learned during a consultation restricts the firm even when no representation follows, so collecting a detailed account first and checking later creates the exact exposure the check exists to prevent.
Q3. Do declined enquiries need to be kept?
Keeping them is usually the safer choice, because a searchable record of what was disclosed and when is what allows the firm to answer a later conflict question. Set an explicit retention period and access rules rather than letting deletion happen by accident, and check the requirements in the firm's own jurisdiction.
Q4. Why do so many legal intake vendors not publish prices?
Most of them sell through a demo and quote for a per-user figure that varies by firm size, practice area and contract length. That is a sales model rather than a quality signal, but it does mean a fair comparison takes calls. Vendors that publish a number can be compared the same afternoon.
Q5. What is the single most useful thing to measure about intake?
The age of the oldest enquiry that has had no reply. Average response time hides the case that has been sitting for nine days, and that case is the one that damages the firm's reputation and, in the worst instance, its position.