Jump to section
A few years ago, automation at a small firm meant a folder of email templates and a shared calendar someone yelled about every Monday. That era is ending, but not in the way the demos suggest. The real shift is quieter, and it changes how a matter moves through your office more than it changes what any single button does.
I want to separate signal from noise here. Some of what gets sold as the future is genuinely durable. Some of it is a slide deck. If you run a firm of three to thirty people, the distinction matters, because you buy tools rarely and you live with the choice for a long time.
From Point Tools to Connected Workflows
The first durable trend is boring to describe and expensive to ignore: firms are moving away from a drawer full of single-purpose tools toward a smaller number of systems that actually talk to each other. Not because integration is fashionable, but because the seams between tools are where the work gets lost.
Think about a routine intake. A prospective client fills something out, someone runs a conflict check, a matter gets opened, a folder gets created, a first invoice gets scheduled. When those steps live in five apps, the automation you build is really just glue, and glue breaks. When they live in one place, the automation is structural. The matter carries its own state, and the next step knows what happened before it.
Tip. Before you buy anything, map one real matter type end to end on a whiteboard. Count how many times work crosses from one system to another. Every crossing is a place where something falls through, and it is the honest measure of how connected your setup really is.
This is where a platform like A1 CMS earns its keep, not by having the flashiest single feature, but by keeping the matter, the intake, the billing, and the documents in one thread. The connective tissue is the point.
The Move From Reminders to Real Routing
Here is the shift I find most interesting. For a decade, automation mostly meant reminders. The system nudged a human, and the human did the actual thinking about what came next. That is useful, but it is low-value. A reminder still puts the whole cognitive load of deciding on a person.
What is emerging is routing: the system deciding, based on rules the firm sets, where a piece of work should go and who should touch it next. A limitation period gets calculated and the file lands on the right desk with the right deadline attached. An unsigned retainer routes back to intake instead of sitting in an inbox. The difference between a reminder and routing is the difference between being told there is a problem and having the problem already moved to the person who fixes it.
A reminder tells you something is late. Routing makes sure it never sat with the wrong person in the first place. The distinction that separates real automation from busywork
The catch, and it is a real one, is that routing only works if your process is legible. You cannot automate a decision you have never actually written down. Most firms discover, the first time they try to build a real rule, that half their process lives in one person's head. That discovery is worth the exercise on its own.
Where Human Review Is Becoming the Bottleneck
As routing improves, the constraint moves. When getting work to the right person is fast and reliable, the slow step becomes the review itself: the lawyer reading the draft, checking the numbers, signing off on the letter. Automation has quietly relocated the bottleneck from moving work to judging work.
This is a good problem, but only if you treat it deliberately. The temptation is to automate faster and pile more finished-looking output in front of a reviewer who now has less time per item. Speed upstream without capacity downstream just moves the pile. The firms handling this well are doing something less obvious: they are deciding, in advance, which review steps genuinely need a lawyer and which need a competent second set of eyes.
- Reviews that must stay with a lawyer: advice, strategy, anything going out under a name attached to professional judgment.
- Reviews a trained staffer can own: formatting, completeness, whether every field in a form is populated, whether the disbursements match the file.
- Reviews the system can handle: arithmetic on an invoice, whether a required document exists, whether a deadline was calculated correctly.
Sort your review steps into those three buckets and you reclaim the reviewer's attention for the work that actually needs it. Skip that step and you have just built a faster way to overload your busiest person.
What Firms Are Quietly Abandoning
Trend reading is as much about what people drop as what they adopt. A few things are being quietly walked back, and it is worth naming them so you do not waste a year rediscovering the same lessons.
| Fading | Why it is fading |
|---|---|
| Sprawling custom macros in one person's spreadsheet | They break the moment that person leaves, and no one else can read them. |
| Chatbots bolted onto the public site to capture leads | Prospective clients want a person, and the handoff to a real file is usually missing. |
| Automating a broken process faster | Speed multiplied by a bad process just produces bad output sooner. |
| Tool-per-task collections | The licensing cost and the training cost quietly exceed the value. |
None of these were foolish bets at the time. They were reasonable first attempts. The firms moving on from them are not smarter, they just tried the thing and learned where it stopped paying off.
Note. If a piece of your automation only works because one specific person maintains it, treat that as a liability, not a feature. The most valuable automation is the kind a new hire can understand in an afternoon.
Placing Sensible Bets for the Next Two Years
So where should a small firm actually put its attention? I would keep it modest and durable. Bet on the trends that survive a staffing change and a busy month.
- Consolidate before you automate. Fewer systems that share data beat more systems that each do one clever thing.
- Write down one process fully. Pick your highest-volume matter type and make the routing rules explicit. If you cannot write it, you cannot automate it.
- Protect review capacity. Decide which sign-offs need a lawyer and defend that person's time as the scarce resource it is.
- Prefer legible over clever. A rule a colleague can read and change will outlast a brilliant one only its author understands.
If you want to go deeper on the review side of this, the piece on cutting admin load pairs well with this one, and the templates and checklists discussion covers how to make a process legible before you ever hand it to software. You can also see how the pieces fit together across the rest of the operations writing.
The honest summary is that firm automation is getting less magical and more structural, which is exactly what you want. The wins over the next two years will not come from a single dramatic feature. They will come from work that moves cleanly, decisions that are written down, and reviewers who have the time to actually review. Automate the routing, protect the judgment, and let the boring, connected version of the future do the heavy lifting.
