Revenue systems for personal injury law

Money in a contingency practice is realised at disbursement, not at signature and not at the click. Between an inbound enquiry and a fee that clears from trust to operating sit an intake CRM record, a conflict check, a matter file in a case management system, a cost ledger, a payoff and lien file and a disbursement statement — objects held in systems that were bought separately, under identifiers that were never designed to match. An advertising platform can observe the first of those objects and none that follow it, and what a matter turns out to be worth is set by facts that are not present when the first object is created. Every entry on this page is the same shape of failure in a different place: a value that existed at one boundary had no field waiting for it at the next.

evidence · public-visible scope · revenue mechanics last reviewed · 2026-08-16

Who this is for

Written for contingency-fee practices that run an intake CRM alongside a separate case management system, take enquiries from more than one source including purchased lead feeds, buy acquisition against a revenue event realised at disbursement, and route some matters out to co-counsel. The operator addressed here owns both the acquisition spend and the fee ledger, and can read both.

How revenue is actually made

The unit of revenue is the signed matter, and the fee is contingent on a recovery rather than invoiced against work performed, so there is no recurring billing event and no periodic figure to reconcile against. How that fee is computed — on gross recovery, on recovery net of advanced costs, or on a schedule set by statute or by the fee agreement itself — varies by jurisdiction and by agreement, and the acquisition layer observes none of it. Nor is realisation necessarily a single moment: separate defendants, separate policies, medical-payments coverage and a follow-on uninsured or underinsured motorist claim can each produce their own recovery and their own disbursement against the same matter. What a matter can be worth is set upstream of the firm by liability posture, available coverage, venue and injury severity, none of which the advertising layer observes. A second revenue line runs beside the first: matters referred out to co-counsel under a written fee-division agreement produce fee income without producing a matter file. Expansion here is not upsell — it is referral reciprocity and prior-client re-referral.

Where demand comes from

  • Google Search paid campaigns against event-triggered injury queries
  • Purchased lead feeds, signed-case marketplaces and mass-tort intake vendors
  • Broadcast television, radio and out-of-home brand advertising
  • Attorney referral and co-counsel networks
  • Legal directories and review platforms

Revenue-leak map

