What changed
HONESTLY: almost nothing changed. The trigger event is a routine federal Title XIX entitlement award of $18,777,363,690 to the Michigan Department of Health and Human Services for FY2026 (FACT, per the USAspending award record 2505MI5MAP). This is the ordinary federal match that funds Michigan Medicaid every year — it is not a new rule, a new form, or a new deadline. The near-identical sibling awards in the demand evidence (OH $26.1B, CA $112.9B, NY $61.3B, TX $38.5B, FL $27.4B, and so on) confirm this is a recurring 50-state entitlement line item, not an event. The actual filing obligation this brief rests on — periodic revalidation of Medicaid provider enrollment at least every 5 years, with ownership/control disclosure and screening — is a standing federal requirement (42 CFR 455.414 / 455.104, HYPOTHESIS: cited from knowledge, not from the provided source text) that has existed since roughly 2011. So: the money is a FACT, the filer class is a FACT-adjacent inference, and the 'what changed' is essentially nothing.
Why now
There is no defensible 'now.' The strongest honest framing is that revalidation is a rolling, continuous obligation — every month some cohort of Michigan providers hits its 5-year mark — so the opportunity is perpetually open rather than time-boxed. That is a weaker position than it sounds: a perpetually open door has been open to every competitor for fifteen years, and several have walked through it. Any brief that manufactures urgency from an $18.8B entitlement award is fooling itself; the award is the reason Medicaid exists in Michigan, not the reason a provider must file this quarter.
Converging signals
Signal 1 (FACT): a very large, recurring federal award to a single named state agency, MDHHS. Signal 2 (INFERENCE): that agency operates a provider enrollment subsystem — CHAMPS — through which providers must enroll and revalidate. Signal 3 (INFERENCE): a standing federal revalidation cadence forces a defined class to re-file periodically. Signal 4 (FACT, from the demand array): the same award structure repeats across roughly 20 states, meaning a Michigan-shaped tool has ~49 structurally similar target markets. Only signal 4 is genuinely load-bearing — it is the template/replication argument. Signals 1-3 are the standing conditions of the Medicaid program, not a convergence.
Customer pain
HYPOTHESIS (not evidenced in the provided input): Medicaid provider enrollment and revalidation is slow, form-heavy, and unforgiving. A missed revalidation deadline results in enrollment termination, which stops Medicaid claim payment entirely — a genuine cash-flow emergency for a small behavioral-health, home-care, DME, or transportation provider. Re-enrolling after termination is materially harder than revalidating on time. Ownership and controlling-interest disclosures must be kept current, and disclosable changes have short reporting windows. NOTE CLEARLY: the input contains zero PAIN evidence — no complaints, no unanswered forum questions, no support threads. This pain description is inference from domain structure, and I am flagging it as such rather than dressing it up.
Who pays
Three candidate buyers, in descending order of reachability. (1) Medical-billing and RCM companies serving Michigan Medicaid providers — they already absorb enrollment/revalidation as an unbilled or thinly-billed service, they have many providers under one roof, and they buy software without procurement committees. This is the right first buyer. (2) Small-to-mid provider groups (5-50 rendering providers) that do credentialing in-house on spreadsheets. (3) Credentialing consultants. NOT a buyer: MDHHS itself. Selling the state its own portal wrapper is enterprise procurement and is explicitly out of scope for this founder.
Solved today
HYPOTHESIS: three ways. In-house staff with a spreadsheet of revalidation due dates, manually re-keying into CHAMPS. Credentialing/enrollment consultants charging per-provider-per-enrollment fees (my estimate, not sourced: roughly $150-$600 per enrollment, more for group/facility). Or established credentialing platforms — Verifiable, Medallion, CertifyOS, Modio Health, Andros, symplr, Availity — which cover payer enrollment broadly and increasingly automate Medicaid enrollment as one payer among hundreds. The existence of that vendor tier is the central problem with this idea.
Why current solutions are bad
The generic platforms are priced and shaped for multi-state, multi-payer health systems and digital-health companies, not for a 12-clinician Michigan behavioral-health agency that only touches CHAMPS. Their per-provider-per-month pricing is heavy for a single-state operator, and their Medicaid coverage is broad-but-shallow — they handle the common case and hand the state-specific weirdness back to the customer. HYPOTHESIS: the specific gap is depth in one state's subsystem — CHAMPS's ownership-disclosure structures, its domain/subsystem quirks, its revalidation letter cadence — where a specialist can be materially better than a generalist. But this is a wedge, not a moat, and I do not have evidence that anyone is dissatisfied enough to switch.
Proposed product
Narrow, and narrower than the convergence title suggests. Not a 'Michigan enrollment filer' — a revalidation deadline and packet product. (a) Ingest a provider group's roster; determine each NPI's revalidation due date from the public Michigan Medicaid provider enrollment data and/or from CHAMPS-issued notices the customer forwards. (b) Alert at T-180/90/60/30/14 days, escalating, with named-owner assignment. (c) Maintain a living ownership-and-controlling-interest disclosure record per entity, versioned, so that the 5%-ownership and managing-employee data is assembled rather than reconstructed each cycle. (d) Produce a completed, validated submission packet plus a step-by-step CHAMPS walkthrough, with the operator submitting through the portal under their own credentials. (e) Only later, and only if the credentialing and access model is clean, offer delegated submission on the customer's behalf. Charge per revalidation filed, with a floor subscription for monitoring.
MVP version
Roster ingest (CSV + NPPES enrichment) → revalidation clock → escalating notifications → ownership-disclosure data model with change-log → generated packet PDF/checklist mapped field-by-field to the CHAMPS screens. Explicitly NOT in the MVP: automated portal submission. Ship the monitoring-and-assembly layer first, sell it, and let the customer press the buttons. This inverts the founder's FMCSA/TPR pattern deliberately — see founder_fit — because ELDT submission was a documented provider-to-registry upload, whereas driving CHAMPS on a provider's behalf means holding provider credentials and PHI-adjacent identity data on day one.
30-day build
No code. Validation only, because the input contains no demand evidence and I will not let the $18.8B number substitute for it. Pull the public Michigan Medicaid enrolled-provider file. Identify 30-40 billing/RCM companies serving Michigan Medicaid. Run 15+ discovery calls with a single question set: how many revalidations did you handle in the last 12 months, who did them, what did it cost you, have you ever had a provider terminated for a missed revalidation, and what would you pay to never have that happen again. Concurrently, read 42 CFR 455 subpart E and MDHHS's provider enrollment bulletins end to end, and get read access to a real CHAMPS account through a friendly provider. KILL THE IDEA HERE if fewer than 8 of 15 report a termination scare or a real dollar cost.
60-day build
If validated: build the monitoring + disclosure + packet MVP against one design-partner billing company's real roster. Do not build submission automation. Get written clarity on two things: whether the design partner's business associate posture requires a BAA (it likely does once you touch provider identity data alongside patient-serving entities), and what CHAMPS's terms say about third-party access. Sign 2-3 design partners at a discounted flat rate in exchange for weekly feedback and a case study with a real number in it ("we caught 6 revalidations that were 40 days out").
90-day revenue plan
First paid, non-discounted contract from a billing company at roughly $200-$400 per provider per year for monitoring plus $150-$250 per revalidation packet produced — undercutting a consultant's per-enrollment fee while being cheaper than a seat on a national credentialing platform. Realistic first-revenue target is 90-150 days, not 30. Target ARR at day 180: $30-60k across 5-8 billing companies. That is a real business only if it replicates; on Michigan alone it caps out small.
Distribution path
Demonstrated value, not relationship sales, which suits the founder. Concretely: build a free public 'Michigan Medicaid Revalidation Lookup' from the public enrolled-provider file — type an NPI, see the due date and days remaining. That is a lead magnet the incumbents have no incentive to build for one state. Then outbound to MI billing companies with their own client roster's at-risk providers already enumerated in the first email. Secondary channels: Michigan provider associations (behavioral health, home care, EMS/ambulance — the last of which the founder's fire-service background gives him real credibility in), and the state's provider-outreach bulletin list.
Pricing hypothesis
Hybrid, deliberately. $199/provider/year monitoring (recurring, predictable, low-friction) + $199 per revalidation packet (transactional, maps to the value moment). For billing companies, volume tiers down to ~$99/provider/year. Avoid per-provider-per-month platform pricing — it invites direct comparison with the incumbents on their terms, which is a comparison this product loses.
Technical difficulty
Low-to-moderate for the MVP as scoped: data ingest, date math, a versioned disclosure model, PDF generation, notifications. The difficulty is entirely in the two things I have removed from the MVP. First, CHAMPS has no public API (HYPOTHESIS), so any submission automation is browser automation against a state portal that can and will change its DOM without notice, and that is ongoing maintenance forever, per state. Second, the data is sensitive — provider SSNs and dates of birth appear in Medicaid enrollment disclosures — which means encryption at rest, access control, and audit logging are day-one requirements rather than day-100 ones. The founder can build all of this; it is not free.
Legal / regulatory risk
Moderate, and higher than the founder's ELDT precedent. Storing provider SSNs/DOBs and ownership records creates real breach exposure. Acting as an agent submitting to a state Medicaid system may require the provider to designate the operator as an authorized agent within CHAMPS; credential sharing is very likely a terms violation and is the wrong architecture regardless. There is also a screening/exclusion dimension (OIG LEIE, SAM exclusions) that the founder must not represent himself as adjudicating. Mitigations: no credential storage, delegated-agent model only, BAA where required, and explicit contractual language that the customer certifies the submission. NOT a licensure barrier — the founder need not become a licensed or certified anything to sell this, which is why I have not set heavy_compliance.
Platform dependency
None in the deplatforming sense — MDHHS cannot ban a competitor, and there is no app store gate. But there is a genuine dependency of a different kind: MDHHS could improve CHAMPS's own revalidation notification and tracking, and it costs them nothing to do so. A state agency shipping a better reminder email is the single most plausible way this product's core value evaporates. That is a real risk and it is not platform-policy risk, so the flag stays false while the risk stays live.
Founder fit
Genuinely strong on shape, weaker on substance than the primary thesis wants it to be. The shape — regulation forces a defined class to file into a government portal, solo operator builds the submission layer, charges per filing — is exactly the FMCSA/ELDT Training Provider Registry pattern the founder has already shipped and monetized. He has proven he can read a mandate, find the forced filers, and build against a federal portal. But there are two material differences from ELDT that I will not paper over. ELDT submissions are certificate uploads with no PHI and no SSNs; Medicaid enrollment carries provider PII and sits adjacent to a HIPAA-covered relationship. And ELDT's Training Provider Registry had no entrenched vendor tier; Medicaid provider enrollment has a well-funded one. The founder's real edges here are public-records fluency (the enrolled-provider file is the lead magnet), ambulance/EMS domain credibility, and willingness to do the unglamorous state-specific work that a multi-state platform will not. Call it 7, not 9.
Breakout potential
The replication argument is the whole thesis and it is the strongest thing in this brief. The demand array itself demonstrates that ~20 states carry structurally identical Title XIX entitlement awards, and by extension near-identical enrollment/revalidation subsystems (MMIS variants, many built by the same handful of vendors — CNSI, Gainwell, DXC — so the portals rhyme). Win Michigan, template it, and Ohio ($26.1B award, per usaspending 2505OH5MAP) is the second instance rather than a second product. But note the asymmetry: replication multiplies a small business into a medium one. It does not turn a monitoring tool into a defensible platform. The ceiling here is a good $1-3M/yr owner-operator business, not a breakout.
Final recommendation
CONDITIONAL PROCEED — but reframed, de-scoped, and gated on 30 days of primary research. Do NOT build 'a Michigan enrollment filer'; that framing walks straight into the credentialing incumbents. Build a revalidation-deadline-and-disclosure product, sell it to Michigan billing companies rather than providers, and treat automated CHAMPS submission as a later, optional layer rather than the wedge. The founder-fit is real and the 49-state replication story is the best thing about this idea. What is NOT real is the urgency: the triggering award is a routine annual entitlement, not a mandate, and this brief would be dishonest if it scored newness or convergence as though something had just happened. The single decisive question is whether a Michigan billing company will pay for deadline monitoring they believe they already do adequately in a spreadsheet. Fifteen discovery calls answer that for the cost of two weeks. Do not write a line of code before they are done, and honor the kill criterion if the answer is no.
Next action
Download the public Michigan Medicaid enrolled-provider file, compute an at-risk list of NPIs whose 5-year revalidation window closes within 180 days, and use that concrete list to book 15 discovery calls with Michigan medical-billing companies this month. Kill the idea if fewer than 8 of 15 can name a real dollar cost or a termination scare from a missed revalidation.