What changed
FACT (source): On 2026-07-09 the FCC published a proposed rule enhancing Know-Your-Upstream-Provider (KYUP) requirements, strengthening STIR/SHAKEN oversight via the Governance Authority, raising caller ID attestation standards, and closing implementation gaps. HYPOTHESIS (from convergence text, not verified in source excerpt): providers are already being removed from the public RMD for deficient filings, and delisting forces downstream carriers to block all their traffic.
Why now
The proposed rule opened its comment/compliance window yesterday, so the requirement wave is just starting — a first-mover window exists before telecom compliance consultancies productize continuous monitoring for the long tail of small filers. Even before finalization, the existing RMD filing/removal regime (if removal frequency is verified) already creates urgency.
Converging signals
(1) FACT: new proposed KYUP + STIR/SHAKEN rule imposing information-collection, verification, monitoring and compliance-review duties on voice providers (Federal Register 2026-13874). (2) HYPOTHESIS: existing pattern of RMD removals with industry-wide blocking as the penalty. (3) Structural: thousands of small VoIP/CPaaS resellers listed in a public database cannot staff a compliance function. Signal list in input was empty; demand_evidence carried the load.
Customer pain
Death-penalty asymmetry: a missed certification update, deficient filing, or improper attestation can get a provider delisted, after which every downstream carrier must block its traffic — total loss of network reachability without the provider's participation. Small operators have no compliance staff and no reliable way to know their RMD posture is deficient until it is too late. LABEL: the blocking-on-delisting mechanism is asserted in the hypothesis and must be verified against FCC rules before selling on it.
Who pays
Small/micro VoIP service providers, CPaaS resellers, and wholesale voice intermediaries listed in the RMD — solo-to-20-person shops with real revenue at stake and no in-house regulatory counsel. The RMD itself is a public, exportable list of every prospective customer with legal contact info, which is unusually good lead data.
Solved today
HYPOTHESIS: telecom regulatory law firms and consultancies (CommLaw Group-style) handle filings on retainer at law-firm prices; STIR/SHAKEN vendors (TransNexus, Numeracle) sell signing/branding tech to mid-market and up; many micro providers filed once at RMD launch and have ignored it since, or assume their upstream carrier 'handles it.'
Why current solutions are bad
Law-firm retainers are overkill and overpriced for a $100-300/mo problem; STIR/SHAKEN vendors sell certificates and signing, not delisting-risk monitoring; upstream carriers have zero duty to protect a downstream reseller's RMD status — under KYUP they are incentivized to cut deficient downstreams loose, the opposite of protection. Nobody productizes continuous 'are we about to be delisted' surveillance for the long tail.
Proposed product
RMD Delisting Sentinel: (a) daily diff of the public RMD for the client's record and its upstream/downstream partners; (b) monitoring of FCC Enforcement Bureau removal orders, deficiency notices, and dockets; (c) attestation-posture checklist mapped to the evolving KYUP/attestation rules; (d) deadline calendar + prepared/updated certification filings on the client's behalf; (e) 'your upstream/downstream just got flagged' counterparty alerts — a KYUP due-diligence artifact the proposed rule effectively obliges them to have.
MVP version
Scraper/exporter of the public RMD + Federal Register/FCC release watcher + per-client record diffing and email/SMS alerts, with a manually-assisted certification-update service behind it. Ship in 2-4 weeks; the founder has already built this exact shape (federal portal + per-filing automation) for FMCSA ELDT.
30-day build
Verify the kill criteria first: pull RMD export and FCC enforcement notices, count removals/deficiency notices in trailing 18 months (target ≥50). Build the diff/alert engine. Cold-email 25-100 small RMD filers with a free 'your current RMD risk posture' report generated from public data as the demonstrated-value hook.
60-day build
Convert free-report recipients to paid monitoring ($99-299/mo). Add counterparty (KYUP) monitoring tier. File a comment in the docket to establish visible expertise; publish a public 'RMD removals tracker' page as SEO/credibility flywheel.
90-day revenue plan
10-30 subscribers at ~$150-250/mo ($1.5k-7.5k MRR) plus one-off certification-update filings at $250-500 each. Revenue timing is inside the 180-day window even though the proposed rule itself may take longer to finalize, because the existing removal regime (if verified) sells the monitoring today.
Distribution path
The customer list is public: RMD export gives name, filing status, and contact of every obligated provider. Demonstrated-value cold outreach (personalized deficiency-risk reports), the public removals tracker for inbound, and VoIP reseller communities/wholesale voice forums. No app store, no enterprise procurement, no ad spend.
Pricing hypothesis
$99-299/mo monitoring subscription per OCN/entity; $250-500 per certification filing/update; higher tier for wholesale intermediaries needing KYUP counterparty monitoring across many downstreams. HYPOTHESIS: willingness to pay is asserted, not yet evidenced — the 25-provider outreach test is the validation gate.
Technical difficulty
Low-moderate and squarely in the founder's lane: public-data scraping, diffing, alerting, document/filing automation against a government system. No carrier-grade telecom engineering, no SIP infrastructure, no STIR/SHAKEN signing required.
Legal / regulatory risk
Moderate but manageable: the service must avoid unauthorized-practice-of-law framing (position as monitoring + filing preparation/submission, like the ELDT product), and bad advice that precedes a client's delisting invites blame. Mitigate with clear ToS and 'we alert and file, you attest' positioning.
Platform dependency
Depends on continued public availability of the RMD and FCC electronic filing access — historically stable and, unlike a private platform, subject to transparency norms rather than commercial whim. The bigger dependency is regulatory: if the proposed rule dies, the product falls back to the existing (smaller) RMD-maintenance obligation.
Founder fit
Very high. This is structurally identical to his shipped FMCSA ELDT product: a federal mandate compels a class of filers to interact with a government portal; he builds the monitoring/submission layer and charges per filing/subscription. Sells through a demonstrated-value artifact (free risk report), matches his compliance-monitor/public-records preference, needs no relationship sales or VC. Applied lesson (conf 0.80): government-portal mandate shape scores highest for this founder; applied lesson (conf 0.90): the 3-6 month rule-finalization ramp is acceptable given runway.
Breakout potential
Moderate-good: wedge into the broader small-carrier FCC compliance stack (Form 499-A, CPNI certifications, robocall mitigation plan refreshes, upcoming KYUP verification duties) — a 'compliance department as a subscription' for micro telecoms, each new FCC rule churn expanding the recurring surface.
Final recommendation
PURSUE, gated on one cheap verification: this is the founder's proven pattern with a public lead list attached, near-zero build risk, and the strongest demand type (forced buyer) — but do not build past the MVP until the RMD-removal frequency check and the 25-provider outreach test confirm that delisting fear is real and monetizable. If removals are rare or replies are zero, kill it in week two having spent almost nothing.
Next action
Today: download the RMD export and FCC Enforcement Bureau removal/deficiency public notices; count removals in the trailing 18 months (kill threshold: <50 and only bad actors). This week: send 25 personalized free 'RMD risk posture' reports to small filers; ≥3 pay-intent replies green-lights the build.