Best Matter Management Software: How to Choose by Operating Problem

Most legal departments can list their open matters. Far fewer can say who owns each one, which entity it belongs to, or what it has cost so far. The problem is not the absence of a tool. It is the absence of a shared operating model that a tool can carry. Choosing the best matter management software starts with naming the operating problem clearly, then testing whether a given product can hold the structure you have already defined.

This article compares the main categories of matter management software by the problem each one is designed to solve, and explains what a global legal department needs to put in place before any product evaluation begins.

Which operating problem does your legal department need to solve first?

No single tool fits every legal department, because legal departments do not share the same operating problem. The shortlist below groups products by the problem they address most directly. Each category reflects a different starting point for a global in-house legal team.

If the main problem is outside counsel spend and invoice control, the tools that address it most directly are Brightflag and TyMetrix 360°. Both connect matter records to budgets, invoices, and vendor performance. They are built for teams where the relationship with outside counsel is as operationally significant as the matter record itself.

If the main problem is legal intake and request routing, LawVu and Checkbox are the stronger starting points. Both centralize requests from multiple channels, route them by urgency and matter type, and connect intake to the matter record. They suit teams where unstructured demand arriving through email, messaging platforms, or business portals is the primary source of operational friction.

If the main problem is configurable enterprise legal management across entities and jurisdictions, Mitratech TeamConnect and Onit Unity are the tools to examine. Both support matter templates, workflow configuration, approval circuits, and spend management at a scale that requires formal implementation and a defined operating model before go-live.

If the main requirement is transparent per-user pricing before a sales conversation, Xakia is the only shortlisted vendor that publishes its plan structure and per-user costs on its public pricing page. That makes it a practical starting point for a legal operations leader building a business case.

Start with the problem, not the feature list. The sequence matters: define the model first, then test how each product carries it.

Matter management tied to outside counsel spend

When outside counsel costs are a primary control problem, matter management and spend management need to live in the same system. Two products address this most directly.

Brightflag

Brightflag connects matter records to outside counsel collaboration, budgets, invoices, and spend reporting. Its matter workspace brings together matter details, status, tasks, milestones, documents, and updates. You define the types of legal work and the data each matter requires. Different departments can use their own views, and access is controlled matter by matter. That suits a global department where local teams and outside counsel need the right information without visibility into every matter across the group.

Brightflag also connects legal intake to matter creation, and supports finance integrations through email, batch files, or an API. It is a strong choice when the operating problem is a controlled view of matters and outside counsel costs. It is a weaker first choice if the main problem is broad employee self-service across many request channels.

TyMetrix 360°

TyMetrix 360° combines matter management with e-billing, invoice review, budget and accrual tracking, and analytics. Law firms can submit matter budgets for review, and the platform connects those amounts to invoicing workflows. It also covers billing guidelines, invoice appeals, firm relationships, and outside counsel performance. Analytics are configurable by entity, jurisdiction, firm, and matter type.

TyMetrix 360° fits teams that need formal billing rules, budget controls, and financial analytics alongside the matter record. If the priority is internal intake and task assignment rather than spend governance, it may be more system than the department needs at that stage.

Matter management built around intake and routing

When unstructured demand is the primary friction point, the right tool starts at intake and connects forward to the matter record, not the other way around.

LawVu

LawVu captures structured requests through a business portal, messaging platforms, and email. You collect information at intake, triage requests by urgency and risk, and route them to the right person or team. The matter record tracks responsibility, tasks, deadlines, documents, communications, and work type. Legal operations can report on request volume, department source, turnaround time, and team performance.

LawVu also supports self-service for contracts, templates, and legal resources, giving business users a controlled route for routine questions while matters that require legal judgment still escalate. Its wider workspace includes contract management, spend management, outside counsel collaboration, and reporting. Pricing depends on the capabilities selected and the number of users.

Checkbox

Checkbox centralizes requests from email, messaging platforms, web forms, and other configured channels. Before routing the work, the system captures the requester, matter type, assignee, documents, and other required details. Routing can use request type, expertise, workload, business unit, urgency, or other configured criteria. After intake, the workflow assigns tasks, requests approvals, escalates exceptions, and connects documents and deadlines to the matter record.

Legal operations can customize fields, statuses, matter types, intake forms, workflows, dashboards, and reports without code. Checkbox dashboards report on request volume, matter type, status, turnaround time, and team utilization. It is best for teams that want intake and workflow visibility to lead the matter management process. It is less suited than Brightflag or TyMetrix 360° when the main requirement is advanced outside counsel billing and spend analytics.

