Fixed quote after a free call

CRM automation for law firms that follows up every enquiry

Prospective clients often contact two or three firms and retain whichever responds first and clearly. We connect your website forms, directory leads, referral emails and call notes to one pipeline in a legal CRM such as Clio Grow or Lawmatics, or a general CRM such as HubSpot, send an approved acknowledgement within minutes, book consultations and follow up until the prospect retains the firm or declines. A typical build costs $1,000 to $2,500 per workflow and takes about four weeks.

The problem

Why law firms lose prospective clients before the first consultation

Legal enquiries arrive at the worst moments: a web form at 11pm about an arrest, a directory lead while every attorney is in court, a referral email buried under correspondence. Whoever reads it first decides how quickly it gets a reply, and the prospect is usually contacting other firms at the same time.

Without one pipeline, the firm cannot say how many enquiries came in by practice area, how many booked a consultation, how many retained the firm or which referral sources bring work worth taking. Unretained prospects simply drift away, and nobody knows why.

What we build

What our CRM for law firms includes

Every source in one pipeline

Website forms, directory and referral leads, call notes and chat enquiries land in one CRM with the practice area tagged.

Fast, careful acknowledgement

An approved first reply within minutes that explains next steps and makes clear no legal advice has been given yet.

Consultation booking

A booking link for the right practice group, with reminders before the consultation.

Follow-ups to a decision

Short sequences for prospects who have not booked or retained, with stop rules and a final close-out message.

Hand-off to the matter

Retained prospects become a contact and matter in Clio Manage, MyCase or your practice system without re-typing.

Source and practice-area reporting

A weekly view of enquiries, consultations and retained matters by source and practice area.

Who does what

Automation does the chasing, people make the calls.

Every step is marked: what runs on its own, what a member of staff reviews and what stays with a person who decides.
  1. 01 Automated

    Enquiry captured

    A form, directory lead, email or call note creates or updates a lead in the CRM.

  2. 02 Automated

    Acknowledgement sent

    The prospect gets approved wording and a consultation link within minutes.

  3. 03 Automated

    Follow-ups run

    Unbooked or unretained prospects get a short, polite sequence with stop rules.

  4. 04 Staff review

    Intake team reviews

    Staff qualify leads, call back and record outcomes.

  5. 05 Attorney or solicitor decides

    Taking the matter

    Whether the firm takes the matter is decided by an attorney after the conflict check.

How it behaves

How the legal CRM pipeline behaves

What each person sees and what runs in the background, including what happens when something goes wrong.

What the prospect sees

  • A prompt, careful acknowledgement with next steps
  • A link to book a consultation with the right team
  • A couple of follow-ups at most, then a polite close-out

What staff see

  • One pipeline by practice area with an owner on every lead
  • Call-back and qualification tasks
  • Retained matters created in the practice system

What the automation does

  • Captures and de-duplicates leads from every source
  • Sends approved messages with stop rules
  • Never tells a prospect the firm will take their case

Edge cases and fallbacks

Enquiry mentions an urgent court date or arrest
Flagged to the duty attorney at once with the firm's urgent wording sent.
Prospect is the opposing party in an existing matter
Flagged for the conflict process; no follow-up is sent until a lawyer clears it.
Same person enquires through two directories
Merged into one lead with both sources recorded.
CRM or practice system outage
Leads are queued and retried, and the intake lead gets an alert.

Architecture

A legal CRM pipeline at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Website forms Practice areas Directories And referrals Call notes Reception n8n Capture and dedupe Legal CRM Clio Grow or similar Follow-ups Email and text Intake team Calls and qualify Practice system Contact and matter
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 Enquiries arrive from website forms, directories, referrals and reception call notes.
  2. 2 n8n removes duplicates and creates or updates the lead with its practice area in the legal CRM.
  3. 3 Approved follow-ups go to the prospect and qualification tasks go to the intake team.
  4. 4 Retained prospects become a contact and matter in the practice management system.

Project planner

How the project runs, phase by phase.

Typical durations for a first version. Your proposal lists the exact phases, dates and what you sign off at each step.

Legal CRM & enquiry follow-up automation project plan

