The Viability Gap Model

Raymond Okafor is the chief actuary for a regional Medicare Advantage plan that covers 340,000 beneficiaries across six states. His job is to find interventions that cost less than the claims they prevent. The math is simple in principle, difficult in practice. Most technology vendors pitch him a cost per member per month and a projected savings figure. He ignores the savings figure and builds his own model from claims data. He has rejected eighty-three technology proposals in eleven years because the unit economics did not survive his model.

When he reviewed BlueMirror’s funding architecture, he found something he had not seen before: a technology platform that priced itself at the cost floor for the population segment that could least afford it, funded the gap through a five-layer stack, and still projected 40% gross margin at scale. His question was not whether the model was plausible. His question was whether the funding layers were real or decorative.

The viability gap concept

#

The cost to serve one BlueMirror subscriber is approximately $35/month at the conservative floor (BMT-10.01). The value that service creates for the healthcare system is $200–400/month in avoided costs: fewer emergency department visits, reduced hospitalizations from medication non-adherence, lower care coordination overhead, earlier intervention on condition changes. The gap between what the subscriber can pay and what the service costs is the viability gap.

This is not a novel concept. It is infrastructure financing applied to personal technology. Highways cost more to build than individual drivers can pay in tolls. The entities that benefit from the highway (businesses, property owners, the regional economy) fund the gap through taxes. Broadband infrastructure in rural areas costs more per household than the household can bear. The entities that benefit from connectivity (employers, telecom providers, the federal government) fund the gap through universal service fees and grants.

BlueMirror is personal infrastructure for aging. The end user cannot always pay the full cost. The entities that capture value from the service (insurers who avoid claims, providers who reduce coordination burden, employers who reduce absenteeism from elder care) fund the gap because the economics justify it. The MA plan that pays $50/month for BlueMirror and avoids $150/month in claims cost is not performing charity. It is purchasing a service whose ROI it can calculate.

The funding stack is path-agnostic. An institutional payer funding a Path A subscriber and the same payer funding a Path F subscriber pay similar rates because the value created is similar. Avoided hospitalizations, improved medication adherence, reduced care coordination cost: these outcomes are generated by the concierge agent layer, which operates identically across paths. The cost difference between paths is absorbed by BlueMirror, not by the funder.

Layer 1: institutional payers

#

The primary funding layer covers 50–60% of the subscriber base at scale. Four channels compose it.

Medicare Advantage plans position BlueMirror as a Special Supplemental Benefit for the Chronically Ill (SSBCI) or a general supplemental benefit under CMS guidelines expanded since 2019. The actuarial case: pay $50/month for BlueMirror, avoid $100–200/month in claims costs from reduced ER visits, improved medication adherence, and fewer hospitalizations. The MA plan pays the full list price. The subscriber pays $0. The payment appears in the subscriber’s plan benefits alongside existing supplemental benefits such as fitness programs, meal delivery, and OTC allowances. Sales cycle: 12–18 months, aligned with the annual benefit design cycle. This channel does not drive year-one volume. It drives year three through five volume, after pilot data demonstrates the claims impact.

Medicaid managed care and HCBS waivers cover dual-eligible populations through Home and Community-Based Services waiver programs in participating states. BlueMirror qualifies under assistive technology, personal emergency response systems, or remote monitoring categories depending on state waiver language. States with established technology coverage include California (CalAIM), New York, Washington, Oregon, Minnesota, and Colorado. The state Medicaid agency or managed care organization pays the institutional rate. The subscriber pays $0.

PACE programs operate under a capitated model where the program receives a fixed per-member-per-month payment from Medicare and Medicaid and is responsible for all care. BlueMirror reduces the PACE program’s care coordination costs, meaning the subscription payment comes from realized savings, not new spending. PACE pays a per-member institutional rate of $40–50/month. This is the beachhead channel. PACE programs have physical locations that can host Zone 2 regional nodes, IT infrastructure, HIPAA compliance, and a financial model that aligns with per-member platform economics. The first deployments will concentrate here because the operational alignment is strongest: PACE already manages total cost of care, already has the physical infrastructure for Zone 2 hosting, and already measures the outcomes that BlueMirror improves.

Employer benefits serve the 50–65 pre-retirement cohort. Employers offer BlueMirror as a dependent elder care benefit. The employer pays the consumer rate. The employee’s aging parent is the subscriber. The subscriber pays $0. The benefit to the employer is reduced absenteeism from elder care responsibilities, reduced presenteeism (the employee who is physically present but managing a parent’s care crisis remotely), and competitive positioning in the benefits market. This channel takes longer to develop than the healthcare channels because employer benefit decisions operate on annual enrollment cycles and require HR buyer education.

