Most PI firms have lead vendor contracts that define price and volume. Very few have contracts that define performance. The result is a relationship with no shared standard — which means every accountability conversation starts from scratch, and every dispute becomes a negotiation about what was supposed to happen rather than whether it happened.
A service level agreement (SLA) changes that. It creates a written standard that both parties agree to upfront — and makes every performance conversation a data review rather than a debate.
Here's what a well-built PI lead vendor SLA actually looks like.
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 Makes a PI Vendor SLA Different
SLAs in most industries focus on delivery metrics: uptime, response time, ticket resolution. In PI lead generation, delivery is table stakes. The metric that matters is what happens after delivery — whether leads convert to signed cases at an acceptable cost.
That distinction drives everything about how a PI vendor SLA should be structured. It needs to define performance at the output level (cost per case, conversion rate) not just the delivery level (leads delivered, contact rate).
The Core SLA Metrics
Cost Per Signed Case Target
The most important SLA metric is cost per signed case — your total spend with this vendor divided by signed cases attributed to their leads. This is the number that determines whether the investment is financially viable.
Define the target in the SLA as a specific dollar threshold, not a range. For a firm with a blended average cost per case of $3,000:
- Ramp period target (months 1–4):Cost per signed case <$3,500
- Steady-state target (month 5+):Cost per signed case <$3,200
- Measurement window: Rolling 90-day average, evaluated on the 1st of each month
The rolling 90-day window is important. It smooths out short-term noise while catching genuine performance changes quickly enough to act.
Minimum Conversion Rate
Lead-to-case conversion rate should have a defined floor. A conversion rate below threshold means you're paying for leads that have no realistic path to a signed case.
For motor vehicle accident leads in a competitive urban market, a minimum conversion rate of 5–6% is reasonable as a steady-state floor. For mass tort or specialty case types, calibrate this to your firm's historical acceptance rate.
Maximum Rejection Rate
Define the rejection rate threshold and the rejection categories that count against it. Not all rejections are the vendor's fault — a prospect who declines representation after intake is different from a lead that was rejected because it was out of geography.
The SLA should specify which rejection reasons count toward the vendor-attributed rejection rate:
- Geographic mismatch (lead is outside defined service area)
- Case type mismatch (incident type is outside defined practice areas)
- Statute of limitations exceeded
- Prior representation confirmed at intake
- Duplicate lead (same claimant submitted previously)
A maximum vendor-attributed rejection rate of 20% is reasonable for most PI lead types. Above 25% triggers the remedy clause.
Monthly Volume Commitment
Define the monthly lead volume floor — the minimum the vendor commits to deliver — and the volume ceiling if you have intake capacity constraints. Both protect you: the floor ensures you get what you're paying for, the ceiling prevents overflow that strains your intake team's ability to respond quickly.
Include a make-good provision: if the vendor misses the monthly volume floor by more than 15%, they carry the shortfall into the next month or provide a credit at the agreed CPL.
Lead Response and Delivery Standards
Speed-to-lead is one of the most consistent predictors of intake conversion. Your SLA should define:
- Delivery format and method: How are leads delivered? API push, email, portal? This should be explicit.
- Delivery hours: Are leads delivered 24/7, or only during business hours?
- Data fields required: What information must be included with each lead? At minimum: full name, phone number, incident date, incident description, geographic location.
- Exclusivity window: Is this lead being sold exclusively to your firm, or is it also sold to competitors? If non-exclusive, how many buyers receive the same lead simultaneously?
| Metric | Ramp Target | Steady-State Target | |
|---|---|---|---|
| Cost Per Signed Case | < $3,500 | < $3,200 | |
| Min Conversion Rate | 5% | 6%+ | |
| Max Rejection Rate | 25% | 20% | |
| Monthly Volume Floor | Negotiated | Contractual minimum |
The Remedy Structure
An SLA without a remedy is a wish list. The remedy structure defines what happens when thresholds are missed — and it's the part of the SLA most likely to drive vendor behavior.
A tiered remedy structure works well:
- Tier 1 (first breach in a 6-month period): Mandatory performance review meeting within 10 business days. Vendor presents a remediation plan.
- Tier 2 (second breach in a 6-month period): Budget reduction of 25% for the following 60 days. Vendor provides a written remediation plan with specific actions and timeline.
- Tier 3 (third breach in a 6-month period, or sustained Tier 1/2 failure beyond the remediation window): Contract termination with [30/60]-day notice.
The credit provision for rejections can sit alongside the performance remedy structure: leads rejected within 48 hours for qualified reasons are eligible for a per-lead credit at the contracted CPL.
The Measurement Methodology Clause
This is the clause most firms forget to include — and the one that prevents the most disputes. Define explicitly how performance will be measured:
- Data source:Performance is measured using the firm's intake and case management system data, not vendor-reported data. Vendor reports may be used as reference but do not override the firm's independent measurement.
- Attribution methodology: A case is attributed to this vendor if the lead that initiated the contact was delivered by this vendor within the preceding [90/120] days.
- Measurement cadence: Performance metrics are calculated on a rolling 90-day basis, updated on the 1st of each month.
This clause eliminates the most common vendor dispute: “our numbers say we're performing; your numbers say we aren't.” When the measurement methodology is agreed in advance, there's no room for that argument.
Tier 1 — First Breach
Mandatory performance review within 10 business days. Vendor presents remediation plan.
Tier 2 — Second Breach
25% budget reduction for 60 days. Written remediation plan with actions and timeline.
Tier 3 — Third Breach
Contract termination with 30/60-day notice. Sustained failure beyond remediation window.
Getting Vendors to Sign an SLA
Some vendors will push back on performance-based SLAs, particularly on cost per case targets, because conversion is partially determined by your intake quality — which is outside their control. This is a legitimate point, and the SLA should acknowledge it.
The standard response: “We understand that intake performance affects conversion rates. That's why we track conversion across all vendors simultaneously — if our intake performance declines, it shows up across all vendors proportionally, not just yours. A vendor-specific decline in conversion rate is a lead quality signal, not an intake signal.”
Vendors who are confident in their lead quality will accept this reasoning. Vendors who push back hard on any accountability standard are telling you something about their confidence in their own performance.
RevenueScale's vendor performance tracking measures the metrics your SLAs are built on — cost per case, conversion rate, rejection rate — in real time and by vendor, so PI firms can hold vendors accountable at scale.