The licence renewal arrives. You sign it. The number's the same as last year give or take a percent, it goes through procurement, and you don't think about it again until the next cycle.

That's the bit of the cost most CIOs can quote from memory.

The bit they can't is everything else. The specialist sitting in IT whose role exists because the platform needs a specialist. The middleware running quietly between the automation tool and the DMS. The consultant invoice that turned up after the last template overhaul. The deal that ran two days slow because the template wasn't ready.

Add it up and the number most firms land on is three to four times the licence fee.

What total cost of ownership really covers

Four costs tend to dominate, and none of them sit on the renewal invoice.

Specialist headcount. Legacy automation needs dedicated technical expertise to build and maintain. That's at least one full-time role, sometimes two, and it's one of the harder roles to recruit for. The person you eventually hire isn't writing documents. They're operating the system that writes them.

Middleware. Most legacy platforms predate modern API standards. Integrations to the DMS, billing systems and client portals tend to be bespoke pieces of infrastructure built years ago, often by someone who's no longer in the firm. They run quietly in the background until something upstream changes.

Consultant dependency. Template overhauls, complex logic updates, new practice group rollouts. The internal team can do some of it. The rest goes out to a consultant on a day rate. None of those days appear on the platform invoice.

Deal friction. When the template queue is backed up, associates draft manually. Senior lawyers review documents that should have been standard. Deals move more slowly than they should. That cost doesn't show up anywhere, but if you ask the partners, they'll tell you.

The middleware story we hear weekly

A global law firm we worked with last year had been paying just over £100,000 a year in middleware costs.

The middleware existed for one reason: to keep their legacy automation tool talking to their DMS. It had been there for years. Nobody questioned it because it had been there for years.

Within three months of moving to Avvoka, the middleware was retired. The integration now runs through a single API connection, owned and maintained by the firm's in-house team. The annual saving covered the cost of the migration in year one.

The platform had never felt expensive. The infrastructure around it had been quietly expensive for a long time.

Start with the cost of staying put

Total cost of ownership isn't a number designed to make old platforms look bad. It's the number you actually want when the renewal comes around.

The firms that evaluate migration seriously usually start here. Not with a feature comparison. With a fair read of what they're already paying to stay where they are.

Most are surprised. Some are uncomfortable.

A few then start moving.

The guide breaks down the full cost picture, license, headcount, middleware, and deal drag alongside how firms have made the move without disrupting active matters. Download it here.