Each entry names the system the leak lives in, the configuration in which it exists, the evidence that would confirm it, and what still cannot be concluded once you have that evidence. None of it is a claim about any particular business.

  1. Acquisition and permission values dropped at the intake-to-matter re-key

    At signature the client stops being an intake CRM lead and becomes a matter in the case management system. Where that transfer is configured as a mapped field sync, the click identifier, the campaign value and the stored permission artifact and its timestamp arrive with the matter. When the transfer is instead a person reading one screen and typing into another, the values with no use in the next job have nothing forcing them across, so the matter is opened without them. This is a configuration state and not a product limitation: the same two systems joined by a field mapping do not lose these values.

    where it lives
    The transfer between the intake CRM lead object and the newly opened matter record in the case management system, at the moment the retainer is executed.
    what would confirm it
    Export the matter list with open dates for one period and the intake CRM records created over the same window, then check which matters carry a populated source, campaign, click-identifier or permission field. When either system exposes its field-mapping configuration, read it directly and list which intake fields have a matter-side destination at all.
    what it still cannot show
    It cannot show which of the empty matter fields were ever populated on the intake side to begin with. A matter with no campaign value may descend from a lead record that never carried one, in which case the mapping is not the failure and the capture form is.

  2. Bid automation aimed at a counted event whose realised value is unknown when it is counted

    The event an advertising account can receive at the moment it happens is a form submission or a connected call. Wherever the conversion action is defined as that event and no later value is imported against it, automation optimizes toward a count of enquiries, and every enquiry in that count carries the same weight whether the matter it becomes resolves with a recovery or with none. A second effect sits underneath the count: where a consent banner is configured to gate storage and a user denies it, consent-aware tags do not store cookies or device identifiers and send measurements without them, and Google products use those pings to model metrics, so the count itself is partly modeled. Offline conversion import exists in these platforms for exactly this shape of problem, so the leak is the state in which no realised value is ever sent back, not a limit on what the platform will accept.

    where it lives
    The conversion action definition inside the advertising account, the consent configuration on the firm's own site, and the absence of any import job that reads the fee ledger.
    what would confirm it
    Read the conversion action definition and the consent configuration, then check the account for any import that writes a value against a click identifier. Take one cohort of clicks and walk it forward through reported conversions, intake CRM records created, matters opened, and matters that resolved with a recovery.
    what it still cannot show
    The walk cannot separate a modeled conversion from an observed one row by row, so the first figure in the chain stays an estimate even when every figure after it is exact. It also cannot attribute a matter that resolved without a recovery to the acquisition decision rather than to the facts of the case.

  3. Purchased and marketplace leads with no identity key shared across vendors

    Leads bought from intake vendors, signed-case marketplaces and mass-tort aggregators arrive as separate feeds. When each feed is configured to create its own intake CRM record and no deduplication rule runs across feeds on a normalized phone number, email address or date of loss, the same enquirer can exist as two paid records under two vendors, and the disposition written on one is invisible from the other. Vendor agreements carry duplicate-handling terms and CRM platforms carry merge rules, so the leak is the state in which none is configured across the whole set of feeds, rather than a property of buying leads.

    where it lives
    The inbound integration from each lead vendor into the intake CRM, and the deduplication or merge rule that either does or does not run across all of those feeds together.
    what would confirm it
    Take one period of purchased leads across every vendor, normalize phone numbers and email addresses, and count the identities that appear under more than one vendor, and those that appear more than once under a single vendor. Compare that against the credits requested from, and granted by, those vendors for the same period.
    what it still cannot show
    A matched pair does not establish which vendor delivered the enquirer first, because the timestamps stored are vendor delivery times rather than the moment the person made contact. It also cannot establish whether a given duplicate was billable under the specific agreement in force with that vendor.

  4. Broadcast and out-of-home demand collapsed into a single tracking number

    Television, radio and out-of-home creative carries a phone number, and that number is what the enquirer dials. Where the call-tracking configuration provisions one number for all offline media, every enquiry it produces is written to the intake CRM under the same source value, so the record can say the enquiry came from offline media and nothing beyond that. Call-tracking platforms provision numbers per creative, per station and per placement, so the granularity available is a provisioning decision rather than a limit of the channel.

    where it lives
    The call-tracking number pool, and the mapping between each provisioned number and the source value written onto the intake CRM lead object.
    what would confirm it
    List the tracking numbers in use and what each one is aired or printed against, then group intake CRM records by the source value the tracking layer wrote and see which distinct placements collapse into a single value. Compare the grouping against the media schedule for the same period.
    what it still cannot show
    Even fully separated numbers describe only the enquirers who dialled the number they saw or heard. Someone who saw a spot and then searched the firm by name arrives through a different surface entirely, and no configuration of the number pool recovers that person for the placement that prompted them.

  5. A co-counsel fee expectation that exists as a document and not as a receivable

    A matter the firm does not take, for conflict, venue or practice-area reasons, can still move to co-counsel under a written fee-division agreement, and that agreement creates an expectation of fee income. Where no matter is opened for it — the firm is not the one working the case — and the executed agreement is filed in the document management system, the expectation exists as a document and as something a person remembers, and as no row in any ledger. When the intake CRM carries a referred-out disposition with a counterparty and an expected-fee field, or the accounting package carries the expectation as a receivable, the object exists and this does not arise.

    where it lives
    The gap between the executed fee-division agreement in the document management system and the fee receipts posted to the operating account, with no record standing between the two.
    what would confirm it
    List intake CRM records closed with a referred-out or declined disposition for one period, pull the executed fee-division agreements from the document system for the same period, and match both against fee receipts posted to the operating account. Note which agreements have no matching receipt and which receipts have no matching agreement.
    what it still cannot show
    The match runs only over referrals that left a document behind. A referral agreed between two lawyers with nothing executed into the document system is not in the population being reconciled at all, so the exercise cannot size what it was never able to enumerate.

  6. Advanced case costs recorded in the accounting package and not against the matter

    Records-retrieval invoices, expert fees, filing fees and service costs are paid by the firm while a matter is open, and whether any of them is recovered from a recovery is set by the fee agreement and the rules in force rather than by default. When each invoice is entered in the accounting package as a vendor bill and no corresponding cost entry is posted against the matter in the case management system, the disbursement statement is assembled from whichever ledger the person assembling it can read. Case management platforms carry matter-level cost entries and accounting integrations for precisely this, so the leak is the state in which the posting step is manual and optional.

    where it lives
    The boundary between vendor bills in the accounting package and matter-level cost entries in the case management system, read at the point the disbursement statement is drafted.
    what would confirm it
    Take matters resolved in one period, pull every vendor invoice in the accounting package coded to those matters, and compare that list against the cost lines printed on each signed disbursement statement, matching on matter identifier and invoice date.
    what it still cannot show
    An invoice with no matching cost line is not automatically an unrecovered cost. It may have been written off deliberately, coded to the wrong matter identifier, or paid on a matter that resolved before it arrived. The comparison locates the discrepancy and says nothing about its reason.

  7. Settlement payoff obligations held as correspondence rather than as matter records

    Before funds move, the obligations attached to a recovery have to be settled: reimbursement claims asserted by health plans and government payers, provider letters of protection, and balances owed to medical-funding companies. Wherever each of those is tracked as an email thread and a letter in a folder, the matter carries no field stating which obligations are outstanding, what each is asserted at, and which have a final written figure, so a statement can be drafted against a figure that is still provisional. When each obligation exists instead as a dated record on the matter with a status and an asserted-amount field, the same statement is drafted against a list that can be checked before funds move.

    where it lives
    The payoff and lien file, and whether it exists as records attached to the matter in the case management system or as correspondence spread across a mailbox and a document folder.
    what would confirm it
    Take matters that disbursed in one period and check, for each obligation shown on the disbursement statement, whether it can be traced to a dated record on the matter carrying a final written figure rather than to a message thread.
    what it still cannot show
    It cannot show whether any figure was correct, because correctness is a question about the underlying claim and not about the record that holds it. It also cannot distinguish an obligation that was resolved and never written down from one that was never asserted against the recovery in the first place.

  8. Outbound requests to third parties with no expected-response date on the matter

    A matter waits on parties the firm does not control: providers producing records, adjusters responding to a demand, experts returning reports. Where the request leaves from a mailbox and the matter carries a status but no field for the date a request went out and the date a response was expected, a matter waiting on somebody else is indistinguishable from a matter where nothing has been sent. Case management platforms carry task and date fields for this, so what is absent is the field being written when the request goes out, not the ability to hold it.

    where it lives
    The matter record in the case management system — specifically whether an outbound request writes a dated field there, or only leaves an entry in a sent-mail folder.
    what would confirm it
    Take open matters and try to produce, from the case management system alone, the list of those with a request outstanding and the date it was sent. Where that list cannot be produced without opening a mailbox, the field is not being written when the request goes out.
    what it still cannot show
    A produced list shows which requests were logged, not which were made. A request made by telephone and never written down is absent from both the field and the mailbox, so the list understates the wait without indicating by how much.

