What changed
CMS issued an interim final rule (2026-11094) implementing a Medicaid community-engagement requirement under §1902(xx) of the Social Security Act; states must implement no later than January 1, 2027, and beneficiaries must document qualifying activities (work, volunteering, caregiving) or lose coverage. This is FACT per the Federal Register text in demand_evidence.
Why now
States are standing up verification/reporting systems now against a hard 2027-01-01 deadline (FACT, FedReg). Prompt-to-native-Android app generation (Google AI Studio, May 2026) and on-device speech-to-text collapse the build cost of a passive activity-logging app to near zero this cycle (capability signals; the specific tooling maturity is source-supported, the 'near-zero cost' framing is inference).
Converging signals
Three signals meet at one point: (1) a federal mandate creating a compelled class (millions of beneficiaries + every state agency), (2) near-zero-cost native Android app generation, (3) on-device STT for frictionless activity capture. The non-obvious convergence is the BUYER — the MCO, whose capitation revenue is destroyed by disenrollment — not the beneficiary or the state.
Customer pain
HYPOTHESIS (well-grounded by rule mechanics, not yet by cited MCO complaints): Medicaid MCOs are paid a fixed per-member-per-month capitation and lose that entire revenue stream the instant a member is disenrolled. The rule's own critics call it 'Unnecessary and Very Burdensome' (FACT, HME Business headline in evidence), and historical work-requirement rollouts (e.g., Arkansas 2018) disenrolled people primarily for reporting failures, not ineligibility — so MCOs face predictable, revenue-destroying churn driven by paperwork, not eligibility. That churn is a direct P&L hit they already staff against.
Who pays
PRIMARY: Medicaid managed-care organizations (MCOs) buying member retention framed as compliance — they have a quantifiable revenue-loss-per-disenrollment. SECONDARY: FQHCs/clinics whose reimbursements depend on continuous enrollment; state Medicaid enrollment brokers. The beneficiary uses the app free.
Solved today
HYPOTHESIS: MCOs run manual outreach call campaigns, mail reminders, and care-management staff to chase members; states are building their own bare-minimum verification portals. No focused passive-logging + multi-state-format product is cited in the input; this is an inference about the gap, not a verified competitor scan.
Why current solutions are bad
Manual outreach is expensive, reactive, and low-yield; beneficiaries fail paperwork because it is burdensome and episodic, not because they are ineligible. A state's own portal verifies but does nothing to help the member remember, capture, or format the evidence — so it drives disenrollment rather than preventing it. That gap is exactly the MCO's loss.
Proposed product
A white-labelable member app: passive/low-friction logging of qualifying activities (calendar/location/voice-note capture via on-device STT), a per-state rules engine that maps logged activity to each state's exemption categories and verification format, deadline reminders, and one-tap submission or export in the state's required format. MCO-side: a retention dashboard flagging members at risk of paperwork disenrollment. Sold to MCOs per-member-per-month or as a retention SaaS seat.
MVP version
One state (pick an early-mover work-requirement state), one MCO design partner. App captures the 2-3 most common qualifying activities + caregiver/medically-frail exemptions, emits that state's verification format, and sends deadline nudges. MCO dashboard = a simple at-risk-member list. Prove retention lift on a member cohort.
30-day build
Read the IFC and the first states' implementation guidance in detail; map one state's qualifying-activity and exemption taxonomy and required verification format. Build the prompt-generated Android app skeleton + activity logging + export. Line up 1-2 MCO or MCO-adjacent (care-management vendor) design conversations using the disenrollment-revenue-loss pitch.
60-day build
Ship a working single-state pilot with one MCO design partner over a small member cohort. Instrument retention/verification-completion metrics. Add the state's submission/export path. Draft the per-member pricing tied to avoided-disenrollment value.
90-day revenue plan
Convert the design partner to a paid per-member-per-month or per-seat contract on measured retention lift; use the pilot data to open 2-3 more MCOs in the same state, then replicate the state rules-engine module into a second state. First revenue plausible in the 90-180 day band given healthcare sales cycles.
Distribution path
Direct to MCO retention/quality (HEDIS/Stars-adjacent) and care-management leaders via the revenue-loss-per-disenrollment ROI pitch; via care-management-vendor and enrollment-broker partnerships; via state Medicaid association channels. NOT app-store consumer acquisition — the MCO distributes to its own members.
Pricing hypothesis
Per-member-per-month (e.g., a small fraction of the capitation-at-risk) or per-retention-seat SaaS; alternatively per-member-retained success fee. Anchor against the MCO's known revenue loss per disenrolled member-month.
Technical difficulty
Moderate. App generation and on-device STT are cheap; the hard, defensible part is the 50-state rules/format engine and integration with MCO member data and state submission formats. Solo-buildable for the first 1-2 states; the moat is accumulated state-format coverage.
Legal / regulatory risk
MEANINGFUL. Healthcare data = HIPAA/PHI handling and a BAA with each MCO; state Medicaid data-use rules; and the anti-kickback/beneficiary-inducement question is LIVE (the input itself cites a CMS RFI on the Anti-Kickback Statute and Beneficiary Inducements CMP, 2026-12676) — giving beneficiaries app-based help could implicate inducement rules and must be structured carefully. This is the single biggest kill risk and requires health-regulatory counsel.
Platform dependency
Low platform-policy risk (submits to state/MCO systems, not a consumer platform gatekeeper), but HIGH dependency on each state's still-forming verification format and on MCO data access — both moving targets until 2027.
Founder fit
Strong on the government-mandate/forced-flow shape the founder has shipped before (FMCSA ELDT pattern: read mandate → identify compelled party → build submission layer → monetize per transaction). WEAKER on healthcare: PHI/HIPAA, MCO procurement, and anti-kickback structuring are outside his stated edge and pull toward the 'heavily regulated medical' and 'enterprise-ish buyer' zones he avoids. The buyer is not a solo consumer paying by card.
Breakout potential
High if it lands: 40+ states adopting work requirements = a replicable per-state module, dozens of MCOs per state, recurring PMPM revenue, and a data asset on qualifying-activity verification. The same engine extends to SNAP/TANF work requirements.
Final recommendation
CONDITIONAL PURSUE / VALIDATE FIRST. The mandate and convergence are real and the MCO revenue-loss logic is compelling, but the two load-bearing assumptions — that MCOs will pay for this, and that it survives anti-kickback scrutiny — are unproven. Do a 2-week validation: (1) one MCO/care-management conversation to confirm willingness to pay against disenrollment loss, (2) a health-regulatory counsel read on beneficiary-inducement structuring. Build only after both clear. This is a higher-ceiling, higher-friction bet than the founder's typical fast-cash forced-filer play.
Next action
Book 3 discovery calls with MCO retention/care-management leaders (or a care-management vendor) to quantify their per-disenrollment revenue loss and confirm they'd pay per-member-retained; in parallel, get a one-page counsel opinion on anti-kickback/inducement structuring.