Custom Case Management for Solicitors: Now Within Reach

Two years ago, custom case management for solicitors was a project costing a couple of hundred thousand pounds. Very few firms could justify it, so almost everyone licensed a package and learned to live with it. That has changed. With AI accelerated development, a custom system built around your firm now typically costs between £50,000 and £80,000 and takes three to five months.

For many firms, that is less than two years of licence fees for a system they would otherwise never own and could never really change.

But price is only half the decision. Owning a system means looking after it, and that suits some firms far better than others. This guide sets out both sides honestly: what you gain, what you take on, and how to tell which way your firm should go.

What changed

AI has changed how software is built. Experienced engineers using AI tools can now design, write and test software far faster than they could two years ago. The quality bar is the same. The cost and the timeline are not.

That changes the maths for law firms. Custom software is no longer only for the largest firms, and the question is no longer "can we afford to build?" but "should we own our system, or rent one?"

The real cost of licences

Take a 20 user firm paying £55,000 a year in licences for its current case management system. That cost rises every time the firm hires, and usually every time the contract renews. After five years the firm has paid £275,000 or more, and still owns nothing.

Here is how that compares with a custom build of around £65,000:

Over five years	Cost	What you own at the end
Licensed package	£275,000 or more, rising with every hire	Nothing
Custom build, run by the firm	About £75,000: £65,000 to build, plus about £2,000 a year in hosting, and someone's time to look after it	The system, the code and the data
Custom build, supported by the builder	About £125,000: £65,000 to build, plus about £12,000 a year	The system, the code and the data

On those numbers, a custom system pays for itself in roughly 15 to 18 months from the licence saving alone, before counting any time your fee earners get back. A smaller firm on cheaper licences will see a slower payback, which is one of the reasons building is not for everyone.

The case for owning your system

It fits how your firm actually works

Off the shelf systems are designed to suit thousands of firms at once, which means they suit none of them exactly. So the firm bends to the software. Steps that do not fit get done by hand, matters get tracked in email, and a spreadsheet appears next to the system, then another.

A custom system starts from your workflow. The matter types, steps, checklists and reports are the ones your teams already use. When the system fits, people keep it up to date, and the reports the partners rely on are true again.

The costs do not grow with headcount

Licences are priced per seat. Every new fee earner, paralegal or secretary adds to the bill. A system you own is not. Hire ten more people and the software bill barely moves.

It changes when you need it to

With a package, a change request joins the vendor's queue. Their roadmap is set by their largest customers, and a 25 person firm has very little say in it. With your own system there is no queue. Small changes take days and a new workflow takes weeks.

It connects to everything else the firm uses

A package connects to the tools its vendor has chosen to support, on the vendor's terms and often at extra cost. Anything else means typing the same details twice, or exporting and re-importing spreadsheets.

Your own system can be built to connect to whatever the firm runs on: billing, accounts, appointment booking, client portals, e-signature, identity checks, document storage, Microsoft 365, and the portals and registries your practice areas depend on. Client details go in once. Time and disbursements flow to billing without being re-keyed. A booking made online opens a matter. A client sees progress in a portal fed straight from the file.

Once everything is connected, the line between a case management system and a practice management system starts to blur, if it was ever really there. Instead of a case management system sitting next to a billing system, a booking tool and a portal, the firm ends up with one joined up way of working, built around how it actually runs.

It grows with the firm

This is the advantage firms tend to underestimate. Firms do not stand still. They add practice areas, open offices, take on teams from other firms, merge, change their fee models and restructure. Each of those changes puts pressure on the system.

With a package, the firm has to fit the change into whatever the software already does. With a system you own, the system follows the firm. A new practice area gets its own matter types and workflow. A merged team's way of working can be brought in rather than forced out. A move to fixed fees gets the reporting it needs. The system becomes a record of how the firm works now, not how it worked when the contract was signed.

It keeps up with new technology

AI is improving every few months. New models are better at reading documents, drafting and checking. New tools appear for signing, identity checks, client portals and search. Regulators keep moving too, from the SRA's August 2026 warning notice on AI to its proposals to write AI into the competence statement.

On a package, you get new technology when your vendor decides to add it, at their price, using the AI provider they chose. On your own system, you decide. When a better AI model arrives, it can be swapped in. When a new tool would help, it can be connected. When the rules change, the workflow can change with them. The system you build today is a starting point, not a fixed product.

You own the data

Your matter data sits in your own cloud account, not inside a vendor's product. You can report on it, connect it to other tools and take it with you if you ever change direction, without exit fees or weeks of extraction work.

The honest downsides

Owning a system is not free of effort. These are the things firms need to plan for, and the ones a good supplier should raise before you ask.

Someone has to own it

A package comes with a vendor who decides what happens next. Your own system comes with decisions. Someone in the firm, usually a partner or operations lead, needs to own it: collecting requests, agreeing priorities and signing off changes. It is not a full time job, but it does need a named person and an hour or two a month.

It needs looking after

