What is it
Per-case pricing is a billing unit used in legal AI platforms where each case or matter processed by the AI is metered.
The case is the professional’s unit of work. A plaintiff’s law firm runs personal injury cases; a pathology lab processes imaging studies. EvenUp, which automates personal injury demand letters, moved to explicit case-based pricing in December 2025 — one predictable cost per case for its full Claims Intelligence Platform, replacing its earlier per-demand / per-document billing. Paige AI, which builds FDA-cleared cancer-pathology AI, currently licenses per slide (from ~£1/slide per the UK’s NICE) and, per NICE, is developing a per-case model — showing the same directional pull toward the case as the customer’s budgeting unit.
The appeal is that the case absorbs all the underlying compute — document parsing, evidence extraction, legal or clinical reasoning, and final output generation — into a single predictable fee. The customer never counts the tokens in a 50-page medical record or the inference calls behind a histology read. They know how many cases they process, and that maps directly to their own value metric. It is a natural fit for regulated domains, where each legal matter or clinical case already carries a per-case compliance record that the billing line item can reconcile against.
How it works
Per-case billing triggers when the platform completes a case’s primary output — the demand letter, or (in Paige’s developing model) the finished pathology case. The billing event is output delivery, not the internal processing steps.
| Company | Case type | Documented pricing basis | Notes |
|---|---|---|---|
| EvenUp | Personal injury demand / full case prep | ”Case-based pricing” — one quoted cost per case (since Dec 2025) | Sales-led, no public rate card; historically per-demand (third-party sources reported ~$300 base, $500–$800+ with add-ons) |
| Paige AI | Digital pathology study (cancer detection) | Per-slide subscription from ~£1/slide (NICE) + one-time ~£15,000 LIS integration | Per-case model reported by NICE as in development; pharma work is custom-contracted |
The unit math for a true per-case model is direct:
Monthly cost = cases_processed × per_case_fee
For EvenUp, that means a firm’s monthly spend scales with the cases it submits: 40 cases at a quoted per-case rate is 40 × that rate, with the platform’s full drafting and MedChron capability bundled into each. The ROI test is whether the per-case fee plus attorney review time undercuts the associate hours to build the demand package manually.
For Paige AI, today’s documented math is per slide: a lab multiplies its per-slide rate by biopsy and slide volume, adds the one-time integration fee, and compares the total against radiologist-labor cost and reimbursement per study. A per-case fee — which NICE reports Paige is developing — would roll the slides-per-case into one number, closer to how healthcare finance already reasons about a study. For how these work-unit metrics compare with token- and seat-based alternatives, see the guide on usage-based pricing models.
Companies using this
Two companies in the corpus meter around the case: EvenUp in legal and Paige AI in clinical pathology. Both are sales-led professional-services platforms — law firms and healthcare labs — where the case is the natural unit of production and a clearly bounded deliverable aligns AI cost with professional billing rates.
Explore this theme in the knowledge graph
FAQ
What is per-case pricing in legal and medical AI platforms?
Per-case pricing meters each legal matter or clinical case processed by the AI platform as a single billable event. As of December 2025 EvenUp uses 'case-based pricing' — one predictable cost per personal injury case for full access to its Claims Intelligence Platform. Paige AI licenses its clinical pathology AI on a per-slide basis (from about £1 per slide per NICE) and, per NICE, is developing a per-case model. The case aligns cost with the customer's natural unit of production — a law firm tracks cases, a lab tracks studies — rather than tokens or API calls.
How much does EvenUp charge per case?
EvenUp does not publish a rate card — its pricing page is not public and firms receive a custom quote after a demo. In December 2025 EvenUp moved to 'case-based pricing,' described as one predictable cost per case for the full platform, explicitly to remove confusing feature tiers and unpredictable add-ons. Historically, third-party review sources reported a base of roughly $300 per demand letter, with totals often reaching $500–$800+ once add-ons were included — those are reported figures, not official EvenUp rates.
Does Paige AI charge per case or per slide?
Paige AI's clinical model is primarily per-slide today: the UK's NICE Medtech briefing reports Paige Prostate pricing typically starts at about £1 per slide, rising with volume, plus a one-time laboratory-information-system integration fee that typically starts around £15,000. NICE also notes Paige is developing a per-case pricing model, but per-slide is the documented commercial structure. Pharma and life-sciences engagements are custom-contracted, not priced per case.
Why do legal and medical AI platforms prefer per-case pricing over token or compute metrics?
Legal and medical professionals measure their work in cases, not tokens. A plaintiff's attorney asks 'what does this personal injury case cost?' — not 'how many tokens does the model consume?' EvenUp's case-based pricing maps directly to that mental model, making procurement predictable. In pathology, a per-slide or per-case fee is comparable to the reimbursement rate a lab earns per study, making the ROI calculation immediate. Token or compute pricing would require a translation layer that adds uncertainty.
Related billing units
- Credit-Based BillingA billing unit where customers pre-purchase or are allocated a pool of credits that deplete as they use the product, often at variable rates per feature.
- Token-Based PricingA billing unit common in LLM and AI products, where customers are charged per input and output token processed.
- Per-Seat PricingA billing unit where the vendor charges a fixed fee per named user, regardless of how much each user consumes.
- Per-Resolution PricingA billing unit unique to AI customer-support products, where the vendor charges only when an AI agent resolves a customer issue without escalation.
- Bandwidth-Based PricingA billing unit where customers are charged per gigabyte of data transferred out of the platform.
- Per-Function-Invocation PricingA billing unit where customers are charged per serverless function invocation, often combined with a separate compute-time charge.
- CPU-Hour PricingA billing unit where customers are charged for the CPU time their workloads consume, typically measured in vCPU-seconds or vCPU-hours.
- GB-Hour PricingA billing unit where customers are charged for the memory their workloads consume over time, measured in gigabyte-hours.
- GPU-Hour PricingA billing unit where customers are charged for GPU time consumed, typically measured per-second or per-hour by GPU type.
- Per-API-Call PricingA billing unit where customers are charged per API request, regardless of payload size or processing time.
- Per-GB Storage PricingA billing unit where customers are charged per gigabyte of data stored on the platform per month.
- Media-Minute PricingA billing unit where customers are charged per minute of audio or video processed — used by speech, voice, and video AI vendors.
- Per-Request PricingA billing unit where customers are charged per request served — the generic meter for inference endpoints, search, scraping, and browser infrastructure.
- Per-Event PricingA billing unit where customers are charged per event ingested — the native meter of observability and billing-infrastructure platforms.
- Vector Storage PricingA billing unit where customers are charged for vectors stored or indexed — the storage dimension of vector database pricing.
- Per-Character PricingA billing unit where customers are charged per character of text processed — the standard meter for text-to-speech and translation.
- Per-Document PricingA billing unit where customers are charged per document processed or generated — common in AI writing, SEO, and document-intelligence tools.
- Per-Page PricingA billing unit where customers are charged per page crawled, parsed, or rendered — the meter for web scraping and document parsing.
- Per-Transaction PricingA billing unit where customers are charged per financial or billing transaction processed — the meter of billing and accounting platforms.
- Active-User PricingA billing unit where customers are charged per monthly or daily active user rather than per provisioned seat.
- Per-Task PricingA billing unit where customers are charged per task an automation or agent executes — Zapier's historical unit, now spreading to AI agents.
- Per-Unit PricingA billing unit used by robotics, hardware AI, and some SaaS companies where the metered object is a physical or abstract 'unit' — a robot deployed, a device sold, or a defined deliverable.
- Workflow Execution PricingA billing unit where each end-to-end workflow or automation run is metered and billed, regardless of the compute steps it contains.
- Per-Message PricingA billing unit where each individual message or reply in a conversation is metered, common in AI chat and voice platforms.
- Per-Invoice PricingA billing unit used by billing infrastructure platforms where each invoice generated or processed is metered as the primary cost driver.
- Per-Action PricingA billing unit where each discrete action taken by an AI agent or automation is metered — common in browser automation and agentic workflow tools.
- Per-Image PricingA billing unit where each AI-generated image is metered, common in image generation APIs and multimodal AI platforms.
- Per-Conversation PricingA billing unit where each complete customer conversation — from first message to resolution — is metered as a single chargeable event.
- Per-Record PricingA billing unit where each data record processed, labeled, or extracted is metered — common in data platforms and web scraping services.
- Per-Word PricingA billing unit common in translation and localization platforms where the metered object is the word count of content processed.
- Per-Video PricingA billing unit where each AI-generated video is metered, common in video generation and synthetic media platforms.
- Milestone-Based PricingA billing unit used in drug discovery and biotech AI where payment is tied to achieving defined research milestones rather than time or compute consumed.
- Per-Outcome PricingA billing unit where payment is triggered by verified outcomes delivered — distinct from outcome-based pricing models, this refers specifically to 'outcomes' as a countable billing unit.
- Per-Datapoint PricingA billing unit where each individual data measurement or signal ingested is metered — common in cloud cost intelligence and ML evaluation platforms.
- Per-Interaction PricingA billing unit where each patient-agent or user-agent interaction is metered, common in healthcare AI and customer engagement platforms.
- Data Licensing PricingA pricing structure where access to proprietary datasets or data assets is licensed separately from the software or services, common in AI training data and clinical data platforms.
- Robot-Hour PricingA billing unit where each hour a robot or autonomous system operates is metered — the robotics equivalent of a GPU-hour.
- Per-Contact PricingA billing unit where each contact or lead in the database is metered, common in AI sales development and outbound automation platforms.
- Per-Mailbox PricingA billing unit where each connected email mailbox or sending account is metered, common in AI outbound sales and email automation platforms.
- Browser-Hour PricingA billing unit where each hour of headless browser compute time is metered, common in web scraping and browser automation platforms.
- Per-Generation PricingA billing unit where each AI-generated creative asset — image, video, or design — is counted as a 'generation' and metered accordingly.
- Per-Ticket PricingA billing unit where each customer support ticket handled by an AI agent is metered — common in AI customer service platforms.
- Per-Log PricingA billing unit where each LLM request log ingested or stored is metered — common in AI observability and evaluation platforms.
- Per-Trace PricingA billing unit where each distributed trace — a complete record of an LLM request chain — is metered, common in AI observability platforms.
- Per-IP PricingA billing unit where each IP address or proxy endpoint allocated is metered — used by web scraping proxy providers.
- Per-Device PricingA billing unit where each hardware device or endpoint connected to the AI platform is metered.
- Per-Report PricingA billing unit where each AI-generated report or analysis document is metered as a discrete output.