What changed
FACT (Federal Register, 2026-07-09): The FCC published an NPRM in WC Docket 17-97 proposing enhanced Know-Your-Upstream-Provider requirements, tighter STIR/SHAKEN Governance Authority oversight, higher attestation standards, and closure of implementation gaps. If adopted, every US voice service provider faces recurring upstream-vetting, information-collection, monitoring, and attestation-review duties.
Why now
FACT: the NPRM published yesterday, opening a comment window that makes provider anxiety and burden arguments publicly visible in ECFS. INFERENCE: a synchronized post-adoption effective date compresses thousands of small providers into one demand spike, and the penalty for noncompliance (RMD delisting → downstream carriers must block your traffic) is existential, not a fine. Building now means owning the category before the compliance deadline lands.
Converging signals
FORCED BUYER: FCC KYUP NPRM (Federal Register 2026-13874). STRUCTURAL: the public Robocall Mitigation Database already enumerates the entire obligated class — a free, downloadable lead list. PATTERN: this matches the Compelled Compliance Dossier shape the founder has already monetised once (FMCSA ELDT per-upload filing app). Note: no PAIN or HIRING/SPEND evidence was retrieved — the two demand items are the same NPRM from two feeds, so demand beyond the mandate itself is currently a hypothesis.
Customer pain
HYPOTHESIS (testable): small VoIP resellers and long-tail voice providers have zero compliance staff and no process for vetting upstream providers, collecting certifications, tracking RMD statuses, or documenting attestation evidence. When KYUP duties become recurring and auditable, they must either build a workflow, hire a consultant/lawyer at telecom-bar rates, or risk delisting. No complaint-level evidence yet — the testable prediction (burden-themed ECFS comments within a week; ≥3 of 30 cold-emailed providers admitting no workflow) is the validation gate.
Who pays
Small and mid-size voice service providers listed in the FCC Robocall Mitigation Database — resellers, CLECs, UCaaS/CPaaS resellers, wholesale VoIP shops. Thousands of entities, individually reachable by cold email (contact info is in their RMD filings), each with an FCC registration to protect and no compliance department.
Solved today
INFERENCE from public FCC practice: the carrier tier uses TransNexus, Numeracle, and telecom counsel (e.g., CommLaw Group) for robocall mitigation plans and STIR/SHAKEN. The long tail mostly filed a one-time boilerplate mitigation plan into the RMD and does nothing recurring. Some rely informally on their wholesale carrier — a key falsification risk to check in discovery calls.
Why current solutions are bad
Incumbent tooling is priced and sold for carriers, not 5-person resellers. Lawyers are per-hour and don't run recurring monitoring. Boilerplate mitigation plans won't survive a KYUP regime that demands current, documented upstream evidence. Nothing today produces an always-inspection-ready dossier at a long-tail price point.
Proposed product
KYUP Dossier-as-a-Service: per-provider subscription in which an agentic pipeline (a) ingests the customer's upstream provider list, (b) pulls each upstream's RMD status, certification/mitigation-plan documents, and attestation-level evidence, (c) monitors for delistings, enforcement orders, and status changes with alerts, and (d) maintains a versioned, timestamped KYUP evidence file formatted for FCC or downstream-carrier inspection. Add a free public 'RMD status check' tool as the lead magnet.
MVP version
Scraper/poller for the RMD (public, downloadable) + FCC enforcement releases; a per-customer dossier generator (PDF/portal) covering their declared upstreams; email alerts on upstream status changes; Stripe subscription billing. No FCC portal write-access needed — this is evidence assembly and monitoring, technically simpler than the ELDT app. 4-6 weeks solo with AI-assisted build.
30-day build
Validation first: scrape WC Docket 17-97 ECFS comments for small-provider burden filings; cold-email 30 RMD-listed small providers; run 5-10 discovery calls. In parallel, build the RMD monitor + free status-check tool to start harvesting inbound leads. Kill/continue decision at day 30 against the stated falsification criteria.
60-day build
Ship the paid dossier product to 3-5 design partners at a founding price ($99-$199/mo). Publish a 'KYUP readiness' explainer targeting the NPRM — small providers searching for what the rule means find you. Build the upstream-change alerting and inspection-ready export.
90-day revenue plan
Convert design partners to paid, scale cold outbound across the RMD list (thousands of enumerated, contactable prospects), and sell 'be ready before adoption' positioning. Target 15-30 subscribers at ~$150/mo (~$2-5k MRR) by day 90-120, with the real spike arriving at rule adoption.
Distribution path
The RMD is a public, downloadable lead list with contact details — near-zero-cost, perfectly targeted outbound. Plus: docket-watching content SEO, the free RMD status-check tool, and partnerships with wholesale carriers who want their resellers compliant. No app store, no ad spend, no channel gatekeeper.
Pricing hypothesis
$99-$299/mo per provider depending on number of upstreams monitored; one-time $499 'KYUP readiness assessment' as a cash-flow wedge during the pre-adoption window. At 100 customers this is a ~$180k ARR business with near-zero marginal cost.
Technical difficulty
Low-to-moderate for this founder: public-data scraping, document assembly, monitoring/alerting, subscription billing — all previously demonstrated. No government portal write-integration required (easier than ELDT). Hardest part is normalizing messy RMD filings and mapping upstream relationships customers self-report.
Legal / regulatory risk
Low. The product assembles public records and customer-supplied documents; it does not practice law. Position as 'evidence file and monitoring,' not legal advice; add a disclaimer and optionally a referral relationship with a telecom attorney. Main risk is regulatory timing, not liability.
Platform dependency
Depends on continued public access to the RMD and ECFS — both long-standing public FCC systems with download interfaces. FACT-adjacent but worth noting: if the FCC restructured RMD access, scraping would need rework. No commercial platform approval needed.
Founder fit
VERY HIGH. This is structurally identical to the founder's proven FMCSA ELDT play: read a federal mandate, enumerate the compelled class from a government registry, build the compliance/evidence layer, charge recurring fees. Accumulated lesson (confidence 0.80) independently flags government-portal mandate opportunities as this founder's best fit. Solo-buildable, outbound-sold via demonstrated value, no VC, no enterprise procurement.
Breakout potential
If KYUP adopts as proposed, this becomes the compliance system of record for the long-tail voice market, expandable into adjacent recurring FCC duties (RMD filing updates, 499 filings support, STIR/SHAKEN attestation tracking) — a telecom-compliance micro-suite. Downstream, wholesale carriers could white-label it for their reseller base.
Final recommendation
PURSUE-WITH-GATE. Spend ≤2 weeks and near-zero dollars on the validation gate (ECFS comment scan + 30 cold emails + RMD monitor MVP). The founder-fit and forced-buyer structure are top-decile; the only real risks are rule timing and carrier bundling, both cheaply testable right now while the comment window makes the market self-identify.
Next action
Today: pull WC Docket 17-97 filings from ECFS and flag small-provider burden comments; download the RMD, segment providers with no parent carrier and small filing footprints; send the first 30 cold emails asking one question — 'who handles your upstream-provider vetting today?'