Skip to content

Services

Bespoke software for law firms

Software that doesn't fit gets paid for twice: once in the subscription, and again in the staff hours spent on the spreadsheet beside it. A conveyancing team doubles its volume, a private client department now does more lasting powers of attorney than wills, a PI team is working two claims portals at once, and each change leaves another list somebody has to remember. A system of your own can win that time back, and it may replace a service you pay for every month. It can also cost more than it saves, so we work out which before anyone writes code.

Who this is for

Small and mid-sized UK firms where a partner, practice manager or COO can point at a process and say it takes too long and nobody owns it. Perhaps one department doesn’t suit a system the rest of the firm is happy with. You might be on a product the vendor has stopped developing, or paying for a service few people use.

Stopping a service you pay for

Sometimes a firm pays every month for a service when a small system of its own may be easier to use, or a simpler fit for the work. A tool bought for one job, with most of its features untouched, deserves a second look.

Someone has to support whatever you bring in-house, though. They fix it when it breaks, keep it working when a connected system changes, and answer the phone when the person who understands it is on holiday. That costs money, whether they’re on your staff or at a supplier like us. A subscription pays someone else to do all of it, so cancelling one can leave you with something cheaper on paper and harder to live with.

Working out whether a build pays

For a particular process, we’d count these with you:

  • Staff hours: who does the task, how often and for how long, and what that time costs. Only hours the system would free up go in.
  • What you’d stop paying: the subscription, per-user fees or support contract the build would replace, and the date the contract lets you leave.
  • The build, including the time your own people spend on it.
  • Running and support, every year: hosting, usage fees, a support arrangement, and changes when another vendor alters its API.
  • Any move: data migration, training and a period of running both systems.

Then we compare them over the years you expect to keep the system. If the hours and fees don’t clear the build and running costs, the answer is no.

A build also fails the test when the task only comes up a few times a month, when a feature of your current system would do the job once someone switches it on, or when a cheaper plan covers it. Some things are best left alone. If you’re not sure where you stand, an AI and technology review would answer that first. You may not need a build at all, and the written findings would say so. We do build software, so test our reasoning on any recommendation to build: the assumptions are written down, and you can ask someone else for a second price.

Build, buy or extend

  • Buy when your work is close to what the market product assumes. Standard residential conveyancing on a well-supported platform rarely needs custom code.
  • Extend when the core system is fine and one part of the work isn’t. If your system offers API access, we can build a tool alongside it that reads and writes the same matters, so fee earners still have one record per client.
  • Build when no product fits without heavy workarounds: a niche commercial practice, a high-volume team with its own process, or two firms combining their systems after a merger.

Most of the projects we expect to take on are extensions.

We connect to systems that offer API access, including Clio, Actionstep and Microsoft 365. LEAP, Proclaim and InfoTrack are possible where the vendor gives access, as the integrations page explains.

Where a build can save time, by practice area

Each of these takes copying and chasing off a fee earner’s desk, and none of them makes a legal decision.

  • Conveyancing: a sale file that fills itself from the TA6 and TA10 the seller completes online, chases the replies still missing, and drafts the completion statement from the figures on the matter for the fee earner to approve.
  • Private client and probate: an estate tracker listing every asset and liability, recording each valuation and closing letter as it comes back, and producing a first draft of the estate accounts from those entries.
  • Personal injury: a limitation diary where the fee earner sets or confirms the limitation date on each new matter, the system reminds the supervising solicitor at set points before expiry, and a file can’t close without a recorded reason.
  • Employment: a tool that turns the client’s dates, pay and pension details into a first schedule of loss for the fee earner to check.
  • Family: a Form E disclosure tracker that shows the client and the fee earner which documents are in and which are still outstanding.
  • Commercial: a due diligence tracker for a share purchase, linking each request, reply and issue to the relevant part of the disclosure letter.

How a project runs

We’d begin with written findings on the process, unless your firm has already decided what it wants. That means sitting with the people who do the work and writing the process down as it runs today, workarounds included. An outline follows, with what the system would cost to run, and your fee earners then click through a working prototype on sample data. We build in short rounds on sample or anonymised data, and check each release on real matters in your live system, with your agreement. If a build replaces an old system, the case management and CRM page explains how the data moves.

We’ll need time with the people who know the process and one person to settle questions. See how we work for each stage.

Who owns the software

The software is built for your firm, around your matters, your precedents and your reporting lines. We aim to document it so that another developer could pick it up. Who owns the code and the data is set out in your agreement.

Data and confidentiality

Access is set by role, so a trainee in the conveyancing team doesn’t see family files unless you decide they should, and each matter keeps a record of who did what. We’d host in the UK by default, or the EU if your firm prefers, and data is shared only with the hosting and AI providers named in your agreement. We build with the SRA’s confidentiality and client care duties in mind. The security and data page has the rest, including where compliance responsibility sits.

Questions

Questions firms ask

Is bespoke software only for large firms?

No. A focused tool that fixes one process in one department is a much smaller project than a whole system.

How much would we save by bringing a service in-house?

We can’t say before we’ve looked, and Basys is new, so we have no figures from other firms to quote. You’d see the figures for your firm, support included, and they may favour the service you already have.

How long does a build take?

You get a timescale after the first stage, once we’ve looked at the work. Larger builds are split into parts your team can use as they arrive.

Who looks after the software once it's live?

We intend to, under a support arrangement agreed before launch and costed from the start.

Start with one process

If your current software doesn't handle a process, or you doubt a bill, talk to us. If you'd rather read the stages first, see how we work.