Ops OS for payer-backed eldercare coordinators to verify coverage, source local services, and close family care tasks across states.

1. A $27 million Series A led by multi-stage investors means eldercare coordination now has the capital base to scale nationally, creating a picks-and-shovels opening for infrastructure software.
2. Supporting more than 1,000 families in the first year shows the category has already reached real operational volume, not just concierge-style pilot demand.
3. A 95% retention rate turns each signed family into a recurring workflow, which makes service quality, case visibility, and coordinator productivity economically urgent.
4. A target of 25-plus states by year-end makes state-by-state provider sourcing and coverage logic a scaling bottleneck now rather than a later enterprise concern.

Catalyst. Hera's combination of 1,000-plus families, 95% retention, and a target of 25-plus states by year-end shows eldercare coordination is moving from boutique service into a multi-state payer fulfillment category that lacks purpose-built software.

The product gives eldercare coordination teams a single workspace for intake, coverage verification, provider matching, task assignment, and payer reporting. A family intake flow captures the household situation, then a rules layer routes the case by need type, urgency, plan coverage, and state. Care guides work from a queue that recommends local home care, transportation, senior living, and caregiver-support options while tracking every referral and family task in one timeline. Managers see which providers convert, which states are understaffed, and which cases stall before service starts. The result is a repeatable care-ops engine that lets one guide serve more families without hiding work inside phone calls and spreadsheets.

What's different. Generic care-management CRMs capture notes after work happens, while consumer caregiver apps help one family stay organized. This wedge sits in the fulfillment layer between payer, care guide, family, and local provider network, so it accumulates hard-to-copy data on coverage rules, provider conversion, time-to-service, and case outcomes by state. That operating graph becomes more valuable as more families and payer partners run through it, making the platform a distribution and quality-control layer rather than another front-end app.

Jobs to be done

flowchart LR
  Buyer[Care Ops Leader] --> Pain[Manual coverage and service coordination]
  Pain --> Product[Eldercare Benefit Fulfillment OS]
  Product --> Outcome[More families served with payer-grade auditability]

Executive takeaways

• Demand is real: Hera’s financing, thousand-family scale, high reported retention, and 25-state ambition show payer-backed eldercare coordination is becoming an operating category rather than a boutique concierge service [1][2].
• The hard problem is not another caregiver-facing app; it is closing benefit, provider, and family tasks across fragmented Medicare Advantage, Medicaid, and local-service systems [7][9][17][19].
• Adjacent vendors prove budget exists, but most compete as full-service navigation programs or employer/member benefits—not as neutral fulfillment software for multi-state coordination operators [21][23][24][25][27].
• Execution risk concentrates in local supply and data freshness: HCBS workforce shortages, narrow networks, and state policy variation can swamp software gains unless the product learns from closed-loop provider outcomes [13][15][9][4].

Market definition

The beachhead is software for payer-backed eldercare benefit fulfillment: the non-clinical work between eligibility, care-guide action, family follow-through, and service start across home care, transportation, senior living, caregiver support, and benefits navigation [2][7][10].

Customer and buyer

Primary users are VP/COO-level care-operations teams at payer-backed navigation vendors and health-plan delegated-services groups that must absorb MA/HCBS complexity, prior authorization, and provider-network variation while improving member experience and throughput [7][8][9][17].

Buying triggers

• A new insurer contract, new plan year, or state launch forces teams to stand up local provider coverage and benefit rules without proportional headcount. [1][2]
• Growth in MA and especially SNP enrollment increases the number of high-need members whose journeys cross payer, family, and community-service workflows. [6][7]
• Prior-authorization, network, and directory friction create visible service delays that generic CRMs do not solve well. [8][9][30]

Willingness to pay

Budget exists because MA plans already use federal rebate dollars to fund supplemental benefits, while scaled navigation vendors market measurable ROI, reporting, and member-experience gains; pricing is almost universally enterprise-custom rather than self-serve. [7][22][25][26]

Category dynamics

Growth signal 3% YoY total Medicare Advantage enrollment growth in 2026; C-SNP enrollment +45% YoY

Validation signals

