
Buying cases
How to evaluate an MVA case acquisition vendor
Velocity Axis
·
·
7 min read
Evaluate an MVA case acquisition vendor by the promises it will put in writing and the claimant-level records it will deliver. Six checks expose most of the commercial difference: criteria, replacement grounds, consent evidence, exclusivity, billable unit, and reporting.
What should the firm request before comparing prices?
Request the proposed order, service agreement, replacement policy, sample claimant record, consent artifacts, and reporting view. Pricing without those materials leaves the firm comparing numbers attached to undefined events.
A usable review begins with this table:
CHECK | WRITTEN QUESTION | EVIDENCE AFTER DELIVERY |
|---|---|---|
Criteria | Which exact claimant facts must be true? | Delivered criteria fields |
Replacements | Which defects qualify, by when, with what proof? | Flag and decision record |
Consent | What documents the origin and opt-in event? | Claimant-level artifacts |
Exclusivity | Who is prohibited from rerouting the claimant? | Contract term and source record |
Billing | What exact event creates a charge? | Timestamped delivered unit |
Reporting | How are delivery, status, and disputes recorded? | Dashboard and receiving-system copies |
Run every vendor through the same six rows. A verbal promise should be marked absent until it appears in the controlling paper.
Are the claimant criteria written field by field?
The criteria should describe a record that intake can test. Terms such as high quality, good case, or prequalified do not state the accident window, treatment condition, coverage requirement, or attorney status.
The Velocity Axis Criteria Written into Each Order page provides a practical field list:
CRITERIA GROUP | QUESTIONS TO PUT IN WRITING |
|---|---|
Case and accident | Which case type and accident-recency window apply? |
Injury | Is a confirmed injury enough, or are severity floors or named injuries required? |
Treatment | Is care required, how quickly must it start, and what gap is allowed? |
Insurance | Whose insurance must exist and which coverage must be available for recovery? |
Status | What fault, representation, and prior-settlement conditions apply? |
Geography | Which states, metros, counties, or ZIP codes are included? |
Ask how each answer is established. A submitted answer, a live-confirmed answer, and an independently verified fact are different evidence levels. If the vendor uses a named case category, confirm which separate injury or commercial conditions the label actually adds.
Finally, ask how changes work. Criteria that can shift informally after launch do not create a stable replacement standard. Velocity Axis requires mutual written agreement for changes to case type, criteria, or delivery method.
Are replacement grounds and exclusions specific?
A replacement promise should name covered defects and excluded later events. It should also state the request clock, evidence requirement, decision process, and what approval changes.
Use examples. Ask how the policy treats a criterion mismatch, duplicate claimant, fabricated submission, dead number, claimant withdrawal, lower case assessment, slow settlement, and missed transfer. The answer should depend on the written format and ground rather than general discretion.
Velocity Axis publishes Replacement Grounds by format. A failed order criterion and a false, automated, or fabricated submission apply across all three formats. Duplicate and contact rules differ because the billable events differ.
The policy should also distinguish replacements from refunds. Under Velocity Axis terms, an approved request removes the original delivery from counted volume and a conforming unit replaces it at no added charge. Refund rules apply separately to undelivered committed volume or termination for an uncured material breach.
Does every claimant carry a consent record?
Ask for artifacts tied to the individual claimant, not a general campaign statement. The firm should be able to reconstruct when and where the claimant submitted, which consent language appeared, and which submission produced the delivered record.
Under Consent and the TCPA Record, every Velocity Axis claimant is captured with prior express written consent under the TCPA and carries:
ARTIFACT | RECORDED INFORMATION |
|---|---|
TrustedForm certificate | Submission timestamp, funnel page, consent language, session replay |
Jornaya LeadiD token | Identifier for the form submission |
Six-digit OTP status | Completion of the passcode check on the submitted mobile |
The TrustedForm certificate and Jornaya token are retained for five years. OTP is separate from consent capture. It establishes completion of the mobile passcode check at submission, not later reachability or accuracy of the case answers.
Ask the vendor to label the evidence level for each field. This prevents a contact check from being presented as independent verification of injury, fault, treatment, or coverage.
Does exclusivity bind the vendor in writing?
An exclusivity clause should say exactly who is restricted and what conduct is prohibited. The useful promise binds the vendor against reselling, rerouting, redistributing, steering, or sequencing the delivered claimant in favor of another firm.
Velocity Axis publishes that commitment in Exclusivity. It applies to every delivered claimant across Signed Retainer Delivery, Live Transfer, and Claimant Delivery.
The clause does not bind the claimant. The claimant remains free to choose counsel. That distinction protects claimant choice while making the vendor’s routing obligation clear.
Ask when exclusivity ends after an approved replacement. Under Signed Retainer Delivery, Velocity Axis keeps exclusivity in place until the firm confirms that its attorney-client relationship with the replaced claimant has ended. For Live Transfer and Claimant Delivery, it ends on replacement approval.
What exact event creates the charge?
The billable unit should be a named event that can be found in the delivered record. Different formats transfer different work to the vendor, so their quoted prices cannot be compared until the unit is made equal.
FORMAT | VELOCITY AXIS BILLABLE EVENT | WORK REMAINING BEFORE SIGNATURE |
|---|---|---|
Signed Retainer Delivery | Delivery of a conforming Signed Retainer | None |
Live Transfer | Transfer sent to the confirmed intake line | Firm conducts signing conversation |
Claimant Delivery | Delivery of the claimant record | Firm contacts, qualifies further, and signs |
The delivery-format comparison also states the verification level and duplicate treatment for each handoff. A Live Transfer is billable when sent during stated intake hours whether or not the firm answers. A Claimant Delivery record is billed when successfully transmitted to the confirmed destination.
Ask whether the fee depends on legal recovery. Velocity Axis prices the delivered unit in the order. Its fee is not a share of a legal fee or recovery and does not depend on case outcome.
Can the firm trace delivery and report disposition?
Every billable event should leave a record with a timestamp. The firm should see what was delivered, where it was sent, whether transmission succeeded, and when the replacement window began.
The Velocity Axis Dashboard keeps the full claimant record and delivery timestamp. The selected email, webhook, API, or CRM route carries another copy to the firm’s confirmed destination.
A reporting system should separate claimant status from replacement eligibility. A disposition records what happened after delivery. A replacement flag asserts that the record meets a listed ground. Combining them can turn a status such as withdrawal or unable to reach into an unsupported billing decision.
Ask the vendor to demonstrate reconciliation. The review should compare the confirmed destination, transmission result, dashboard copy, and delivered fields in that order. This shows whether a missing value is a routing problem, a receiving-system problem, or a genuine field mismatch.
How should the firm score the answers?
Use three results for each check: written and demonstrated, written but not demonstrated, or absent. Do not award full credit for a sample that is not incorporated into the order or policy.
RESULT | MEANING |
|---|---|
Written and demonstrated | Contract term exists and a sample record or workflow proves the mechanism |
Written but not demonstrated | Promise exists, but the operating record has not been shown |
Absent | Promise is verbal, vague, or missing |
The firm can then compare price against the amount of acquisition work transferred and the defects covered. A lower price for an earlier event may require more intake capacity and expose the firm to more conversion loss. A later billable event may carry a higher unit price while removing several pre-signature stages.
What Velocity Axis does
Velocity Axis publishes the mechanics behind all six checks: written criteria, replacement grounds, consent records, exclusivity, billable events, and dashboard reporting. The executed MSA and order control each engagement.
06
Questions
Sources
Related

Buying cases
Pay per signed case vs a pay per lead vendor: cost math
Follow the arithmetic from purchased records to signed cases, then compare it with a delivered Signed Retainer as the billable unit.
·
6 min read

Buying cases
What does an MVA claimant replacement guarantee cover?
A replacement guarantee should name the covered delivery defects, deadline, evidence rule, approval effect, and exclusions in writing.
·
7 min read

© Velocity Axis 2026
28 Geary St, Suite 650
San Francisco, CA 94108
Built for a bigger screen
The mobile experience is still in the works. Open Velocity Axis on a desktop for the full picture.





