FirmOps.io
Law Firm OperationsUpdated November 10, 2026• 12 min read

How to Automate Law Firm Intake Without Dropped Balls

A lead with no owner is a dropped ball. Name the owner, connect the handoff, and keep a human on every client-facing send.

J

Jonathan Mahler

Founder, Vertana · Non-attorney founder and Firm Manager, Conduit Law

Reviewed by Jonathan Mahler

#law firm intake automation#intake#case launch#firm brain#approval gates#Clio

One workflow

Request demo

Bring one recurring bottleneck. If it is a good first firm-brain build, the next step is a live demo, not a pitch deck.

Most firms do not have an intake-software problem. They have a lead that nobody owns.

Law firm intake automation should make sure every lead gets captured, owned, followed up, signed, and opened without staff copying the same facts between five systems. I operate the business side of Conduit Law, a Denver personal injury firm operating in four states. I am the founder, and I am not an attorney. We operate the firm so owners can practice. Conduit Law is the proof. The offer is a Managed Firm Brain: read the systems the firm already has, prepare the next step, and stop where a human has to decide.

When I review intake, I am not looking for a cute workflow. I am looking for dropped balls, duplicate entry, and the place a client is waiting while the firm thinks someone else has it. That work sits under law firm operations, not inside a software project. Staff copy-pasting between tabs is an expensive way to open a file.

Key Takeaways

  • Intake breaks at the handoff, not at the form.
  • If the owner is "the team," the lead has no owner.
  • At Conduit, case launch was 47 steps and about 2.5 hours. It is now one click and about 10 minutes, and a person still approves the send.
  • Relay between systems can be connected. Judgment, live calls, and client-facing sends stay human.
  • A boxed intake login will not name your owner. That decision is operating work.
  • Lawyers stay responsible for generative AI they use. I do not hold that duty, and a gate does not transfer it.

Where ownership actually breaks

The break is boring. Someone took the call and wrote the notes. Someone else was supposed to open the matter. The first person thinks they handed it off. The second person never got a named task, so they think they never received it. The client sits in that gap, and the firm thinks someone else has it.

The public version of that gap at Conduit was the welcome email. It went out twice, or not at all, because nobody was sure the matter was open. The team got told by whoever remembered. Oops is not a workflow. That was not a lazy staff problem. The status did not exist, so ownership could not exist either.

A lead can arrive from an ad, a referral, a form, a phone call, a chat, or co-counsel. Notes land in one tool. A CRM update lands in another. A paralegal opens the matter if someone remembers to ask. A document packet goes out. Then the firm still has to know who followed up, who got the signature, who created the folder, and who told the attorney. Miss any one of those and a good lead becomes a rumor.

A completed handoff is seven fields

A completed handoff is a short list, not a feeling. The lead has a source. It has a status that is not "someone has it." It has one owner, a deadline, qualification notes, a next task, and a file location. I check those seven before I care which login holds them. If any one is blank, the firm does not have an intake process. It has a pile of messages.

That list is also how you see staff routing around the tool while the habit is still small. The case system is quiet. The inbox is loud. People answer from memory because the file does not say who owns the next step. Another intake product at that moment adds a tab the team will also ignore. Name the owner on the stack you already pay for. Then connect the relay.

The wait in that old path was not a clever bottleneck. It was two people, each sure the other had the file. Notes existed. A matter did not, or a matter existed and the welcome did not. I do not publish a minute count for that wait. The status was missing, so the clock was not the point. The client was already in the gap. The retype is annoying. The unowned handoff is the dropped ball.

What the 47 steps actually were

When I mapped how a signed client became an open matter at Conduit, the map had 47 steps across six tools that did not talk, and about 2.5 hours of a case manager's day.[2]FirmOps. "Conduit Law case study." The steps were not a Conduit quirk. They are what happens when a file has to be born in tools that do not share a fact.

