Skip to content

How we work

How we work

Technology spending in a law firm can go wrong in a few ways. It can be decided by people who don't do the work, or on the word of someone selling the answer, and the cost of running it may only show up later. We work in two parts so you can stop after the first: we find out what's worth doing, and then, only if it pays, we build it.

Part one: find out what's worth doing

01 Understand

This stage is the review. Before it starts, you'll already have the short written outline we send after the first call. Now we go into detail with the people who do the work: a fee earner, a secretary, whoever opens matters and whoever chases the bills. We watch how a matter moves through your firm, where it gets typed twice, where it waits for someone, and where the current software stops and a spreadsheet takes over. We also go through what you run and what you pay, and check what your existing systems allow us to connect to. We don't need your files or any client data handed to us. Sitting with your staff may mean seeing live matters, so a confidentiality agreement comes first.

02 Findings

You get written findings: what to do and in what order, what to leave alone, what you could stop paying for, and the sums behind each one. If a product you can buy will do the job, or what you've already got will, the findings say that. The AI and technology review page has the detail.

03 Decide

You decide what happens next. Many firms could reasonably stop here and act on the findings themselves, with another supplier or with us.There's no obligation to build.

Part two: build it, if that's the answer

The findings then become the plan: what we'd build, what it connects to, what it would cost to run and the order of the releases. If your firm has already decided what it wants, we write that plan after enough time with the people who do the work.

04 Prototype

Before the real build, you see a working version on screen. It looks and behaves like the finished tool, with sample data, so the people who'll use it can click through and tell us what's wrong. Changes cost less at this point than after the build, so we'd rather hear the objections now.

05 Build

We build in small releases, each one doing something useful on its own. Every release is built and tested against your matter types using sample or anonymised data. Once a release is live in your firm's own system, we check it on real matters, with your agreement, before anyone depends on it. You see progress every couple of weeks, and the order can change if something more urgent comes up.

06 Support

Once the system is live, we stay on. We fix what breaks, improve what people find awkward, and extend it as the firm changes. Most of the value in firm software comes after launch, when people start using it on live matters and ask for the next thing.

What we need from you

We’d ask for five things:

  • Time with the people who do the work, and short check-ins after that
  • A list of what you run and what you pay, even a rough one
  • Sample or anonymised examples of your matters and documents to build against
  • One decision-maker who can say yes or no when the team disagrees
  • Someone who can request access from your software vendors if we need it

We don’t need a full specification document. Writing that is part of our job, and it’s better written after we’ve seen the work.

What you get

  • Written findings with the working shown, which you can use with any supplier
  • If you go on to build: working software early, in the prototype, rather than a document describing it
  • Small releases you can use as they arrive
  • Documentation your team can follow, for the people who use the system and for anyone who maintains it
  • A system built for your firm, on terms set out in your agreement
  • Direct contact with the people doing the work: the directors plan to do it themselves

After launch: support, changes and hosting

Support. Before launch we agree how support works: how you report a problem, how quickly we respond, and what’s covered. Keeping connections to other systems working when a vendor changes its API is part of it.

Changes and new features. Firms change. A new practice area, a new regulation, a new partner who wants a different report. Small changes go into the support arrangement. Larger pieces of work go through the same steps as the first build, at a smaller scale.

Hosting. If we host the system for you, we intend to host it in the UK by default, or in the EU if your firm prefers, and set up access controls from the start. Your data is shared only with the hosting and AI providers named in your agreement. The security and data page explains where data lives and who can reach it.

If you ever leave

Firms change suppliers, and they should be able to without a fight. Your data stays yours, and you can take it with you.When a firm leaves, we intend to export its data in a form another system can read, hand over the documentation, and help with the handover to whoever takes over. The terms will be set out in your agreement before any work starts, so nobody finds out what they own at the point they want to leave.

Questions

Questions about how we work

Do we have to build anything?

No. Part one stands on its own, and the findings may tell you not to build anything.

What does the review look at?

How your people work, what you pay for, where AI would help and where the firm is exposed. The AI and technology review page goes through each.

Will you see client files during the review?

You won’t need to hand any over. We may see live matters while sitting with your staff, which is why a confidentiality agreement comes first.

How long does a project take?

It depends on the size of the problem. A single tool, such as an intake form that opens the matter, is a much shorter piece of work than a new case management system. The detailed plan at the end of the understand stage sets out the releases, so you can see what arrives first.

Do you work with small firms?

Yes. What we build is aimed at small and mid-sized firms, from sole practitioners to firms of a few hundred people. The method is the same at either end. The size of the build is what changes.

Will we have to change how we work?

As little as possible. The point is to build around how your firm runs. Where a step only exists because the old software forced it, we’ll point it out, and you decide whether to keep it.

What if the project isn't working?

That’s why the prototype comes before the build and the releases are small. If something isn’t right, you’ll see it within weeks, and we change course early.

Who will we deal with?

The directors plan to do the work themselves, from the understand stage through to support.Basys is a new company, and you’ll know who is working on your system before the build starts.

Start with a conversation

If there's a process that eats into fee earners' time, or a bill you're not sure is worth paying, tell us about it and we'll say whether it's worth looking at.