How to Turn Your PI Intake Team Into a Revenue Intelligence Function

Most personal injury firms treat intake as an operations problem. They hire intake specialists, build scripts, track call volume, and measure how fast the phone gets answered. All of that matters. But none of it answers the question your managing partner is actually asking: are the cases we're signing worth what we paid to get them?

That question doesn't belong to operations. It belongs to a revenue intelligence function — one where intake is no longer just a cost center that processes leads, but a data layer that tells you which lead sources are producing cases you actually want to take.

Reframing your intake team this way is one of the highest-leverage moves a PI marketing director can make. Here's how to do it.

Why Intake Is a Revenue Function, Not a Processing Function

The traditional intake model treats every lead as essentially equivalent until the attorney does a case review. Intake's job is to screen, qualify, and sign — as fast as possible. Volume is the metric. Conversion rate is the KPI.

That model breaks down the moment you have more than a handful of lead sources. When you're running Google Ads, a lead aggregator, a television buy, and a referral network simultaneously, “conversion rate” as a single number becomes meaningless. Conversion rate from which source? Converting into what kind of case?

A revenue intelligence function asks a different set of questions. Not just “did this lead sign?” but:

• What type of case did they sign, and what's the projected value?
• What was the rejection rate for this source, and why were leads rejected?
• How many signed cases from this source withdrew within 90 days?
• What is the cost per signed case — not cost per lead — for this vendor?
• At settlement, which sources are producing the highest-value outcomes?

Intake teams already have access to most of this data. The problem is that it's rarely captured, rarely attributed back to the source, and almost never surfaced in a format that a marketing director can act on.

The Five Metrics That Define an Intake Intelligence Layer

To turn your intake team into a revenue intelligence function, you need five specific metrics tracked consistently by lead source — not in aggregate, and not just for the current month.

1. Conversion Rate by Source

This is the ratio of signed cases to total leads received, broken out by each vendor or channel. A source that sends 200 leads and converts 40 has a 20% conversion rate. A source that sends 80 leads and converts 32 has a 40% conversion rate. The second source is almost certainly more valuable — but most firms are spending more on the first because the lead volume looks impressive.

2. Rejection Rate by Source

Rejection rate measures the percentage of leads your intake team turns away — either because the case doesn't meet your criteria, the liability is unclear, or the statute of limitations has passed. High rejection rates from a specific vendor are a signal that the vendor's targeting is misaligned with your case mix. If you're rejecting 60% of leads from one aggregator and 15% from another, you have a vendor problem, not an intake problem.

3. Withdrawal Rate by Source

Withdrawal rate tracks how many signed clients eventually drop their case or terminate their agreement — attributed back to the lead source that brought them in. This metric is undertracked at most firms and profoundly important. A source with a 25% withdrawal rate is effectively costing you four times what the cost-per-signed-case number suggests, because one in four cases disappears before it produces any revenue.

4. Case Severity by Source

Not all signed cases have equal value. A vendor sending primarily soft tissue cases is producing a fundamentally different ROI profile than one sending surgical cases or fatalities. Tracking average case severity or projected case value by source — even in rough tiers — gives your marketing director a tool to optimize for case quality, not just case volume.

5. Speed-to-Lead Response Time

This one cuts the other direction: it measures how quickly your intake team contacts a new lead. Research consistently shows that response time within 5 minutes dramatically improves contact rates. Speed-to-lead is not a revenue intelligence metric in isolation — but when tracked by source and correlated with conversion rate, it tells you whether a low conversion rate is an intake execution problem or a lead quality problem.

How to Build the Data Infrastructure

You cannot run an intake intelligence layer from a spreadsheet. Spreadsheets can't join your lead source data to your CRM data to your case management data in real time. They can't attribute withdrawal events back to the original vendor. And they can't surface trends across 6-month cohorts without hours of manual work each week.

The infrastructure you need has three components:

A CRM or Intake Platform That Captures Source at the Lead Level

Every lead that enters your system needs to carry a source tag — not just “Google” or “television,” but specific enough to distinguish between Google search and Google display, or between two different aggregator contracts. If your intake platform (LeadDocket, Filevine, Clio, or others) doesn't capture source at intake, that's the first thing to fix.

Attribution That Persists Through the Case Lifecycle

The source tag needs to follow the lead as it becomes a prospect, becomes a signed client, progresses through case management, and eventually settles or closes. Most firms break this chain somewhere — usually at the point where intake hands off to case management. Without persistent attribution, you can measure conversion rate but you can't measure withdrawal rate, case value by source, or settlement outcomes by source.

A Reporting Layer That Connects Marketing Spend to Intake Outcomes

The final piece is the connection between your media spend data and your intake performance data. This is where revenue intelligence platforms like RevenueScale sit — joining your vendor invoices and ad spend with your CRM data to produce a true cost-per-case number by source, updated in something close to real time.

Structuring the Intake Team to Contribute Intelligence

Technology is necessary but not sufficient. Your intake specialists also need to understand that the data they capture matters beyond the individual call.

Two practical changes make a significant difference:

First, standardize rejection reason codes. When a lead is turned away, intake should select from a defined list of reasons — wrong case type, statute of limitations, liability unclear, prior representation, client unresponsive. Generic “not qualified” tags are useless for vendor evaluation. Specific reason codes let you tell an aggregator exactly why their leads are being rejected, which creates a feedback loop that improves lead quality over time.

Second, route leads by source to specialists who know that source's typical case profile. A specialist who primarily handles television leads will have a different conversation than one who handles aggregator leads. Mixing them without differentiation dilutes both conversion rate data and actual conversion performance.

What Changes When Intake Becomes a Revenue Intelligence Function

The shift is partly structural and partly cultural. When intake is positioned as a revenue intelligence function, a few things change quickly.

Marketing and intake start having a shared vocabulary. Instead of “your leads are bad” vs. “your intake team isn't closing,” the conversation becomes “Vendor C has a 58% rejection rate and a 22% withdrawal rate — what does that tell us about their targeting?”

Vendor conversations become evidence-based. When you can show a vendor their specific rejection rate, withdrawal rate, and cost per signed case compared to your portfolio average, the negotiation changes. You're no longer arguing about lead quality in the abstract. You have numbers.

Budget decisions get more defensible. When your managing partner asks why you're cutting one vendor and doubling down on another, you can show them cost per case by source — not cost per lead, not conversion rate, but the actual cost to acquire a case that is likely to produce revenue.

That is what a revenue intelligence function looks like. And it starts with treating intake as the data layer it already is — one that most firms have simply never been equipped to read.