What changed
FACT: The Department of Commerce awarded $1,735,323,221 in BEAD funds to the Missouri Dept. of Economic Development, and the award text explicitly states the recipient 'DOES intend to subaward funds,' with challenge and subgrantee-selection processes named among funded activities. This converts a federal appropriation into a concrete state-run subgranting program with a defined filer class.
Why now
BEAD is at the subgranting phase across the country — states are running challenge processes and opening subgrantee selection now. FACT: Missouri's award funds 'programmatic activities associated with BEAD (e.g., challenge and subgrantee selection processes).' Applicants must assemble coverage/financial packages on a state deadline; winners then carry a 4–5 year semiannual reporting tail. The window to sell the application-assembler side is time-boxed by the state's selection round.
Converging signals
Three signals meet at one point: (1) a funded federal mandate ($1.7B to Missouri, FACT), (2) a defined forced-filer class — ISPs, electric/telephone co-ops, municipalities competing for subgrants (inference from BEAD structure; subawarding is FACT), and (3) a state portal + NTIA reporting stack each of 56 states/territories replicates near-identically (inference).
Customer pain
HYPOTHESIS: Subgrant applications require reconciling FCC Broadband Data Collection (BDC) location/fabric data into the state's required coverage-map and eligible-location formats, plus financials, matching, and challenge filings — then, if awarded, milestone certifications, semiannual performance reports, and speed/uptime attestations for the life of the build. This is spreadsheet-and-consultant labor today. Note: BDC-to-state-format mapping and reporting cadence are inferred from BEAD program structure, not stated in the source award text.
Who pays
The subgrantees themselves — regional ISPs, rural electric/telephone cooperatives, and municipalities/broadband authorities bidding for multi-million-dollar subgrants — and the broadband-grant consultants who currently do this by hand and would white-label a tool. NOT the state procurement office (that is not the buyer).
Solved today
HYPOTHESIS: Broadband grant consultants and engineering firms billing hourly or a percentage of the award; internal staff wrangling BDC exports, GIS, and Excel; generic grant-management platforms not tailored to BEAD's specific NTIA/state schemas.
Why current solutions are bad
HYPOTHESIS: Consultants are expensive (percentage-of-award or high hourly) and don't scale across a firm's multiple applications; generic tools don't ingest FCC BDC fabric data or emit the exact state/NTIA reporting artifacts, so the compliance work stays manual and error-prone against hard deadlines.
Proposed product
Two connected modules. (1) Application Assembler: pulls FCC BDC location/fabric data via the public FCC API, maps served/unserved/underserved locations into the state's required coverage formats, and generates the application coverage-map + eligible-location packages. (2) Post-Award Reporting SaaS: a per-award workspace that tracks milestones and generates the semiannual state performance report + NTIA submission artifacts, low-cost-plan attestations, and speed/uptime evidence for the 4–5 year build tail.
MVP version
Missouri-only, reporting-first. Build the FCC BDC ingest + a Missouri Office of Broadband Development (OBD) reporting-artifact generator: input award/build data, output the exact semiannual report file/format Missouri requires. Manually reverse-engineer Missouri's forms from published NOFO/subgrant guidance. Sell to a handful of Missouri applicants/consultants as a paid pilot before generalizing.
30-day build
Confirm the concrete filing surface: obtain Missouri OBD's BEAD subgrantee NOFO, subgrant agreement template, and semiannual reporting form/schema; confirm NTIA's performance-reporting format. Pull the FCC BDC API and prove BDC-fabric → eligible-location mapping on Missouri locations. Interview 8–12 candidate subgrantees (rural co-ops, small ISPs) + 3–5 broadband consultants to validate willingness to pay and confirm the manual pain is real.
60-day build
Ship the reporting-artifact generator (Missouri) + BDC ingest as a working SaaS. Onboard 2–3 paid pilots (consultant white-label or direct subgrantee). Templatize the state schema layer so a second state is config, not a rebuild.
90-day revenue plan
Convert pilots to paid per-award annual subscriptions; charge per-application fees for assembler use during the active Missouri selection round. Line up state #2 (a neighboring state at the same BEAD phase). Target first real revenue from Missouri subgrantees/consultants within 90–150 days.
Distribution path
Direct outreach to Missouri BEAD applicants (list is discoverable once challenge/selection is public), rural electric/telephone cooperative associations, state broadband/municipal-utility associations, and — highest-leverage — broadband grant consultants who serve many applicants and can white-label. Demonstrated-value selling: show a generated compliant report, not relationship sales.
Pricing hypothesis
Per-application assembler fee $1,000–$5,000 (trivial against multi-$M subgrants) + per-award annual subscription $3,000–$12,000 for the 4–5 year reporting tail. Consultant white-label seat/volume tier.
Technical difficulty
Moderate. FCC BDC data is large and GIS-heavy; the hard part is faithfully reproducing each state's and NTIA's exact reporting schemas — a documentation/reverse-engineering problem more than an algorithmic one. Solo-buildable with AI assistance; matches the founder's proven government-portal-integration pattern.
Legal / regulatory risk
Low-moderate. Attestations and certifications are signed by the subgrantee, not the vendor — the tool assembles/formats, the filer certifies. No licensure required to operate. Compliance is the moat, not a barrier.
Platform dependency
None of the deplatform kind — submissions go to government systems (state OBD portals, NTIA) with no private platform owner. Dependency risk is state-schema churn and whether portals allow file upload vs. only manual web entry (which would cap automation to artifact-generation).
Founder fit
Very high. This is the exact shape the founder has already shipped (FMCSA ELDT: read a federal mandate, identify the forced filers, build the submission/formatting layer, charge per transaction). Public-money forced-filer + government portal + per-filing/per-seat monetization is his maximal-fit thesis, and the 56-state near-identical replication mirrors his '50 near-identical markets' expansion edge.
Breakout potential
High. $42.45B BEAD, ~2,000+ subgrantees nationwide, 56 near-identical state portals. Win Missouri, then replicate the state-schema layer state by state; the reporting tail is recurring revenue for 4–5 years per award. Adjacent expansion into other broadband programs (BROADBAND EQUITY, Tribal Connectivity, RDOF/USDA ReConnect reporting) reuses the same BDC + reporting engine.
Final recommendation
PURSUE — strongest founder-fit shape available. Build reporting-first for Missouri, validate the exact NTIA/state schema and one paid pilot before generalizing, then replicate the state layer. Do not overbuild the multi-state abstraction until Missouri produces a paying customer.
Next action
Obtain Missouri OBD's BEAD subgrantee NOFO + semiannual reporting form and NTIA's performance-report format, and confirm on a call with 3–5 candidate subgrantees/consultants that (a) the reporting burden is manual today and (b) they'll pay a per-award subscription to automate it.