Revenue intelligence platforms are easy to sell in a demo. The data is clean. The presenter knows exactly where to click. The dashboard looks like it was built for your firm specifically. Forty-five minutes later, you're ready to sign — before you've tested the one thing that actually matters.
This guide tells you what to demand from any demo, which questions cut through the polish, and which red flags should make you pause — even when the rest of the presentation looks strong.
What the Demo Must Cover
A revenue intelligence demo for a PI firm is not a generic SaaS analytics demo. The platform has to prove it understands your business: 18-month settlement cycles, five to twelve lead vendors competing for budget, intake as a revenue function, and managing partners who want one number — cost per case. Not impressions. Not click rates.
Here's what you should see — and what to ask if it doesn't appear.
Cost Per Case at the Vendor Level
This is the single most important thing the demo must show. Not cost per lead. Not conversion rate. Cost per signed case, by individual vendor — without exporting anything.
Give the presenter a concrete scenario: “I spend $45,000 per month with Vendor A and $30,000 per month with Vendor B. Both deliver about 60 leads per month. Show me which one is cheaper per signed case.”
The answer should be immediate, visual, and obvious. If the presenter switches screens, starts building a custom report, or says “We can set that up during implementation” — that's your signal. Cost per case is the core use case. It should be on the home screen, not in a configuration menu.
Settlement-Cycle Attribution
PI cases take 6 to 18 months to settle. So push the demo into the past: “Show me the ROI for leads that came in 14 months ago. How many signed? How many settled? What was the average settlement value?”
A platform built for PI will have cohort-based tracking ready — every lead from a given month followed through to settlement. That's what tells you whether the $50,000 you spent with a vendor in January actually produced profitable cases, or just a lot of leads that went nowhere.
If the platform only shows trailing-30-day data, it is not built for the PI revenue cycle. Full stop.
Vendor Grading and Comparison
You manage five, eight, maybe twelve lead vendors. You need an apples-to-apples comparison — not just on volume, but on signed case rate, cost per case, case type mix, and settlement value.
Ask to see a vendor scorecard. It should rank vendors on multiple dimensions and make it immediately obvious who is over- and underperforming. A firm spending $350,000 per month across seven vendors could be wasting $40,000 to $70,000 on underperformers — but only if the platform surfaces it clearly. If you have to dig for that answer, you will never act on it fast enough.
Intake Intelligence
Lead quality is an intake problem as much as it is a vendor problem. The demo should show:
- Rejection rate by lead source — which vendors send leads your intake team can't sign?
- Time-to-contact by source — are some vendor leads sitting for hours before the first call?
- Conversion rate from lead to signed case by intake team member — is the bottleneck the lead or the follow-up?
The diagnosis changes the action. If Vendor C's conversion rate is low because the leads are bad, you cut the vendor. If it's low because your intake team takes 6 hours to call them back, you fix the process. Without this data, you're guessing — and usually blaming the wrong side.
Alerts and Proactive Monitoring
Revenue intelligence isn't just reporting what happened. It should tell you when something is wrong before it becomes a $30,000 problem. Ask to see the alert system. Strong examples:
- “Vendor D's lead volume dropped 40% this week compared to the prior 4-week average.”
- “Your cost per signed case with Vendor B has increased from $2,800 to $4,100 over the past 60 days.”
- “Intake rejection rate for Google Ads MVA leads is 35% higher than your firm average.”
No alerts means you're buying a reporting tool. Someone still has to stare at dashboards every morning to catch problems. That's not intelligence — that's just a fancier spreadsheet.
The Report You'd Show Your Managing Partner
This is the demo moment that predicts adoption. Ask: “Show me the report I'd pull for my monthly partner meeting. What does it look like? How long does it take to generate?”
It should take seconds. It should show cost per case by vendor, budget vs. actual, signed cases by source, and trend lines. A managing partner who never logs into the platform should be able to look at it and ask informed questions.
If generating that report means exporting data and reformatting it in PowerPoint, the platform hasn't solved your 15-hours-per-week problem. It's just moved it one step downstream.
Red Flags to Watch For
Keep reading
Not every red flag means “walk away.” Some mean “ask harder questions.” But together, they answer one question: is this platform genuinely built for PI, or just marketed to PI?
The Demo Uses Generic Sample Data
If the demo shows leads, conversions, and revenue from an unnamed company with suspiciously round numbers, the vendor may not have enough PI customers to build realistic sample data. Ask to see anonymized data from a real PI firm. If they don't have it, they're early in their PI journey — which isn't fatal, but changes your risk calculation.
They Can't Show Cost Per Case Without Custom Configuration
“We can build that view during implementation” means cost per case is not a native concept — it's a calculated field added later. That usually means it's fragile. It breaks when data formats change, when new vendors are added, or when someone edits the underlying report. You want cost per case baked in, not bolted on.
No PI-Specific Integrations
“We integrate with any CRM via API” sounds flexible. In practice, it means weeks of custom integration work with your case management system. Native integrations with LeadDocket, Filevine, or Clio mean the vendor has already solved the data mapping problem. “Custom API” means they haven't.
The Platform Requires a Data Analyst to Operate
If the presenter is an engineer walking you through SQL queries and custom report builders, ask yourself: could my marketing director do this alone? Most PI firms with 10 to 50 attorneys don't have a dedicated analyst. The platform needs to work for a marketing director with 30 minutes a day, not 30 hours a week.
Everything Is “Coming Soon”
Every platform has a roadmap. That's fine. But if two or three of your must-have requirements are in “coming soon” rather than production, you're buying a promise. Promises don't show you cost per case.
They Avoid Discussing Limitations
Every platform has limitations. Vendors who claim otherwise are either not being transparent or don't know their own product well enough to be honest. The best vendors tell you upfront what they don't do well — and explain why it doesn't matter for your use case, or what workaround exists.
Questions That Expose the Truth
Keep these ready for any demo. They're harder to rehearse around:
- “What percentage of your current customers are PI firms?” Under 30% means PI is a secondary market — you're not their core customer.
- “Can I see the platform live, right now, with real data — not a prepared slide deck?” Canned demos hide the messy parts.
- “What does onboarding look like for the first 30 days? How many hours of my team's time will it require?” Vague answers mean they haven't done enough implementations to predict accurately.
- “If I called one of your PI customers right now, what would they say is the biggest limitation?” This forces honesty in a way that “What are your weaknesses?” never does.
| Dimension | Green Flag | Red Flag | |
|---|---|---|---|
| PI-specific depth | Built for PI from the ground up | Adapted from a generic platform | |
| Core capability | Cost per case by vendor, natively | Requires custom configuration | |
| Usability | Marketing director can operate solo | Requires data analyst or IT support | |
| Integration readiness | Native LeadDocket, Filevine, Clio | Generic API — custom build required | |
| Transparency | Proactively shares limitations | Everything is perfect or coming soon |
After the Demo: What to Do Next
Within 24 hours, have every stakeholder score the platform independently — before discussing impressions. Individual assessments prevent groupthink from taking over.
Score on five dimensions:
- PI-specific depth — Did this feel built for PI, or adapted for PI?
- Core capability — Can it show cost per case by vendor, through to settlement?
- Usability — Could a marketing director operate this without IT support?
- Integration readiness — Does it connect natively to your case management system?
- Transparency — Was the vendor honest about what the platform doesn't do?
The highest score doesn't automatically win. But the scoring process keeps the decision grounded in what matters — not in who had the slickest slides.
The Bottom Line
A demo is a vendor's best 45 minutes. The data is clean, the presenter knows every click, and the narrative flows perfectly. Your job is to break that flow — push the platform into real-world PI conditions: messy data, twelve active vendors, an 18-month settlement cycle, and a managing partner who wants one number.
The platforms that hold up under that pressure are worth buying. The ones that deflect, defer, or go quiet are telling you exactly what you need to know. Listen.
Related guide:This post is part of our pillar onRevenue Intelligence for Personal Injury Law Firms — start there for the full framework, including the 3 ROI Blockers and the full enrichment stack.
Related guide:For the strategic context this analysis is part of, seePersonal Injury Marketing for Law Firms: The Definitive Guide — covering channels, vendors, attribution, and the executive reporting that ties them together.
