"In the law firm engagements we have run, the number that surprises people most is not how long automation takes to build. It is how much senior time was being spent on work that should never have needed a senior person."
The loss is not dramatic. No single task takes an entire day. It is twenty minutes here — a document reformatted for a different jurisdiction. Forty minutes there — a client report compiled from four separate systems. An hour at the end of the week — compliance checklists filled in by hand because the system does not talk to the matter management software.
Multiply that by the number of fee-earners. Multiply that by fifty-two weeks. The number that comes out is not a productivity problem. It is a structural cost that has been normalised into invisibility.
Where the time actually goes
When we map the workflows at a law firm before starting an engagement, we look for five categories. In our experience, they show up at most firms, in some proportion.
Category breakdown
| Category | Typical task | Time per week (per fee-earner) |
|---|---|---|
| Document preparation | Reformatting, jurisdiction-specific versions, template population | 3–5 hrs |
| Client reporting | Matter status updates, billing summaries, periodic reports assembled from multiple sources | 2–4 hrs |
| Compliance documentation | AML/KYC checklists, conflict checks, engagement letter generation | 2–3 hrs |
| Cross-system data entry | Copying information between practice management, billing, and document systems | 1–3 hrs |
| Internal coordination docs | Briefing notes, file notes, meeting minutes, handover documents | 1–2 hrs |
| Total | Across all five categories | 9–17 hrs/week |
At a mid-market firm billing senior associates at €250–€350 per hour, even the low end of that range — a few hours a week of non-billable document admin — adds up to a meaningful chunk of misallocated senior capacity per fee-earner, per year. Multiply that across a team of ten and the figure gets hard to ignore.
Why delegation does not fix it
The instinctive response is to delegate. Push the document preparation to a paralegal. Ask the junior associate to handle the compliance checklists. Have someone more junior build the client reports.
This works until the paralegal is at capacity. At that point, the bottleneck moves — it does not disappear. You have now created a queue that sits in front of the same wall. Senior people wait for juniors who are already overloaded. The output that senior clients are paying for is now delayed by a staffing problem that grows with volume.
Hiring into the problem is the other answer firms reach for. It works in the short term. It also compounds the cost: each new hire needs management attention, ramp-up time, desk space, and salary — and each new hire is subject to the same efficiency loss as the people already there.
Automation does not have these properties. A workflow that runs automatically handles three times the volume at the same cost. It does not need a manager. It does not go on leave. It does not need to be onboarded when a partner retires and takes their process knowledge with them.
What the automatable work actually looks like
Not every document task is automatable. Work that requires legal judgment, client relationship management, or complex novel reasoning is not a candidate. But the work in the five categories above shares a set of properties that make it structurally automatable:
It is structured. The inputs are predictable — a matter type, a client profile, a set of facts. The output format is fixed — a report template, a checklist, a letter. The transformation between them follows rules that a senior person could write down if they had to.
It is repetitive. The same task runs on Monday that ran the previous Monday. The same report format goes to the same client category every month. The same compliance checklist applies to the same matter type every time.
It is high-volume. The task is not a one-off. It runs across every client, every matter, every reporting cycle. That volume is exactly what makes it expensive — and exactly what makes automation financially justified.
The calculation that closes the conversation
When we present the workflow map to a managing partner, the most useful thing we show is not the process diagram. It is the number.
Take the hourly rate. Multiply by hours per week per fee-earner. Multiply by the number of fee-earners. Multiply by fifty-two. That is the annual cost of the status quo — not in salary, but in senior capacity directed at work that should not require senior capacity.
Compare that number to the cost of an automation engagement. In most cases, a workshop and working prototype costs between €22,000 and €30,000. A full deployment costs more. The payback period, at the numbers above, is measured in weeks — not years.
The question is never whether the ROI is there. It is always whether the firm is ready to model the actual decisions and information dependencies that drive the workflow. That distinction — and how to construct auditable pathways — is what our methodology on decision audit trails covers.