Typical time to launch: about 4 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Lead sources, practice areas, current tracking, CRM choice and what counts as retained.

  2. 02

    Design

    2 to 3 days

    Stages, acknowledgement wording, follow-up rules, duplicate rules and the matter hand-off.

  3. 03

    Build

    1 to 2 weeks

    Source connections, pipeline, booking, follow-ups and reporting.

  4. 04

    Shadow run

    About 1 week

    Leads flow into the CRM while the intake team keeps its current list, and we compare.

  5. 05

    Launch

    1 to 2 days

    Switch over and train the intake team.

  6. 06

    Support

    Ongoing

    New sources, practice areas and report changes.

What it runs on

Real products only, connected through the access each vendor provides. See all integrations

n8n Clio Grow API, Lawmatics (Zapier or API on request) or HubSpot CRM API Clio Manage API v4, MyCase Open API or your practice system Calendly API v2 or Outlook calendars Twilio SMS Microsoft 365 or Gmail

Cost estimate

What it costs, line by line.

Estimates to plan with. Your fixed quote follows a free call, once we have seen your systems and volumes.
  • Discovery and design

    Sources, practice areas, stages and wording.

    $200 – $450

  • Build

    Capture, de-duplication, booking and follow-ups.

    $500 – $1,250

  • Integrations

    Legal CRM, practice system, calendar and messaging.

    $150 – $400

  • Testing and shadow run

    QA and a side-by-side run with the intake team.

    $100 – $250

  • Launch and training

    Switch-over and intake team training.

    $50 – $150

  • Total project estimate

    $1,000 – $2,500

Optional monthly care after launch is quoted with your proposal. Fixed quote after a free call. Legal CRM, messaging and n8n subscriptions are billed to you directly. A two-way link with the practice system can add a second workflow.

Monthly running costs you pay directly

