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

Your intake team processes hundreds of leads a month, codes rejections, signs cases, and logs everything in the CRM. They're capturing more revenue intelligence than any other function in your firm — and in most cases, none of it is being used. Not by marketing. Not by the managing partner. Not by anyone making vendor budget decisions.

That's the gap. Intake as an operations function measures speed and volume. Intake as a revenue intelligence function measures which lead sources are producing cases worth keeping — and which ones are quietly draining budget through high rejection rates, fast withdrawals, and low-value case types.

The shift isn't expensive. It's structural. Here's how to make it.

Why Intake Is a Revenue Function, Not a Processing Function

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

That model breaks down once you have five or more active lead sources. When you're running Google Ads, two aggregator contracts, a television buy, and a referral network simultaneously, a single conversion rate number is useless. Conversion rate from which source? Converting into what type of case — soft tissue or surgical?

A revenue intelligence function asks harder 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?

Your intake team already touches most of this data on every call. The problem: it's rarely captured at the source level, rarely attributed back to the vendor, and almost never surfaced in a format marketing can act on.

The Five Metrics That Define an Intake Intelligence Layer

Five specific metrics — tracked by lead source, not in aggregate, not just for the current month — are what separate an intake intelligence layer from a processing function.

1. Conversion Rate by Source

Signed cases divided by total leads received, broken out by vendor or channel. A source sending 200 leads and converting 40 runs a 20% conversion rate. A source sending 80 leads and converting 32 runs 40%. The second source is worth more — but most firms are spending more on the first because raw lead volume looks impressive on a vendor invoice.

2. Rejection Rate by Source

The percentage of leads your intake team turns away: wrong case type, unclear liability, statute of limitations, prior representation. High rejection rates from a specific vendor signal a targeting mismatch, not an intake problem. Rejecting 60% of leads from one aggregator and 15% from another is a vendor problem — and without source-level data, you'll never see it.

3. Withdrawal Rate by Source

How many signed clients drop their case within 90 days — attributed back to the originating lead source. Most firms don't track this. Those that do often find it changes everything. A vendor with a 25% withdrawal rate is effectively quadrupling your real cost per case, because one in four signed files disappears before generating any revenue.

4. Case Severity by Source

Not all signed cases carry equal value. A vendor sending primarily soft tissue cases produces a fundamentally different ROI profile than one sending surgical injuries or fatalities. Tracking case severity or projected value by source — even in three rough tiers — gives marketing a tool to optimize for case quality, not just case count.

5. Speed-to-Lead Response Time

How fast does intake contact a new lead? Contact rates drop sharply after the first five minutes — firms that respond within that window consistently outperform those that don't. Speed-to-lead alone isn't a revenue intelligence metric. But when tracked by source and correlated with conversion rate, it separates a lead quality problem from an intake execution problem.

How to Build the Data Infrastructure

You cannot run an intake intelligence layer from a spreadsheet. Spreadsheets can't join lead source data to CRM data to case management data in real time. They can't attribute a withdrawal back to the original vendor. They can't surface 6-month cohort trends without burning 10 hours a week on manual work. The infrastructure has three components.

Source Capture at the Lead Level

Every lead entering your system needs a source tag — not just “Google” or “television,” but specific enough to distinguish Google Search from Google Display, or between two separate aggregator contracts. If your intake platform — LeadDocket, Filevine, Clio, or otherwise — doesn't capture source at intake, that's the first thing to fix. Everything else depends on it.

Attribution That Persists Through the Case Lifecycle

The source tag has to follow the lead as it becomes a signed client, moves through case management, and eventually settles or closes. Most firms lose this chain at the intake-to-case-management handoff. Without persistent attribution, you can calculate conversion rate — but you can't calculate withdrawal rate, case value by source, or settlement outcomes by vendor.

A Reporting Layer Connecting Spend to Outcomes

The final piece connects your media spend to your intake data. This is where revenue intelligence platforms like RevenueScale sit — joining vendor invoices and ad spend with CRM data to produce a true cost per case by source, updated continuously rather than manually each month.

Structuring the Intake Team to Contribute Intelligence

Technology is necessary but not sufficient. Your intake specialists need to understand that the data they capture matters beyond the individual call — and two practical changes make the biggest difference.

• Standardize rejection reason codes.When a lead is turned away, intake should select from a defined list: wrong case type, statute of limitations, liability unclear, prior representation, client unresponsive. A generic “not qualified” tag is useless for vendor evaluation. Specific codes let you tell an aggregator exactly why their leads are being rejected — a feedback loop that actually improves lead quality over time.
• Route leads by source to matched specialists.A specialist who primarily handles television leads has a fundamentally different conversation than one handling aggregator leads. Mixing them without differentiation dilutes both conversion rate data and actual conversion performance. Source-based routing isn't just operational — it keeps your intelligence clean.

What Changes When Intake Becomes a Revenue Intelligence Function

The shift is structural and cultural at the same time. When intake is positioned as an intelligence layer, three things change fast.

Marketing and intake get a shared vocabulary.The conversation stops being “your leads are bad” versus “your team isn't closing” and starts being “Vendor C has a 58% rejection rate and a 22% withdrawal rate — what does that say about their targeting?” That's a different conversation. It leads somewhere.

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

Budget decisions get defensible.When your managing partner asks why you're cutting one vendor and doubling another, you can show cost per case by source — not cost per lead, not overall conversion rate, but the actual cost to acquire a case likely to produce revenue. That is what makes a budget conversation stick.

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