How LexSteer Works

LexSteer helps PI firms practice Intake Yield Management — continuously improving intake performance by identifying, classifying, and preventing avoidable loss — by making intake loss visible, then governing the critical Handoffs where paid-for demand is most often lost. It is designed first for the COO, intake director, and operations leader who need a factual picture of how intake is behaving day to day — and then for firm leadership that needs confidence the findings are real, the rollout is controlled, and the gains will hold over time.

INTRODUCTION

Most firms do not need another abstract intake improvement program. They need a way to see where cases are actually disappearing, separate operational loss from lead-quality issues, and govern the Handoffs where response delays, ownership gaps, and missed transitions quietly turn paid-for demand into Lost Pipeline.

LexSteer does that in a controlled sequence:

  1. Run a Visibility analysis on the firm's own historical data.
  2. Show where loss is occurring and what kind of loss it is.
  3. Run Shadow Mode in live operations without taking action.
  4. Activate Operational Governance only after the firm has seen how the rules behave in practice.

For the COO or intake director, that sequence replaces guesswork with a concrete map of where the operation is underperforming today and what it would take to protect those points in live traffic.

FIG-001 — The CAS Handoff Chain

WHERE LEXSTEER SITS

The diagram below shows LexSteer's position relative to the firm's existing systems. It is not a replacement for any of them — it is a different kind of layer entirely.

The CRM, the phone system, the case-management platform, and everything else in that stack run the practice: they record what happened and route what's next. LexSteer sits above that stack and does the one job none of them is built to do — continuously check whether the practice is getting better, on purpose, month over month, and act on the Handoffs where it isn't. That's the same distinction the rest of this site draws between running a practice and improving one; this diagram is what it looks like at the systems level.

LexSteer Architecture: The Control LayerThree-layer diagram showing the firm's existing systems at the bottom (telephony/messaging and CRM/LPMS, both read-only except where governance writes back), the LexSteer control layer governing every handoff in the middle, and the three outputs it can trigger at the top — reassignment first, escalation if that fails, then a governance report. Outputs are shown in green, the LexSteer control layer in blue, and the firm's existing systems in dark grey.OutputsControl Firm's systems, read-only ReassignmentReroutes stalled handoffEscalationAlerts to supervisorGovernance reportViolation log, outcomesLexSteer — control layerEvery handoff. Governed.Telephony / messagingLeading telephony providersReads only — no replacementCRM / LPMSPI-focused CRM and case-management platformsReads; writes only under governancereadsreadsgovernsLexSteer reads from the firm's systems and writes back only under Governance — it replaces nothing.
LexSteer's control layer relative to the firm's existing telephony and CRM systems.

LexSteer reads from the firm's telephony and CRM systems continuously. Under the Governance Pack, it writes back selectively — escalations and reassignments — only when a Handoff has stalled past its configured response window. Nothing below it in that stack is replaced. Nothing below it is displaced. What's added is the layer whose job is the practice's improvement, not its day-to-day operation.

Why this isn’t “operational governance” with a new name →

PHASE 1 — VISIBILITY PACK

Start with your own historical data.

The Visibility Pack begins with a structured analysis of the firm's historical intake data, typically across roughly 180 days of inbound arrival records, CRM activity, and intake-stage movement.

The purpose is not to generate another dashboard. It is to identify where cases disappeared, attribute that loss to the right source, and give operations and leadership a shared factual starting point for action.

LexSteer evaluates intake against the core loss framework used across the site:

  • Capture Loss — prospects never entered the intake system reliably.
  • Process Loss — prospects entered the system but stalled at a callback, review, retainer, or other critical Handoff.
  • Qualification Failure — the prospect was followed up appropriately but was not a case the firm would have signed.
FIG-002 — The Three-Category Loss Taxonomy

That's the taxonomy the rest of the Visibility Pack works from — three separate, solvable problems, each with its own owner, not one blended “conversion rate.”