INTAKE CONTROL LOOP Connect the relay. A person still sends. 1. Capture Form, call, referral, or co-counsel. One record, not five notes. 2. Name one owner If the owner is the team, the lead has no owner. 3. Read the file first Case system, mail, folder, and billing. No send on a guess. 4. Connect the relay Matter, folder, fields, and tasks come from the intake data. 5. Human approves the send Held draft. The person reads it and presses send. Live calls stay with people.
The loop a firm can copy before it buys another intake login. Gold marks the gate.
RelayBeforeAfter
The factDate of loss lives on the intake form. Someone retypes it into the case system. The copies drift the first time one gets corrected.Fields fill from the intake data. One copy.
The matterSomeone remembers to create it, then builds the folder tree, fills the custom fields, and sets the tasks by hand.When the packet is signed, the matter, folder, fields, and tasks are created from that packet.
The signatureThe engagement letter leaves an e-sign tool. The signed copy lands in an inbox. Someone saves it back to the folder.The signed packet is filed where the matter already expects it.
The welcomeSent from memory. Twice, or not at all, because nobody is sure the matter is open.A held draft in the case manager's own drafts. They read it and press send.
The owner"The team," which means nobody.One named person per status. If the name is missing, the path stops.

None of those steps is hard. Every one of them is a place to drop a client. In personal injury, a dropped client calls another firm. Two and a half hours of a good case manager's day went to clerical relay between tabs the firm already paid for.

The rebuild did not add a login. It connected the case system, the mail, the document store, and billing into one layer. When the packet is signed, that layer opens the matter, builds the folder, fills the fields from the intake data instead of from a retyped copy, sets the tasks, files the signed packet, and drafts the welcome. The case manager reads the draft and presses send. Case launch takes about 10 minutes, and most of that is the human reading. The pattern has run across more than 1,500 cases. The parts we can share publicly are in the Conduit Law case study. The longer teardown of the same rebuild is in the case-launch note.

What got cut, and what stayed human

Relay got cut: the retype, the hand-built folder, the second copy of the fields, the inbox-to-folder save, and the welcome written from scratch because nobody trusted the status.

Judgment stayed. The case manager still reads the welcome and presses send. Live calls stay with people. Qualification that needs a person stays with a person. Anything a lawyer has to stand behind stays with the lawyer.

The rule I use is plain. If the step exists only to move a fact between tabs the firm already pays for, connect it. If the step changes what a client hears, what the file says, or what a lawyer is responsible for, a human releases it. That is the same split as read-first on the way in and approval gates on the way out. Read-first AI is the longer version of the inbound rule: if the system cannot see the file, it should not touch the file.

ABA Formal Opinion 512 says a lawyer who uses generative AI has to understand the tool well enough to meet the duty of competence, and stays responsible for the work.[1]American Bar Association. "Formal Opinion 512." I am not an attorney. I do not hold that duty. An approval gate does not move it onto a vendor, and it does not move it onto me. This page is an operating note, not legal advice.

The path has to match how the team already works

The first win is still that handoff, not a new CRM. If the seven fields are blank, automation just moves the mess faster.

If the firm uses Clio, Dropbox, Gmail, Dialpad, DocuSign, DocuSeal, QuickBooks, or another core system, the automation has to respect the way the team already moves. Clio, or whichever case system you run, stays the system of record. We do not replace the stack. If the path fights the work, staff will route around it within a week. You will see a quiet case system and a loud inbox.

The workaround we closed at Conduit was the welcome sent from memory, because the open-matter state was a rumor. The draft now lives in that person's own drafts folder, tied to a matter that is actually open. The failure staff see when a connection is slightly wrong is not a dashboard badge. It is two copies of the same fact. The date of loss on the form does not match the date of loss on the matter. Or the signed packet is in an inbox and not in the folder. Fix the copy. Do not add a tab.

What a subscription cannot decide

A boxed intake product can store a form. It cannot decide which of your steps are the job and which are relay. It cannot decide which sends your lawyer still has to release. It cannot cancel the subscription you no longer need because the relay now happens in the layer you already have. Those are operating decisions. A login does not make them.