Software is never finished. Hosting has to be paid for and monitored. Security patches have to be applied. Backups have to be tested. The libraries the system is built on get updated, and the system has to keep up with them. If AI is built in, the AI provider's terms and models change over time and need checking. None of this is difficult, but it has to happen, every month, whether anyone is thinking about it or not.

You carry the upfront cost

A package spreads its cost over time. A build front loads it. Even when the five year numbers are clearly better, some firms would rather not commit £50,000 or more in one go. A fixed price, agreed before the build starts, at least makes the number predictable.

You depend on whoever supports it

If one supplier builds and supports your system, you rely on them. That is a real risk, and the answer is not to trust the supplier more. It is to make sure the firm owns the code and the data, that the system is built on mainstream, widely used technology, that it is properly documented, and that it runs in the firm's own cloud account. Then any competent developer can take it over.

Migration takes effort

Moving matters, clients, documents and history out of an old system is the hardest part of any switch. It needs care, checking and some of your people's time. Running the old and new systems side by side for a while, and moving one practice area at a time, takes most of the risk out of it.

Your people's time during the build

A system built around your firm needs input from your firm. Fee earners, your accounts team and partners will need to give time during scoping, and to test working software as it is built. It is a few hours each, spread over a few months, but it is real time.

Some things are better bought

Client money is the obvious example. A proven legal accounting ledger, trusted by your COFA and your reporting accountant, is worth more than a bespoke one, however good. The sensible approach is to connect to it, not rebuild it, and to put the effort into the matters, workflows, documents and reporting instead.

Owning versus renting, side by side

	Licensed package	Your own system
Fit to your workflow	Partial. The firm adapts to the software	Close. The software adapts to the firm
Cost as you grow	Rises with every user	Mostly flat
Changes	Join the vendor's queue	Days or weeks, on your priorities
New technology and AI	When the vendor adds it, on their terms	When you choose, on your terms
Connections to other tools	Limited to what the vendor supports	Built to connect to whatever the firm uses
Upkeep	Handled by the vendor	Handled by you or your support partner
Who decides what comes next	The vendor	The firm
Upfront cost	Low	Fixed price build
Your data	Inside the vendor's product	In your own cloud account
If the supplier goes	Your system goes with them, or changes hands	You keep everything and find another developer

Two ways to keep it running

Once the system is live, there are two sensible ways to look after it.

Run it yourselves. Hosting, backups and the essentials usually come to around £2,000 a year. The bigger cost is not the hosting. It is having someone who can keep an eye on the system, apply updates and fix small problems when they come up. That might be someone in the office with a technical bent, your IT provider, or a freelance developer on call. With a proper handover from whoever built it, good documentation and today's AI tools, that work is far easier than it used to be. It is still a real cost, and worth budgeting for, but for most firms the benefits of owning the system comfortably outweigh it.

Have your builder support it. Usually £10,000 to £15,000 a year, less for smaller systems. That covers hosting, security patching, fixes, small changes, keeping the technology up to date, and someone who knows your firm when something goes wrong. For most firms without an in house developer, this is the safer choice.

Either way, it is worth setting aside a small annual budget for improvements. The firms that get the most from owning their system are the ones that keep improving it as they grow.

What a build looks like

A good project runs in clear stages, with the price fixed before the build starts:

1. A free half day review. Time with your partners and the people who run the matters, to see how the firm works and where the current system gets in the way.
2. A working prototype. Built from that review, so you see your own workflow on screen before you have paid for anything.
3. Scoping. The prototype is refined with your fee earners and your accounts team, every connection is mapped, and the price is fixed.
4. Build. Working software every fortnight, so your people can test it and change their minds while it is cheap to do so.
5. Pilot. A team runs real matters through the new system alongside the old one.
6. Migration and launch. Data moved across and checked, one practice area at a time, with training built around your own matters.

Is it right for your firm?

Building usually makes sense when:

• you have more than about 20 to 25 fee earners, so licence costs are significant;

• your workflow does not fit the package, and people work around it every day;

• you are growing, adding practice areas or expect to change how you work;

• you want AI built into the work on your own terms. Buying usually makes more sense when:

• you have fewer than about 15 fee earners and a good cloud package already covers what you do;

• your workflow is standard for your practice area and your current system handles it well;

• nobody in the firm has the time or appetite to own a system. Sometimes the right answer is neither. If your system is fine but the admin around it is not, building what is missing around it can be faster and cheaper. And if you are not sure where the real problem is, start with an Assessment.

Questions to ask any supplier

Whoever you choose to build with, ask these before you sign:

• Who owns the code and the data? You should, from day one.
• What technology is it built on? It should be mainstream and widely used, not anything exotic.
• Who keeps it up to date, including security patches and the libraries it depends on?
• How will our data be migrated from the current system, and how is it checked?
• Where is it hosted, and what security testing and backups are in place?
• What happens if we want to change supplier, or if you stop trading?
• How are compliance needs handled, such as audit trails, conflict checks and record keeping?
• What does support cost after launch, and what is included?