BitBoard

What do they actually do

BitBoard builds and runs trained “AI workers” that take over repeat administrative tasks for healthcare providers. Instead of asking customers to adopt a new app, BitBoard operates inside the tools clinics and health systems already use — EHRs, inboxes, spreadsheets, and scheduling systems — through browser automation and integrations product page.

Today they handle tasks like patient-intake review and chart prep, e-fax/PDF extraction and triage, cross-system scheduling, and email/spreadsheet workflows. The engagement is high-touch: customers show BitBoard the manual process, BitBoard documents and trains an AI worker, the customer grants access and signs off, and BitBoard manages the worker in production. They claim “1,300+ hours recovered for the average customer per year” and “9 days from process review to a functioning AI worker” product page.

Who are their target customer(s)

• Small independent clinics / single-site practices: Front-office staff and clinicians are tied up with intake paperwork, chart prep, and scheduling; hiring more admins is hard or expensive. They need automation that works in their existing EHR and inboxes product page.
• Multi-site medical groups / ambulatory networks: Operations teams repeat the same admin work across locations (spreadsheets, scheduling, fax triage), causing inconsistent workflows and hidden labor costs; they want standardization inside current systems product page YC profile.
• Health system / hospital operations leaders: High volumes of referrals, faxes, and chart prep create backlogs and slow throughput; solutions must operate with enterprise EHRs rather than introducing a new platform product page YC profile.
• Revenue-cycle and scheduling teams (prior auth, billing schedulers): Time is lost extracting data from PDFs/e-faxes and coordinating appointments across systems, delaying authorizations and creating scheduling inefficiency product page.
• Practice managers and supervisors (buyers): They’re measured on staff efficiency and cost, but lack low-risk ways to offload repeat admin work; they want trained automation that plugs into current tools and shows clear hours saved product page YC profile.

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

• First 10: Run targeted, white-glove pilots via YC and founder intros plus direct outreach to local clinics and small groups; document processes, build the worker, operate it, and capture ROI metrics and short case studies to drive referrals product page YC profile.
• First 50: Use a channel-and-template motion: partner with RCM vendors/EHR consultants to resell a few pre-built worker templates (intake, fax/PDF triage, scheduling) with fixed-price onboarding; add targeted outbound to multi-site groups and provider associations using early references to compress sales cycles.
• First 100: Launch lower-touch onboarding and a catalog of validated workers for common automations; bring formal compliance materials and multi-site references to win larger groups/health systems, with a split motion (self-serve/channel for clinics; direct enterprise for larger providers).

What is the rough total addressable market

Top-down context:

Administrative costs in U.S. healthcare are in the hundreds of billions annually. McKinsey estimated hospital administrative costs at about $250B and administrative costs in clinical services at about $205B, framing a large ceiling for tools that reduce admin work Commonwealth Fund.

Bottom-up calculation:

Hospitals: There are about 6,093 U.S. hospitals. If an average hospital buys ~$100k/year of AI-worker automation across several workflows, that implies ~$0.61B (6,093 × $100k) AHA. Physician offices: Employment in offices of physicians is ~3.02M. Assuming ~30% are administrative roles, one AI worker per 20 admin staff, and ~$30k ACV per worker yields ~45k workers and ~$1.36B (3,022,500 × 30% ÷ 20 × $30k) BLS/FRED. Combined preliminary U.S. TAM ≈ ~$2.0B for BitBoard’s current scope of repeat admin automations.

Assumptions:

• Average hospital ACV of ~$100k/year across multiple automations.
• In physician offices, ~30% of staff are administrative; one AI worker per ~20 admin staff; ~$30k ACV per worker.
• Scope limited to U.S. hospitals and physician offices; excludes payers, post-acute, and international.

Who are some of their notable competitors

• Notable: Builds EHR-embedded AI automations for intake, chart prep, and back-office workflows; overlaps with BitBoard on EHR-first agents and reusable flows rather than bespoke-only builds Notable.
• UiPath: General enterprise RPA platform widely used in health systems to script EHR/browser actions and process documents; customers or SIs can build similar automations, but it’s more DIY tooling than a managed service UiPath.
• Phreesia: Specialist in patient intake, registration, and eligibility checks with bidirectional EHR/PM integrations; competes directly on intake and pre-visit workflows Phreesia.
• Waystar: End-to-end revenue-cycle platform automating eligibility, claims, denials, and patient payments; overlaps where BitBoard targets RCM workflows but is a broader RCM suite Waystar.
• Olive: Known for automating high-volume provider tasks like prior authorization and document workflows; positioned as an enterprise automation vendor in provider settings Olive.