What changed
CMS issued an interim final rule (2026-11094, effective/implementation deadline stated in-source as no later than January 1, 2027) implementing a Medicaid community-engagement (work) requirement under a new SSA section: applicants and beneficiaries in scope must demonstrate qualifying activities or lose coverage, and every state must stand up verification/reporting. This is FACT from the Federal Register source. The IMAGINATIVE LEAP — that the proof lives at the tiny org where the activity happens, not the state — is a HYPOTHESIS about where the buildable wedge sits.
Why now
The rule is live with a hard state implementation deadline (stated as Jan 1, 2027), so states, MCOs, and community orgs are all being forced into motion inside a fixed window. Prompt-to-native-Android build (AI Studio) and per-request machine payment rails (x402/Cloudflare Monetization Gateway) are cited capabilities that lower build/monetization cost — but neither is required to ship this; both are secondary.
Converging signals
A federal forced-documentation mandate (regulation) + near-zero-cost native app build (android) + metered per-transaction payment (platform). The genuine convergence is the mandate meeting a defined, un-tooled actor class (volunteer coordinators / small employers) who currently hold only paper sign-in sheets.
Customer pain
HYPOTHESIS, not yet evidenced: enrollees lose coverage over undocumented-but-real activity; community coordinators get pestered for attestation letters; MCOs lose capitation when members are disenrolled. The input contains NO complaint threads, job postings, or MCO/org interviews proving any of these parties will pay — the convergence itself flags the KILL TEST (interview 5 MCOs + 5 orgs) as unrun.
Who pays
Two proposed buyers: (1) Medicaid MCOs, on a churn-reduction thesis (they lose per-member capitation on disenrollment); (2) community orgs / small employers, on a low per-seat 'stop pestering me for letters' fee. Both are UNVALIDATED. The actual enrollee (beneficiary) receives the benefit but is not the buyer.
Solved today
Paper sign-in sheets, ad-hoc attestation letters, and — critically — whatever free end-to-end portal each state is REQUIRED to build under the same rule. The state system is the incumbent and it is mandated to exist.
Why current solutions are bad
Paper is unverifiable and lossy; state portals may be built for the enrollee/agency side and may not capture structured third-party attestations well. But this is asserted, not shown — if the state portal captures third-party attestations directly, the community-side tool has no reason to exist.
Proposed product
White-label attestation issuer: a coordinator confirms an activity; the app emits a signed, timestamped, verifiable record (QR/link) the enrollee submits to the state. Web + offline-capable mobile for non-technical coordinators. Optional MCO dashboard showing at-risk members and attestation status.
MVP version
A single-screen 'confirm activity → issue signed record' web app with a shareable verification link, plus a printable QR. No payments, no MCO dashboard. Buildable in 2–4 weeks solo.
30-day build
Do the KILL TEST FIRST, not the build: interview 5 MCOs and 5 community orgs in one active work-requirement state; obtain and read that state's actual verification portal spec to confirm whether it already ingests third-party attestations. Only build the MVP if the free portal leaves a real gap.
60-day build
If validated: pilot the issuer with 3–5 nonprofits in one state; get real attestations flowing into the state portal; document time saved and any disenrollment averted.
90-day revenue plan
Convert one pilot into paid: either a low per-seat fee from orgs OR a paid churn-reduction pilot with one regional MCO. Revenue here is plausible but NOT within 30–180 days with confidence — it depends on MCO procurement, which is slow.
Distribution path
Direct to community orgs via state nonprofit associations, food-bank networks, and faith networks; MCO side is relationship/pilot sales, not self-serve.
Pricing hypothesis
Community org: $10–30/seat/mo or per-attestation micro-fee. MCO: pilot fee (few $k) → per-retained-member or per-attestation. Numbers are hypotheses.
Technical difficulty
Low-to-moderate. The signed-record issuance is easy; the hard part is integrating with each state's submission format and proving the record is accepted — that varies by state and is undefined here.
Legal / regulatory risk
Real. Attestations feed a benefits-eligibility determination affecting people's health coverage — a false or mishandled record can cost someone Medicaid. Handling enrollee PII and activity data raises privacy exposure disproportionate to a small fee. This is a vulnerable-population product; monetization must not be predatory and accuracy liability is nontrivial.
Platform dependency
Not platform-deplatformable, but DEEPLY dependent on each state's portal accepting third-party attestations — an integration dependency, not a policy one. If the state portal is closed-loop, the product is stranded.
Founder fit
Partial. It matches the government-mandate / forced-flow shape the founder does well, and he can build the submission layer. But the buyer is NOT the forced filer paying per-filing (the FMCSA pattern) — the forced party (enrollee) doesn't pay, and the proposed payers (MCOs) are exactly the slow, indifferent, procurement-driven buyer the founder avoids.
Breakout potential
If MCO churn-reduction is real and one state works, it replicates across ~40 work-requirement states and every MCO — large. But that upside rides entirely on the unproven MUST-BE-TRUE.
Final recommendation
CONDITIONAL / VALIDATE-BEFORE-BUILD. Do not build yet. The mandate is real and large, but every dollar of revenue depends on two unproven claims — that state portals leave an attestation gap, and that MCOs (or orgs) will pay for it. Run the interviews and read one state's portal spec first; if the free portal already ingests third-party attestations or MCOs are indifferent to this churn, kill it. A better-fit adjacent play in the same rule may be a per-filing tool for a party that IS the forced filer AND the payer.
Next action
Pick one active work-requirement state; pull and read its Medicaid community-engagement verification portal spec to see if it accepts third-party attestations; in parallel, cold-interview 5 community orgs and 3 MCOs on whether they'd pay to reduce documentation-driven disenrollment. Decide build/kill on those answers.