Law-Firm Business Intelligence: The Dashboard Your Practice-Management System Won't Give You

Quick answer: Your practice-management system already holds almost every number a partner needs — matter profitability, utilisation, work-in-progress, cash tied up in unbilled and unpaid work. What it doesn’t do well, in our experience, is hand those numbers back as a live picture of how the firm is actually performing this week. A business-intelligence (BI) layer fixes that: it pulls data out of LEAP, Smokeball or Actionstep through their APIs into a dashboard the partners can read at a glance, refreshed automatically instead of assembled by hand at month-end. This is a reporting and data project — the trust-accounting and compliance obligations stay firmly with the firm.

The visibility gap most firms live with

Ask a managing partner how the firm did last month and you’ll usually get one of two answers: a confident number that turns out to be a feeling, or “let me get the practice manager to pull that together.” Neither is real-time visibility.

The data exists. Every time entry, every bill, every payment, every open matter is sitting in the practice-management system (PMS). The problem is that the built-in reporting was designed to answer questions about a matter — what’s billable on it, what’s outstanding — far more than questions about the firm. Those firm-level questions tend to require exporting to a spreadsheet, joining reports by hand, and hoping nobody fat-fingered a formula. By the time the report is finished, it’s describing a month that’s already gone.

“Business intelligence” sounds like enterprise jargon, but for a law firm it means something concrete: the operational numbers, current, in one place, that you don’t have to be an accountant to read.

The metrics that actually tell you how the firm is doing

Here are the measures worth putting on a dashboard, in plain English. None of these are exotic — the value is having them live and side by side rather than reconstructed once a quarter.

• Matter profitability. Not just what a matter billed, but what it cost to deliver — the fee earners’ time at their real cost, against what the client actually paid. A matter can bill well and still lose money if it soaked up senior time nobody recovered.
• Billable utilisation. Of the hours a fee earner is available, how many turned into recorded billable time? This is the single clearest read on whether the firm is busy in a way that pays, or just busy.
• Realisation rate. Of the time recorded, how much was actually billed and collected? Time that gets written down before it hits an invoice, or written off after, is invisible in most day-to-day views — but it’s money the firm decided not to earn.
• Work-in-progress (WIP). Work that’s been done but not yet billed. High WIP means the firm has effectively lent its effort to clients for free until someone raises an invoice.
• Lockup and aged WIP. Lockup is the total cash tied up in unbilled WIP plus billed-but-unpaid invoices — the gap between doing the work and getting paid for it. “Aged” means how long it’s been sitting there. Lockup is where a profitable firm quietly runs out of cash.
• Lead-to-matter conversion. Of the enquiries that come in, how many become paying matters — and from which sources? This connects the firm’s marketing spend to its actual pipeline.
• Cash-flow visibility. Money in, money out, and what’s realistically collectable in the next 30, 60 and 90 days, drawn from real invoice and payment data rather than a gut feel.

Put utilisation, realisation and lockup on one screen and a partner can see, in seconds, whether the firm is working hard, charging properly, and getting paid on time. Those are three different questions, and a firm can be winning one while quietly losing another.

How a BI layer is actually built

You don’t rip anything out to do this. The PMS stays exactly where it is as the source of truth for matters, time and trust accounting. The BI layer sits alongside it. Conceptually there are three moving parts.

1. Pull the data out. Modern practice-management platforms expose an API — a defined, permissioned way for other software to read their data. LEAP, Smokeball and Actionstep all provide one, though each differs in what it exposes and how. A scheduled job reads the relevant records — time entries, bills, payments, matters, contacts — on a regular cadence. The mechanics of doing this reliably are the same API integration work we do across other platforms; the patterns are well established. Where a platform supports webhooks, the dashboard can update closer to real time, an approach we’ve written about in the context of Actionstep’s event architecture.

2. Store and shape it. The raw data lands in a small reporting store — a data warehouse, in the usual jargon, though for most firms it’s modest in size. This is where the calculations that the PMS doesn’t do natively get applied: apportioning partner time at its real cost, joining a client’s matters together, ageing the WIP, working out realisation. Doing this in a separate layer means the logic is consistent and repeatable, rather than living in one spreadsheet only the practice manager understands.

3. Show it. The shaped numbers feed a dashboard the partners open themselves — whether that’s a business-intelligence tool or a purpose-built screen inside a custom web app. It refreshes on its own. Nobody has to be in the office on the last day of the month for the firm to know how the month went.

The reason this is usually a custom build rather than an off-the-shelf report is that the definitions are firm-specific. What counts as a fee earner’s available hours, how partner time is costed, which matters are “strategic” loss-leaders versus ones that must pay — every firm draws these lines differently, and the dashboard is only trustworthy if it draws them the way the firm actually thinks.

Where the PMS ends and BI begins

To be fair to the platforms: matter-level reporting is genuinely a strength of the leading Australian systems, and their trust accounting is built to handle state-by-state requirements that no third-party tool should go near. The trade-off is simply one of design focus. A PMS is built to run matters brilliantly; firm-wide, cross-matter, leadership-facing analytics is a different job, and in our experience it’s the one most often left to spreadsheets.

That division also matters for compliance. A BI layer should be built to read from the PMS and report — never to move money or write back into a trust ledger. The audit trail belongs inside the PMS where it’s regulated. The dashboard’s job is visibility, not control, and the firm’s trust-accounting and professional obligations remain the firm’s own.

When it’s worth building — and when it isn’t

A sole practitioner or a firm in its first few months on a new platform probably doesn’t need this yet; the volume isn’t there and the operational rhythm is still settling. The point where a BI layer earns its place is usually a handful of fee earners across more than one practice area, and a managing partner or practice manager who is spending real time each month assembling reports by hand — or worse, flying without them.

If you’re running on LEAP, Smokeball or Actionstep and you can feel that gap — the data’s all in there, but you can never see the firm as a whole without a fortnight’s notice — that’s the prompt. We’ve covered the platform-specific integration surfaces in more depth for LEAP and Smokeball, and where AI fits into legal workflows in agentive AI for Australian legal practice.

The firms we’ve built for don’t want another report. They want to open a screen on a Monday morning and know, honestly, how the practice is doing. That’s a data problem with a well-understood solution — and the data is already yours.

Wondering what this would look like on your platform and your numbers? Start a project and we’ll map it out.