11 July 2026 · Airtective Team
Automating a Law Firm's Client Intake Process
The Intake Process Nobody Wants to Admit Is This Manual
We sat down with a small firm a few weeks back to map out how a new client actually becomes a client. Skip the tidy version in the process document on the shared drive, we wanted the version that actually happens day to day. Took about an hour and a half and pulled in four different pieces of software, plus at least one step that only survives because the paralegal's been there six years and just remembers to do it.
Here's roughly what it looked like. A prospective client calls or fills out a contact form. Someone writes their details into an email to send to the attorney. The attorney says yes, open a file. Someone opens PC Law, creates a new matter, assigns a file number, runs a manual conflict check by searching old client names. Once that clears, someone drafts an engagement letter in Word and turns it into a PDF in Adobe, then emails it out of Outlook to the client. The client prints it, signs it, scans it back, or drives it over in person. Retainer payment gets requested by phone or a separate email, and somebody watches the bank account to see when it lands. Once it does, somebody opens Outlook Calendar and books the first consult, and separately updates a tracking spreadsheet so the partners can see how many new matters opened that month.
None of that is unusual. Most small firms run intake close to exactly like this, and it mostly works, until volume goes up and something drops. A missed conflict check flag. A retainer that came in on a Friday and nobody noticed until Wednesday.
Why "Just Switch to a New Platform" Is Bad Advice Here
The instinct a lot of legal tech vendors push is to rip out PC Law and move to something newer with a built in client portal and API. That would've been the easy pitch for a software vendor to make. For a firm with a decade of billing history and matter numbers referenced in old court filings, plus staff who know the software cold, that's a project measured in months and tens of thousands of dollars. It's nowhere close to a weekend fix, and it doesn't even solve the intake problem since it just moves the same manual steps into a different interface.
We don't think that's the right first move for most firms. PC Law, or whatever practice management tool a firm has run for years, usually isn't the actual bottleneck. The bottleneck is everything happening around it, the emails, the copy pasting between Outlook and the file, the manual conflict check, the calendar entry someone forgets to make until the client calls asking where their appointment confirmation went. That's usually the part you can automate without touching the case management system at all.
What the Automated Version Looks Like
The tools involved here are the same ones most firms already have some version of. Outlook, a form or intake page, Adobe for signing, and something to track matters and payments. We layer n8n or Make on top to connect them, since PC Law itself doesn't expose a modern API for most firms to hook into directly.
Step 1: Inquiry comes in. Whether it's a web form or an email (or a phone intake a receptionist logs into a shared form), that submission triggers a workflow. Within a couple minutes the prospective client gets an automatic acknowledgment, by email and by SMS through Twilio if a phone number was given, confirming someone received the request and will follow up. This alone fixes a surprising amount of the "did anyone even see my message" anxiety that sends prospects calling a competing firm instead.
Step 2: The intake gets logged and routed. The workflow writes the inquiry into a Google Sheet that acts as the intake tracker: matter type, contact info, referral source, urgency flag. That sheet becomes the one place partners look to see intake volume without anyone compiling a report by hand at month end. The attorney assigned gets a notification, by Outlook email or Teams if that's set up, with the client's details already formatted instead of buried three replies deep in an email thread.
Step 3: Conflict check gets kicked off instead of forgotten. The automation doesn't run the conflict check itself, since that search still needs to happen against PC Law's client history. What it does is generate the request the moment intake is approved and drop the client name and matter details into a flagged row, then hold the file from moving forward until someone marks the check complete. It stops the step from getting skipped when things are busy, which is usually how conflicts slip through in the first place.
Step 4: Engagement letter and signature, handled through Adobe. Once the conflict check clears, the workflow pulls a template and fills in the client and matter details, along with the fee terms, then sends it for signature through Adobe Sign. No printing or scanning, no PDF sitting stuck in someone's downloads folder. When the client signs, Adobe fires a webhook that n8n or Make picks up and uses to update the intake tracker and notify the attorney the file's ready to open.
Step 5: Matter creation in PC Law still happens by hand. This is the part that matters most for the "without switching software" angle. The staff member still opens PC Law and creates the matter themselves, because that's where PC Law lives and nobody's replacing it. But instead of retyping everything from an email thread, the automation hands them a formatted summary, or in some setups a CSV they can import directly into PC Law's new matter wizard, with the client and matter details already pulled straight from the intake form. What used to be five minutes of retyping and a decent chance of a typo turns into copying a few fields over and confirming.
Step 6: Retainer payment and calendar booking. Once the retainer is confirmed, whether that's flagged by a bank feed or an invoicing tool (or someone just noticing it manually), the workflow triggers the calendar step on its own. It books the first consultation directly in Outlook Calendar and invites the attorney and client, then sends a reminder text through Twilio 24 hours before the appointment. Nobody has to remember to do this at 4:45pm on a Friday.
Step 7: Reporting. Because every step writes back to the same Google Sheet, the partners get a weekly summary automatically: a Make or n8n scheduled run that compiles new inquiries and conversion to signed matters, along with average time from inquiry to retainer, sent as a short email every Monday. No one manually building this in Excel anymore.
The Objection We Hear on Nearly Every Legal Intake Call
"PC Law doesn't have a real API, so how much of this can actually be automated."
Fair question, and honestly the reason a lot of firms assume automation isn't possible for them at all. PC Law itself stays untouched. What gets automated is everything that currently happens by hand around it, the acknowledgment, the intake log, the conflict check trigger, the signature request, the calendar booking, the reporting. PC Law stays the system of record for the actual matter and billing, exactly like it is now. The one manual step left, opening the matter in PC Law itself, takes a couple minutes instead of the fifteen or twenty it used to, because the information arrives ready to go instead of scattered across three email threads.
Firms that have tried automation before and had it "break" usually tried to force a direct integration into a closed system that was never built for that, or handed the whole thing to a developer who built something clever and fragile instead of connecting tools already designed to talk to each other. n8n and Make exist specifically to sit between tools like Outlook, Adobe, Google Sheets, and Twilio and pass information between them reliably. That's a different exercise entirely from reverse engineering a 20 year old desktop application's database.
What This Actually Saves
For a firm handling, say, 40 to 60 new inquiries a month, the manual version of this process eats somewhere around 3 to 5 hours a week across intake staff and attorneys, just in retyping details and chasing down signatures, plus booking calendar entries by hand. Across the firms we've worked with, response speed is consistently one of the bigger factors in whether a prospective client actually retains a firm or calls the next name on their list, so the faster acknowledgment alone tends to move the needle on conversion, not only on staff time.
This doesn't ask the firm to learn new case management software or retrain staff on a completely different interface, and nobody has to migrate years of matter history anywhere else. What actually changes is that the information already sitting on people's desktops starts moving on its own instead of piling up in someone's inbox.
Where to Start
If your intake process looks anything like the one above, forget the new platform idea for a minute. What actually helps is mapping the real steps, not the tidied up process document version, and figuring out which ones genuinely need a person's judgment versus which ones are pure manual busywork. A conflict check needs a person, and so does the final review of a matter before it opens. Plenty of the rest is just retyping the same client details into four different places because nobody's stopped to change it yet. That's the same line we draw more broadly in where AI genuinely helps a law firm and where it just adds risk, separating judgment calls from repetitive intake work that's safe to hand off.
We do this mapping for free. Book a free 60-minute call and we'll walk through your current intake process, tool by tool, and show you exactly where the automation fits without touching PC Law or whatever else you're already running.
Related articles
25 July 2026
Do You Need an AI Agent, or Just Better Automation?
Before signing off on an 'AI agent' project, use this simple test to see if one automation with a single LLM call handles it for a fraction of the cost.
25 July 2026
What Is an "AI Agent," Really?
Every vendor calls their chatbot an AI agent now. Here's the plain definition and the questions that expose which pitches are just relabeled automation.