Fixed quote after a free call

Client matter updates that keep clients informed without more calls

A large share of calls to a law firm are clients asking what is happening. We build a workflow that sends plain-language updates when a matter reaches milestones you define, such as documents received, filing made, hearing listed or completion booked, using wording the lawyer approved. Replies and questions are routed to the right person, and nothing goes out on a matter the lawyer has paused. A typical build costs $1,000 to $2,500 per workflow and takes three to four weeks.

The problem

Why clients call to ask what is happening

Clients in a legal matter are often anxious and rarely see the work happening. Silence feels like neglect, so they call, and each call interrupts a lawyer or paralegal to give an update that could have been sent automatically.

In the US, ABA Model Rule 1.4 expects lawyers to keep clients reasonably informed about the status of a matter and promptly comply with reasonable requests for information. Consistent milestone updates support that duty, but only if each message is accurate and sensitive matters are handled personally.

What we build

What our client matter updates include

Milestones per matter type

Defined stages for conveyancing, probate, litigation, family or immigration matters, mapped to your practice system.

Approved plain-language updates

Short messages for each milestone, approved by the lawyer, explaining what happened and what comes next.

Document requests from the client

Requests for what the client still owes, with a secure upload link and reminders.

Pause control

Lawyers can pause updates on sensitive matters with one click.

Reply routing

Client replies go to the responsible lawyer or paralegal with the matter attached.

Portal or email

Updates through your practice system's client portal where it has one, or secure email.

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

    Milestone reached

    A status change or calendar entry in the practice system marks a milestone.

  2. 02 Automated

    Update prepared

    The approved message for that milestone is filled with matter details.

  3. 03 Automated

    Update sent

    Unless the matter is paused, the client receives the update and any request.

  4. 04 Staff review

    Team answers replies

    The paralegal handles routine replies and passes the rest on.

  5. 05 Attorney or solicitor decides

    Legal questions

    Any question about strategy, merits or outcome is answered by the lawyer.

How it behaves

How matter updates behave

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

What the client sees

  • A short, plain update when something happens on their matter
  • A clear request when the firm needs something from them
  • A person replying when they have a question

What staff see

  • Fewer status calls
  • Replies routed with the matter attached
  • A pause switch for sensitive matters

What the automation does

  • Watches status changes and calendar entries
  • Sends only approved wording
  • Never comments on merits or outcome

Edge cases and fallbacks

Status changed by mistake
A short delay lets staff undo the change before an update goes out.
Client has asked for post only
Updates are listed for staff to send by post.
Matter paused by the lawyer
No messages until the pause is lifted.
Practice system webhook failure
Missed events are picked up by a nightly check and the team is alerted.

Architecture

Client matter updates at a glance.

The setup we usually start from. We adapt it to the phone system and practice software you already use.
Practice system Status changes n8n workflow Milestone rules Approved wording Per milestone Client update Portal or email Paralegal Routine replies Lawyer Legal questions
  • Input
  • Logic and services
  • Data
  • Output
  • People

How it flows

  1. 1 A status change or calendar entry in the practice system marks a milestone.
  2. 2 The workflow checks for a pause and picks the approved wording for that milestone.
  3. 3 The client receives the update through the portal or secure email.
  4. 4 Replies are routed: routine ones to the paralegal, legal questions to the lawyer.

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.

Client matter updates & status communication project plan

Typical time to launch: about 3 weeks, then support

  1. 01

    Discovery

    2 to 3 days

    Matter types, milestones, how status is recorded and what clients call about most.

  2. 02

    Design

    2 to 3 days

    Milestone map, message wording with lawyers, pause rules and reply routing.

  3. 03

    Build

    About 1 week

    Status triggers, messages, document requests, pause control and routing.

  4. 04

    Shadow run

    About 1 week

    Updates go to a test inbox while lawyers check each one.

  5. 05

    Launch

    1 to 2 days

    Start with one matter type, then widen.

  6. 06

    Support

    Ongoing

    New milestones and wording changes.

What it runs on

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

n8n Clio Manage webhooks or your practice system API Practice system client portal or secure email Twilio SMS for opt-in text alerts Microsoft 365 or Gmail Slack or Teams for routing

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

    Milestones, wording and routing rules.

    $200 – $400

  • Build

    Triggers, messages, requests, pause and routing.

    $500 – $1,300

  • Integrations

    Practice system, portal or email and chat routing.

    $150 – $400

  • Testing and shadow run

    Test inbox run with lawyer checks.

    $100 – $250

  • Launch and training

    Launch on one matter type and team walkthrough.

    $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. Each additional matter type is quick to add once the first is live. Messaging and n8n costs are billed to you directly.

Monthly running costs you pay directly

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

  • Messaging: Your email provider; Twilio at about $0.0083 per US message segment plus carrier fees if text alerts are used (Twilio's published US pricing).
  • n8n: Free self-hosted Community edition, or n8n Cloud from about €20 a month (Starter, billed annually).

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: keeping clients informed

ABA Model Rule 1.4 expects a lawyer to keep the client reasonably informed about the status of the matter and to comply promptly with reasonable requests for information.

Source: www.americanbar.org

US: confidentiality of client information

Model Rule 1.6(c) requires reasonable efforts to prevent inadvertent or unauthorised disclosure of client information, so updates avoid sensitive detail in texts and use secure channels.

Source: www.americanbar.org

England and Wales: costs updates

Paragraph 8.7 of the SRA Code requires the best possible information about pricing, including as a matter progresses; cost milestones can trigger an update for the lawyer to send.

Source: www.sra.org.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

Client matter updates & status communication questions, answered.

Factual milestone updates such as documents received, filing made, hearing date listed or completion booked, plus requests for what the client still owes. Anything about strategy, merits or likely outcome stays with the lawyer.

We draft them with your lawyers, who approve every template. The workflow only fills in matter details like dates and names.

Lawyers can pause updates on any matter, and some matter types can be excluded entirely, such as family matters where a shared email account could be a risk.

That is the aim, and we measure it. Track inbound status calls and emails per matter before and after launch rather than relying on a promised number.

Where your practice system has a client portal and API support, updates can appear there; otherwise we use secure email. The route is confirmed per project.

Status calls per matter, client replies needing a lawyer, time to answer replies and client feedback at matter close.

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