The matter nobody has touched in three weeks
The client calls to ask where things stand. The partner says they will check and get back to them. They check.
The matter is waiting on a document the firm requested five weeks ago. The associate assumed the paralegal was chasing it. The paralegal assumed the client had been told it was urgent. The client assumed silence meant the firm was working. Everyone behaved reasonably and the file sat still for over a month.
Nothing failed here. Nothing was supposed to catch this.
What pipeline tracking with staleness alerts is
It is one board of every open matter, deal and engagement, each with a last-activity date, and a rule about how quiet is too quiet.
The important part is where the last-activity date comes from. It is computed from the systems the firm already uses: a time entry, a filed document, a sent email on the matter, a status change in practice management. It is not a field someone has to remember to update. A pipeline that depends on people updating a status field has the same failure as the matter above, wearing a different hat. The point of the system is to notice things when nobody is paying attention, which is exactly when nobody updates fields.
Thresholds are set per stage, because quiet means different things in different places. A new enquiry that has not been answered in four hours is a problem. A matter waiting on client documents is fine for two weeks and suspicious at four. Litigation waiting on a court date can sit for months and be entirely healthy. One global rule produces either constant noise or nothing at all.
Alerts escalate rather than nag. The first one goes to whoever owns the matter, quietly. If it is still quiet after the second threshold, it goes to the partner responsible. That order matters: the associate gets a chance to say “waiting on the court, all fine” before anyone above them sees a list with their name on it.
Every flag carries its evidence. The last activity, what it was, who did it and what the matter is waiting on. A flag without evidence is a demand for a status meeting, which is the thing this is supposed to prevent.
It reads from the firm’s systems and changes nothing in them.
Does a firm your size need it
Here is the test. Without opening anything, name the three oldest open matters in the firm and say what each one is waiting on.
Most partners can name the oldest. Almost nobody can name the third, and the third is where the damage is. Very old matters are usually known and deliberate. It is the middling ones, six weeks quiet and nobody worried, that turn into a complaint or a missed limitation date.
The clearest signal is that the pipeline is a person. If the answer to “what is open right now” is a partner’s memory plus a spreadsheet they maintain, the firm has a reporting system with one point of failure and no alarm.
The second signal is handoffs. Work that moves between people stalls in the gaps between them, because the person who let go assumes the person who picked up is on it. Firms with paralegals, associates and partners on the same matter have more of these gaps than firms where one person does everything.
The third is clients asking for updates. Every “just checking in” email is the client doing the firm’s monitoring for it, and only on the matters where the client is attentive. The quiet clients are not quiet because they are happy.
The pattern shows up in the numbers across the systems we run: 16,062 leads tracked from first contact to outcome, with a response time measured on 7,912 of them, and 70 percent of inbound leads reached on the first call. None of that comes from people being more diligent. It comes from the delay being visible while it is still small.
What it costs
This is built as a fixed-price phase inside a plan, and it is usually the least expensive build in its pillar, because it reads from systems rather than writing to them. There is no migration and no change to how anyone works.
The audit prices it as a phase before anything is built, and its own fee is credited against that phase if the firm goes ahead.
Running costs are close to nothing. It is mostly scheduled queries against data the firm already holds.
The real cost is a decision, not a build. Someone at the firm has to say how long is too long for each stage of each kind of work, and then live with being told about it. Firms that skip that conversation end up with thresholds set by whoever configured the system, alerts that fire on healthy matters, and a team that turns the notifications off in the second month.
What the first week looks like
We start by reconstructing the present. Every open matter, with its last real activity pulled out of the systems, as of today.
That first list is usually uncomfortable, and it is the most valuable output of the week. Firms consistently find matters quieter and older than anyone believed, including a few that should have been closed and a few that nobody currently owns. Cleaning those up on its own often pays for the phase.
Then the thresholds get set, with the people who run the work rather than for them. This is a working session with the practice leads, one kind of matter at a time. It goes faster than people expect, because everyone already has an instinct for when a file has gone quiet. The session writes it down.
Alerts run to a test channel first, for a couple of weeks, so the firm can see what it would have received without anyone being pinged. The false positives get tuned out there. Thresholds nearly always move at least once.
Then it goes live, when the people who will receive the alerts agree they are worth receiving. As in every build, the people who do the work decide when it is ready.
The full scope is on the service page: /services/billing-pipeline-capacity. The live demos are here: /demos.