What changed
FACT (USAspending award ASST_NON_2920B275N_013): BEAD money is now flowing to states as awards (e.g., $1.735B to Missouri's Dept. of Economic Development). The program has moved from application to the POST-AWARD obligation phase — states are subgranting to ISPs who now carry multi-year federal/state reporting duties. FACT (capacityglobal.com source premise): the operative question in the market is 'you received BEAD funding, what's next?'
Why now
The award phase is the trigger. Subgrants are being executed state-by-state right now, and each one starts a recurring semiannual reporting clock that runs the length of the build. The compliance burden is arriving as a wave over the next 12-24 months, before any incumbent SaaS is entrenched around post-award BEAD specifically.
Converging signals
Three signals meet at one point: (1) a $42.45B federal program (FACT: program description) pushing money through 56 state/territory portals; (2) a defined forced-filer class — BEAD subgrantee ISPs — who must report for the life of the build (inference from BEAD/NTIA structure); (3) small ISPs that lack dedicated compliance staff (hypothesis). Rule + filer class + portal = convergence.
Customer pain
Recurring, high-stakes paperwork: semiannual progress/deployment reports, Build America Buy America (BABA) documentation, Environmental & Historic Preservation (EHP) conditions, financial reporting, and speed/service certifications — each on a different state's forms, in a different state portal, on state deadlines, with clawback/default risk if missed (inference from BEAD/NTIA requirements; specific forms vary by state).
Who pays
Small/regional BEAD subgrantee ISPs (the recipients of the state subawards). Secondary buyer: the broadband consultants and grant-management firms already engaged to shepherd these ISPs, who could white-label the tool. NOT the state broadband office as sole buyer — selling to subgrantees is not enterprise procurement.
Solved today
Spreadsheets, shared drives, a part-time grant consultant billing hourly or a percentage, or the ISP's owner assembling reports by hand from invoices and field photos (hypothesis — not directly evidenced in source, but consistent with 'small ISPs lack compliance staff').
Why current solutions are bad
Non-repeatable, error-prone, and expensive per report; BABA/EHP evidence (invoices, certs, buildout photos/GIS) is scattered and hard to reassemble at audit time; consultants don't scale across a 4-5 year cadence cheaply; a missed deadline or missing certification risks disbursement holds or clawback.
Proposed product
Multi-tenant SaaS, one workspace per subgrant. Core: (a) per-state deadline calendar seeded with each state's semiannual/financial reporting cadence; (b) evidence locker that tags invoices, BABA compliance certs, EHP documentation, and geotagged buildout photos/GIS to milestones; (c) report assembler that maps stored evidence into the state's semiannual progress/financial/service-certification format for export/upload. Start with 2-3 states, template the rest.
MVP version
One state (pick a large, already-awarded state — e.g., a state where subgrants are executing), one report type: the semiannual progress report. Deadline calendar for that state + evidence locker + a one-click assembled report (PDF/CSV/portal-ready package). Manual template-mapping is fine at MVP; no live portal API needed on day one.
30-day build
Read the target state's BEAD post-award manual and semiannual report template cover-to-cover; map required fields to a data model. Build the single-tenant evidence locker + calendar + report assembler. Recruit 3-5 design-partner subgrantee ISPs (via state award lists, which are public) and one broadband consultant for feedback.
60-day build
Multi-tenant; add BABA evidence workflow and financial reporting fields; harden the report export to match the state's exact format. Onboard the design partners with their real award data. Add a second state's template. Publish a short 'BEAD post-award compliance checklist' as an inbound lead magnet.
90-day revenue plan
Convert design partners to paid at $200-500/mo per subgrant. Sell into the public list of subgrantees in the two launched states via direct outreach and via the consultants (white-label/referral). Line up states 3-5 by cloning templates. Target first recurring revenue inside 90-180 days.
Distribution path
Direct outreach to named subgrantees (award recipient lists are public record — the founder's public-records edge). Partner channel: broadband grant consultants who serve many ISPs at once. Content: a per-state 'what's due when' resource that ranks for BEAD post-award searches. Demonstrated-value selling (a filled-in sample report from their own award), not relationship sales.
Pricing hypothesis
$200-500/mo per subgrant workspace (per-award subscription) over the 4-5 year build; optional annual prepay. Consultant/white-label tier at a multi-workspace rate. Undercuts a percentage-of-award or hourly consultant on the recurring-reporting slice.
Technical difficulty
Moderate. No ML required. The hard part is domain modeling per state (each state's forms/portal differ) and keeping templates current — not the software. Evidence locker + GIS photo tagging + templated document assembly are all standard. Portal auto-submission is a later, optional add-on; export-to-upload is enough initially.
Legal / regulatory risk
Low-moderate. It's a document-preparation/record-keeping tool, not a filer-of-record; keep 'you remain responsible for accuracy' terms. No licensing required for the founder to operate. Compliance is the moat, not a barrier. No platform owner can deplatform a tool that packages reports for a government portal.
Platform dependency
None in the deplatform sense — buyers submit to state/NTIA systems. Risk is instead that state report formats change; mitigated by the per-state template model (updating templates is the recurring product value).
Founder fit
Very high. This is exactly the founder's proven shape: public money flows → a defined class must report to government portals → build the submission/compliance layer and charge per award/seat. Direct analog to his shipped FMCSA ELDT portal-filing product. Leverages public-records sourcing, systems thinking, and fast AI-assisted prototyping.
Breakout potential
Strong horizontal expansion: 56 near-identical state markets from one working template, plus adjacent federal pass-through grant programs (Digital Equity Act, USDA ReConnect, other infrastructure grants) with the same evidence-locker + assembled-report engine. The build compounds: each new state is a template, not a rewrite.
Final recommendation
PURSUE. Textbook forced-filer, public-money opportunity in the founder's strongest lane, with hard funded-mandate evidence ($42.45B program, a $1.7B state award on record) and a reachable, non-enterprise buyer. De-risk by nailing ONE state's semiannual report end-to-end with 3-5 real subgrantee design partners before templating others; validate the actual per-state subgrantee count early to size revenue.
Next action
Pull the public list of executed BEAD subgrantees for one large awarded state, obtain that state's semiannual progress-report template and post-award manual, and build the single-state MVP (calendar + evidence locker + assembled report) while recruiting 3-5 of those subgrantees as design partners.