Partner reports without the Friday scramble
Friday afternoon. Someone exports a report from practice management, exports another from the accounting system, pastes both into a workbook, fixes the columns that moved since last month, retypes two figures that would not import, and emails a PDF at ten past six.
It takes most of an afternoon. It happens every month, or every week, forever. And the one person who knows which columns to fix is the reason it happens at all.
What automated reporting is
Reporting on autopilot has two parts, and firms usually want the first one and end up relying on the second.
The first part is the pack itself, compiled on schedule from the systems where the numbers live. Practice management, accounting, time recording, and the ad platforms if the firm spends on acquisition. Same layout every month, delivered where the partners already read it. No exports, no pasting, no retyping.
The connections are read-only. Nothing is written back to the accounting system, and the accountants keep their tools exactly as they are. What changes is that the numbers stop being assembled by hand.
Every figure links back to the rows that produced it. A partner who thinks realization looks wrong clicks the number and sees the matters and time entries behind it, without asking anyone. That single property ends most of the arguments that reports normally start, because the disagreement moves from “is this number right” to “what should we do about it”, which is the conversation the meeting was for.
The second part is asking questions between reports. How is realization on that matter. What is aged over ninety days. Which practice area grew last quarter. Cost per new matter this year against last.
How that answer is produced matters more than that it exists. The question is turned into a query against the firm’s own data, the system runs it, and the system renders the figures. The numbers on the screen are computed from the firm’s rows, not typed out in a sentence by a model. That distinction sounds pedantic until the first time a partner quotes a figure to a client. A model writing prose about numbers will eventually produce a confident, wrong, well-formatted total. A model that writes a query and hands the arithmetic to the database will not.
When an answer needs a caveat, it says so. When the data cannot answer the question, it says that instead of estimating.
Does a firm your size need it
Two questions. How many hours a month go into producing the reports the firm already reads, and who could produce them if that person left tomorrow?
If the answer to the second is “nobody without a lot of digging”, the firm has a continuity problem that has nothing to do with AI and will be solved by the same work.
The strongest signal is that the report is late, or arrives after the decision it was meant to inform. Monthly numbers that land on the fifteenth are history, not management.
The second signal is meetings spent establishing the numbers rather than discussing them. If the first twenty minutes go to reconciling two versions of the same figure, the firm is paying its most expensive people to do data entry out loud.
The third is the spreadsheet that only one person understands. Every firm has one. It usually holds something genuinely important, and it usually has a formula in it that nobody has checked in three years.
The pattern at volume: 160,896 ledger rows parsed from monthly spreadsheet packages into 48 versioned client reports, 51,867 daily ad-spend rows reconciled against the leads they produced, and more than 765,000 app events and 216,000 calls and texts consolidated into one store feeding 19 dashboards from four source systems. That is a reporting layer nobody rebuilds by hand each month.
There is an honest exception. If nobody actually reads the report, do not automate it. Stop making it. That is question one of the audit, and reporting is where it gets the most use.
What it costs
Reporting is built as a fixed-price phase in a plan. The price depends on how many source systems are involved, how clean they are, and how many reports are in scope. One report from two systems is a small build. Client-facing statements plus a partner pack plus practice-level reporting, drawn from five systems with a decade of inconsistent data behind them, is a larger one.
The audit prices it as a phase before any work starts, and credits its own fee against that phase.
Running costs are modest: storage for the firm’s own data, and model usage only for the question-asking layer, which is a small share of the total.
The cost that surprises people is definitions. What counts as realization here. When is a matter open. Which entity does this client belong to when they appear three times under slightly different names. Does a written-off hour count as utilized. These are firm decisions, not technical ones, and they have to be made once and written down. Most firms discover during this phase that two departments have been using the same word for different things, which explains a number of past arguments.
What the first week looks like
The first week rebuilds the report the firm already has, exactly as it is. Not an improved version, not a redesign. The existing one, produced by the system instead of by a person.
That constraint is deliberate. A report the partners already know how to read can be checked figure by figure against the last three months of hand-built versions. Every difference gets explained before anyone is asked to trust it, and about a third of the differences turn out to be errors in the manual version that had been quietly carried forward.
The definitions get written down as the rebuild happens, in the report itself, next to the figures they govern. That document outlives the project.
Once it reconciles, it goes on a schedule and the person who used to build it stops building it. Their Friday afternoon comes back. That time goes to the work only they can do, which is usually reading the report rather than assembling it.
The ask-a-question layer comes after, never before. A firm that cannot yet agree on what realization means will not be helped by being able to ask about it faster.
The full scope is on the service page: /services/firm-numbers. To ask a fictional firm’s ledger about realization, aged receivables or last quarter’s growth, the demo is here: /demos/numbers.