How to Choose a Legal Technology Supplier: The Questions Worth Asking Before You Sign

Chuck Silva
|
PublishedNovember 16, 2026
|
Clock8 min read

Key Takeaways

  • Most legal technology supplier decisions are made on the demo. Most supplier relationships succeed or fail after go-live.
  • Ask for evidence: what the supplier fixed for a similar firm in the last 12 months, and how they measured it.
  • Ask about their last complaint and what they did about it. The answer tells you more than a reference call.
  • Check which legal entity a security certificate actually covers, what's in scope, and who issued it.
  • Agree the handover before you sign: documentation, training, and who supports what's been built.

Five black document folders on a dark slate desk, one open beneath a brass loupe resting on an embossed seal, lit by warm orange light.

Most firms pick a legal technology supplier on the strength of a demo.

That makes sense on the day. The demo is clean data, a rehearsed presenter and the product at its best. Month 7 is when you find out what you actually bought: a matter-type change breaks a workflow, the person who sold you the system has moved on, and your IT team needs someone who picks up the phone.

We've had to answer every question below about ourselves this year. So this is the list we'd use if we were sitting on your side of the table.

What a Legal Technology Supplier Should Prove Before You Sign

Two people usually sign off a legal technology purchase. The COO or Finance Director owns the budget. The Head of IT or Innovation owns the risk if it goes wrong.

They need different proof. The COO wants to know the cost comes back, and when. The Head of IT wants to know it won't disrupt fee earners, and that someone will fix it fast when something breaks.

A good supplier can answer both with documents and numbers. Before the final round, ask every shortlisted supplier for 5 things in writing:

  1. A result from the last 12 months at a firm like yours, with a before and after figure.
  2. Their most recent formal complaint, and what changed because of it.
  3. The certificate behind every security claim in their proposal.
  4. Exit and handover terms, as a schedule to the contract.
  5. Their longest-running client relationship, and why it's lasted.

Each one is easy for a strong supplier and awkward for a weak one. That's the point.

Evidence Over Demos: Measuring What a Legal Technology Supplier Delivered

Ask this exactly: "What did you fix for a firm like ours in the last 12 months, and how did you measure it?"

A good answer is specific. It names a function (billing, intake, document review), a baseline, an after figure and who did the measuring. Something like: "Assessment time on new claims fell by a set percentage, measured from the case management system over 3 months, signed off by the client's operations lead."

Watch for these instead:

  • Percentages with no baseline. "40% faster" means nothing until you know faster than what.
  • Outputs dressed up as outcomes. "We deployed 12 automations" tells you about activity. Ask what each one saved.
  • Pilots presented as production. A 6-week pilot with 10 users is a promising start. Ask how many fee earners use it today.

Then ask to speak to the person at the client who owns that number. The sponsor who signed the contract will give you a warm summary. The person who runs the function will tell you what it took to get there, and what still annoys them.

One more question worth asking: "What would you do differently on that project?" A supplier who has a clear answer has been paying attention.

The Complaint Question

This is the question most buyers skip, and probably the most useful one on the list.

"Tell us about your last formal complaint. What happened, who handled it, and what did you change afterwards?"

Every supplier who has done real work for more than a year has had a complaint. If the answer is "we haven't had one," either the supplier is very new or they're managing the conversation.

What a good answer sounds like:

  • It's specific. A date, a client type, a named failure (a missed deadline, a data mapping error, a slow response during a go-live).
  • They own it. No blaming the client's data or the client's IT team, even if that was part of it.
  • Something changed. A new checkpoint, a different escalation route, a change to how they staff go-lives.

Reference calls are curated. The supplier picks the client, and the client is usually someone who likes them. The complaint question is harder to stage-manage, so it tells you how the supplier behaves when things go wrong, which is the only time it really matters.

Security Certificates: Entity, Scope and Certifier

Almost every legal technology supplier will tell you they hold ISO 27001 certification. Fewer buyers check what the certificate actually covers.

