Automating Client Onboarding for a Small Law Practice
Automating Client Onboarding for a Small Law Practice
In small professional services practices, admin often grows around the work rather than being designed to support it. Over time it becomes layered, messy, and harder to manage. Nothing breaks outright it just quietly erodes profitability per client.
That was the situation when I started working with an immigration lawyer on her onboarding process. The practice was running across a fragmented set of tools and an offline database. One client had required over 60 emails back and forth just to collect the information needed to prepare a visa submission.
Setting the right scope
The brief was to improve onboarding without heavy upfront investment. The practice was small and growing and the tools needed to be workable now and scale in cost as the business did. That constraint shaped everything including the tool selection, what to automate and how far to take the project.
A low-code stack made sense: Cal.com, Make, Airtable, JotForm and SendPulse. All have generous free tiers and relatively low switching costs, which matters when you’re building something that may need to adapt over time.
Sorting the website first
The lawyers SSL certificates were broken and the site was built on Google Sites. Clients need to see a credible, professional presence before they’ll trust someone with their visa application and the website wasn’t providing that. I reduced the page count, gave each page a clear job and made sure the key information was findable and easy to understand: services, process, pricing, reviews, and the lawyer’s background.
I also worked with the lawyer on starting a blog. She had years of case knowledge and real expertise, but none of it was visible anywhere online. Publishing that content builds authority and supports organic search, neither of which was happening.
Deciding what to automate
Before building anything, I mapped the existing workflow with the lawyer and worked through where automation would genuinely help and where it wouldn’t.
The key decision was around the post-consultation case summary. After each paid call, the lawyer writes a personalised assessment and recommendation for the client. That document is also the conversion point between a $60 consultation and a $600 full visa service. I looked at whether AI could draft it from the call transcript. We decided against it.
The lawyer felt strongly that her expertise and judgement needed to be applied manually to each summary and the reasoning was sound. Clients are paying for a personal service, not a fast process. Automating that step would have saved some time while eroding the thing that makes the service worth paying for. So the summary stayed manual, and the decision to progress a client stayed with the lawyer. The automations were built around those fixed points.
The onboarding flow
When a consultation is booked, the client now receives a confirmation automatically with payment instructions and preparation guidance. Reminders go out at 24 hours before and on the day of the consultation. When the lawyer is ready to progress a client to a full service, she sends a structured form link generated in Airtable. The submitted data connects back to the client’s record automatically, replacing the email chains. The client receives clear next-step instructions and the lawyer is notified when action is required.
Airtable holds three linked tables clients, cases and dependants with all unique rows. This schema supports repeat clients, multiple applications per person and a clear paper trail as well as GDPR compliant storage of personal information.
Renewal reminders
The lawyer mentioned that clients often returned for visa renewals too close to their expiry dates, which created unnecessary stress and, if left too late, legal complications. I set up automated reminders at three months, two months, and one month before each renewal date. When a visa is approved, the expiry date goes into Airtable and Make handles the rest.
This protects clients from avoidable risk and creates a reliable pipeline of repeat work for the practice. Both things that are useful to have and neither required much to build.
What this kind of project involves
The technical side of this wasn’t complex. Most of the work was in asking the right questions early particularly about where the lawyer’s expertise was the product and where it wasn’t and then building something proportionate around the answers.
There’s more that could be added as the practice grows. But adding more before the volume is there wouldn’t have served the client well. The right scope was the one that addressed the actual bottlenecks without creating new complexity to manage on top of them.
