What changed
USDA is paying out Child Nutrition Program block grants to state agencies as annual pass-throughs — $600,046,613.34 to Michigan Dept of Education alone (FACT, USAspending), with parallel awards to CA ($1.5B+, $2.5B), NY, FL, IL, OH, TX, MD. Every dollar reaches a school food authority or CACFP/SFSP sponsor only after that sponsor files a monthly reimbursement claim to the state.
Why now
FY2026 block grants are landing now (FACT: multiple 2026-dated CNP CN BLOCK PROG awards on USAspending), so the claim/reimbursement cycle for this funding year is live and recurring 12×/year per site.
Converging signals
Three signals meet at one point: (1) a large funded pass-through (CNP block grant), (2) a defined forced-filer class (SFAs + CACFP/SFSP sponsors who cannot get reimbursed without filing), and (3) a state portal (MI NexSys / MDE CNP claiming system) — replicated across 50 states.
Customer pain
HYPOTHESIS (not in source): small sponsors — daycares, single-site charters, summer sites — do meal counts and eligibility by hand or in spreadsheets, and claim errors trigger clawbacks, deferred payment, and Corrective Action Plans during Administrative Reviews. The claim edit-check is the pain; source confirms the filing obligation but not the error rate.
Who pays
Small/under-tooled SFAs, and CACFP/SFSP sponsor organizations (daycare networks, Head Start, summer-meal sponsors) that draw reimbursement from the state agency. Buyer is the sponsor's food-service director or sponsor bookkeeper — not a procurement office.
Solved today
Big districts use full nutrition-ops suites (Titan, PrimeroEdge/Cybersoft, Heartland, Nutrikids, MealViewer, LINQ). Small sponsors use POS + Excel + the state portal's own web forms, or pay a regional consultant/co-op to prep claims.
Why current solutions are bad
The incumbent suites are priced and scoped for districts, not tiny sponsors; small sponsors fall back to manual claiming with no pre-submission edit-check, which is exactly where clawback errors originate.
Proposed product
A thin SaaS that ingests a POS meal-count export (CSV/API), holds the sponsor's enrollment + free/reduced eligibility roster, runs USDA edit-checks (counts ≤ enrollment × attendance-adjusted, eligibility category totals reconcile, no claim exceeds approved sites), then outputs a portal-ready claim packet + flags exceptions before submission. Start as an assembler/validator; add direct portal submission per-state once the wedge is proven.
MVP version
Michigan-only: CSV import from the 2-3 most common small-sponsor POS systems, an eligibility roster table, the CNP monthly-claim edit-check ruleset, and a one-page 'claim-ready' export matching MDE NexSys fields. Manual copy-into-portal at first — no scraping needed to earn revenue.
30-day build
Confirm the exact MI CNP monthly-claim fields and edit rules from public MDE CNP guidance and USDA FNS instructions; build the edit-check engine + CSV import; recruit 5-10 small MI sponsors from CACFP/SFSP sponsor lists (public) for free pilot in exchange for feedback.
60-day build
Turn pilots into paid seats; add the 2nd/3rd POS import formats; write the eligibility-verification-summary helper (annual pain that recurs). Document a repeatable 'add a state' spec.
90-day revenue plan
Charge live in MI, begin cloning to a 2nd state (OH/IL/NY/FL all have equivalent large CNP awards on USAspending — FACT); target consultants/co-ops as resellers who prep claims for many sponsors.
Distribution path
Direct outreach to CACFP/SFSP sponsors and small SFAs (state agencies publish sponsor directories); state/national CACFP sponsor associations and listservs; content demonstrating a live edit-check catching a real claim error (demonstrated value, not relationship sales).
Pricing hypothesis
$50-150/mo per sponsor, or $10-25/site/month for multi-site sponsors; consultant/co-op tier billing per claim across their book.
Technical difficulty
Low-moderate. CSV import + a deterministic rules engine + roster storage is squarely solo-buildable. The only hard part is per-state edit-rule accuracy and (later) portal submission integration.
Legal / regulatory risk
Low. Handles child eligibility PII (free/reduced status is protected under NSLA §9) — needs encryption, access control, and a data-handling agreement, but no operator licensing. This is compliance-as-moat, not a licensing barrier.
Platform dependency
None that can deplatform it — submits to/for a government portal. Dependency is on POS export formats and state portal field specs, both stable and public.
Founder fit
Very high. This is the founder's proven shape: a funded mandate forces a defined class to file to a government portal, and a solo operator builds the submission/validation layer and charges per site/seat — exactly the FMCSA ELDT pattern, with 50 replicable state markets.
Breakout potential
Moderate-high. 20k SFAs + 30k CACFP sponsors nationally (PIE figure is inference); land small sponsors incumbents ignore, then move upmarket or become the per-state claim rails. Recurring monthly revenue, not one-shot.
Final recommendation
PURSUE as a validation pilot. The funded mandate and forced-filer class are real and on-thesis; the open risk is small-sponsor willingness-to-pay, not demand existence. De-risk by shipping a MI-only edit-check/assembler and getting 3-5 sponsors to pay before building portal submission or cloning states.
Next action
Pull public MDE CNP monthly-claim instructions + the MI CACFP/SFSP sponsor directory, encode the edit-check ruleset, and line up 5 small sponsors for a paid pilot.