Enterprise configuration across entities and jurisdictions

Large or complex legal departments operating across multiple entities and jurisdictions need a system that can carry a formal operating model, not just a matter register. Two products are built for that level of configuration.

Mitratech TeamConnect

TeamConnect covers matters, documents, workflows, legal spend, e-billing, reporting, and analytics. It tracks matter status, deadlines, documents, tasks, budgets, and outside counsel performance. Its workflows handle intake, assignments, escalations, and approvals. The system supports reusable matter templates, business rules, dashboards, and integrations, with configuration tools that let teams manage rules, workflows, and notifications without custom code.

TeamConnect also supports country-specific approval and validation rules and pro-forma invoice workflows, which matter when legal spend crosses local invoicing systems and regulatory processes. Dashboards show matter volume, workload, cost, and risk across the group. It is a poor fit if the team has not yet agreed which entity owns a matter, which fields are mandatory, which approvals apply, and who may see the record. That structure must exist before the system can carry it.

Onit Unity

Onit Unity connects legal requests, matters, vendors, contracts, spend, workflows, and reporting. It routes requests and organizes matters across teams and business lines, tracking a request through its full lifecycle. The platform connects vendor oversight and spend management to the matter record, so the legal team can track budgets, invoices, vendor performance, and approval workflows in one place.

Unity supports no-code workflows and a library of community-created workflow patterns. Each workflow still needs a named owner, an approval threshold, an exception path, and a retention rule. It suits legal departments that want requests, matters, vendors, contracts, and spend in one legal operations program, particularly when managing the handoff from an internal request to an outside provider, an invoice, and a report.

SimpleLegal

SimpleLegal suits legal departments that want matter management, legal spend, vendor collaboration, and reporting in one system. It supports matter templates and configurable fields, matter groups for related work, and embedded document management. Permissions can be confidential, role-based, and matter-based, which matters when a global team handles employment, investigations, or acquisition work with restricted access. Reporting covers internal workload, external performance, staffing, budgets, vendor activity, and matter status. SimpleLegal sits within Onit’s enterprise legal management offering.

What to structure before you evaluate any tool

The issue is not which tool has the longest feature list. It is whether your legal department has defined the operating model that any tool will need to carry. A matter management system can only reflect the rules, responsibilities, and workflows that already exist in explicit form. When those rules live in people’s heads, or differ from one subsidiary to the next, no software resolves the underlying problem.

Before booking a demonstration with any vendor, a global legal department needs clear answers to four questions. First, which entity owns a matter, and does that ownership follow the entity where the legal risk sits, the entity where the contract is signed, or the entity where the work is performed? Second, which fields are mandatory at intake, and are those fields consistent across subsidiaries or adapted by jurisdiction? Third, who may see the matter record, and does access follow a user’s role, a specific matter, or both? Fourth, where is the final decision kept, and is that location the same for every matter type across every entity?

Each vendor will answer those questions differently. The answers will tell you more about fit than any comparison table. A useful demonstration should include a real matter type, a real entity, a real approval circuit, and a real exception. If the vendor cannot walk through that scenario, the product may not carry the operating model you need. For teams building that model in parallel with a tool evaluation, legal project management provides a useful framework for defining dependencies, responsibilities, and validation steps before go-live.

The same logic applies to AI agents. An AI agent operating inside a matter management system can only act reliably when the authority model is explicit: the entity, the jurisdiction, the applicable policy, the responsible role, the permitted data, the approval threshold, and the exception path. Without that structure, an agent increases volume without increasing control. AI automation in legal departments works when the organizational context is already governed, not when it is being built around the agent.

How Alf connects matter management to the operating model

Alf is the operating infrastructure for global legal departments: it connects people, processes, knowledge, and AI agents in one governed system. Where matter management software tracks what is happening, Alf organizes the legal organization itself, so that what is happening is always connected to who is responsible, which entity is involved, which policy applies, and what was decided.

In Alf, each dossier holds a chronological history of the matter: documents, communications, tasks, deadlines, validations, and decisions. Access rights are set by user, group, or dossier, so a subsidiary team sees what it needs without visibility into matters across the group that are not relevant to them. Configurable workflows and approval circuits reflect the rules of each entity without requiring a separate system for each one. When a new entity joins the group, it joins the existing operating model rather than creating a parallel process.

