What InQuery users actually want

Nine sources document low-friction acquisition tactics (free trials, transparent pricing, demo scheduling), but the current buyer journey still requires scheduling a demo before hands-on experience. One source explicitly states that 'document upload and indexing is positioned as instant,' signaling that speed is a core value proposition in onboarding. However, the friction of demo scheduling delays time-to-value and introduces drop-off risk, especially for mid-market buyers who prefer self-education.

Fourteen sources detail InQuery's credit-based pricing model, where costs scale with volume and complexity (1 credit/page for indexing, 1 credit/page for summaries, 2 credits/page for case info extraction). Typical 1,000-page cases range from 1,000 to 7,000 credits depending on analysis depth. The Growth plan is marked as 'Most Popular,' indicating strong adoption, but no sources describe how users track credit consumption or forecast overages as case volume grows. This visibility gap creates friction in budget planning and delays Enterprise tier adoption.

Eight sources validate that carriers represent a key segment with urgent pain points around measurability and auditability of workflows. Content targeting carriers explicitly states that 'manual medical record review workflows lack measurability and auditability, creating compliance and transparency challenges.' InQuery is positioning medical chronology as a core output for carrier workflows, but without auditable process logs, carriers cannot demonstrate regulatory compliance or defend decisions during litigation.

Eleven sources confirm that InQuery delivers configurable case-level and document-level summaries customized by case type, targeting multiple use cases including case reviews, peer reviews, MSAs, and life care plans. Users report that the system 'absolutely makes a difference, especially in those cases without any clear direction and with voluminous files.' Claims metrics advertise up to 50% fewer revision cycles. However, no sources describe whether users can predefine which fields, sections, or data points summaries should include before generation. This gap forces users to edit generated summaries post-hoc, reintroducing manual work that automation should eliminate.

Fourteen sources document InQuery's expansion into the IME referral marketplace, connecting physicians and insurance carriers with zero-friction onboarding (no membership fees, no upfront commitments). The platform promises physicians 'a steady stream of IME referrals' and emphasizes that the process is 'faster, simpler, and more efficient than ever.' However, no sources describe whether physicians have visibility into their referral pipeline, earnings over time, or performance metrics that influence future referral volume. Without this transparency, physicians cannot assess whether the marketplace delivers meaningful volume or plan their availability strategically.

Eleven sources confirm that InQuery enables users to process 3x more cases with the same team, targeting high-volume operations including carriers, law firms, and MSP consultants. The Enterprise tier offers contractual flexibility and SLA alignment, indicating InQuery targets high-volume legal and medical operations. However, no sources describe whether users can upload multiple cases simultaneously or track processing progress across a queue of cases. This gap creates operational friction for high-volume users who receive dozens of cases daily and need batch processing rather than serial uploads.

Thirty-two sources document InQuery's enterprise-grade security posture, including SOC 2 Type I, HIPAA certifications, 123+ documented security controls, and comprehensive compliance across GDPR, CCPA, and state privacy laws. The Data Processing Addendum explicitly states that InQuery 'commits to SOC 2 Type II and/or alternative compliance certifications, with audit rights available to customers.' However, no sources provide a timeline for when SOC 2 Type II will be achieved or what milestones remain. This creates uncertainty during enterprise procurement, where buyers require Type II certification before signing contracts.