Estimates from the vendors' published pricing, checked November 2026. Billed to you by each vendor, never marked up.

  • Legal CRM: Your CRM vendor's own plan (Clio Grow, Lawmatics, HubSpot or what you use).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).
  • Twilio SMS (US): About $0.0083 per message segment each way plus carrier fees (Twilio's published US pricing).

What pushes cost up

  • Systems without an API, or with integration access that must be requested from the vendor
  • Writing data back into your core system rather than only reading from it
  • Several locations, brands or very different processes to support
  • Custom apps, dashboards or a voice line on top of the workflows

What keeps cost down

  • One location and one clear process to start with
  • Cloud software with a documented API
  • Using tools you already pay for instead of adding new ones
  • Approved wording and sample data ready at the start
Get a fixed quote

Privacy and consent

Rules we design for, with the sources.

General information to plan with, not legal advice. Your counsel or data protection adviser confirms what applies to your practice.

US: duties to prospective clients

ABA Model Rule 1.18 treats someone who consults about possibly forming a lawyer-client relationship as a prospective client, with confidentiality duties even if no matter follows. CRM access is limited accordingly.

Source: www.americanbar.org

US: marketing texts need consent

Promotional follow-up texts are marketing under the TCPA rules and need prior express written consent; we keep texts to replies the prospect asked for.

Source: www.law.cornell.edu

UK: marketing by email and text

PECR requires consent, or the soft opt-in conditions, for marketing by electronic mail, with a simple way to refuse in every message.

Source: www.legislation.gov.uk

How we deliver

Agile delivery, in 1 to 2 week sprints.

We deliver in short Agile sprints using Scrum, so you see working software every one or two weeks instead of waiting for a big reveal at the end.

Every sprint

  1. 1 Sprint planning. At the start of each sprint we agree which backlog items we will finish, each with written acceptance criteria you can check.
  2. 2 Daily stand-up. A short internal check-in on progress and blockers. You get a written update in your Slack or Teams channel, not another meeting.
  3. 3 Sprint review and demo. At the end of each sprint we demo what was built on test data or in a shadow run, and you accept it or ask for changes.
  4. 4 Retrospective. The team looks at what went well and what to change in the next sprint, and we share anything that affects you.

How scope stays under control

Product backlog
Every feature, fix and question in one prioritised list you can see at any time.
Acceptance criteria
Plain-language conditions for "done" on each item, agreed before work starts.
Change requests
New ideas go into the backlog with an estimate. Nothing changes scope or price without your written approval.
User acceptance testing (UAT)
Before launch your team tests the real workflow against the acceptance criteria and signs off.

Tools we use

Jira, ClickUp or Trello for the backlogSlack or Microsoft Teams for updatesGitHub for code and version historyLoom or a live call for demos

Project manager / Scrum master

Runs the sprints, keeps the backlog and timeline honest, and is your single point of contact.

Business analyst

Maps how the work runs today, writes the workflow specification and acceptance criteria with your team.

Automation engineer

Builds the n8n workflows, integrations, AI steps and error handling.

Backend developer

Writes custom code where a no-code step is not enough: APIs, data sync, secure storage.

Frontend / mobile developer

Builds forms, booking pages, dashboards, web apps or Android apps when the project needs them.

QA engineer

Tests every workflow against the acceptance criteria, including edge cases and failure paths.

DevOps engineer

Sets up hosting, access, backups, monitoring and alerts, and the deployment pipeline.

Who does what at each phase

Free call
Project manager, business analyst
Understand the problem, check it is worth automating and outline a rough range.
Discovery
Business analyst, automation engineer
Map the current process, systems and data, and agree success measures.
Design
Business analyst, automation engineer, backend developer
Write the workflow specification, data flows, compliance notes and backlog with acceptance criteria.
Sprints
Automation engineer, developers, QA
Build, test and demo in 1 to 2 week sprints; you accept or adjust after each demo.
UAT and launch
QA, DevOps, project manager
Your team tests and signs off, we switch on, monitor closely and train the team.
Support
Automation engineer, DevOps
Stabilisation window, then optional monthly care with monitoring and changes.

A point of contact

One person who can answer questions and approve decisions, with about an hour a week during the project.

Access

Admin or API access to the systems involved, created as separate accounts with the least access needed.

Sample data

Real but non-sensitive records (or de-identified ones) so we can design and test against reality.

Approved wording

Message templates, policies and consent wording (for SMS, your opt-in and opt-out text) reviewed by you.

Vendor agreements

Signed agreements with the software vendors that will handle personal data, such as a BAA or processor contract.

Time for testing

A few hours from the people who will use the system, for the demos and user acceptance testing.

Working system

Workflows, integrations and any apps running in your accounts, under your keys.

Documentation

Workflow specification, data-flow map, run book and exported workflow files.

Training

A walkthrough for the team and a short recorded video for new starters.

Handover

All access, credentials and code handed over; you can keep us or take it in-house.

Stabilisation window

Fixes for anything that does not meet the agreed acceptance criteria after launch.

Support options after launch

  • No plan

    You run it yourselves after the stabilisation window and contact us when you need a change.

  • Monthly care

    Monitoring, error alerts, small changes and updates each month, with an agreed response time.

  • Priority care

    Faster response times for business-critical workflows and a monthly review call.

How a project moves through our team

Free call PM and analyst Discovery Process and data Design Spec and backlog Sprints Build, test, demo Your review Accept or adjust UAT and launch Sign-off, go live Support Monitor and improve
  • Input
  • Logic and services
  • People
  • Output
  • Data

How it flows

  1. 1 A free call with the project manager and business analyst to understand the problem and whether it is worth building.
  2. 2 Discovery and design produce a written specification, data-flow map and a backlog with acceptance criteria.
  3. 3 The team builds in 1 to 2 week sprints; you review a demo at the end of each and accept or adjust.
  4. 4 Your team runs user acceptance testing, we launch, then monitor and improve under a support plan.

FAQ

Legal CRM & enquiry follow-up automation questions, answered.

Legal CRMs such as Clio Grow and Lawmatics are built around intake and connect to legal practice systems; general CRMs such as HubSpot or Zoho are flexible with documented APIs. The right choice depends on your practice system, lead volume and budget, and we can work with the CRM you already have.

If enquiries arrive from more than one source or follow-up depends on memory, usually yes. A small firm often needs one pipeline, an acknowledgement and a follow-up rule, which fits a single workflow.

Yes. Clio publishes a Grow API on its developer platform, including a lead inbox endpoint for adding leads from other sources. We confirm the scopes your account allows before quoting.

Lawmatics offers native integrations and a Zapier app with triggers such as converted matters, and an API that Lawmatics enables on request. We pick the supported route for your account.

No. Sequences are short, stop as soon as the prospect books, retains or declines, and respect opt-outs. A final message closes the enquiry politely.

Enquiries by source and practice area, time to first response, consultations booked, matters retained and reasons prospects did not proceed.

Free 20-minute call

Want this for your law firm?

Book a free 20-minute call. We will look at how the work runs today, tell you honestly whether it is worth building and give you a fixed quote if it is.

Book a free 20-minute call