What changed
FACT (source: Federal Register, 2026-06-25): the FCC adopted eligibility restrictions and a limit on the number of applications each applicant may file in the upcoming 2026 filing window for new noncommercial educational (NCE) reserved band FM translator station construction permits.
Why now
FACT: the rule is adopted and the window is described as 'upcoming' in 2026. INFERENCE: a filing window is a hard, short-duration burst — historically NCE/LPFM windows run days, not months — so every affected applicant must be ready before it opens, and the new cap changes the strategy applicants used in prior windows (file many, sort it out later).
Converging signals
Only one signal exists here, and it is the rule itself. FACT: the source document supplies the rule, the filer class (NCE applicants), and the submission (construction-permit applications). INFERENCE: the portal is FCC LMS. There is no independent complaint, hiring, or spend signal in the input — the 'convergence' is structural (rule + filer class + portal), not corroborated by a second, independent stream.
Customer pain
HYPOTHESIS (not evidenced in the source text): applicants must now prove eligibility under new restrictions and count applications across attributable/commonly-controlled parties, which is exactly the kind of thing a church network, a state university system, or a multi-entity community-radio nonprofit gets wrong. An over-cap filing risks dismissal of applications after the window closes, when nothing can be re-filed. The asymmetry (miss the cap, lose the permits, wait years for the next window) is the pain.
Who pays
NCE applicants: religious broadcast groups, community radio nonprofits, schools and universities. INFERENCE: in practice the check is usually written by the applicant's communications counsel or consulting engineer, not by the nonprofit directly — which matters, because it means the true buyer may be the intermediary this product is trying to disintermediate.
Solved today
HYPOTHESIS (I have no source in this input, and this is the weakest part of the brief): FCC broadcast counsel and consulting engineering firms prepare these filings today, typically bundling the engineering exhibit (spacing/contour study) with the legal eligibility showing. REC Networks has, in prior LPFM windows, offered low-cost or free filing assistance to exactly this constituency. None of that is in the provided source text — treat it as an unverified competitive assumption that must be checked before spending a dollar.
Why current solutions are bad
HYPOTHESIS: counsel is expensive per application and doesn't scale across a 20-application church network; nobody maintains a live cross-entity application counter during the window. The counter is the genuinely novel piece — no one sells 'a governor that tells you the 14th application you're about to file is attributable to you and will bust your cap.'
Proposed product
Three components: (1) an eligibility questionnaire scoring the applicant against the new restrictions; (2) an application-count governor that aggregates commonly-controlled/attributable applicants into a single ledger and blocks the over-cap filing before it goes out; (3) an assembler that produces LMS-ready application packages. Engineering exhibits are subcontracted to a licensed consulting engineer, not built.
MVP version
The governor alone. A hosted attribution ledger where one organization registers all its affiliated entities, logs each intended application, and gets a hard stop plus an audit trail before the cap is exceeded. No engineering, no LMS submission. This is the only piece that (a) doesn't need an RF engineer and (b) doesn't already exist.
30-day build
Do NOT build. Read the full adopted rule (not the Federal Register summary) and pull the actual per-applicant limit, the attribution standard, and the window dates. Then call ten NCE applicants and three communications-law firms and ask who filed in the last translator window, what they paid, and whether they'd pay for a cap-tracking tool. If counsel says 'we already track that in a spreadsheet and we bill for it anyway,' stop.
60-day build
Only if step one survives: build the governor as a single-tenant web app, sell it to two multi-entity applicants at cost, and use their real filings to harden the attribution logic. Line up one consulting engineer on a per-exhibit revenue share.
90-day revenue plan
Revenue arrives if and only if the window falls inside the 90 days. It is entirely gated on window dates I do not have. If the window is Q4 2026, there is no 90-day revenue path at all — there's a wait.
Distribution path
Direct outreach to state broadcaster associations, the National Religious Broadcasters, community-radio mailing lists, and — most realistically — a referral deal with the two or three law firms that dominate NCE filings. That last channel is also the reason margins compress.
Pricing hypothesis
Hypothesis: $300-600 per prepared application, or a flat $2,500 for a multi-entity governor seat covering a whole network for the window. Not recurring.
Technical difficulty
The governor is easy. The eligibility scoring is a rules engine over a rule the founder hasn't read in full yet. The engineering exhibit is genuinely hard, requires domain expertise the founder does not have, and must be bought from a licensed engineer — which means the highest-value part of the deliverable is not his.
Legal / regulatory risk
Preparing FCC applications for compensation edges toward practicing before the Commission. FCC practice rules permit non-attorney practitioners in many contexts, but eligibility showings are legal determinations, and a wrong eligibility call that gets an application dismissed is a real liability. Unverified; must be checked with counsel before selling.
Platform dependency
None in the deplatforming sense — FCC LMS is a government system with no owner who can revoke access. But there is total *timing* dependency on a window the founder does not control.
Founder fit
The shape matches his proven ELDT play: a federal mandate, a defined filer class, a government portal, a per-filing fee. That is why this surfaced. The mismatch is that ELDT filings are a continuous, recurring stream driven by an ongoing training market, while an FCC window is a one-shot burst — the same shape with the annuity removed.
Breakout potential
Low as scoped. The generalization ('window-filing assembler for any FCC auction/window') is a real product, but it puts him in direct competition with established broadcast-services firms in a market with a few hundred customers.
Final recommendation
KILL as a standalone business — and the reason is not that it needs upfront spend, which the founder can fund. It is that the revenue is a single non-recurring burst against a few-hundred-customer market whose incumbent gatekeepers are the natural distribution channel, and the highest-value component must be subcontracted. The forced-buyer mandate is real and the founder-fit shape is genuine, which is exactly what makes this a trap: it pattern-matches to the ELDT win while missing the property (a continuous filing stream) that made ELDT work. Two things worth salvaging. First, the 'attributable-party application-count governor' is a genuinely novel primitive that recurs across every capped FCC window, every capped grant program, and several state award programs — that abstraction, not this window, may be the product. Second, and more important for the system than for the founder: this brief rests on one Federal Register summary and I could not verify the per-applicant limit, the window dates, the filer count, or what anyone currently pays. Everything above marked HYPOTHESIS is genuinely unverified. FedMoney should not promote single-source, single-window items to brief status without a second retrieval pass against the adopted rule text.
Next action
Do not build. Spend two hours pulling the adopted Report & Order behind this Federal Register entry to extract the actual application limit, the attribution standard, and the window dates. If the window is already open or opens within 60 days, drop it outright. If it is 6+ months out, run the ten-applicant validation call list before writing any code — and specifically ask whether counsel already tracks the cap.