Operational flow and systems of record

The path from demand to revenue, and which system holds the truth at each step. The boundaries between them are where state has to be handed over, so they are where this page looks.

  1. Enquiry capture and qualification Intake CRM lead object, written into by call tracking, web forms and lead-vendor feeds

    Where the conflict check runs against a separate party database and its result returns to the person who ran it rather than to a field on the lead object, the enquiry can move to signature, decline or referral without the record carrying which of those three paths it took, so the next stage has to be told rather than read.

  2. Retainer execution and matter opening Case management system matter record

    Where the matter open date is treated as the start of the relationship, the enquiry arrival timestamp held on the intake record has no destination field, so the interval between arrival and qualification exists as a value in neither system and cannot be operated on.

  3. Treatment, records and case development Case management system matter record and the outbound request log, where one is kept

    Where a request to a provider, adjuster or expert leaves without writing a dated field on the matter, the matter carries a status but not what it is waiting on, and the wait becomes visible only when somebody opens the file.

  4. Cost advance and vendor billing Accounting package vendor bills and matter-level cost entries

    Where an invoice is coded in the accounting package and the matching cost entry against the matter is a separate manual step, a cost can be paid in full and never appear on the object the disbursement statement is built from.

  5. Referral to co-counsel Executed fee-division agreement held in the document management system

    Where no record is opened for the referred matter in any system that holds money, the expected fee has no counterparty field and no status, so the firm learns the outside case resolved when payment arrives rather than before it does.

  6. Payoff resolution and disbursement Payoff and lien file, trust account records, and the fee ledger after transfer

    Where an obligation is marked resolved on the strength of a message rather than a final written figure, the statement is drafted against a provisional position; and where the fee ledger carries no acquisition field, the one stage that produces cash is the one stage acquisition reporting cannot read.

Relevant OmniLabs systems

These are capability domains inside the systems portfolio, delivered as scoped custom builds. The operating model that sequences them is Revenue OS.

Questions you can answer from your own systems

  • Open a resolved matter at random: can you name the campaign, vendor, directory or referring firm that produced it from the case management record alone, without asking a person?
  • Has a realised fee ever been sent back to your advertising account as a conversion value, and do you know which part of your reported conversion count is modeled rather than observed?
  • When the same enquirer is delivered by two lead vendors, what key in your intake CRM establishes that it is one person and not two?
  • Can you list every cost advanced on a resolved matter from the case management system alone, without opening the accounting package?
  • For a matter in payoff negotiation, is each outstanding obligation a dated record on the matter with a status and a written figure, or a thread in somebody's inbox?