Alf’s features include centralized dossiers and documents, configurable workflows and forms, approval circuits, a shared calendar with deadline alerts, a chronological history for each dossier, dossier creation and connection from Outlook, document generation from Alf templates, electronic signature, role-based access rights, a multilingual interface, activity reports and dashboards, and an AI agent that works from the context of the dossier. Data is hosted in the European Union, encrypted at rest and in transit, and protected by two-factor authentication. Validations and decisions are logged, which makes it possible to respond when a regulator, a client, or leadership asks how a matter was handled or how AI was used.

Legal departments including Air France, SNCF, ENGIE Home Services, and CCI Paris Ile-de-France use Alf to run their teams, processes, and AI agents as one system. The goal is to scale legal operations without scaling complexity. A collection of tools is not an operating model, and the right moment to build that model is before the next entity, the next jurisdiction, or the next AI agent arrives.

Frequently asked questions

What is the difference between matter management software and enterprise legal management software?

Matter management software focuses on tracking who owns each matter, what its status is, which deadlines apply, and which documents are attached. It is the operational record of legal work in progress. Enterprise legal management software adds modules for outside counsel spend, e-billing, vendor management, invoice approvals, and financial controls alongside the matter record. The distinction matters when choosing a starting point: a team whose primary friction is intake and ownership tracking needs a different tool than one whose primary friction is invoice review and spend governance.

In practice, many products now cover both areas to varying degrees. The more useful question is which problem is most urgent and which product addresses it most directly at the level of configuration your department can actually implement. A system that covers everything but requires six months of configuration before it reflects your operating model may be less useful in the short term than a narrower tool that is live and adopted within the quarter.

What should a global legal department define before evaluating matter management software?

Four things need to be explicit before any product evaluation begins. First, which entity owns a matter, and does that ownership follow the entity where the legal risk sits or the entity where the work is performed. Second, which fields are mandatory at intake, and whether those fields are consistent across subsidiaries or adapted by jurisdiction. Third, who may see the matter record, and whether access follows a user’s role, a specific matter, or both. Fourth, where the final decision is kept, and whether that location is consistent across matter types and entities.

Without those answers, a demonstration will show you features rather than fit. Each vendor will configure their system differently depending on your answers, and the gap between what the demo shows and what the system does in production is often explained by the absence of those definitions at the evaluation stage. Define the model first, then test whether the product can carry it.

How does matter management software handle access rights across subsidiaries?

Access control in matter management software typically works at three levels: role-based access, which gives a user visibility based on their function; matter-based access, which restricts visibility to users named on a specific matter; and entity-based access, which limits what a subsidiary team can see to matters within its own scope. Most enterprise-grade systems support combinations of these approaches, but the configuration requires explicit decisions about which team sees what, and those decisions need to be made before the system is set up.

In a global legal department operating across multiple entities and jurisdictions, access control is not a technical setting. It is an expression of the authority model. A subsidiary team handling employment matters in one country should not have visibility into acquisition work in another entity unless there is a defined reason for that access. The tool can enforce the rule, but the rule must exist first. Teams that skip this step during implementation typically find that access settings are inconsistent across entities, which creates both operational and governance problems later.

What should a legal department look for in a matter management demonstration?

A useful demonstration should be built around a real scenario, not a generic walkthrough. Bring a real matter type, a real entity, a real approval circuit, and a real exception. Ask the vendor to show how the system handles a matter that involves two entities, requires approval above a certain threshold, and generates a document that must be signed by an external party. Ask where the decision is recorded and how it can be retrieved if a regulator or internal audit asks about it six months later.

The answers will tell you more about fit than any feature comparison. Pay attention to how much configuration is required before the system reflects your operating model, who performs that configuration, and what happens when a new entity or a new matter type needs to be added. A system that requires significant technical work for each change may be difficult to maintain as the group grows or reorganizes.

How does Alf relate to matter management software?

Alf is the operating infrastructure for global legal departments. It connects people, processes, knowledge, and AI agents in one governed system across entities and jurisdictions. Within that system, each dossier holds the full history of a matter: documents, tasks, deadlines, validations, and decisions, with access rights set by user, group, or dossier. Configurable workflows and approval circuits reflect the rules of each entity without requiring a separate system for each one.

Where dedicated matter management tools focus on tracking the status of legal work, Alf organizes the legal organization itself, so that every matter is connected to a responsible owner, a relevant entity, an applicable policy, and a recorded decision. Its AI agent works from the context of the dossier and operates within the authority model the department has defined, so that AI increases capacity without increasing the complexity of oversight. Teams that want to understand how Alf fits alongside or instead of a dedicated matter management tool can walk through a real matter type with the Alf team to see how the operating model translates into the system.