• Hera reports 1,000-plus families served, 95% retention, and a plan to reach 25-plus states.
• Medicare Advantage now covers 35 million beneficiaries, or 55% of the eligible Medicare population.
• AARP says the U.S. now has 63 million family caregivers and that over 40% provide high-intensity care.
• Scaled adjacent vendors already sell caregiver navigation or support directly to health plans.

Regulatory & technical constraints

• Coverage and preauthorization logic will depend on payer data access, API readiness, and compliance timelines that vary through 2026 and 2027.
• HCBS, self-direction, and caregiver support rules vary by state, making national playbooks difficult to standardize.
• Provider-network and directory quality limitations make local service matching materially noisier than core clinical-network claims data.
• Any buyer subject to utilization-management accreditation or plan-quality reviews will expect auditable system controls and denial/notification discipline.

The visible market splits into full-service caregiver support/navigation vendors (Wellthy, Papa, Homethrive, DUOS, Cariloop) and generic payer-admin stacks. The proposed startup is differentiated only if it sells neutral, multi-state fulfillment workflow to operators who do not want to become a services-heavy navigation vendor themselves [21][23][24][25][27].

Why incumbents do not win by default

• Cloud platforms. Generic CRM and workflow stacks can store notes and tickets, but they do not come with payer-specific eligibility logic, eldercare provider knowledge, or outcome loops for local fulfillment.
• Health plan care-management suites. Plan-side care-management tools are strong on reporting and utilization management, but they still depend on external provider directories, prior-auth processes, and fragmented community-service supply.
• Full-service navigation vendors. Scaled competitors prove demand, but most package their own care teams, networks, or in-home labor with software, which can make them partners, competitors, or expensive substitutes for neutral operator tooling.
• Internal build plus BPO. Large operators can piece together spreadsheets, call-center notes, and offshore support, but the missing asset is closed-loop learning on which local providers, benefit routes, and family nudges actually convert to service starts.

Eldercare Benefit Fulfillment OS should start as a workflow sidecar for payer-backed senior-care coordination vendors that are expanding into new states faster than their care-operations teams can standardize coverage checks, provider sourcing, and family follow-through. The first buyer is the COO or VP Care Operations at a multi-state operator with roughly 1,500-3,000 active families, 40-80 care guides, and at least one new payer line or state launch in the next 12 months. The immediate pain is not generic case management; it is getting families from intake to first booked service with payer-grade documentation while local provider supply, benefit rules, and prior-authorization friction vary by state. The best entry product is therefore a paid state-launch pilot that layers on top of the customer’s existing CRM, verifies coverage, routes tasks, captures referral outcomes, and emits a payer-ready case summary. Research supports real demand and budget, but it also shows the initial market is narrow at an estimated $50M beachhead SAM and that direct willingness to buy neutral workflow software is still unproven. The company wins only if it stays neutral relative to services-heavy navigation vendors and compounds proprietary provider- conversion, time-to-service, and benefit-rule data from real episodes. The biggest disconfirming risks are that customers may keep extending spreadsheets and generic CRMs, or that data-retention limits prevent the benchmark moat from forming. A second open question is whether plans will buy this workflow directly or continue to route spend through delegated-service vendors, so the first 18 months should prioritize proof with operators before broader expansion.

Problem

• Multi-state eldercare coordination teams still run coverage verification, provider sourcing, family follow-through, and payer documentation across generic CRMs, spreadsheets, call notes, and Slack, so cases stall between handoffs.
• New insurer contracts and state launches force operators to stand up local provider coverage and benefit rules quickly, yet guide headcount and QA burden rise almost linearly when workflows stay manual.
• Payers care about service-start speed, auditability, and member experience, but current tools do not show which providers convert, which family tasks block progress, or where state-specific supply constraints are destroying margin.

Solution

• Start with a state-launch sidecar that ingests intake context, verifies coverage where payer data exists, assigns care-guide and family tasks, and keeps every referral and document request on one episode timeline.
• Add closed-loop provider outcome capture so managers can see which local providers convert fastest, which states need more supply curation, and which cases are stuck before service start.
• Turn each episode into a payer-ready case summary and operating dashboard so buyers can prove SLA performance and expand families served per guide without replacing every upstream system on day one.

Why we win

