Careforce (prev. Helpcare AI) logo

Careforce (prev. Helpcare AI)

AI Workers for Healthcare Orgs to Find, Call & Schedule More Patients.

Fall 2024active2024Website
Artificial IntelligenceHealth TechHealthcareHealthcare ITCall Center
Sponsored
Documenso logo

Documenso

Open source e-signing

The open source DocuSign alternative. Beautiful, modern, and built for developers.

Learn more →
?

Your Company Here

Sponsor slot available

Want to be listed as a sponsor? Reach thousands of founders and developers.

Report from 2 months ago

What do they actually do

Careforce provides autonomous software agents that handle patient outreach and scheduling work for healthcare organizations. One agent (David) ingests data from EHRs and portals via API or UI, deduplicates and matches identities, and builds outreach lists such as care gaps, due screenings, or no-shows. Another agent (Angelica) contacts patients by phone, SMS, and email using editable scripts, confirms intent, books appointments directly into scheduling/EHR systems, and logs outcomes for staff review Angelica · David.

The system is built to operate across messy, partially integrated tech stacks. It supports both API-based and UI-based data pulls, uses Twilio for voice and messaging infrastructure, and logs all interactions back to the customer’s systems Integrations · VentureBeat/Twilio coverage. Careforce reports it is live with health centers and digital-health companies and targets payors, FQHCs/CHCs, primary care, and specialty practices homepage · YC profile.

In practice, customers provide access to data sources or portals, David prepares prioritized outreach lists, and Angelica executes multi-channel outreach and books visits, with everything recorded for re-runs and audit. The product focuses on administrative coordination rather than clinical decision-making Angelica · David.

Who are their target customer(s)

  • FQHCs and community clinics: Small admin teams struggle to reach and book patients for preventive care and follow-ups, leading to missed visits and reporting gaps that affect quality metrics and funding.
  • Primary care practices: Front-desk and care-coordination staff spend significant time calling and texting patients for scheduling and rebooking, causing burnout and inconsistent follow-up.
  • Specialty practices (cardiology, imaging, behavioral health, etc.): Revenue and timely care are lost when patients miss pre-op steps, referrals, or imaging appointments, forcing staff into constant manual outreach and confirmation work.
  • Payors and managed care organizations: They need to identify members with care gaps and hit HEDIS/STAR/UDS targets but lack a scalable, low-cost way to find, contact, and schedule those members across fragmented systems David.
  • Digital-health companies and virtual care providers: Scaling outreach and scheduling across many EHRs and portals is slowed by fragmented integrations and manual list preparation, creating operational bottlenecks Integrations.

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

  • First 10: Run hands-on pilots with closely matched clinics and payors sourced through YC and Twilio networks; staff the pilots to prove appointment and care-gap outcomes while ironing out integrations, then convert to paid with 1–2 clear KPIs and a case study per pilot Angelica · David · Twilio coverage.
  • First 50: Package the pilot playbook into vertical templates (FQHCs, primary care, imaging/behavioral health, payors) with standard scripts, onboarding checklists, and success metrics; use referrals from the first 10 and targeted outreach, with a small sales/implementation team running 4–8 week proofs of value Angelica · David.
  • First 100: Add channel partnerships (EHR marketplaces, Twilio, value-based care vendors) and productize UI/API connectors plus a lighter self-serve onboarding tier to lower deployment cost; use clear pricing tiers and partner revenue shares to land both payors and many smaller clinics Integrations · Twilio announcement.

What is the rough total addressable market

Top-down context:

Covers budgets for patient outreach, scheduling, and care-gap closure across US FQHCs/CHCs, ambulatory primary and specialty practices, digital-health platforms, and payors. Purchases are typically justified by filling schedules and improving quality metrics such as HEDIS/STAR/UDS David.

Bottom-up calculation:

Illustrative US-focused estimate: FQHC/CHC organizations (~1,400) at ~$50k average annual contract value ≈ $70M; mid-sized primary care and specialty practices (~35,000) at ~$12k ACV ≈ $420M; payors and digital-health platforms (~200 buyers) at ~$250k ACV ≈ $50M. Combined initial TAM ≈ $540M.

Assumptions:

  • US market only; counts reflect reachable buyers in target segments, not all providers.
  • Average contract values reflect outreach+scheduling automation budgets, excluding broader IT spend.
  • Buyer counts approximate FQHC organizations, a subset of ambulatory practices most likely to buy, and a limited set of payors/platforms.

Who are some of their notable competitors

  • Luma Health: Patient engagement and self-scheduling platform integrated with major EHRs; overlaps on automated outreach and schedule fill but is positioned as a front-office platform rather than autonomous calling plus portal UI automation.
  • Klara: Two-way patient messaging and workflow automation (reminders, digital intake, call-to-text); competes on reducing phone calls via text and web, while Careforce leans into autonomous calling and booking.
  • Phreesia: Patient intake and engagement (online scheduling, pre-visit registration, reminders, between-visit outreach); overlaps on recalls and pre-visit workflows, whereas Careforce emphasizes higher-touch outreach and list creation from messy sources.
  • NexHealth: EHR-integrated scheduling and messaging with automated recalls; competes on fast integrations and access tools, while Careforce pairs outreach with agents that can perform UI/API pulls and place calls.
  • Conversa Health: Automated conversational pathways for chronic care and peri/post-op monitoring; overlaps on automated patient conversations, but Conversa centers on chat-based care pathways rather than outbound phone/SMS plus booking and portal automation.