Services
Case management and CRM, built or connected
Per-user fees for case management and CRM come round every year, and the cost of a poor fit doesn't appear on any invoice. It sits in the PI team's spreadsheet beside the system, the CRM nobody trusts because it knows nothing about the matters, and the WIP that goes missing when time is recorded in one place and billed from another. There are good products on the market, and the cheapest answer may be to keep yours and use it better. We look at both and say whether to keep, connect, replace or build.
Who this is for
Firms that have outgrown a system, or never quite fitted it. Picture a commercial practice whose CRM can’t tell it which matters it has won, a firm on a product the vendor has stopped developing, or two merged firms reconciling systems by hand.
Counting the cost of each route
Start with the bill: seats, including licences for people who’ve left or barely log in, add-ons, support, and the date your contract lets you leave. Then count staff hours lost to double entry and side spreadsheets, and ask who could tell you how much WIP slips through.
Then cost the route you’re considering. Replacing a system adds a subscription or build, migration, training and lost pace. Connecting adds a build plus upkeep whenever a vendor changes its API. A custom system adds all of that, and you carry its support.
Sometimes none of those is worth it. Removing unused seats, moving to a cheaper plan or switching on a module you already pay for may cover most of the gap. Your vendor may offer its own Outlook add-in. A system with a few annoying screens and years left on its contract may be best left alone. If you aren’t sure, our AI and technology review compares the routes. No build may be needed, and the findings are written to say so. We also build, so test any recommendation to build: the assumptions are written down for you to take elsewhere.
Stopping a service you pay for
A firm can end up paying for a service when an in-house solution may be easier or simpler, especially for a single job done alongside the main system.
Someone then has to support it. A subscription includes the fixes, the upkeep and the person to ring. In-house, that falls to your staff or a supplier you pay, for as long as the firm relies on the tool. If it would have no owner, keep paying. We’d also be slow to bring core case management in-house at a small firm, because far more depends on it than on a side tool.
Built, extended or connected
A custom system
For a practice whose work doesn't match what the market products assume, we can build the matter system around it: a high-volume conveyancing team with its own stages and checks, a niche commercial practice, or a firm whose departments each need different matter screens. We'd say early whether a job that size suits a small new company.
Extending what you run
If the core system is fine and it offers API access, we can build alongside it: a screen for a process it doesn't support, an automated step it can't do alone. Fee earners keep one record per matter, because the extension reads and writes the same data. We connect to systems that offer API access, including Clio, Actionstep and Microsoft 365; for LEAP, Proclaim and InfoTrack, the vendor has to give access. We check what that allows for your firm before any work, as the integrations page explains.
Connecting the systems you have
Examples of what can be connected: Outlook emails filed to the right matter through Microsoft 365, or a new client added in the CRM opening as a matter with the contact details already filled in.
CRM that knows about the matters
A law firm CRM is only useful if it’s linked to the work. Built around the matter, every contact shows the matters they’re on, every introducer shows what they’ve referred and what it was worth, and every lost enquiry carries a reason. Your business development lead can see which estate agents sent conveyancing work this quarter.
Examples by practice area
- A conveyancing system where each matter moves through your own stages, with exchange blocked until searches, mortgage conditions and source of funds checks are signed off.
- Probate matters holding the full estate inventory, with a task per asset and the estate accounts drawn from them.
- PI matters tracking each defendant’s insurer, the claims portal stage, medical evidence and limitation in one view, with the supervisor’s caseload screen on top.
- Employment matters carrying tribunal deadlines and the ACAS early conciliation dates from the start.
- Family matters keeping hearing dates, court orders and financial disclosure together, with access tighter than the rest of the firm’s files.
- Commercial matters linked to the company, its directors and its past transactions, so a new instruction starts with the history.
Data migration
Migration is where a change of system gets expensive, so we’d cost it first. We map every field from old to new: clients, matters, contacts, key dates, documents, time entries, unbilled work and closed files. You decide with us what moves, what goes into a searchable archive, and what your retention policy says can be destroyed. Trial migrations run on a test copy of your real data, under a data processing agreement, and your staff check a sample of matters against the old system before the final move. We plan for the old system to stay readable until you’ve confirmed nothing is missing, and that needs checking against your contract with its vendor.
Billing and time recording
Linking time recording and billing sends a fee earner’s time entries to the right matter, ready for billing without re-keying, and fixed fee matters warn the supervisor when recorded time passes the fee. Your accounts team keeps control of the client account and the posting rules.
From findings to release
If your firm has already decided what it wants, we can go straight to the outline. Otherwise findings come first, from seeing how each department uses the current system. The outline sets out what we’d build and what it would cost to run, and your fee earners click through a prototype on sample data. Each release is built in a short round on sample or anonymised data, then checked on real matters in your live system, with your agreement. We’ll need time with each department and a decision-maker. See how we work for each stage.
Ownership of the system
The system is built for your firm, and the agreement sets out who owns its code and your data.
Access and client data
Case management holds everything, so we design access first. Permissions follow your teams and roles, sensitive matters can be restricted further, and every change is logged. We’d host in the UK by default, or the EU if your firm prefers, sharing data only with the providers named in your agreement. We build with the SRA’s confidentiality and client care duties in mind. See security and data for more, including what stays with the firm.
Questions
Case management and CRM questions
Should we build our own case management system or buy one?
Buy if a product fits with ordinary set-up. Build only when products would need heavy workarounds. In between, extend.
Can you add to Clio instead of replacing it?
Clio publishes an API, so we can check what it allows for your firm and build screens, steps and reports alongside it.
We use LEAP or Proclaim. Can you connect to them?
Where the vendor gives access. We check what’s available at the start, before any work is agreed.
How much could we save by changing system?
We don’t quote figures, and as a new company we have none from other firms. Staying put may turn out cheaper once migration and training are counted.
Where to begin
Bring your renewal date and the part of your system that costs the most hours, then talk to us. Or start with the method: see how we work.