What is it
Per-report pricing is a billing unit where each AI-generated report or analysis document is metered as a discrete output.
The report is a naturally countable, auditable unit in professional services. EvenUp generates demand packages — legal reports that synthesize a personal injury case into a settlement demand letter for insurance negotiations. Rad AI generates radiology report impressions — AI-drafted diagnostic summaries that radiologists review and sign inside their reporting workflow. Both sit in industries where customers think in reports produced: how many demand packages went out this month, how many radiology reads were completed today.
Unlike token-based pricing, which charges for compute regardless of what the output is worth, per-report pricing ties value to a completed, usable professional deliverable — a framing that resonates in regulated fields where an incomplete AI output has no professional value. The report is also a clean compliance anchor: legal and medical reports are already numbered, tracked, and archived, so counting reports maps directly onto records systems professionals already maintain. Choosing the report as the value metric is a deliberate call about how the buyer measures work — see choosing the right usage metric.
How it works
The conceptual unit is a completed report delivered to a professional reviewer — a demand package reaching the plaintiff’s attorney, or an impression populated into the radiologist’s reporting field. In both companies the report is what the customer counts, but the commercial terms are quoted, not published as a public per-report fee.
| Company | Report unit | Pricing posture | Real figures on record |
|---|---|---|---|
| EvenUp | Personal injury demand package | Sales-led; historically per-demand/per-document, now one quoted cost per case (Dec 2025) | Third-party sources reported ~$300 base per demand, totals often $500–$800+ with add-ons — never published by EvenUp |
| Rad AI | Radiology report impression | Sales-led; quoted annual enterprise contract per practice/health system | No posted per-report fee; Continuity framed on ROI at $50–$250 net reimbursement per follow-up study |
The report-count value metric, in its simplest form:
Reference cost = reports_generated × per_report_value
EvenUp targets plaintiff law firms and processes roughly 10,000 cases per week. Its early per-demand model was reported by third parties at a ~$300 base that could reach $500–$800+ once token-based add-ons were included; in December 2025 EvenUp deliberately collapsed those add-ons into “one predictable cost per case” to remove per-artifact unpredictability. So even where the report was the meter, EvenUp moved coarser — to the case — rather than finer.
Rad AI integrates into radiology workflow software: when a radiologist opens a study, its Impressions product has already drafted the impression in 0.5–3 seconds. Rad AI quotes annual enterprise contracts scoped by product mix (Reporting, Impressions, Continuity), radiologist count, and report volume — there is no posted per-impression price. For Continuity it publishes an ROI calculator rather than a fee, projecting additional imaging revenue at $50–$250 net reimbursement per follow-up study. Both illustrate that per-report is the customer’s mental unit even when the invoice is a negotiated contract — the value-metric logic behind that choice is covered in introduction to usage-based pricing.
Companies using this
Two companies in the corpus treat the AI-generated report as their billing unit: EvenUp, whose demand package synthesizes a personal injury case into a legal report, and Rad AI, whose impressions draft radiology reads inside the clinical workflow. Both are sales-led with no public rate card, targeting high-throughput professional environments — law firms and radiology departments — where report volume tracks directly to departmental productivity.
Explore this theme in the knowledge graph
FAQ
What is per-report pricing in AI document generation platforms?
Per-report pricing treats each structured analytical report the AI produces — a legal demand letter, a radiology read — as the value metric the customer is buying, rather than tokens or compute. EvenUp historically billed per demand package (a legal report synthesizing a personal injury case) before shifting to one cost per case in December 2025; Rad AI drafts radiology report impressions inside the radiologist's workflow. In both cases the report is the finished professional deliverable, and the fee bundles all data retrieval, analysis, and generation into one charge.
Do EvenUp and Rad AI publish a per-report price?
No. Both are fully sales-led with no public rate card — each company's /pricing page 404s and every path routes to a demo request. Third-party sources reported EvenUp's historical per-demand model at roughly a $300 base, with totals often reaching $500–$800+ once token-based add-ons were included, but EvenUp never published those figures; it now quotes one cost per case. Rad AI quotes annual enterprise contracts scoped per practice or health system, and frames its Continuity product on downstream-imaging ROI ($50–$250 net reimbursement per follow-up study) rather than a posted per-report fee.
How does per-report pricing differ from per-page or per-document pricing?
A report is a higher-order artifact than a page or a generic document: it synthesizes multiple inputs into one analytical output. EvenUp's demand letter synthesizes medical records, bills, and case facts into a legal document; Rad AI's impression synthesizes imaging findings into a diagnostic summary. Per-page pricing would meter output length and per-document pricing would meter any file regardless of synthesis complexity — per-report pricing specifically charges for the AI's analytical work, which is why it tends to appear in regulated professional services rather than in raw-generation tools.
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-Case PricingA billing unit used in legal AI platforms where each case or matter processed by the AI is metered.