FirmOps is not an MSO. It does not employ your staff, take over your operations, or do case management. It builds the firm a Managed Firm Brain on the systems already in use, and we operate that layer so the owners can practice. The firm keeps its case system and its people.

Map the handoff before you touch a login

If you handed me the current intake tomorrow and told me not to touch a login yet, I would not start with a vendor demo. I would write the map.

  1. List every step from lead to open matter. Count them. At Conduit that count was 47.
  2. Put one name on each status. "The team" does not count.
  3. Mark relay separately from judgment. Relay is a candidate to connect. Judgment is not.
  4. Write the release rule. Which drafts a person must send, which questions stay read-only, and which calls never leave a human.

Until that page exists, software has nothing honest to automate. You will buy a happy path, and staff will keep the real path in their inbox.

When this is a bad fit

Skip this if you want a tool that talks to clients on its own, a replacement for your case system, or someone to practice law for you. I do not practice. Phones stay with people. The lawyer stays on the file. If the job is one recurring handoff and you want it run on the stack you already pay for, Request demo. Bring the step count and the list of systems a lead touches before a matter is open.

Questions owners actually ask

What should law firm intake automation do first?

The lead-to-matter handoff. Source, status, one owner, a deadline, notes, a next task, and a file location. If those are not true, a new CRM just gives the mess a login.

How many steps should intake take?

Map yours. At Conduit the case-launch map was 47 steps and about 2.5 hours across six tools. It is now one click and about 10 minutes, and a person still approves the send. Your number will differ. The shape usually does not. Most of the steps are relay between tools you already pay for.

What has to stay human?

Live calls. Qualification that needs a judgment. Any send a client will read. Anything the lawyer has to stand behind. ABA Formal Opinion 512 does not move that duty onto a vendor, or onto a non-attorney operator.

Will staff route around the automation?

Yes, if the path fights how they already work. The tell is a quiet system of record and a loud inbox. Close the gap in the path. A training video will not do it.

Does this replace Clio?

No. Clio, or whatever case system you run, stays the system of record. The firm brain reads it and prepares the next step. It does not become a second case system.

Is FirmOps an MSO or a boxed intake product?

No. FirmOps is not an MSO. It does not employ your staff, take over your operations, or hand you a login and leave. The offer is a Managed Firm Brain on the stack you already have.

Where do we start if we cannot buy software yet?

Write the map. Count the steps, name one owner per status, and mark relay separately from judgment. Do that before any login. If you want a second set of eyes on the map, Request demo and bring the count.

Article Sources

FirmOps cites primary sources on factual claims. Operator notes are not legal advice.

  1. American Bar Association. "Formal Opinion 512." Accessed November 10, 2026. ↩
  2. FirmOps. "Conduit Law case study." Public proof for the 47-step case launch, the 2.5 hour to 10 minute change, and more than 1,500 cases. Accessed November 10, 2026. ↩

Keep moving up the operating system

Get the Managed Firm Brain Notes

Follow the practical path: live workflow builds, CRM-aware automation when the data is ready, and supervised work after approval.

✓

Demo Context

What to watch for in the Managed Firm Brain walkthrough

✓

Live-Lab Proof

How Conduit informs the first external deployments

✓

Fit Criteria

API-ready systems, workflow scope, and approval gates

By subscribing, you agree to receive emails from FirmOps. You can unsubscribe at any time.

Low-volume updates only. The primary CTA remains reviewing the offer or booking an AI live demo. Follow our insights in Google.

J

About Jonathan Mahler

Jonathan Mahler is the founder of Vertana (FirmOps is a Vertana brand) and the non-attorney founder and Firm Manager of Conduit Law. He runs the systems of a live PI firm every day, then turns reusable patterns into practical Managed Firm Brain workflows: approved context, supervised drafts, approval gates, and a path into deeper automation when the first workflow proves value. Meet Jon and Elliot.

Request demo

Bring one recurring bottleneck and see whether it is a good first firm-brain build. If the first workflow is concrete, the next step is a live build session, not a broad advisory project.

Live demo | Human approval before external action