Sample

What do they actually do

Sample provides a hosted platform that reads clinical documents (medical records, correspondence, payer paperwork) and turns them into structured data and step-by-step workflows with LLM-powered “copilots.” It sits alongside a provider’s existing EHR/RCM systems, extracting and classifying information, surfacing concise patient summaries for staff, and routing tasks through an auditable workflow (samplehc.com, YC).

Teams use it for patient intake, medical record abstraction, and prior authorization/appeals preparation: the copilot pulls facts from long records, gathers supporting documents, prepares reviewer-facing packets, and pushes structured outputs back into customer systems via connectors to EMRs, data platforms, and communication endpoints. The company emphasizes quick deployment, HIPAA compliance, SOC 2 Type II, and end-to-end audit trails (samplehc.com).

Who are their target customer(s)

• Clinical operations leaders at hospitals and large provider groups: Intake and chart review require staff to search through PDFs and re-enter data across systems, slowing onboarding and patient throughput. They need tools that extract and surface key clinical facts to speed routine work (samplehc.com).
• Prior authorization and appeals teams: Compiling supporting records and preparing authorization packets is manual and slow, delaying care and reimbursement. They want help gathering documents and producing packets while keeping expert review in the loop (samplehc.com).
• Revenue cycle managers / denial-management leads: Missing or poorly organized documentation drives denials, longer AR days, and costly rework. They need structured outputs and connectors that feed required information back into RCM systems to reduce failures (samplehc.com).
• Medical abstractors and specialty clinic staff (e.g., oncology registrars): Extracting structured data and summaries from long, fragmented records is time-consuming, slowing reporting, research, and quality tracking. They want copilots that accelerate reliable abstraction and summaries (samplehc.com, YC).
• IT and compliance leads at provider organizations: New tools must integrate cleanly with EHRs/data platforms and meet HIPAA/SOC 2 and audit requirements. They seek turnkey deployments, robust connectors, audit trails, and a clear compliance posture (samplehc.com).

How would they acquire their first 10, 50, and 100 customers

• First 10: Leverage founders’ provider and oncology network (and YC introductions) for tightly scoped, hands-on pilots with an embedded engineer, connecting to document sources and delivering extract+workflow outputs while benchmarking time/accuracy; use HIPAA/SOC 2 materials and existing connectors to pass IT/compliance review (samplehc.com, YC).
• First 50: Turn early pilots into referenceable case studies and a repeatable deploy kit (playbooks, connectors, security pack, standard success metrics) to sell similar clinical-ops, prior-auth, and RCM teams with less bespoke work; run joint pilots with EHR/data-platform partners and fund implementation via a standard onboarding fee (samplehc.com).
• First 100: Expand beyond direct sales via EHR/data-platform marketplaces, referral/reseller deals with RCM vendors and regional GPOs, and a certified implementation partner program; productize model customization/monitoring so more customers can progress from assisted copilots to reliable automation with minimal per-account engineering (samplehc.com).

What is the rough total addressable market

Top-down context:

Document-heavy clinical operations and revenue-cycle workflows at U.S. providers are large spend pools: there are about 6,093 U.S. hospitals and hundreds of integrated health systems, and the U.S. revenue cycle management market alone is estimated at >$170B in 2024 (AHA, Grand View Research). Persistent prior-authorization burden documented by AMA/CAQH underscores demand to reduce manual work (AJMC, CAQH Index).

Bottom-up calculation:

Focus on roughly 600 U.S. health systems and several hundred large provider groups with substantial document workflows; if 1,000 organizations adopt at an average $200k ARR for 1–2 copilots and integrations, the initial serviceable TAM is about $200M. This can expand with additional workflows and sites per organization (AHRQ Compendium via Mathematica, IQVIA Top 50 Groups).

Assumptions:

• U.S.-only focus on integrated health systems and large multi-specialty/specialty groups in the near term.
• Average contract value ~$200k per org covering platform, connectors, and 1–2 high-volume workflows.
• Pricing and penetration expand with more workflows, sites, and automations per customer.

Who are some of their notable competitors

• Notable: Automates patient intake, EHR data entry, and upstream workflows (including prior-auth prep); overlaps with Sample on document intake, summarization, and routing into clinical workflows (Notable).
• Olive: Enterprise automation platform that targeted revenue-cycle and utilization tasks such as prior authorization; overlapping focus on prior-auth and RCM automation for large systems (Medigy overview).
• Waystar: End-to-end revenue-cycle platform including financial clearance and prior-authorization automation; competes where hospitals want RCM products that connect to EHRs and reduce manual auth/denial work (Waystar).
• Apixio: Extracts structured clinical data from unstructured records for risk, payment integrity, and prior-auth decisioning; overlaps on chart abstraction and automated authorization support, with stronger payer/MA emphasis (Apixio).
• nference: Provides large-scale clinical data extraction, annotation, and model tooling for health systems and life sciences; competes on high-volume record abstraction and building proprietary clinical datasets (nference).