Path mix varies within the layer. PACE concentrates Path A because PACE facilities host Zone 2 nodes and PACE programs fund Local Pane devices. HCBS waivers concentrate Path C and Path F because state waiver programs are less likely to fund dedicated hardware. Employer benefit subscribers concentrate Path C and Path D because the pre-retirement demographic overwhelmingly owns smartphones. The path mix within each institutional channel affects BlueMirror’s cost structure but not the institutional payer’s rate.

Volume projection at scale: 2.5–3.0 million subscribers across all four channels and all deployment paths.

Layer 2: provider-mediated billing

#

This layer reaches Original Medicare beneficiaries through existing fee-for-service billing codes. BlueMirror partners with physician practices, health systems, or virtual care providers. The provider bills CMS under Remote Patient Monitoring codes (CPT 99453–99458, reimbursing $50–120/month) and Chronic Care Management codes (CPT 99490–99491, reimbursing $40–80/month).

BlueMirror provides the technology platform: monitoring, data collection, care coordination. The provider provides clinical oversight: data review, care plan management, clinical decision-making. The provider bills CMS and receives reimbursement. The provider pays BlueMirror a platform fee of $40–50/month from the reimbursement and retains the balance as margin for clinical labor.

The subscriber pays $0 or a small copay (20% of the RPM charge under Original Medicare). This layer is more operationally complex than Layer 1 because it requires clinical partnerships, CMS compliance, and clear contractual boundaries between BlueMirror as technology vendor and the provider as billing entity. The provider must perform clinical oversight: reviewing monitoring data, adjusting care plans, making clinical decisions. BlueMirror does not bill CMS directly and does not provide clinical services. This separation is not bureaucratic; it reflects the actual skill boundary. BlueMirror provides the data. The clinician interprets the data and acts on it.

The operational challenge is that provider partnerships require local relationships. Each practice or health system has its own billing infrastructure, clinical workflows, and compliance posture. Scaling this layer requires either a dedicated channel team that builds these relationships market by market, or partnerships with intermediary organizations (virtual care platforms, remote monitoring companies) that already have the provider relationships and CMS billing capability. The second approach is more scalable. BlueMirror provides the technology; the intermediary provides the clinical wrapper and billing.

But it works under existing Medicare fee-for-service, reaching the approximately 37 million Original Medicare beneficiaries that the MA channel does not serve.

Path mix within this layer concentrates on Path C and Path F. Original Medicare beneficiaries less commonly receive dedicated device hardware through their providers, so many enter through the smartphone or no-device paths.

Volume projection at scale: 300,000–500,000 subscribers.

Layer 3: BGO self-funding

#

A subscriber whose Context Shard earnings through the BlueMirror Global Opportunity marketplace generate income can offset her subscription cost. The earning concierge routes BGO income against the subscription balance. The financial concierge models the interaction between BGO income and any benefits thresholds (IRMAA brackets for Medicare premiums, Medicaid asset limits) before activating the offset, ensuring that the BGO income does not inadvertently trigger benefits reductions that cost the subscriber more than the subscription.

This layer is elegant but dependent on marketplace maturity. The BGO marketplace needs a critical mass of Context Shard buyers (health systems, FQHCs, educational institutions, businesses) to generate meaningful Sage income. Realistic timeline: year three and beyond for early Sages, year five and beyond for meaningful volume. A retired nurse practitioner whose medication review Context Shard is purchased by twenty FQHCs generates enough to cover her subscription and then some. A retired teacher whose literacy methodology Shard is purchased by three school districts covers part of her cost. A retired electrician whose residential wiring diagnostic Shard is purchased by fifteen property management companies generates $300/month in passive income, more than enough to offset the $35–50/month subscription.

The earnings are path-agnostic. A Path F subscriber can be a successful BGO Sage because BGO earnings depend on the value of her expertise, not on her hardware configuration. The Context Shard is created through the earning concierge’s guided methodology (BMT-01.11), which works identically across zones. The Shard itself lives in Zone 3 infrastructure regardless of the Sage’s personal deployment path.

Volume projection at scale: 200,000–400,000 subscribers partially or fully self-funded by year five.

Layer 4: the Viability Gap Fund

#

The residual layer for subscribers who fall through Layers 1–3. This person is typically rural, on Original Medicare with Medigap supplemental insurance, limited income, no Medicaid eligibility, no employer connection, and not in a region with a provider partnership. She is the person most likely to need the service and least likely to have a pathway to pay for it.

