The Legal Vertical Isn't Hard to Win. It's Hard to Serve.

Law firms aren’t difficult as commercial clients. They have deposits, compliance requirements, and workflows that repeat predictably across every matter they open. The challenge isn't understanding what they need. It's whether your bank is built to deliver it.

Many aren't.

What legal escrow actually requires

When a law firm holds client funds, whether settlement proceeds, real estate transaction funds, or retainers, those funds must be tracked to the individual client matter. Larger and longer-term funds belong in discrete accounts of their own, with documentation that meets bar compliance requirements and withstands a state audit.

That's not something a core processor handles cleanly. The typical workaround is manual: individual accounts opened one by one, reconciled by hand, and managed through a process that works fine at low volume, but eventually breaks down as the client grows.

For the bank, the volume ceiling is a problem. A law firm with ten active matters is manageable. A firm with fifty is a staffing issue. A book of legal clients at scale is operationally untenable without purpose-built subaccounting underneath it.

When this happens, banks either cap how many legal clients they take on or turn them away entirely. Either way, those deposits go somewhere else — to a larger institution that made the infrastructure investment, or to a platform the bank had nothing to do with.

The cost of that ceiling

This is where the disintermediation risk is most underappreciated. Legal escrow clients don't churn casually. Once a law firm has built its trust accounting workflow, it sticks. Escrowed attorney funds are long-duration and high-balance by nature; matters don't close on a schedule, and funds don't move until they do.

That stickiness is what makes legal deposits so valuable, and those are the deposits banks give up when they can't serve this valuable commercial vertical properly.

A $25 billion New England bank made the decision to invest in a platform to help them serve and capture this important vertical. Over two years, total ZEscrow deposits grew from $4.1M to $26.8M. Attorney deposits averaged $11.5M per month across six months, never dipping below $10.6M. That floor matters as much as the ceiling: it reflects what legal escrow looks like when the infrastructure is right. Funds arrive, they stay, and they compound into a deposit base that doesn't require constant reselling.

What changes when the infrastructure is right

The operational argument is straightforward. Purpose-built subaccounting handles the matter-level segregation, the bar compliance documentation, and the account volume without adding headcount. What once required manual workarounds runs on the platform.

But the more durable change is strategic. When a bank can say yes to a law firm compliantly, efficiently, at any volume, the relationship dynamic shifts. The bank isn't a commodity anymore. It's infrastructure. And clients who depend on your infrastructure for their compliance workflows don't leave for a better rate.

That same New England bank didn't stop with one commercial vertical. The platform that handled attorney trust accounts also extended into municipalities, property managers, healthcare organizations, and nonprofits — five commercial verticals, 258 clients, nearly 7,000 subaccounts — without adding operational complexity. The infrastructure turned out to be the foundation for much of their commercial client growth.

The question for your institution

Attorneys and law firms in your market are already solving their trust accounting problem somewhere. They've found a bank that said yes, or they've built a workaround that your institution plays no role in.

The question isn't whether the legal vertical is worth pursuing. The deposit profile alone answers that. The question is whether your bank has the infrastructure to serve it at the volume, the compliance standard, and the operational efficiency that makes it worth winning.

If the answer is no, that's not a client problem. It's a platform problem. And it's one that's solvable.