What changed
FACT (Federal Register, 2026-07-10, 2026-13998): the FCC adopted a FINAL rule requiring entities essential to delivering emergency calls in the NG911 environment to implement measures safeguarding NG911 network reliability and reduce the risk of 911 outages, and requiring certain entities to report on their support for NG911 interoperability. The same rule eliminates some legacy 911 reliability rules. This is an adopted rule, not an NPRM — the obligation is real, and the class of obligated parties is named.
Why now
HYPOTHESIS (inference, not in the provided text): the adopted rule carries compliance dates that start a clock, and the first NG911 interoperability report will be a new artifact no covered entity has ever produced before. FACT: the rule is final and published. The window where nobody has a purpose-built tool for the new report is the window to sell one. The provided text does NOT state effective or compliance dates — that is the single most important unknown and must be extracted from the full document before committing a dollar.
Converging signals
Three things meet at one point: (1) a final FCC rule imposing reliability safeguards on NG911 networks; (2) a defined filer class — covered 911 service providers, NG911 service providers, and originating service providers delivering 911 traffic; (3) an existing federal submission channel (the FCC's 911 reliability certification system, and ECFS). The rule also sits atop the ongoing legacy-to-IP NG911 migration, which is exactly what makes the old evidence-gathering process break: circuit diversity in a legacy TDM footprint is a spreadsheet of physical circuits, while in an IP footprint it is a live, changing topology across ESInets and transit providers.
Customer pain
HYPOTHESIS (structural inference, not evidenced in the provided text): the annual 911 reliability certification requires a corporate officer to attest, under penalty, to circuit diversity and critical-component safeguards across every 911 circuit and aggregation point in the footprint. The evidence lives in OSS/inventory systems, network diagrams, vendor attestations and email. Assembling it is a months-long manual exercise repeated annually. The new NG911 interoperability report adds a second, unfamiliar artifact with no established template. The pain is not 'we do not know the rule' — it is 'proving continuously that we still comply, and reconstructing the proof twelve months later for an officer who has to sign it.'
Who pays
The regulatory-affairs or network-compliance owner at a covered entity. NOT the PSAP and NOT the state 911 authority — they are described by the reports, they do not file them. The realistic buyer segment is the long tail: mid-size ILECs/CLECs, regional 911 system service providers, and NG911/ESInet operators who have a filing obligation but no in-house FCC compliance team. Tier-1 carriers (AT&T, Verizon, Lumen) and the large 911 vendors (Intrado/Comtech, Motorola) have regulatory departments and outside counsel and are NOT the target.
Solved today
HYPOTHESIS: telecom regulatory law firms and specialist consultants assemble the certification, billing hourly; internally it is Excel plus a shared drive plus network-engineering interviews. The 911 reliability certification regime has existed since 2013, so an incumbent consulting practice certainly exists — the provided text does not name one, and I will not invent one.
Why current solutions are bad
Consultants produce a point-in-time document, not a continuously maintained evidence base. Between filings the network changes — circuits get re-groomed, a diverse pair collapses onto one conduit, a vendor is swapped — and nobody knows until next year's scramble. The officer signing the attestation is signing on stale evidence. That is the wedge: continuous evidence, not annual archaeology.
Proposed product
A single-tenant SaaS that (a) ingests circuit/route inventory and topology from the provider's own systems (CSV/API import first, not deep integration), (b) applies the rule's diversity and critical-component tests continuously and raises an exception when a route stops being diverse, (c) stores dated evidence artifacts and vendor attestations against each control, and (d) generates the annual reliability certification package and the NG911 interoperability report as submission-ready output. Filing itself is submitted by the customer's officer — this is an assembler, not an agent-of-record.
MVP version
Start with the evidence layer for ONE control: circuit diversity. Import a circuit inventory, model aggregation points, flag non-diverse routes, produce a dated evidence pack and a draft certification narrative. Do not build portal auto-submission in v1 — the FCC certification system likely has no public submission API, and the officer attestation makes hands-off submission legally awkward.
30-day build
Fetch and read 2026-13998 in full. Extract: the exact filer class definitions, every compliance date, the precise content of the NG911 interoperability report, and the Paperwork Reduction Act section — the PRA respondent count and burden-hour estimate is the single hardest demand number available and it is in that document. Pull the FCC's published list of prior 911 reliability certification filers to build the actual named prospect list. Interview 8-10 compliance owners at mid-size filers. If the PRA respondent count is under ~150, kill it.
60-day build
Build the circuit-diversity evidence engine against two design-partner inventories. Ship the evidence pack and draft certification narrative. Charge design partners a discounted first-year fee — paid pilots only, no free ones; a free pilot at this buyer profile is a signal you are talking to someone who cannot sign a purchase order.
90-day revenue plan
Convert design partners to annual contracts and sell into the named filer list ahead of the first compliance date. Revenue is annual-contract, not transactional — 5 customers at $12k/yr is $60k ARR and a real business at this scale. Realistic first cash is 120-180 days, not 30.
Distribution path
Direct outbound to a finite, publicly enumerable list of prior 911 reliability certification filers — this is the best distribution asset in the idea, because the FCC effectively publishes the customer list. Secondary: NENA and APCO events, and partnering with the telecom regulatory law firms who currently bill the hours (sell them the tool, let them keep the relationship).
Pricing hypothesis
$8k-$15k/yr per covered entity for the continuous monitor plus both annual artifacts. Do NOT price per-filing: there is one filing a year, which caps revenue and misprices the value, which is the 364 days of evidence between filings. Undercutting a consultant's $20k-$40k annual engagement is the wedge.
Technical difficulty
Moderate. The hard part is not code — it is modeling 'circuit diversity' and 'critical component' precisely enough to match how the FCC and the customer's counsel read the rule. Get that wrong and you produce confidently incorrect attestations for a document an officer signs under penalty. No integration heroics needed if v1 is import-based.
Legal / regulatory risk
Real and specific. The product generates the substance of an attestation a corporate officer signs. Contract must place the attestation squarely on the customer, disclaim legal advice, and carry E&O insurance. This is not 'heavy compliance' in the sense of the founder needing a license — he does not. It is product liability shaped like a document.
Platform dependency
None meaningful. The FCC cannot deplatform a tool that prepares its own filings. Dependency is on the rule persisting, and on the customer's willingness to export their circuit inventory.
Founder fit
Strong but not maximal. The shape is exactly the founder's proven ELDT edge — a federal mandate compels a defined class to file into a federal portal, and the software layer is the business. What differs, and matters: ELDT filers were thousands of small training providers buying a $-per-upload utility with no procurement. Here the filer class is telecom carriers, the artifact is officer-attested, and the sale is an annual contract to a regulatory department. That is a slower, more consultative sale than the founder's stated preference for demonstrated-value self-serve. His fire-service background gives genuine credibility in the 911 world, but the buyer is a carrier, not a PSAP.
Breakout potential
Moderate. The same evidence engine generalizes to the FCC's other network-outage and reliability regimes (NORS/DIRS, submarine cable reporting, CPNI certifications) — same buyer, same department, same annual-attestation shape. That is the real expansion path: become the compliance-attestation system of record for a mid-size carrier's regulatory desk. It does not generalize to 50 states the way a state pass-through program would; this is one federal regulator.
Final recommendation
CONDITIONAL BUILD — gated on one day of reading. This has the founder's exact structural shape (final federal rule, named filer class, federal submission channel, per-entity monetization) and a publicly enumerable customer list, which is rare and valuable. It fails his stated preferences in two ways the input's scoring rules should not paper over: the buyer is a telecom regulatory department rather than a self-serve small filer, and no compliance deadline has been established. Do not build yet. Read 2026-13998 in full and extract three numbers: the PRA respondent count, the compliance dates, and the exact required content of the NG911 interoperability report. If respondents are >250 and the first compliance date is inside 12 months, this is a strong build. If respondents are <150 or the clock is >18 months out, kill it and spend the runway on a state pass-through program with more filers and a nearer deadline.
Next action
Fetch https://www.federalregister.gov/documents/2026/07/10/2026-13998/ in full and extract the Paperwork Reduction Act respondent count and burden estimate, every compliance/effective date, and the required content of the NG911 interoperability report. That single document resolves the two kill arguments that decide this idea.