The recommended structure is a separate 501(c)(3). Revenue sources: premium subscriber margin allocation (5–10% of gross margin from year 1–3 subscribers at $100/month), institutional partner contributions, philanthropic and impact capital from foundations focused on aging and health equity, crowdfunding through a public contribution mechanism, and government grants from ACL, HRSA, CMMI demonstrations, and USDA rural health programs.

At one million premium subscribers contributing an average of $5/month in margin allocation, the fund generates $60 million per year, covering gap assistance for approximately 140,000 subscribers at $35/month. This is before institutional, philanthropic, and government contributions.

The unbiased funding firewall governs the fund. This is a structural requirement, not a policy preference. Funders contribute to the pool. The pool allocates to subscribers based on income qualification. Funders never select, identify, or influence which subscribers receive funding. Funders receive aggregate impact reporting: number of subscribers served, hospitalizations avoided, medication adherence improvements, average cost savings. Funders never receive individual-level data. A funder’s commercial relationship with BlueMirror (integration partnership, marketplace participation) is governed by a separate agreement with independent terms. Contributing to the fund does not create preferential integration access. Withdrawing from the fund does not affect existing commercial agreements.

The firewall is enforced at the architecture level. Fund contributor identity is not available to any concierge agent or SLM. The buying agent’s recommendations, the health concierge’s provider suggestions, and every other agent output operate identically for a fund-supported subscriber and a self-paying subscriber. The enforcement is architectural because policy firewalls can be overridden by management decisions. Architectural firewalls cannot.

The Fund subscriber’s deployment path is determined by her hardware situation and regional infrastructure, not by her funding source. The Fund does not require a dedicated device. It also does not exclude one. If a PACE program in her region hosts a Zone 2 node, she can be on Path A or Path C regardless of her Fund status.

Volume projection at scale: 200,000–400,000 subscribers.

Layer 5: consumer payment

#

The residual after all layers process. For institutionally funded subscribers: $0. For provider-mediated subscribers: $0 or a small copay. For BGO self-funded subscribers: variable, often $0. For Gap Fund subscribers: $0–15/month depending on income level and gap coverage amount. For self-paying subscribers above the income threshold: the consumer rate schedule ($100/$70/$50).

The guarantee: no income-qualified subscriber pays more than $35/month out of pocket, regardless of her deployment path. Income qualification is based on household income relative to the Federal Poverty Level, adjusted for geographic cost of living. The threshold and the calculation method are published, not opaque. A subscriber knows whether she qualifies before she enrolls.

What the subscriber sees on her bill is the list price, the funding applied, and her residual cost. She does not see her deployment path on the bill because the price she pays is path-independent. She does not see the breakdown of which fund source covered her gap because the source is irrelevant to her. She does not see a label that identifies her as “subsidized” or “fund-supported” because the billing system does not distinguish between funding sources in the subscriber-facing interface. The bill shows what she owes, the assistance she received, and nothing else. This is an intentional design choice. The subscriber who pays $0 because her MA plan covers the full cost and the subscriber who pays $0 because the Viability Gap Fund covers her see identical billing interfaces. Neither is marked. Neither is differentiated. The service is the same.

Revenue composition at scale

#

At five million subscribers in year five, the blended economics:

Annual revenue at five million subscribers: $3.0–3.6 billion. Against $35/month conservative cost to serve ($2.1 billion at five million): approximately 40% gross margin. The channel mix matters because institutional payers provide steady, predictable revenue while direct-to-consumer provides higher margin. The path mix within each channel also matters because Path A subscribers have higher hardware-related costs offset by lower Zone 3 inference cost. The architecture is built so that no single path mix breaks the unit economics.

Raymond’s model confirmed the actuarial logic. The MA plan’s cost to cover BlueMirror was $50/month per member. The MA plan’s average monthly claims cost for the eligible population was $1,200. If BlueMirror reduced claims cost by 5%, the savings exceeded the investment by a factor of twelve. His recommendation was not to approve BlueMirror. His recommendation was to request pilot data, because he had been doing this long enough to know that projected savings and actual savings are different things. The model worked on paper. His job was to determine whether it worked in practice.

Cross-References

#

The Unit Economics (BMT-10.01). The per-subscriber cost profiles by deployment path that produce the cost floor used throughout this article.

The Institutional Channels (BMT-09.03). The procurement and sales architecture for institutional payer relationships.

What This Does to Cost Structure (BMT-10.06). The specific cost-impact analysis that justifies the $200–400/month avoided-cost claim.

The Financial Concierge (BMT-01.04). The benefits interaction engine that manages the relationship between BGO earnings and benefits thresholds.