Telling the three apart isn't always instant. Prospects handled within the firm's configured Attribution Confidence Window set the floor: whatever still doesn't qualify at that speed is a Resolved, high-confidence Qualification Failure attribution — a clean lower-bound estimate, since response speed is no longer a credible explanation.

Past that window, the rejection rate climbs — but that rise mixes Qualification Failure with Process Loss in a way timing data alone can't separate. The Visibility Pack calls this population Non-Distinguishable, and reports it as such rather than guessing. As response times improve, the Non-Distinguishable population shrinks and the Qualification Failure estimate sharpens — a progressive narrowing that begins to resolve the three-way argument with evidence, not a single clean finding on day one. Ruling out timing this way also doesn't, by itself, say who owns the fix: a Resolved Qualification Failure still splits into Qualification Failure — Lead Quality or Qualification Failure — Judgment, separated by the Qualification Failure Dispersion Check, not assumed by default.

FIG-003 — Attribution Confidence: Resolved vs. Non-Distinguishable

Resolved and Non-Distinguishable are exactly what the map above shows — a floor you can trust immediately, and a population that narrows as response speed improves.

See it in a sample Visibility Pack

Illustrative Visibility Pack sample, drawn from one internally consistent synthetic dataset — every percentage below reconciles to an underlying integer count and to the stage before it. The figures are not any real firm's data.

The sample firm

7-Attorney PI Firm, Midwest. 180-day analysis, report generated March 2026.

Stage Count % of arrivals Stage conversion
True arrivals 1,800 100.0%
CRM captured 1,404 78.0% 78.0% (Capture)
Contacted within required window 1,264 70.2% 90.0% (CFR)
Qualified 1,095 60.8% 86.6% (FQR)
Attorney consultation 684 38.0% 62.5%
Retainer offered 540 30.0% 78.9%
Signed 432 24.0% 80.0%

CFR — Contact Follow-up Rate: of prospects captured, the fraction contacted inside the firm's own configured response window. FQR — Follow-Up-to-Qualified Rate: of those contacted, the fraction that passed intake qualification.

Capture — your true arrival count.

Your CRM only shows what got captured. The Visibility Pack reconstructs the arrivals you never logged — prospects you paid for that appeared as nothing.

True arrivals
1,800
CRM captures
1,404
Capture Loss Rate
22.0%
Never captured
396

396 prospects reached you and were never logged — every one paid for.

True arrivals span every inbound channel — telephony, web form, SMS, WhatsApp, and chat. Telephony calls that disconnect within 15 seconds are excluded as likely misdials (the threshold is configurable); web, SMS, and chat submissions are counted regardless of duration, since any deliberate submission signals a prospect.

Where your coverage fails — missed arrivals by hour and day

Relative concentration of the 396 missed arrivals — darker cells are heavier loss. After-hours cells are structural. Business-hours cells are recoverable through governance.

Missed arrivals heatmap

12a 3a 6a 9a 12p 3p 6p 9p
Mon
Tue
Wed
Thu
Fri
Sat
Sun

Illustrative example. Your Visibility Pack is built from your firm’s own data.

Process — your timing picture.

Time-in-stage: your firm vs. benchmark

0h 2h 4h 6h 8h 10h 12h Contact Callback Review Retainer Benchmark range Typical firm range Flagged Callback range

How fast captured prospects received follow-up contact

under 5 min

18%

5–15 min

12%

15–60 min

20%

1–4h

28%

4–24h

17%

over 24h

5%

Prospects in the slower buckets are at elevated risk of competitive loss before contact is made.

Process Failure Rate — weekly pattern: Unstable

Unstable

Week-by-week, the firm's Process Failure Rate is tracked as a statistical pattern and classified using the same four-state health model — Stable, Improving, Deteriorating, Unstable — described under Phase 3 below, so a genuine trend is never confused with ordinary week-to-week noise.

Illustrative example. Your Visibility Pack is built from your firm’s own data, including SPC analysis across all tracked stages.

