Skip to content

Integrations

Connects to the systems your firm already runs

You may not need to replace your practice software, or add anything to it. Before anyone builds or buys, check whether what you already pay for covers the gap. If it doesn't, connecting two systems can cost less than replacing one, so we build what's missing and connect it to the rest, wherever the system offers access. Where a system publishes an API, as Clio, Actionstep and Microsoft 365 do, we can build against it. LEAP, Proclaim and InfoTrack decide who connects to their platforms, so with those we connect where the vendor gives access.

What a connection means

An API is how a software vendor lets other systems read and write data in a controlled way. When a system has one, we can build tools that sit alongside it: an intake form that creates the matter, a document generator that files the finished letter in the right place, a dashboard that reads time and billing data without anyone exporting a spreadsheet.

What we can connect depends on what the vendor exposes, and that changes over time. So the first thing we do on any integration project is check what your system allows today, for your firm’s account, and tell you what’s possible before any build starts. Each connection is built for your firm’s project; we don’t sell a ready-made connector.

A connection has running costs of its own, because someone has to keep it working when a vendor changes its API. We count those against the cost of a replacement (licences, data migration, staff time to change and any overlap while both run) so you can compare the two. An AI and technology review sets out that comparison if you haven’t yet decided whether to change anything.

Systems

Clio

Clio publishes an API that covers matters, contacts, documents, calendar entries, tasks, time entries and bills. That makes it a good base to build on. Examples of what can be connected: an online enquiry form that creates the contact and opens the matter in Clio, documents generated from matter data and saved back to the matter, and reports that combine Clio's time and billing records with figures from elsewhere in the firm.

API access

Actionstep

Actionstep has an API covering its matters (which it calls actions), participants, custom data fields, documents and time records. Actionstep is built around workflows the firm configures inside it, so a tool we add would sit at the edges: getting structured data in from a client portal or intake form, producing documents from the matter's fields, and reporting across matters in a way the built-in reports don't.

API access

Microsoft 365

Microsoft's API gives access to Outlook mail and calendars, SharePoint and OneDrive files, Teams and user accounts. We could use it to let people sign in to a tool we build with the account they already have, so access would follow the roles your firm has set. We can also file emails and attachments to the matter, save generated documents into the right SharePoint folder, and put key dates into fee earners' calendars.

API access

LEAP

LEAP is practice management software for law firms, and it controls who can connect to its platform. Where LEAP gives access for your firm's project, we can build around it in the same way: getting matter data in and out, and producing documents and reports from it. Where it doesn't, we look at what else can be done, such as working from exports or keeping a tool alongside LEAP with a clear manual step between them, and we'll be clear about the trade-off.

Where the vendor gives access

Proclaim

Proclaim is a case management system in which firms configure their own workflows. Access for outside developers is set by the vendor. Where the vendor gives access, we can connect intake, client updates and reporting to the cases in Proclaim. Where access is limited, we'll say so at the understand stage, and help you decide whether the tool is still worth building.

Where the vendor gives access

InfoTrack

InfoTrack provides searches, ID checks, e-signing and filings for law firms. Where InfoTrack gives access, we can bring search orders and results into the matter, so the fee earner isn't copying references between screens. As with the others, what's possible is confirmed with the vendor before we plan around it.

Where the vendor gives access

System names are trademarks of their owners. Basys is not affiliated with or endorsed by them.

Systems not on this list

Plenty of firms run accounts packages, document management or older practice systems that aren’t named here. If a system has an API, or the vendor will give access, we can usually connect to it. If it has neither, we’ll talk through the options, including moving the data out of it.

Questions

Integration questions

Connections touch client data, so they follow the same rules as everything else we build. Our security and data page sets those out.

Do we have to replace our case management system?

Not necessarily. Keeping it as it is may be the answer. If something is missing, building what your current system doesn’t do and connecting it in is usually the smaller and less disruptive route, and it can cost less. If replacing it is the better answer, we’ll explain why, and we can handle the data migration.

What do you need from our vendor?

Sometimes nothing beyond your firm’s own API credentials. For systems where the vendor controls access, we may need you to request it on your firm’s behalf. We’ll tell you exactly what to ask for.

What happens if the vendor changes its API?

Vendors do change their APIs, and they usually give notice. Keeping connections working after a change is part of the support we agree with you after launch, which is covered on how we work.

Talk to us

Tell us what your firm pays for and what's taking up your fee earners' time. We'll arrange a short call and tell you whether a review is worth doing.