Buying a Revenue Intelligence platform is not like buying a marketing dashboard or a case management system. It's a category purchase. You're not comparing feature lists — you're evaluating whether a vendor can deliver the four intelligence layers in a way your firm can actually operate. This buyer's guide is the evaluation framework PI firms use to make that decision confidently.
The guide is organized into three parts: the must-haves that every legitimate Revenue Intelligence platform should include, the nice-to-haves that differentiate strong vendors from adequate ones, and the red flags that mean you're looking at the wrong vendor. At the end, there's a 10-point evaluation scorecard you can use during demos.
Part 1: The Must-Haves
These are the capabilities that define Revenue Intelligence. A platform that doesn't ship all of these is something else — a dashboard, a BI tool, or a CRM add-on — not Revenue Intelligence. Don't compromise on this list.
| Capability | Why It Matters | |
|---|---|---|
| Cost per case by vendor | The core metric. Without it, vendor grading is guesswork. | |
| Native case management integration | LeadDocket, Salesforce, HubSpot, Filevine, Clio, or MyCase. Without native integration, data plumbing takes months. | |
| Source taxonomy standardization | Platform enforces consistent source labels across intake, marketing, and vendor feeds. | |
| Intake conversion by source | Without it, vendor grades default to cost-per-lead — the wrong metric. | |
| Settlement-level attribution | Closes the loop from first dollar spent to last dollar collected. This is what makes RI different from BI. | |
| Vendor scorecards with threshold alerts | Automated red/yellow/green flags. No manual report assembly. | |
| Partner-ready ROI reporting | One-page exec summary that answers the four questions managing partners ask. | |
| Role-based dashboards | Different views for Marketing Director, Intake Manager, and Managing Partner — not the same view for everyone. |
If a vendor can\u2019t deliver all eight of these on day one, the platform isn\u2019t Revenue Intelligence yet. It\u2019s either a dashboard trying to be one or a roadmap promise that may or may not ship.
Part 2: The Nice-to-Haves
These are the capabilities that differentiate a strong Revenue Intelligence platform from a serviceable one. Not deal-breakers if absent, but they signal category leadership when present.
- Proactive critical alerts.The platform surfaces problems before they show up in the monthly review. A vendor whose conversion rate is declining for three weeks should trigger an alert in week two, not show up in week five's scorecard.
- Case severity / quality scoring by source. Going beyond cost per signed case to cost per settlement dollar. This is the layer that separates mature platforms from basic ones.
- Pace tracking against goals. Month-to-date tracking of signed cases and spend against targets, updated in real time. This is how a Marketing Director runs a Monday morning check in five minutes.
- Multi-location support. If the firm has multiple markets, the platform should standardize source taxonomy across offices while allowing market-level segmentation.
- Forecasting / predictive trends.Leading indicators that flag vendor performance shifts before they hit the P&L. Requires the platform to have accumulated enough historical data to be meaningful.
- Monthly analyst touchpoint.A human from the vendor who reviews the firm's intelligence monthly and surfaces patterns the firm might miss. Strong signal of category seriousness.
Part 3: The Red Flags
If you see any of these during evaluation, it's not a Revenue Intelligence platform. Walk away.
- “You'll need to configure the attribution logic yourself.” This is a BI tool with marketing branding. Not Revenue Intelligence.
- No native PI case management integration.If the vendor requires you to build the CMS connection via custom API work, you're buying a dashboard.
- Cost per lead is the headline metric.If the demo leads with CPL instead of cost per signed case, the platform doesn't have Source Intelligence in the meaningful sense.
- “We work with all industries.” Revenue Intelligence for PI is a vertical category. A horizontal platform that claims to work for PI usually means “you'll build the PI-specific logic yourself.”
- 6-month implementation. Revenue Intelligence should deliver Phase 1 value in week one, not quarter two.
- No SOC 2 Type II certification. Non-negotiable for any vendor touching firm data.
- Vague on data ownership.The firm must own the data. Any vendor that doesn't make this explicit in the contract is a risk.
- “The dashboard is fully customizable.” Customization sounds good but it often means the vendor has pushed the configuration work onto you. Look for opinionated, role-based views instead.
The 10-Point Evaluation Scorecard
Score each vendor you're evaluating on the following ten criteria. Give each item 0, 1, or 2 points (0 = missing, 1 = partial, 2 = delivered). Maximum score is 20. A vendor scoring 16+ is ready to buy. A vendor scoring 12–15 has potential but should answer specific gaps before signing. Anything under 12 is not Revenue Intelligence yet.
Illustrative example of how to score a vendor on the 10 evaluation criteria. Total possible: 20 points. Target: 16+.
Questions to Ask During the Demo
The demo is where vendors separate themselves. Ask these four questions and watch how the vendor responds. The answers tell you everything.
1. “Show me cost per case by vendor for a real firm similar to ours.”Not a mockup, not a placeholder. If they can't show it live, the capability either doesn't exist or requires custom build.
2. “Walk me through how you connect to our case management system.”Native integration should be a single sentence. If they describe a multi-week data engineering process, you're buying promises.
3. “What does the managing partner see on day 30, day 60, and day 90?”Revenue Intelligence is a milestone business. Vendors who can't describe the milestones clearly haven't delivered them.
4. “What happens if we decide to leave in year two?” Their comfort level with this question tells you how confident they are in the product. Vendors who dodge exit-conversation questions usually have a reason.
One Last Thing: The Category Test
Before you sign, ask yourself one question: is this vendor trying to own a category, or trying to sell you features? Category owners talk about the Four Intelligence Layers, the maturity model, the Three Enemies, and the PI payment delay as a design constraint. Feature sellers talk about dashboards, integrations, and report customization.
The difference matters because category owners are building long-term advantage into the platform. Feature sellers are building until someone else builds the same feature cheaper. You're making a multi-year commitment. Buy the category, not the features.
Related guide: For the full category framework that should inform every evaluation, see Revenue Intelligence for Personal Injury Law Firms: The Definitive Guide.