What changed
NTIA's Tribal Broadband Connectivity Program has funded a wave of greenfield broadband operators: the $65,168,000 award to NANA Regional Corporation explicitly includes 'CREATE A WIRELESS INTERNET SERVICE PROVIDER' as a funded activity (FACT, USAspending award text), alongside at least 12 similar $40-75M tribal awards in the provided evidence (Bethel Native Corp $42.4M, Calista $52.6M, Navajo Tribal Utility Authority $50.8M, Muscogee Creek Nation $41.2M, etc. — all FACT). A new TBCP round is open, closing 09/17/2026 (FACT, Grants.gov 2026-NTIA-TBCP), so the pipeline of new tribal ISPs is still growing.
Why now
Each of these networks is moving from construction to operation now. The moment a grantee lights up service it becomes a facilities-based broadband provider, which under the FCC's Broadband Data Collection rules must file availability data twice a year (filing windows close ~Sept 1 and ~March 1 — INFERENCE from FCC BDC rules, not in source text; verify 47 CFR 1.7004). Simultaneously the grant itself imposes NTIA semiannual performance reports, federal financial reports, and (for construction) Davis-Bacon certified payroll (INFERENCE from standard NTIA award terms). These operators have zero filing history, zero compliance staff, and a fixed deadline they cannot defer.
Converging signals
Three signals meet at one point: (1) appropriated money — a dozen-plus cited awards totaling >$600M across tribal recipients (FACT); (2) a defined filer class — each award creates or funds an ISP that becomes an FCC/NTIA filer (WISP creation is FACT for NANA; recurring FCC obligation is INFERENCE); (3) named portals — NTIA Grants Portal and the FCC BDC system (INFERENCE). Per the system's own heuristic, a mandate + filer class + portal is the founder's highest-fit convergence shape.
Customer pain
A brand-new tribal WISP must produce geospatial availability data (coverage polygons or location lists keyed to the CostQuest Fabric), navigate CORES/FRN registration, certify filings with an engineer, and separately keep the NTIA award in good standing — or risk FCC enforcement and grant clawback. None of this is their competence; their competence is now running a network in remote Alaska. HYPOTHESIS: they currently either lean on their build consultant at consulting rates or are simply not yet aware of the BDC obligation.
Who pays
The grantee organization (tribal corporation, tribal utility authority, or its new WISP subsidiary) — it has federal money that explicitly covers administration/compliance costs, so budget exists by construction of the award. Secondary buyer: the small engineering/consulting firms serving multiple tribal grantees, who would white-label the filing pipeline. Tertiary expansion: the ~2,000 existing small-ISP BDC filers and future BEAD subgrantees (INFERENCE on count).
Solved today
Telecom consultants (Vantage Point, CCG, Finley) prepare BDC filings as billable-hours engagements; Ready.net sells a broadband-operator OS with grant-compliance modules aimed at BEAD; large grantees use in-house regulatory staff. HYPOTHESIS: the smallest greenfield tribal operators are underserved because consultants chase the big BEAD money and platforms price for enterprise.
Why current solutions are bad
Consulting is priced per hour with no product leverage — exactly the 2-5%-of-award-style spend the thesis says to undercut with software. Platform incumbents require adopting a whole operating stack; a grantee three months from its first BDC window needs the filing done, not a platform migration. Nobody sells a simple per-filing, deadline-driven productized service scoped to tribal grantees.
Proposed product
'Compliance Desk' for new tribal/small WISPs: (1) a compliance calendar auto-built from the public award record (USAspending gives every buyer, award ID, and scope — the prospect list is literally a federal dataset); (2) BDC filing-as-a-service — ingest tower/sector or serviceable-location data, generate compliant availability polygons/location files, handle CORES/FRN and certification workflow, submit; (3) NTIA reporting module — semiannual performance report and SF-425 drafting from templated data pulls. Charge per filing, upsell an annual compliance subscription. Human-in-the-loop first, automate the repeatable parts (the founder's proven ELDT pattern: read the mandate, own the portal, charge per submission).
MVP version
No-code-first service MVP: compliance-obligation audit + first BDC filing done-for-you for 2-3 pilot grantees, supported by an internal pipeline (Python + QGIS/open RF tooling for coverage data prep, checklists for CORES/BDC portal steps). The product IS the filing delivered on time; software hardens behind it.
30-day build
Verify the regulatory spine (BDC applicability and window dates, NTIA TBCP special award conditions, whether a certified professional engineer must sign BDC submissions — this affects COGS); build the target list from USAspending TBCP awards (~every tribal grantee, all public); email/call 15 grantees and 5 tribal-broadband consultants with a free 'compliance obligations audit' of their specific award; deliver 3 audits.
60-day build
Convert audits into 2-3 paid pilot engagements ($2-4k each) to prepare their next BDC filing or NTIA semiannual report; build the data-prep pipeline against real pilot data; get one consultant to agree to white-label.
90-day revenue plan
Invoice pilots on delivery (~$6-12k), convert each to a $10-15k/yr compliance subscription ahead of the following BDC window, and use the named-client proof to sweep the rest of the TBCP grantee list before the next filing deadline. 180-day target: 8-12 accounts, $60-120k ARR-equivalent.
Distribution path
Direct outreach to a fully-enumerated, publicly-named buyer list (USAspending award records — cite their own award number in the first email); NTIA TBCP grantee webinars and technical-assistance channels; TribalNet/AIPI and WISPA communities; white-label through the handful of engineering firms that built these networks. No ad spend, no marketplace, no platform gatekeeper.
Pricing hypothesis
$2,000-3,500 per BDC filing cycle (vs. consultant hourly engagements), $10-15k/yr all-in compliance subscription (BDC ×2 + NTIA semiannual ×2 + FFRs + deadline monitoring). Grant-funded buyers are price-insensitive within these bands (HYPOTHESIS — validate in pilot calls).
Technical difficulty
Moderate. Portal submission and report drafting are squarely within proven capability. The real technical risk is BDC availability-data preparation for fixed wireless (propagation-based coverage polygons meeting FCC spec) — mitigate by starting with location-list-based filings and partnering with an RF engineer for the certification/propagation piece rather than building it.
Legal / regulatory risk
Low-moderate. No license required to prepare filings as an agent of the provider (verify BDC certification rules — if a PE must certify propagation maps, that's a contractor line-item, not a blocker). Accuracy liability sits with the provider who certifies; contract accordingly. Compliance is the moat here, not a burden on the founder.
Platform dependency
Government portals (FCC BDC, NTIA Grants Portal) — no platform owner can deplatform the tool; portal UI changes are routine maintenance the founder has already handled in the ELDT business.
Founder fit
Near-perfect match to the proven edge: a federal program compels a defined class to submit into government systems, and the founder has already built and monetized exactly this shape (FMCSA ELDT per-upload submissions). Operational credibility with industrial/field operators translates well to WISP operators; no relationship-sales dependence because the deadline sells for you.
Breakout potential
The tribal-TBCP wedge is a beachhead, not the market. The same pipeline serves ~2,000 existing small BDC filers and the coming wave of BEAD subgrantees in 50 states (each with state-portal reporting on top — the state pass-through thesis). A per-filing engine that works for one WISP works for all of them.
Final recommendation
PURSUE as a productized service pilot. The forced-filer shape is real and cited, the buyer list is public and enumerated, budget exists inside the awards, and founder fit is maximal. It survives the kill attempts if — and only if — two things check out in the first 30 days: (1) BDC certification rules allow an agent+contracted-engineer model, and (2) at least 2 of 15 contacted grantees will pay for the next filing window. Do not build software before those calls.
Next action
Pull the full TBCP grantee list from USAspending, verify BDC filing obligations/windows and certification requirements against FCC rules, then send 15 award-specific compliance-audit offers to mid-size tribal grantees (skip NANA-scale ANCs first pass).