Your Lawyers Are Mobile. Your Software Wasn't Built for Them.

It is 4:30 in the afternoon, and a managing partner is standing on the courthouse steps.

The hearing ran over. The client needs an update. There is a file that needs to be pulled and sent to the associate before tomorrow morning. A new matter was mentioned in passing, and someone needs to open it and assign the work. And somewhere between the second-floor courtroom and the front door, the partner had a thought about a draft letter that needs to change before it goes out.

Four things. Phone in hand. Three minutes before the taxi arrives.

Every tool this partner's firm has purchased for them was built for someone at a desk.

Why was legal technology built for the desk?

The legal technology industry did not design its products for a lawyer in a corridor. It designed them for a lawyer in an office: settled, connected, with a large monitor and a keyboard and the time to work through a system that assumed all three.

This is not a criticism. It is a description of how enterprise software gets built. The people who evaluate it, negotiate the contract, and approve the purchase are sitting in offices. The demos happen in boardrooms. The use cases presented by the vendor show someone logging into a desktop application, moving through a clear interface, and completing a structured task. The software is built to impress in those conditions.

The conditions in which lawyers actually work are different.

Lawyers, particularly the senior lawyers whose time is most expensive, are among the most mobile professionals in any industry. A managing partner's day might include a client breakfast, a morning in court, a site visit, two external meetings, and a commute at both ends. The lawyer sitting quietly at their desk for four uninterrupted hours is not the managing partner. It is, at most, the associate.

The infrastructure has been built for the associate's context. It is being marketed to the partner's budget.

What happens when mobile lawyers meet desktop-first tools?

The consequences of this mismatch are predictable. And they are expensive.

Time entry

The primary failure. Time entry tools were built for end-of-day desk sessions, requiring a lawyer to reconstruct what they did and when. On mobile, most time entry interfaces are barely functional: small fields, deep menus, no voice input. The result is a pattern every lawyer recognises: "I'll log it when I'm back at my desk." Some of it gets logged. Most of it gets estimated. A significant portion disappears entirely. Clio's Legal Trends Report consistently finds firms capturing 30-35% less than actual billable time. The mobile context is a primary cause: work happens away from the desk, recording is tied to the desk, and the gap between the two is filled with guesswork.

Task delegation

The managing partner who has four things in their head and three minutes before the taxi has two choices: make a phone call (which creates a follow-up problem), or carry the thought forward ("I'll email the associate when I'm back"). Carrying thoughts forward works until it doesn't. The associate who needed that instruction by this afternoon is now waiting until tomorrow. The draft letter that needed to change goes out uncorrected. This is why delegation fails in firms full of capable people.

Document review

Technically possible on a phone. In practice, a document management system designed for a 27-inch monitor produces an experience on a 6-inch screen that lawyers will endure once and then route around permanently.

Communication routing

A client emails a question. The managing partner reads it on their phone, knows the answer, and sends a one-line reply, bypassing the DMS, the matter file, the time entry, the associate who should have handled it. Not because the partner wanted to bypass the system. Because the system required a desk, and there was no desk available.

Each of these failures is individually recoverable. Collectively, they describe an infrastructure that captures a fraction of what happens, routes less than was intended, and creates a compounding backlog of things the professional meant to do when they got back to their desk, which they may or may not do, hours later, with the context partially gone.

The carry-forward problem

There is a specific cognitive load that desktop-first tools impose on mobile lawyers. Call it the carry-forward problem.

Every instruction not sent, every time entry not logged, every document not tagged at the moment of work becomes an item in the lawyer's working memory. It has to be held until the desk is available, then reconstructed from that memory and recorded.

Working memory is limited, and it decays. The instruction that was clear at 4:30 on the courthouse steps is vaguer at 7pm when the lawyer finally opens their laptop. The time entry that was vivid in the taxi is a guess an hour later. The thought about the draft letter (the one that seemed obvious in the corridor) may simply not surface again. Those are the four minutes managing partners never get back, repeated all day.

The cost of this is real but largely invisible. Firms do not measure the value of thoughts that were not captured. They measure the billable hours that were not logged, and that number is significant. But the full cost is wider: decisions not routed, instructions not given, context not preserved, file notes not made.

Desktop-first legal infrastructure does not just create friction. It creates leakage. Systematically, every day, across every lawyer in the firm.

What should legal infrastructure do instead?

The correct framing for legal technology infrastructure is not "how do we put the desktop on the phone?" It is a fundamentally different question: "how do we capture what the lawyer needs to express, at the moment they need to express it, without requiring them to stop and engage with a system?"

Voice is the obvious answer, and it is not a new observation. What is less obvious is what voice-first infrastructure requires architecturally.

It requires capture at the point of thought, not at the point of convenience. A lawyer who can say "add a note to the Henderson matter, I agreed to extend the deadline to the 15th" as they leave the client's office has preserved that instruction completely. The same lawyer who tries to find the correct matter in a mobile app, type the note, and save it, while walking, will either stop walking, stop trying, or produce an incomplete record. Speaking is faster than typing in every one of those conditions.

It requires results delivered where the lawyer already receives information (email, existing communication channels, the tools the firm already uses) rather than in a new dashboard that requires a separate login and a separate habit.

And it requires no learning curve on mobile. Adding a new app to a lawyer's phone is easy. Adding a new behaviour is hard. Adding a new behaviour that only works well in conditions the lawyer is rarely in (sitting still, with time, with patience for the interface) is almost impossible.

This is not a convenience argument

It is tempting to frame mobile-first legal infrastructure as a convenience upgrade. It is not. It is a fidelity upgrade.

The managing partner leaving court with four things in their head is not looking for a more enjoyable experience. They are trying to prevent work from falling through the gap between when it happened and when the desk is available.

Every firm that runs primarily on desktop-first infrastructure is running a firm whose senior professionals carry a leakage problem they cannot measure and cannot easily solve. Some of that leakage is billable time. Some of it is the quality of direction their team receives. Some of it is the client relationship moments that were not followed up because the note was never made.

The firms that will lead the next decade of legal practice are not necessarily the ones with the most AI tools. They are the ones whose infrastructure matches where their lawyers actually work.

For most lawyers, that is a phone, and a corridor, and a thought that has to go somewhere before the taxi arrives.

Frequently asked questions

Why is legal technology built for the desk?

Because the people who evaluate, negotiate and approve enterprise software sit in offices, and the demos happen in boardrooms. Vendors show someone at a desktop completing a structured task, so the software is built to impress in those conditions. The lawyer who actually sits at a desk for four uninterrupted hours is the associate, yet the tools are marketed to the partner's budget.

What is the carry-forward problem?

It is the cognitive load desktop-first tools impose on mobile lawyers. Every instruction not sent, time entry not logged or note not made at the moment of work has to be held in working memory until a desk is available. Working memory decays, so the instruction that was clear on the courthouse steps is vaguer by evening and the time entry becomes a guess.

How much billable time do firms lose to desktop-first tools?

Clio's Legal Trends Report consistently finds firms capturing 30-35% less than their actual billable time. Work happens away from the desk while recording is tied to it, and the gap is filled with estimates. The wider cost is harder to measure: decisions not routed, instructions not given, and client follow-ups that never happened because the note was never made.

What should mobile-first legal infrastructure look like?

It captures what the lawyer needs to express at the point of thought, by voice, rather than asking them to stop and engage with a system. It delivers results into the channels the lawyer already uses, such as email, rather than a new dashboard. And it demands no new behaviour that only works when the lawyer is sitting still with time and patience.