Most PI marketing directors know they should be tracking vendor performance more systematically. What stops them isn't willingness — it's the assumption that building a real accountability system requires either a dedicated analytics hire or a complex software implementation that takes months to stand up.
Neither is true. A functional vendor accountability system can be built incrementally, starting with what you already have, and maintained in a few hours per month — not per week. Here's how to build it.
Related guide: See our complete guide to evaluating PI lead vendors — the 7 metrics that define vendor quality and how to build a vendor scorecard.
What a Vendor Accountability System Actually Needs to Do
Before getting into the mechanics, be clear about the objective. A vendor accountability system needs to do three things:
- Tell you, for each vendor, what cost per signed case you're achieving — updated at least monthly
- Show you whether that number is getting better or worse over time
- Create a clear decision trigger when a vendor crosses a performance threshold
Everything else is optional. Start with these three. Add complexity only when you have a reason to.
Layer 1: Data Collection (The Foundation)
Vendor accountability starts with data collection. The minimum viable data you need — most of which you probably already have somewhere:
Vendor Invoices
Collect every vendor invoice in a single place. A shared folder, a bill-pay system, or a simple expense tracking sheet will do. What matters is that you can look up total spend per vendor for any given month without digging through emails.
Lead Source Tags in Your Intake System
Every lead that enters your intake system needs to be tagged with the vendor or source that sent it. This is the critical data connection. Without it, you can't connect spend to outcomes.
If your intake system doesn't currently capture lead source at the lead level, adding this field is the single highest-leverage operational change you can make for marketing analytics. It requires no new software — just a protocol: every new lead gets tagged with a source code that maps to a vendor.
Intake Disposition by Lead
What happened to each lead? Signed, rejected (with reason), declined by claimant, not reached, still in process. This data should already exist in your intake system or CRM. The key is ensuring it's being captured consistently — not just for cases that convert, but for every lead that comes in.
Case Attribution to Lead Source
When a lead becomes a signed case, can you trace it back to the vendor who sent it? This linkage — lead source to signed case — is what makes cost per case calculable. If your intake and case management systems aren't connected, this linkage needs to be maintained manually or through a bridging process.
Layer 2: The Monthly Calculation (The Engine)
Once data collection is in place, the monthly calculation takes 1–2 hours. For each vendor in your portfolio:
- Pull total spend from invoices for the 90-day rolling window
- Pull signed cases attributed to this vendor from intake/case management data for the same window
- Divide spend by signed cases = cost per signed case
- Calculate conversion rate: signed cases divided by total leads received from this vendor
- Calculate rejection rate: rejected leads divided by total leads received, with breakdown by rejection reason
Record these numbers in a simple tracking sheet with a date column. Month-over-month, this sheet becomes your trend data. After three months, you have a meaningful baseline. After six, you have enough data to identify performance patterns with confidence.
Layer 3: The Scorecard (The Output)
Convert your monthly calculation into a simple scorecard. For each vendor, a single-page scorecard shows:
- Current cost per case:This month's 90-day rolling number
- Firm average cost per case: Blended across all vendors for the same period
- Gap vs. average: Dollar and percentage
- Conversion rate: Current vs. prior period
- Rejection rate: Current vs. prior period
- Trend: Up, flat, or down (with 3-month direction)
- Grade: A, B, C, or D based on your defined thresholds
The grade is the output that drives decisions. Define the grade thresholds once and use them consistently. A vendor at grade C or below triggers a defined response — regardless of relationship history or gut instinct.
Layer 4: The Decision Protocol (The Action)
A scorecard without a decision protocol is just a report. The decision protocol defines what each grade requires you to do:
- Grade A: Eligible for budget increase. No additional action required.
- Grade B: Maintain current budget. Monitor monthly.
- Grade C: Budget freeze. Schedule an accountability conversation within 10 business days. Set a 60-day improvement target.
- Grade D: Budget reduction of 25–50%. Define a 60-day improvement window. Exit if target not reached.
The protocol removes judgment from the monthly decision. You're not deciding how to feel about Vendor A this month — you're following a process. This consistency is what makes the system trustworthy to you, to your vendors, and to the managing partners who need to see that budget decisions are grounded in data.
| Grade | Performance | Required Action | |
|---|---|---|---|
| A | Below target CPC | Eligible for budget increase | |
| B | At or near target CPC | Maintain budget, monitor monthly | |
| C | Above target CPC | Budget freeze, accountability call in 10 days | |
| D | Significantly above target | 25-50% budget cut, 60-day exit window |
The Monthly Operating Rhythm
Block two hours at the start of each month. Here's the routine:
- Week 1, Day 1: Pull vendor invoices for the prior month. Pull intake data for the prior 90 days. Update the tracking sheet.
- Week 1, Day 2: Calculate cost per case, conversion rate, and rejection rate for each vendor. Update the scorecard. Assign grades.
- Week 1, Day 3: Review grade changes. Any vendor that dropped a grade triggers the decision protocol. Any vendor that improved gets noted.
- Week 1–2: Schedule any accountability conversations required by C or D grades.
That's the full monthly cycle. Two hours of data work, one decision review, and accountability conversations only when required. No full-time analyst needed.
When to Automate
The manual version of this system is a significant upgrade over informal vendor management. It also has a ceiling. As your vendor portfolio grows beyond six or seven vendors, the data collection and calculation work grows proportionally. A firm managing ten lead sources manually is spending 4–6 hours per month on the mechanics — which is where automation starts to make economic sense.
A revenue intelligence platform automates the data collection, calculates cost per case and conversion rate in real time, and surfaces performance alerts when vendors cross defined thresholds — without requiring the monthly manual pull. The scorecard logic stays the same. The platform just eliminates the hours of data assembly that the manual system requires.
Start with the manual system. Build the habit. Learn what the data tells you about your vendor portfolio. Then evaluate whether automation is worth the investment at your current portfolio size and complexity. For most firms managing five or more vendors, the answer is yes — usually within the first 90 days of use.
The One Thing That Makes All of This Work
Every component of this system — the calculation, the scorecard, the decision protocol — depends on one foundational discipline: tagging every lead with a vendor source at intake. Without that tag, you can't connect spend to outcomes. Without that connection, every other piece of the system falls apart.
Start there. Add the lead source field to your intake process today. Everything else builds on that foundation.
RevenueScale's vendor accountability platform automates the data collection, calculation, and alerting that the manual version of this system requires — so PI marketing directors get vendor accountability without the analyst overhead.
Related guide: See our complete guide to evaluating a PI marketing agency — 7 evaluation criteria, red flags to watch for, and how to hold agencies accountable with data.
Related guide:For the foundational guide that frames every post in this cluster, seeRevenue Intelligence for Personal Injury Law Firms: The Definitive Guide — the category thesis, the Four Intelligence Layers, and the path to Level 3 maturity.