• The wedge targets the operator fulfillment layer that generic care-management CRMs and member-facing caregiver apps do not own well.
• Every fulfilled episode can improve a reusable graph of benefit rules, provider conversion, and family-task completion that gets harder for internal teams or services vendors to replicate.
• The first sale attaches to a dated state launch or new payer rollout, which makes ROI measurable faster than a broad platform replacement.

Milestones

flowchart LR
  Wedge[Paid state launch pilot] --> MVP[Sidecar fulfillment workflow]
  MVP --> Proof[Faster service starts and cleaner payer reporting]
  Proof --> Expansion[More states and payer lines]
  Expansion --> Moat[Benefit rules plus provider outcome graph]

Founding team

Experiment roadmap

Risk assessment

What must be true

• At least 6 of the first 15 target operators rank multi-state launch and fulfillment workflow as a top-three budgeted problem.
• At least 2 of the first 4 paid pilots convert to annual subscriptions within one plan cycle.
• Early production accounts improve median time to first booked service by at least 20% or active families per guide by at least 15%.
• Buyers permit enough retention and reuse of provider-conversion and task-outcome data to build a benchmark moat.
• A second segment such as regional insurers or delegated-services groups shows willingness to buy the same core workflow by month 24.

Open diligence questions

• How many U.S. operators actually fit the 1,000-plus family, multi-state expansion ICP today?
• Which service categories consume the most coordinator time and should define the first template library?
• Who controls budget when the coordination vendor sells to the operator but the payer demands auditability?
• What MSA, BAA, or data-retention terms allow provider and task outcome reuse across episodes or payer relationships?
• When a buyer refuses this product, do they extend internal tools, customize a generic CRM, or choose a services-led competitor?

Model sanity

• Revenue engine. Base-case revenue grows by expanding active paid deployments from 3 at Y1 exit to 15 at Y3 exit at about $260K of blended annual value each.
• Must go right. The first operator pilots must turn into reusable state and payer templates so second deployments land faster and keep gross margin near 69%.
• Model breaks if. If pilot conversion, data-retention rights, or template reuse slip toward the downside case, cash compresses toward roughly $56K before Y3 ends.
• Next-round proof. A credible seed story appears once the business reaches 8 paid deployments, benchmark reporting across early accounts, and one plan-side design partner with visible cash buffer left.

Scenarios

Sensitivity

flowchart LR
  Pipeline[Founder and partner pipeline] --> PaidDeployments[Paid pilots and launch deployments]
  PaidDeployments --> AnnualContracts[Annual production subscriptions]
  AnnualContracts --> Revenue[Revenue per active paid deployment]
  Revenue --> GrossProfit[Gross profit after delivery and hosting]
  GrossProfit --> Cash[Cash that funds template reuse and expansion]

Flags: The base case counts paid deployments rather than pure logos, so Y2-Y3 growth depends on early accounts expanding into additional states or payer lines rather than staying single-scope. · The researched beachhead is only about 100 buyer accounts, so missing the operator wedge or the plan-direct expansion path would cap the market faster than the topline alone suggests. · Gross margin only holds if the company actually achieves the business-plan milestone of cutting second-deployment effort by more than 50%; otherwise implementation headcount pulls forward. · The downside scenario ends near the cash floor, so any slip in pilot conversion, procurement timing, or data-retention permissions likely forces an earlier raise.

• Services Margin Trap. Customers may believe eldercare coordination is inherently bespoke and keep adding humans instead of standardizing work in software. Mitigation: Sell first to operators already feeling care-guide productivity pressure, price on active families served, and prove time-to-service and case-load gains before trying to expand the workflow surface area.
• Payer ROI Ambiguity. Insurers may like the concept but hesitate to expand budgets if reduced medical spend or retention gains are not yet visible. Mitigation: Anchor the first sale in operator productivity, SLA compliance, and family retention metrics, then layer in payer-outcome reporting once the workflow is embedded.
• Fragmented Local Supply Data. Provider availability, service quality, and coverage details vary by state, which can weaken recommendations and slow implementations. Mitigation: Start with a few high-volume service categories and launch states, then build closed-loop provider scoring from real referral outcomes rather than relying on static directories.