When a law firm decides it has a billing problem, the solution it shops for is a better billing tool. New software, cleaner invoices, more payment options, faster processing. If the problem is scoped that way, the solution makes sense.
But most firms that think they have a billing problem have something else. The invoices aren’t the issue — or they’re not the whole issue. The real problem is upstream and downstream: work that doesn’t get captured, timelines that create cash flow gaps, systems that don’t talk to each other, and financial reporting that arrives too late to act on. Buying a better billing tool addresses one stage of that problem. The other stages stay intact.
That’s the distinction between a billing problem and a Legal Revenue Operations problem. It matters — not because the terminology is important, but because how you name the problem determines what you buy, what you fix, and whether the fix actually works.
What a Billing Problem Looks Like
A billing problem is a failure at a specific, bounded stage of the revenue cycle. Invoices aren’t going out on time. Clients aren’t receiving statements promptly. Payment options are limited and adoption is low. Write-down rates at billing review are high. AR aging is climbing because follow-up isn’t systematic.
These are real problems. They’re also solvable at the billing layer without touching the rest of the revenue cycle. Better billing software, tighter billing workflows, a more consistent invoicing cadence — these interventions move the needle on collection rate and days to collect. A firm whose billing process is genuinely the bottleneck will see measurable improvement from addressing it directly.
The test is narrow: if fixing the invoice-to-payment workflow would close most of the gap between what the firm billed and what it collected, it’s a billing problem. Fix it at the billing layer.
What a Revenue Operations Problem Looks Like
A Revenue Operations problem is structural. It’s not isolated to a single stage — it runs through the full cycle, from the first client interaction through final collection, and it’s caused by disconnection between the systems and workflows that handle each stage.
The tell is that fixing one stage doesn’t fix the problem. A firm that improves its billing process and still can’t explain the gap between what it earned and what it collected has a RevOps problem. The gap is somewhere else — or it’s at multiple stages simultaneously — and a better billing tool isn’t going to surface it.
Revenue leaks everywhere there’s a gap between systems: time that doesn’t get captured, invoices that go out without complete billing data, collections follow-up that depends on individual initiative rather than system triggers, reporting that comes after the fact rather than during the cycle. Each of these is a stage problem, but the root cause — disconnection — is structural. Patching individual stages doesn’t close it.
Why the Distinction Is Sharpest at a Contingency Firm
At an hourly firm, the billing problem and the RevOps problem can at least be partially confused — both show up in collection rate and days to collect, and improving billing discipline does move those numbers.
At a contingency firm, the distinction is impossible to miss. There are no billing cycles. There are no invoices in the traditional sense. The revenue mechanism is entirely different — and no billing tool, however good, touches the actual revenue problem.
What a PI or employment law firm loses between case open and cash collected is not a billing problem. Case costs that aren’t tracked consistently and don’t come back at settlement: not a billing problem. Lien exposure that wasn’t managed proactively and reduces the firm’s net recovery: not a billing problem. Settlement proceeds sitting in trust for 60 days while lien resolution stalls: not a billing problem. Partner distributions calculated from incomplete data: not a billing problem.
These are Legal Revenue Operations problems — structural, end-to-end, and invisible to any tool that only handles the invoice layer. The firm that buys better billing software to fix them is buying the wrong answer to the right question.
The Evaluation Criteria Shift
Once a firm correctly identifies its problem as a RevOps problem rather than a billing problem, the evaluation criteria for solutions change fundamentally.
A billing tool is evaluated on invoice quality, payment processing, collections automation, and reporting on the AR cycle. All of those matter. None of them are the primary measure of a Legal Revenue Operations platform.
A RevOps platform is evaluated on data continuity across the full lifecycle — does data entered at intake still drive accurate reporting at close? On integration depth — not whether tools are connected, but whether the connection eliminates manual handoffs or just reduces them. On reporting that covers the full cycle — not just AR aging, but realization, collection rate, days to collect, matter profitability, and the visibility to act on all of them before the problem has already compounded.
Every billing model carries its own version of this problem. The hourly firm’s gap is in realization and AR. The fixed fee firm’s gap is in matter profitability. The contingency firm’s gap spans the entire case lifecycle. In every case, the problem looks different on the surface. Underneath it, the root cause is the same: a revenue cycle managed in pieces, by systems that weren’t built to work together, by people spending time on handoffs that should be automatic.
That’s the Legal Revenue Operations problem. And naming it correctly is the first step toward solving it.
