What changed
FACT (Federal Register, 2026-06-03, doc 2026-11094): CMS issued an Interim Final Rule with comment period implementing the Medicaid community engagement requirement under section 1902(xx) of the Social Security Act. FACT (same source): states must implement no later than January 1, 2027. The rule specifies requirements for states AND for the Medicaid applicants/beneficiaries who must demonstrate compliance.
Why now
Hard statutory deadline: every expansion state must stand up verification, ex-parte data matching, and exemption processing within ~6 months of now. HYPOTHESIS: states will meet the deadline with minimal, clunky portals (as Arkansas and Georgia did), pushing the real documentation burden onto enrollees and the safety-net orgs that serve them. The window to build and sell is exactly now-to-Q1-2027, and a second wave hits as each state publishes its own forms.
Converging signals
Three signals meet at one point: (1) the federal rule itself (FedReg 2026-11094, primary source), (2) a defined compelled class — enrollees who must attest/document, states that must verify, providers/CBOs that must support exemption documentation, (3) a named submission surface — regulations.gov near-term for IFC comments, state eligibility portals for ongoing compliance. Per the forced-filer scoring rule, this is full convergence even though it is unglamorous.
Customer pain
When enrollees fail paperwork (not the work itself — Arkansas 2018 showed most disenrollments were procedural), clinics, FQHCs, and Medicaid MCOs lose paying patients/members. HYPOTHESIS grounded in history: procedural disenrollment, not actual non-compliance, is the dominant failure mode; orgs whose revenue is per-Medicaid-patient will pay to prevent it. Near-term pain: hospitals, states, and associations must file substantive comment letters on the IFC within the comment window.
Who pays
Primary: FQHCs, community clinics, hospital Medicaid-enrollment departments, and navigator/enrollment-assister organizations (thousands of orgs, already staffed with enrollment workers). Secondary and larger: Medicaid managed-care organizations, which lose per-member-per-month capitation on every procedural disenrollment — a direct, quantifiable ROI story. NOT the state agencies (that is enterprise procurement for Deloitte/Gainwell — explicitly avoided).
Solved today
Enrollment assisters and clinic staff do this manually today for renewals (the 'unwinding' era proved the workflow exists and is paid for); consultants and law firms (Holland & Knight, Epstein Becker — the very sources here) bill hourly for IFC analysis and comment letters. No incumbent tool exists yet for THIS rule's exemption/engagement documentation because state forms don't exist yet — that is the opening, not a defect.
Why current solutions are bad
Manual attestation-chasing doesn't scale to a new recurring obligation layered on top of renewals; enrollment staff are already the bottleneck. State portals will be built for the state's reporting needs, not for the clinic-side workflow of collecting proof (pay stubs, school enrollment, caregiver status, disability exemptions) from hard-to-reach patients. Consultants at hourly rates are proof of spend and the wedge to undercut.
Proposed product
A clinic/navigator-side compliance workbench: patient roster ingestion, per-patient engagement/exemption status tracking, mobile-first document capture (text a link, patient photographs pay stub/school letter), AI-assisted exemption classification against the IFC's exemption categories, generated submission-ready packets per state's forms, deadline reminders, and an audit log. Charge per completed filing packet. Phase 0 (immediate revenue): an IFC comment-letter intelligence product — structured extraction of the rule's verification mechanics, deadlines, and state obligations, plus comment-letter drafting support sold to provider associations and hospitals during the comment period.
MVP version
Week 1-3: parse the actual IFR text (public, on federalregister.gov) into a structured exemption/verification matrix; ship the Phase 0 rule-intelligence brief + comment-letter tool. Week 3-6: single-state (pick the fastest-moving expansion state to publish guidance) documentation tracker: CSV roster upload, exemption checklist per patient, SMS document capture, PDF packet output. No state-portal API integration required for v1 — output is a submission-ready packet the assister files.
30-day build
Read the full IFR and build the exemption/verification matrix (founder's proven skill: read a federal mandate, find the forced filers). Ship the rule-intelligence/comment-letter product; sell it to 5-10 state primary-care associations and hospital associations while the comment window is open. Use those conversations as discovery for which states' guidance drops first.
60-day build
Ship the single-state MVP tracker with 2-3 design-partner FQHCs or navigator orgs (free or discounted pilot in exchange for workflow access). Instrument the per-filing packet flow end-to-end. Begin outreach to one Medicaid MCO's retention/quality team with the disenrollment-ROI pitch.
90-day revenue plan
Convert pilots to per-filing pricing ($3-8/completed packet) or per-site subscription ($300-600/mo per clinic site). 10 clinic sites at ~$400/mo or equivalent per-filing volume = ~$4k MRR, plus one-time comment-window revenue ($1-3k per association brief). Replicate state-by-state as each publishes forms — the 40-state replication is the expansion story.
Distribution path
State primary-care associations (each state has one; they aggregate FQHCs), NACHC, enrollment-assister networks, Medicaid MCO quality departments, and the health-law-alert ecosystem already covering this rule. Demonstrated-value selling: publish the free exemption matrix as lead generation — exactly the founder's non-relationship sales style.
Pricing hypothesis
Phase 0: $500-2,500 per association/hospital for the rule-intelligence + comment-letter package. Core: per-completed-filing ($3-8) mirroring his proven ELDT per-upload model, with a per-site monthly floor ($300-600). MCO deals later at per-member-touched pricing.
Technical difficulty
Low-to-moderate and squarely in the founder's lane: document parsing, SMS/upload capture, PDF generation, roster management, AI classification. No state-portal write integration needed for v1 (packets, not API submission), which removes the hardest dependency; portal automation can come later per state, exactly like ELDT.
Legal / regulatory risk
HYPOTHESIS: litigation against the rule is likely (Arkansas-era work requirements were vacated in court), BUT this rule implements a statute (section 1902(xx)), not a demonstration waiver, so wholesale invalidation is less likely than in 2018-19; an injunction delaying implementation is the real tail risk and would freeze revenue, not kill the asset. Handling enrollee documents brings HIPAA/PII duties — needs BAAs and sane security, a cost the founder can fund, not a license he must hold.
Platform dependency
None that can deplatform him: the submission targets are government systems (regulations.gov, state eligibility portals) and the v1 output is a document packet. Dependency risk is regulatory (rule enjoined/delayed), not platform.
Founder fit
Maximal under the primary thesis and the ELDT precedent: a regulation compels a defined class to document and submit; he builds the paperwork layer and charges per filing. Adjacent strengths apply: public-records fluency, AI workflow automation, fast prototyping, low-budget execution. The one mismatch to manage: buyers are healthcare orgs, slower than trucking schools — mitigated by leading with the deadline and the free exemption matrix.
Breakout potential
High within the niche: 40 expansion states × thousands of Medicaid-dependent provider orgs × a recurring (not one-time) compliance obligation. If procedural-disenrollment pain is as severe as the Arkansas precedent suggests, MCO contracts turn this from micro-SaaS into a real company without VC. Also a template for the next CMS paperwork mandate.
Final recommendation
PURSUE, staged. This is the founder's exact proven shape (federal mandate → forced filer class → per-filing paperwork layer) with a statutory deadline and a huge compelled population, and the primary source is the Federal Register itself. Stage it to de-risk: (1) this week, pull the full IFR and extract the comment deadline and verification mechanics — this is cheap and monetizable immediately; (2) sell rule-intelligence during the comment window; (3) build the clinic-side documentation MVP only after confirming with 3-5 assister orgs that manual exemption documentation (not state auto-verification) will be the dominant workflow. Abort the core build if discovery shows states are mandated to resolve >80% of cases ex parte.
Next action
Fetch the full text of Federal Register doc 2026-11094 (published 2026-06-03), extract: the comment-period close date, the exemption categories, what states MUST verify ex parte vs. what enrollees must submit, and the enrollee-facing submission mechanics — then call 3 state primary-care associations this week with the free exemption matrix as the opener.