Ask for the certificate itself (a PDF, not a logo on a slide) and run 3 checks.

1. Which legal entity is certified? The certificate names a company and an address. A supplier with offices in 4 countries may have 1 certified entity. Make sure it's the one that will hold, process or support your data.

2. What's in scope? Every certificate has a scope statement listing the activities covered. If the service you're buying isn't described there, the certificate doesn't cover it, however prominently the logo appears in the proposal.

3. Who issued it, and are they accredited? ISO writes the standard. It doesn't issue certificates. A certification body does, and in the UK that body should be accredited by UKAS (or an equivalent national accreditation body). UKAS runs a free database, CertCheck, where you can search a supplier's name or certificate number and see the scope, the dates and the certification body in one place. Check the expiry date while you're there.

We apply the same test to ourselves. Our ISO/IEC 27001:2022 certificate covers 3Rive Technologies (Pvt) Ltd, our delivery centre in Colombo, Sri Lanka. It was issued by Bureau Veritas under UKAS accreditation and runs to May 2027. Our other offices aren't covered by it, and we say so. You can see the full details on our ISO 27001 page.

While you're on security, ask for the data processing agreement early. The ICO is clear that whenever a controller uses a processor, there has to be a written contract with specific minimum terms, including security measures, use of sub-processors and what happens to the data at the end. The ICO's guidance on what needs to be included in the contract is a good checklist to hold a supplier's draft against. Ask for their sub-processor list at the same time.

Exit Terms and the Handover

Talking about the end of a relationship before it starts feels awkward. Do it anyway.

The questions to settle before signing:

  • Who owns what we build together? Configurations, workflows, templates, integrations, prompts, trained models and the documentation behind them.
  • How does our data come back? In what format, how quickly, and at what cost.
  • What does exit assistance look like? How many hours, which named people, and for how long after notice.
  • What will our team be able to run on day 1 after the supplier leaves? If the honest answer is "nothing," you're buying a dependency.

Put the answers in a handover schedule attached to the contract. It should set a documentation standard, a number of knowledge transfer sessions and a transition support period. Then test it during the contract, by asking for the current documentation at the 6-month mark. If it's thin then, it'll be thinner at exit.

This is also where commercial models differ most. Under our Cognitive Outsourcing model, for example, the AI assets we build are handed back to the client at the end of the term. Whatever model you're offered, the question is the same: what do you keep if you walk away?

Why Clients Stay: What Happens After Go-Live

The best single signal of a good legal technology supplier is how long their clients stay. So ask directly: "Who's your longest-running client, and why are they still with you?"

For us, it's a top-30 global insurance-led firm we've been embedded with for 7 years. That relationship has outlasted several technology cycles, a lot of change in their team and a lot of change in ours.

Long relationships tend to share a few habits. Ask whether your supplier has them:

  • Named people after go-live. You should know who's on your account at month 6, and it shouldn't only be the person who sold you the system.
  • Cover for absence. Ask what happens when your main contact is on leave or leaves the company. Shadow cover, where a second person already knows your setup, is worth asking for.
  • A regular review with numbers. Ask to see a redacted quarterly review pack they've sent another client. If they don't produce one, you'll be the one chasing updates.
  • Honest roadmap conversations. A supplier who'll tell you when a feature isn't right for your firm is one you can plan around.

Your clients are asking harder questions about the tools their law firms use, a shift we covered in getting ready for clients who use AI too. The answers your supplier gives you are the answers you'll end up giving them.

Putting the Questions to Work

Add the 5 questions to your RFP and weight the answers. Give at least as much weight to evidence, complaints and exit terms as you give to the demo.

Then hold every shortlisted supplier to the same standard, including the incumbent. Most firms have never asked their current supplier for a complaint history or a certificate scope. It's a useful exercise either way.

If you'd like to see how we answer these questions, ask us. You can find out more about 3Rive, or get in touch and we'll walk you through our own answers, certificate included.

Frequently Asked Questions