Qualification — who owns the fix.

Contact Follow-up Rate (CFR)

90.0%

Stable

PROCESS (OPERATIONS)

Benchmark: ≥ 85% — higher is better. Measured against this firm's own configured response window, not a fixed industry threshold.

Qualification Failure Rate

13.4%

Stable

DIAGNOSED BELOW — OPERATIONS OR MARKETING

Lower is better.

Attribution confidence — what the timing data can and cannot prove

The Qualification-vs-Process split is only clean for prospects handled within the firm's configured Attribution Confidence Window. For those, delay is not a credible explanation for non-conversion, so a rejection at qualification confidently rules out a timing problem. For prospects handled more slowly, the cause is ambiguous — the data alone cannot separate a genuine decline (or an agent's misjudgment) from Process Loss.

Qualification Failure

Resolved

103of 169 failures — 61%

Handled within the configured Attribution Confidence Window. Timing is confidently ruled out — see the Dispersion Check below for whether the remaining cause is lead quality or agent judgment.

Non-Distinguishable

Unresolved

66of 169 failures — 39%

Response was delayed; cause is ambiguous. Consistent with either a genuine decline or Process Loss. As response speed improves, this population thins and the estimate sharpens.

Qualification Failure — Resolved is confidently attributed within the configured Attribution Confidence Window. The remainder is Non-Distinguishable — Qualification Failure and Process Loss that timing data alone cannot separate. Counts and percentages reconcile to the sample dataset above.

Ruling out timing isn't the same as knowing who owns the fix. A confirmed Qualification Failure could mean the leads themselves aren't converting — Qualification Failure — Lead Quality — or it could mean an intake agent is misjudging cases that should have qualified — Qualification Failure — Judgment. Both produce the identical outcome and timing signature.

The bigger loss sits at a different Handoff.

Qualification Failure — even fully diagnosed — accounts for 169 of the 1,800 arrivals. A larger, separately-owned loss shows up one stage later: of the 1,095 prospects who qualified, only 684 reached an attorney consultation. That's 411 qualified prospects — 37.5% of the qualified population — stalled at the qualified-prospect-to-consultation Handoff. This is not a lead-quality question, and it is not the same finding as Qualification Failure — Judgment below: it is Process Loss at a specific, later Handoff, and on this sample firm's numbers it is the larger of the two losses.

Qualification Failure Dispersion Check — who owns the 103

