The Institutional Channels

Terrence Washington is the chief strategy officer for a four-state PACE organization serving 2,800 enrollees. He has watched three technology vendors pitch AI-for-seniors solutions to his clinical team in the past year. Each pitched a compelling demo. Each collapsed under the same question: who pays for it, and through what mechanism? The vendors who said “the subscriber pays” did not understand PACE economics. The vendors who said “the health plan pays” could not explain how the plan would classify the expense. The vendors who said “it pays for itself through reduced hospitalizations” could not produce the clinical evidence that a plan actuary would accept.

The deployment architecture is only as real as the funding mechanism that sustains it. The institutional channels are not just acquisition paths. They are funding paths, hardware provisioning paths, and trust paths simultaneously.

The acquisition, funding, and hardware bundle

#

Each institutional channel bundles three functions that direct-to-consumer must perform separately. The channel acquires the subscriber (identifies, qualifies, enrolls). The channel funds the subscription (pays for it in full or contributes toward the cost). The channel often provides or subsidizes hardware (the Local Pane device or the smartphone that runs Zone 1-Phone).

The bundling is what makes institutional channels viable at scale. A direct-to-consumer subscriber must discover the platform, decide to subscribe, pay the subscription fee, and purchase or provision hardware. Each step is a friction point. An institutional channel collapses those steps into a benefit the subscriber already receives. She does not discover BlueMirror; her PACE care coordinator tells her about it. She does not pay for it; her PACE capitation covers it. She does not buy a device; the program provides one. The enrollment workflow (BMT-09.02) handles the rest.

MA plan integration

#

Medicare Advantage plans position BlueMirror as a Supplemental Benefit for the Chronically Ill (SSBCI) or as a high-touch member engagement service. The MA plan pays $50 to $100 per member per month from its supplemental benefit budget, covering the subscription in full for the enrolled member. The subscriber pays nothing.

Hardware varies by plan generosity. Some plans subsidize the Local Pane device for high-risk members (dual-eligible, three or more chronic conditions, prior year hospitalization). Most fund only the subscription. When the plan does not provide hardware, the subscriber’s deployment path depends on her existing hardware: Zone 1-Phone if her smartphone qualifies, No Zone 1 if it does not.

The sales cycle is 12 to 18 months. BlueMirror engages the plan’s supplemental benefits team, the clinical outcomes team, and the actuarial team. The clinical evidence requirements are specific: hospital readmission reduction (target: 15 to 25 percent relative reduction for enrolled members), emergency department use reduction (target: 10 to 20 percent), member retention improvement (target: 2 to 5 percentage points). The evidence comes from pilot deployments, initially through PACE program data (where the clinical outcomes are measurable in a capitated environment) and later through MA plan-specific pilots.

The operational constraint: MA plan sales cycles are long and evidence-dependent. The first MA plan contracts will not close until 12 to 18 months after PACE deployment generates publishable outcomes data. BlueMirror does not project significant MA plan revenue before month 24.

PACE program integration

#

PACE is the beachhead market. Approximately 70,000 enrollees nationally across roughly 170 PACE organizations. The capitated model creates direct alignment: every dollar BlueMirror saves in care coordination costs, every hospitalization avoided, every emergency department visit prevented is a dollar the PACE program retains against its capitated rate.

PACE programs typically fund both the subscription and the Local Pane hardware for every enrollee. The per-enrollee cost (subscription plus amortized hardware) is justified against the per-enrollee savings: reduced care coordination labor, reduced hospitalization rate, improved medication adherence, and earlier detection of cognitive or physical decline. A PACE program spending $4,500 per member per month on capitated care can absorb $100 to $150 per member per month for a platform that reduces downstream costs by multiples of that amount.

Many PACE facilities also host Zone 2 Community Pane nodes for their enrolled population. The PACE facility has the physical space, the HIPAA-compliant infrastructure, and the IT staff to manage a regional compute node. The facility becomes a deployment site for all three zones simultaneously: subscribers receive Local Pane devices (Zone 1), the facility hosts the Community Pane (Zone 2), and Zone 3 provides deep reasoning over the internet. The PACE enrollment is almost entirely Path A: dedicated device, regional node, cloud reasoning. Full stack.

The PACE sales cycle is shorter than MA plans, typically 6 to 12 months, because the decision-maker is the PACE organization’s leadership rather than a plan’s actuarial team. The value proposition is operational: “your care coordinators spend less time on phone check-ins because the system handles daily monitoring, and you detect problems earlier because the system is always present.” PACE organizations evaluate this claim against their own care coordination costs, which they know precisely.

The performance guarantees BlueMirror offers to PACE programs are tied to measurable outcomes: hospitalization reduction, emergency department diversion, medication adherence rates, and care coordinator time savings. These guarantees include risk-sharing provisions where BlueMirror’s per-member fee is partially contingent on achieving agreed targets. A PACE program that does not see the projected hospitalization reduction within the first twelve months can renegotiate the per-member rate or exit the contract. This structure aligns BlueMirror’s revenue with the PACE program’s financial outcomes, which is the alignment that makes the capitated model work.

PACE is also the clinical evidence engine for the rest of the institutional channel strategy. The outcomes data generated by PACE deployments becomes the evidence base that MA plans require before contracting. A PACE deployment that demonstrates a 20 percent reduction in 30-day readmission rates across 500 enrollees produces exactly the kind of data that an MA plan’s actuarial team needs to justify a supplemental benefit line item. The PACE beachhead is not just a market. It is the proof infrastructure for every subsequent channel.

Medicaid HCBS waiver channels

#

