Custom Kleos integration development
Appfront builds integrations with Kleos, Wolters Kluwer's cloud software for case and practice management at law firms. Kleos has standard integrations with accounting software and Microsoft 365, among others, and an API for custom work. We use that API to connect Kleos to your firm's other systems, such as a client portal, an intake form, a reporting tool or a custom application.
What is a Kleos integration?
Kleos is Wolters Kluwer's cloud software for law firms, covering case management, documents, time recording and billing. Kleos has standard integrations, for example with accounting software and Microsoft 365. There is also the Kleos API, which lets a firm connect Kleos to specialist applications, reporting tools or in-house systems.
Many firms use systems alongside Kleos: a website with an intake form, a client portal, a CRM for relationship management, or an application for a specific area of law. A new matter from intake is created in Kleos by hand. A client asks by email for the status of their case. And productivity reports are compiled from exports into a spreadsheet.
We build custom solutions because firms differ: which systems you have alongside Kleos, which data needs to move in each direction, and who should see it. What the API makes possible and under which conditions is set out in Wolters Kluwer's documentation; we will look into that in the first step. What you may do with client data is governed by your professional rules and the GDPR.
Kleos connected
Files, relationships and hours between Kleos and your other systems, via the API.
New matters, automatically
An intake on the website becomes a file in Kleos, without retyping.
Insight for clients and the firm
Status for clients in a portal, and reporting for the firm.
How we build your Kleos integration
We start with your firm: which systems you use alongside Kleos, which data is currently moved by hand from one to the other, and who needs to see what. Then we look at what the API offers for your situation. We build first the integration that removes the most manual re-keying, and expand from there.
Your systems alongside Kleos, data and who needs to see what.
What the Kleos API offers for your situation.
Files, relationships and hours back and forth, with controls.
Go-live, monitoring, and maintenance when Kleos changes.
What a Kleos integration does in practice
The components below come up in almost every Kleos integration. Which ones you need depends on your firm.
Files
Creating and updating files.
Relationships
Clients and counterparties kept aligned.
Intake
A new matter from the website.
Hours
Activities for reporting or invoicing.
Portal
Status and documents for clients.
Reporting
About files and productivity.
Who we build Kleos integrations for
The integration is intended for firms and vendors who want to connect Kleos with other systems.
Law firms
Kleos alongside a portal or CRM. Avoiding retyping is the core.
Specialist firms
One application per practice area. Files matter most.
Larger brokerages
Steering on productivity. The reporting is what is needed.
Software suppliers
A product for lawyers. The API is the core.
Technology and integrations
This page is about integrations with Kleos. For law firms there is our page on law firm software, for legal documents our page on legal document software, and for legislation in your own systems our page on BWB integration. You can read about our way of working under getting software built.
Why choose Appfront for your Kleos integration?
A matter retyped from intake, and a client emailing for an update, cost a firm time every day. That is what we build around: Kleos connected to your systems, new matters automatically, and insight for clients and the firm.
Less retyping
Data moves back and forth automatically.
Clients kept informed
Status in the portal.
Steering
Reporting without exports.
Security and privacy in a Kleos integration
The integration handles confidential client data, which is subject to professional secrecy. Only the data that is needed is exchanged, access credentials are stored encrypted and used only by the integration, and every message is logged.
The integration runs in a European data centre or in your own environment, with encrypted storage and daily backups.
Frequently asked questions about a Kleos integration
Questions law firms ask before starting with this.
Kleos is cloud software from Wolters Kluwer for law firms, with file management, documents, time recording and invoicing. Firms work with it from the browser, in the office or on the move.
Yes, including with accounting software and Microsoft 365, so invoices reach your bookkeeping and email and documents reach the case file. If your system is among them, you don't need a custom integration. A custom integration is for systems that aren't on that list, such as your own portal, intake tool or application.
Through the Kleos API, which Wolters Kluwer provides for integrations with other systems. We look at what the API makes possible for your situation, and under which conditions, in the first step.
Yes, if the API allows it for your situation. A completed intake form becomes a new relationship and a new file, ready for the conflict check and the matter, without anyone retyping anything.
Yes, through a client portal connected to Kleos. A client can see the status and the documents you share, and doesn't need to email to ask how things are going. You decide what you share for each case.
Then we adapt the integration. In our maintenance we keep track of changes to the API and test the integration before any change affects your firm. That way the integration keeps working, even when Wolters Kluwer adds new features or integrations to Kleos.
For firms that use Kleos alongside their own portal, intake tool, CRM or reporting tool, and for software vendors who want to connect their product to Kleos. For a firm that only uses Kleos and its standard integrations, a custom integration is usually not needed.
Want Kleos connected to the rest of your practice?
Tell us which systems you use alongside Kleos and which data is currently transferred by hand. We'll show you what the integration via the Kleos API would look like.