Recurring failure modes

  • A reactivation build is scoped as a messaging sequence before the record it would run against exists. When the intake CRM lead object carries no stored permission value with a timestamp and a capture source, there is no per-record state for a sequence to read, so the work that has to happen first is a change to the capture form and the intake script rather than anything inside the messaging platform.
  • Acquisition reconciliation is joined on reporting period rather than on identity. When matters that resolved in a period are set against spend in that same period, the two sides describe different populations, because the clicks that produced those matters were bought under a configuration that may no longer exist.
  • The integration between the intake CRM and the case management system is scoped as a one-way create at signature. Wherever it is configured to open the matter and then stop, a value corrected on the intake record afterwards — a permission change, a corrected source, a decline that later became a referral — has no route onto the matter, and the two records begin drifting apart from the day they are joined.
  • A signed case is defined by a disposition value in the intake CRM and by a matter open date in the case management system. When a report is built from whichever of the two the reader happens to have open, the same period yields two figures that are each correct against their own definition, and the difference is treated as a data-quality problem rather than as a definition nobody settled.
  • Inbound referrals from other firms are recorded as matters and outbound referrals to co-counsel are recorded as documents. Where the two directions live in different object types, a report of referral relationships can be produced for one direction and has to be assembled by hand for the other, so the reciprocity the relationship runs on is only half visible inside a system.
  • Deadline and calendaring rules are configured once, per matter type, and then left in place, while acquisition planning is done against intake CRM fields. Where those fields carry no expression of the docketing load a signed matter adds, an acquisition plan can be sized without that load appearing anywhere in it, and the first place it appears is the calendar.

Evidence and claim boundaries

[CLAIM BOUNDARY] Nothing on this page carries a magnitude. That follows from the evidence position rather than from style: no verified benchmark exists for this vertical, so any figure printed here would be an invented one. Nor does anything here describe a real practice — every mechanism is written as a configuration state, and whether it exists in any particular firm is a question only that firm's own systems can answer. When a rule is named, only its existence and its author are named: lawyer advertising and solicitation requirements are set by state bars and vary, and fee-division and trust-accounting requirements are adopted state by state. None of them is interpreted here, and no sentence here decides how any of them applies to a practice; that determination belongs with qualified counsel and the relevant state bar. OmniLabs Systems is a systems implementation studio, not a law firm, and it holds no legal credential of any kind.

Industry pages describe revenue mechanics structurally. No conversion, retention or churn benchmark is published for any industry, because no verified benchmark was obtained for any of them — the mechanics are real, the magnitudes are not established here. Nothing on these pages describes work performed for a business.

Named regimes that constrain the systems

  • Consent-state handling in the Google tag platform, and Chrome's stated third-party cookie approach applies to Conversion measurement on a firm's own website and landing pages, where a consent banner is configured to gate storage before tags run. Google's tag documentation states that when a user denies consent for storage, consent-aware tags do not store cookies or device identifiers and instead communicate consent state and user activity without them, and that Google products use those pings to model metrics. Google's Privacy Sandbox update states that Chrome maintains its current approach to offering users third-party cookie choice, and that a named set of proposals, including the Attribution Reporting API and Topics, is being retired while CHIPS, FedCM and Private State Tokens continue. What that constrains in this vertical is specific: the only event an advertising account can observe here sits at the very start of a path whose value is settled at disbursement, and where the count of that first event is itself partly modeled, the join to a realised fee has to be carried by an identifier the firm owns end to end or it is not carried at all. source SRC-18 · SRC-16

Regimes are described structurally, as constraints on how systems and follow-up get built. Nothing here interprets them, and nothing here is legal, medical, veterinary, financial or regulatory advice.

Sources

  • Source-to-Revenue Visibility The ability to trace a real revenue event back to the source — campaign, content, channel, referral — that produced it, using internally verified data.
  • Tracking Gap A missing, duplicated, or inconsistent measurement handoff that prevents an event from being reconciled across the systems expected to record it.
  • Intake Boundary The operating boundary that defines which prospect data the public intake collects, which fields it does not, and how the surface enforces both.
  • Delayed Revenue Event A revenue event that occurs so long after the acquisition event, and across so many record boundaries, that no advertising platform can observe it.
  • Modeled Conversion A conversion estimated by a measurement platform where an observable link between an ad interaction and a conversion is unavailable.
  • Referral Revenue Ledger A system of record for work sent outside the business, holding the counterparty, the expected fee, the status and the aging clock.
  • Denominator Integrity The property of a conversion metric whose denominator includes every inquiry that occurred, not only the inquiries a system of record happened to receive.
Trace a fee back to its origin All industries

There is one diagnostic. The Revenue Leak Scan reviews public-visible signals for any business; it is not an industry-specific product, and this page does not create one.