State-by-state variation defines this channel. Some states have assistive technology categories under Home and Community-Based Services waivers that can fund BlueMirror subscriptions. Some include hardware in the same assistive technology category. Many do not.

The states with existing AT coverage under HCBS waivers (approximately 30 states as of 2025, with varying definitions of “assistive technology”) are the initial targets. In these states, BlueMirror can be classified as an assistive technology service under the waiver, with the subscription funded as a monthly AT service and the Local Pane device funded as an AT equipment purchase where the state’s waiver covers equipment.

In states where HCBS waivers do not cover AT, or where the AT definition is too narrow to include an AI concierge platform, the channel requires policy advocacy. Working with state Medicaid agencies and HCBS administrators to expand AT category definitions is a 12 to 24 month process per state. BlueMirror prioritizes states with large HCBS waiver populations and existing AT category infrastructure.

The average HCBS-funded subscriber receives subscription funding only, not hardware. She is deployed on Path C (Zone 1-Phone if her smartphone qualifies) or Path F (No Zone 1 if it does not). Hardware provisioning through HCBS waivers is possible in some states but not typical. The Viability Gap Fund (BMT-10.02) may supplement HCBS funding to cover the cost differential for subscribers whose per-subscriber cost exceeds what the waiver pays.

The HCBS channel is the largest addressable population. Approximately 4 million people receive HCBS waiver services nationally. Even a small penetration rate across priority states represents a subscriber base that exceeds the total PACE enrollment many times over. The channel’s challenge is not demand but infrastructure: each state requires separate regulatory classification work, separate Medicaid agency relationships, and separate billing integration. The appendix (BMT-09.03-A) details the priority state list and the current status of AT category coverage in each.

Care agency channels

#

Home care agencies purchase BlueMirror for their client population as a force-multiplier for their caregivers. The agency pays a per-client license. The client pays nothing. The agency caregiver uses the BlueMirror dashboard to coordinate care, review alerts, and monitor the client’s status between visits.

The value proposition to the agency is straightforward: the caregiver who visits three times a week has no visibility into what happens between visits. BlueMirror provides continuous monitoring (for subscribers with Zone 1-Dedicated), daily check-ins (for all subscribers), medication adherence tracking, and early detection of cognitive or physical changes. The caregiver arrives at each visit with context she did not have before.

Hardware provisioning varies. Some agencies purchase Local Pane devices in bulk for their client population. Most rely on the client’s existing phone or no device. The agency may host a Zone 2 Community Pane node at its office, serving its full client population within a geographic region. A mid-sized agency with 200 clients in a metro area can justify a single Community Pane node serving all of them. The node costs $12,000 to $15,000 to deploy and serves 150 to 500 subscribers depending on configuration, making the per-subscriber infrastructure cost $30 to $100 amortized over the node’s operational life.

The care agency channel is the PE roll-up thesis accelerator (BMT-10.03). A PE firm that acquires home care agencies can deploy BlueMirror across the portfolio companies’ combined client base, creating a technology layer that increases operational efficiency, improves client outcomes, and raises the portfolio’s enterprise value. The Community Pane node the agency hosts becomes infrastructure the portfolio company owns.

Employer benefit channels

#

Adult children enroll aging parents through dependent care benefits or employer-funded caregiver support programs. The employer covers the subscription as a benefit. The adult child sometimes purchases a Local Pane device as a gift.

The path mix is highly variable. Some parents have smartphones; some do not. Some adult children gift a device; most do not. The employer channel is the most heterogeneous in deployment path distribution because it depends on individual family circumstances rather than institutional decisions about hardware provisioning.

The employer channel’s primary value to BlueMirror is acquisition efficiency: the employer handles benefit administration, payroll deduction if applicable, and employee communication. The primary value to the employer is reduced caregiver-related absenteeism and presenteeism among employees managing aging parents’ care. Studies consistently show that employees managing elder care for a parent lose 6 to 20 hours per week in work productivity through phone calls, appointment coordination, and anxiety-driven distraction. A platform that handles daily monitoring, medication management, and care coordination reduces the employee’s cognitive load.

The employer channel also serves as a low-friction entry point for subscribers who might later transition to institutional funding. A seventy-year-old enrolled through her daughter’s employer benefit may later qualify for PACE or an MA plan supplemental benefit. When that transition occurs, the subscriber’s funding source changes but her deployment path, her MoC, her concierge relationship, and her data remain continuous. The platform does not restart when the payer changes.

The deployment path distribution across channels

#

Approximate path mix by channel at Phase 3 maturity, based on hardware provisioning patterns and subscriber demographics per channel.

Across the full subscriber base at scale: approximately 35 to 45 percent Path A, 40 to 50 percent Path C, and 15 to 25 percent Path E and F combined, with Paths B, D, and E absorbing small percentages that vary by regional Zone 2 coverage.

The architecture is built so that every distribution shape is operationally viable. A subscriber base that is 90 percent Path A (a PACE-heavy early deployment) and a subscriber base that is 50 percent Path F (a Medicaid HCBS-heavy deployment in a state without hardware funding) both produce a functional, economically sustainable deployment because Zone 3 scales to handle whatever workload the distribution assigns it.

Cross-References

#

BMT-09.01 The Three-Zone Architecture. The deployment paths whose distribution this article maps across channels.

BMT-10.01 The Unit Economics. Per-path unit economics that determine the viability of each channel’s funding structure.

BMT-10.02 The Viability Gap Fund. The funding mechanism that covers the cost differential for subscribers whose channel funding does not meet the per-subscriber cost floor.

BMT-09.02 Getting Into Homes. The enrollment workflow that each channel feeds into.

Technical Appendix BMT-09.03-A is available to partners and investors at partners.bluemirror.tech.