The Resolved share splits further into one of three outcomes: Qualification Failure — Lead Quality (the cause tracks the leads, not the people), Qualification Failure — Judgment (declines concentrate with specific intake agents — a coaching and training question, not a marketing one), or Qualification Failure — Undetermined (Shared Cause) (the data doesn't yet support a confident split either way, and the honest answer is to say so rather than guess). LexSteer's Dispersion Check looks at how declines are distributed — across agents, and across lead channels — to determine which of the three applies, rather than defaulting to an assumption in either direction.

Blind Spot

Pending data field

Lead source field population in your CRM is required to produce channel-level attribution. This finding is available once source tracking is configured.

What recovering the bigger loss is worth.

Not all 411 stalled prospects would have signed — only the firm's own observed downstream conversion should be applied. At this sample firm's observed consultation-to-signed rate (432 signed ÷ 684 consultations = 63.2%):

Recovery of missed Handoffs Additional signed cases / yr
10% ~52
20% ~104
30% ~156
50% ~260

180-day figures annualized. Recovery = missed Handoffs × recovery rate × the firm's own 63.2% consultation-to-signed rate, doubled to a 12-month basis.

The 50% row matches the leakage calculator's own default recovery target further down this page, which states its own 30–50% conservative-starting-point guidance. Same math, different assumed recovery rate — not two methods. Typed into that calculator, this firm's numbers sit at or better than benchmark on process and qualification, and worse on capture (22.0% loss against an 18% benchmark) — and at 49.3% against an 80% benchmark on qualification-to-retainer. That qualification-to-retainer gap is the finding.

At the firm's own average contribution margin per signed case, any row converts directly into a dollar figure — the Visibility Pack does that conversion using the firm's own numbers, never an industry-average one.

Illustrative example. Your Visibility Pack is built from your firm’s own data.

Sample report excerpt

Visibility Pack — Intake Diagnostic

Sample Report — 7-Attorney PI Firm, Midwest

Stage-by-Stage Fallout

Arrival (all channels)
100%
CRM Entry
78%
Qualification
61%
Consultation
38%
Retainer Offered
30%
Signed
24%

37.5% of qualified prospects — 411 of 1,095 — stalled before reaching attorney consultation, the firm's largest single operational loss.

Verdict: Primary finding — the qualified-prospect-to-consultation Handoff. Secondary finding — Qualification Failure — Judgment, concentrated among two intake agents.

Recovering 10% of the missed Handoffs implies roughly 52 additional signed cases per year, at this firm's own observed consultation-to-signed rate (180-day figures annualized). Revenue and recovery target are yours to set — at your average case economics, that is the recoverable value.

Report generated: March 2026  |  Data period: 180 days

Your data stays within the scope of intake, CRM, and telephony records — the Visibility Pack works from operational metadata about your intake process, not clinical or treatment records.

How the data is handled

To run the Visibility Pack, LexSteer works from the firm's historical data under standard confidentiality safeguards. The process begins with a mutual NDA and relies on a guided export session so the firm can provide the necessary historical records without LexSteer taking control of live operations. The data in scope is intake, CRM, and telephony metadata — call and message records, timestamps, and stage movements — not clinical or treatment records.

At this stage, the goal is Diagnosis — naming which kind of loss you actually have — rather than intervention. The Visibility Pack is a bounded historical analysis designed to show what happened, where it happened, and what it may be costing.

Visibility Pack deliverables

Loss Inventory

A firm-specific view of where loss is concentrated across the intake journey, including where opportunities disappeared by stage and source.

Economic Impact Assessment

An estimate of what those losses imply in likely lost signed cases and recoverable financial impact, built from the firm's own case economics rather than a generic industry figure.

Prioritized Improvement Roadmap

A sequenced view of which issues to act on first. Sequencing isn't by raw metric size alone — each finding is surfaced because it violates a threshold the firm itself configured, because it diverges materially from the firm's own peer pattern (which agent, which channel), or because it shows a genuine statistical shift rather than ordinary week-to-week noise. That three-part basis is what keeps the roadmap grounded in evidence rather than a generic checklist.

PHASE 2 — SHADOW MODE

See governed behavior before anything is enforced.

Once the Visibility phase is complete and the firm wants to evaluate live Operational Governance, LexSteer moves into Shadow Mode.

For approximately 30 days, Shadow Mode observes the live intake operation exactly as full Operational Governance would, but stays read-only: it logs every Handoff that missed its expected timing, every case where a backup path would have been used, and every unresolved stall that would have required escalation — without actually rerouting, escalating, or touching a single live case. That's the proving ground: the COO sees exactly which Handoffs would have triggered intervention and how often, before any of it is allowed to act.

Week 1

Baseline intake patterns established. First escalation candidates identified.

Week 2

Weekly summary delivered: how many escalation alerts, how many reassignments, at which stage.

Week 3

Patterns stabilize. Systemic vs. episodic breakdowns become clear.

Day 28

A concrete picture of what governed execution would look like in the firm's own intake environment. One question: do you want the specific protections you have already seen turned on?

PHASE 3 — GOVERNANCE ACTIVE

Govern the Handoffs that matter most.

When the firm approves activation, LexSteer begins governing the critical Handoffs where delay, ambiguity, or missed ownership are most likely to destroy yield.

A Governed Handoff is not just a task with a reminder attached. It is a transition watched against a defined timing expectation, with a rule for what happens if the intended owner does not respond in time.

Step 1: Detect

LexSteer detects that a critical Handoff has stalled — a transition that should have advanced and hasn't.

A prospect calls at 9:14 PM on a campaign tracking number. Your telephony platform logs the call. Your CRM has no matching record. The Handoff has stalled — LexSteer sees the gap immediately.

Step 2: Apply rules

It applies the firm's timing and ownership rules — the SLAs and policies that define how that specific Handoff is supposed to behave.

Step 3: Reroute

It reroutes to a backup owner or path when the primary owner does not respond in time, so the case keeps moving instead of waiting.

Step 4: Escalate

It escalates when the backup path does not resolve the gap — carrying the problem upward until someone can act on it.

Step 5: Verify

It verifies whether the case actually recovered and moved to the next stage. The loop doesn't close on the alert — it closes on the outcome.

That whole sequence creates a single Operational Obligation. It moves from created to alerting automatically, is acknowledged only by a committed resolution date — never by a claim that the fix worked — and closes only when Visibility itself confirms the case actually moved forward, or reopens and escalates to a different role if the committed date passes first.

This is the difference between alerts and Operational Governance. Alerts can tell a team that something went wrong. Operational Governance carries the problem through to a known operational outcome.

FIG-004 — The Governance Closed Loop

How drift gets classified

Not every warning sign means the same thing, and treating them as if they do wastes a firm's attention on the wrong problem. Once a Handoff is governed, LexSteer classifies its stage into one of four health states, because each calls for a different response.

Stable

A Stable stage that's underperforming needs a calibration change, not an investigation.

Improving

An Improving stage needs to be watched to confirm the gain holds, not treated as already fixed.

Deteriorating

A Deteriorating stage needs early intervention before it breaches control limits — the cheapest point to catch it.

Unstable

An Unstable stage needs investigation into a specific event, because something identifiable just happened.

This is what lets Operational Governance respond to the right kind of problem instead of treating every fluctuation as an emergency or every slow decline as noise.

FIG-006 — The Four-State Health Model

For a COO responsible for intake performance, this is the layer that turns “we assigned it” into “we know it was handled,” with a traceable loop from detection, to response, to verification.

Just as importantly, Operational Governance is about protecting gains — not only achieving them. It helps ensure improvements are executed, verified, and sustained over time, long after the original project ends.

See exactly what happened, and what LexSteer did about it

Operational Governance runs continuously, but a COO or managing partner sometimes needs to look backward, not just trust that it worked. Operational Playback lets you move to any point in your firm's intake history and see, at that exact moment, what the operation looked like and what LexSteer was doing about it — which Handoffs were open, what had already been escalated, and what verification had or hadn't completed.

It's historical and read-only: Playback doesn't change anything or re-run anything, it shows you what already happened.

YOUR CURRENT TOOLS

LexSteer works with the systems you already use.

LexSteer is not a replacement for telephony, CRM, workflow, analytics, or the intake team itself. Those systems already do useful jobs. But their responsibility usually ends before governed execution begins.

CRM / case-management systems

Record status and activity, but do not ensure that critical Handoffs complete on time.

Workflow automation

Can trigger actions, but often assumes the action was completed unless a separate Operational Governance step verifies it.

Dashboards and analytics

Explain the past, but usually do not intervene in live stalled work.

Consultants and process redesign

Can improve operating design, but do not usually remain inside the live system governing whether gains hold.

People and managers

Often approximate this layer through effort and oversight, but that layer is usually fragmented, inconsistent, and not timely enough for perishable demand.

FIG-008 — Why LexSteer Is a Different Category of Software

For a COO, this is the missing layer between “we have systems” and “the critical work is actually getting done on time.”

LexSteer is designed to sit as that layer between systems of record and day-to-day execution.

CONTINUOUS OPERATIONAL IMPROVEMENT

Improvement should not fade after the first fix.

The work does not stop at Visibility and Governance Pack activation.

Visibility supplies the full picture of where loss is occurring and how much it's worth. Operational Governance keeps each fix from leaking back out as staff change, priorities shift, and local workarounds reappear. Together they form Continuous Operational Improvement: not a one-time intervention, but a loop the firm controls — Visibility identifies the next Source of Loss, the specific stage where the largest recoverable loss now sits; Operational Governance sustains the fix; and the four-state health picture shows exactly when the next constraint needs attention.

FIG-010 — The Continuous Operational Improvement Cycle

The goal is a more durable intake operation whose critical Handoffs are visible, governed, and less dependent on memory or heroic oversight.

For the COO or intake director, that means a way to keep signed-case performance from sliding backward in the background while day-to-day demands compete for attention. For firm leadership, it is how gains hold instead of fading after the initial fix.

What this looks like as a firm grows

Numbers are illustrative. The structural pattern is the point.

Operational clarity vs firm sizeTwo lines diverging as firm size grows. Without governance, operational clarity degrades. With LexSteer, it is maintained.Operational clarity5 attorneys15 attorneys20+ attorneysDirect visibilityGoverned (LexSteer)Uncontrolled drift

Operational Drift Across Firm Growth Stages

Operational drift across firm growth stages

Numbers are illustrative. The structural pattern is the point.

5 ATTORNEYS · BASELINE

Process working.
Governed by proximity.

Outcome metrics (visible to leadership)

Arrivals / month
120
Signed cases / month
18
Conversion rate (ASR)
15.0%

Internal stage metrics

AC capture rate
88%
Avg. response time
14 min
Timing compliance
94%
Retainer cycle time
3 days
After-hours coverage
82%

Direct oversight catches failures in real time. The managing partner sees everything — no formal system needed.

A Visibility Pack taken here establishes the reference baseline while the process is clean.

10 ATTORNEYS · DRIFT BEGINS

Internal decay.
Outcomes appear stable.

Outcome metrics (visible to leadership)

Arrivals / month
210
Signed cases / month
29
Conversion rate (ASR)
13.8%

Internal stage metrics

AC capture rate
79%
Avg. response time
31 min
Timing compliance
76%
Retainer cycle time
7 days
After-hours coverage
61%

Internal metrics degrading materially, but signed-case count grows with headcount — outcome numbers mask the decay. No alarm is triggered.

No stage-level data is gathered; no statistical processing is applied. The 1.2pt conversion drop reads as normal variance.

15 ATTORNEYS · CRISIS VISIBLE

Outcome collapse.
No baseline to explain it.

Outcome metrics (visible to leadership)

Arrivals / month
310
Signed cases / month
31
Conversion rate (ASR)
10.0%

Internal stage metrics

AC capture rate
63%
Avg. response time
74 min
Timing compliance
51%
Retainer cycle time
11 days
After-hours coverage
34%

Outcome collapse now visible. 2.6× more arrivals, only 1.7× more signed cases. The firm is spending more to produce proportionally fewer results.

Baseline is gone. The firm cannot attribute failure to any stage or period. Recovery requires working backward from a degraded state.

Key insights

Why drift is invisible until it's expensive

No stage-level data is gathered as the firm grows, and no statistical processing is applied to what little exists. Without continuous measurement against a reference baseline, there is no mechanism by which drift becomes visible before it has produced a signed-case shortfall.

Marketing quality vs. operations failure

At 15 attorneys, the firm cannot determine whether the conversion drop reflects lead quality decline or process failure. The Visibility Pack resolves this by measuring at the telephony arrival point — before the CRM — separating what the marketing channel delivered from what the intake process did with it.

Adding volume amplifies the loss

At 15 attorneys: 310 arrivals × 10% = 31 signed cases. At 5 attorneys: 120 × 15% = 18. The firm spent more on marketing, received more arrivals, and the failure rate applied to every incremental dollar. Spend growth into a drifting process is not a recovery strategy.

The baseline question depends on where you are in the journey

For a firm planning to grow, the right time to commission the Visibility Pack is before growth adds complexity: a baseline established while the process is still working is the reference point that makes drift detectable as it begins. For a firm already in growth, the diagnostic value is unchanged — it shows where the current process is failing and what recovery is worth from here, even though the baseline it establishes reflects the current state rather than a known-good prior one. You cannot recover the window that has passed. You can close it from today.

A process that runs on the managing partner's direct knowledge is not an asset — it is a dependency. It does not transfer to a successor, scale with headcount, or survive sustained absence. Encoding the standard in a control system is what makes it durable.

Why yield beats spend in a consolidating market →

ESTIMATE YOUR OWN LEAKAGE

Estimate what your own leakage is costing you

The calculator below lets you work through your intake funnel with your own numbers — or leave the industry benchmarks in place to see what a typical mid-market PI firm is losing. Nothing you enter is stored or shared.

Your firm
$
Funnel rates
18%

What fraction of prospects who contacted your firm were never logged in the CRM? This is an intake coverage metric.

25%

What fraction of captured prospects were lost due to process failures — late or absent follow-up contact? This is an operations metric.

30%

What fraction of followed-up prospects did not convert? Owner depends on the cause — Qualification Failure — Lead Quality (marketing) or Qualification Failure — Judgment (operations) — see the Dispersion Check above, not assumed by default.

Adjust advanced inputs (QRR, RSR, avg case value)
80%

Of qualified prospects, what fraction proceed to retainer offer?

90%

Of retainer offers made, what fraction are signed?

Net contribution margin per signed case (not gross settlement).

$
Recovery target
50%

What portion of this identified loss do you believe is addressable in the first year? A conservative starting point is 30–50%.

Lower-bound annual leakage

$0

0 recoverable signed cases / year

Current cost per signed case: → With recovery:

Composite loss rate:

This estimate uses your Capture Failure Rate, Process Failure Rate, and Qualification Failure Rate inputs. QRR and RSR are held at benchmark values unless you have adjusted them. Your actual leakage is likely higher — the Visibility Pack is built from your firm's own telephony and CRM data and will show you the precise number at each stage.

These inputs are estimates based on your judgment or industry benchmarks. Process Failure Rate and Qualification Failure Rate can only be precisely separated when response timing data is available from your firm's actual intake system. Process failures include both execution gaps — follow-up or consultation that did not occur within SLA — and capacity constraints, where demand exceeded available intake or attorney bandwidth at that stage. The Visibility Pack identifies which stage the timing failures are concentrated in — the intake response stage or the attorney consultation stage — pointing to the right owner and the right remedy: a governance fix or a resourcing decision. Losses in the QRR and RSR stages — between consultation and retainer offer, and between offer and signed — are measured but not classified in the current framework. They include attorney execution factors — retainer offer cycle time, follow-through after consultation — which are within the firm's control, and case or prospect fit factors — case merit, prospect's choice of another firm — which are not. The Visibility Pack surfaces these as separate stage metrics.
Funnel detail
Funnel waterfall — current vs. benchmark Bar chart comparing the current funnel against industry benchmarks across six stages: arrivals, after capture filter, after process filter, after qualification filter, after QRR, and signed cases. Current Benchmark Arrivals 0 Capture 0 Process 0 Qualification 0 After QRR 0 Signed 0
100 prospects through each funnel stage — your inputs (primary bars) vs. industry benchmark reference (dashed overlay).

Benchmarks: Capture Failure Rate from Clio 2024 Legal Trends Report. Process Failure Rate and Qualification Failure Rate are illustrative starting points — adjust to reflect your firm. QRR/RSR from Clio 2024 Legal Trends Report. Industry CPS $4,200 from same source.

See what your own intake looks like.

The right first step is Diagnosis, not product commitment. The strongest starting point is Visibility — because better action depends on seeing where loss is actually occurring, what kind of loss it is, and what it may be worth to recover.