What changed
FACT: A federal rule published July 6, 2026 (federalregister.gov 2026-13609) extends counter-UAS detection and mitigation authority to state, local, tribal, and territorial law-enforcement and correctional agencies under a defined certification framework — activity that was previously restricted to federal agencies. FACT: Open-source projects now demonstrate RF visualization on ~$100 commodity hardware (QuadRF) and laptop-based non-cellular 5G/RF prototyping (DECT NR+), per the two Hackster sources. HYPOTHESIS: these cheap RF tools are usable for agency familiarization/training, though neither source mentions counter-UAS or law enforcement.
Why now
The rule is four days old. Agencies are at the absolute start of the certification pipeline and no low-end incumbent exists because the market was legally impossible before July 6, 2026 (FACT from rule signal). Counter-argument (HYPOTHESIS): being first into a market with no buyers yet also means months of waiting while implementing guidance, certification procedures, and grant funding materialize.
Converging signals
(1) Regulatory unlock gated on certification for thousands of SLTT agencies (federalregister.gov, FACT). (2) ~$100 commodity RF sensing/visualization hardware (QuadRF, hackster.io, FACT). (3) USB-form-factor non-cellular 5G/RF prototyping (hackster.io, FACT). Honest assessment: the regulatory signal carries nearly all the weight; the two hardware signals prove RF tooling is cheap but do not prove it satisfies any certification requirement — that mapping is pure inference.
Customer pain
HYPOTHESIS ONLY — the provided demand_evidence array is EMPTY. No complaints, no job postings, no procurement activity was supplied showing agencies struggling with this certification. Inferred pain: correctional facilities face contraband drone deliveries and small agencies lack budget for defense-grade vendors, so they will need cheap training and auditable reporting to use the new authority. Plausible, but currently unsupported by any evidence in this input.
Who pays
HYPOTHESIS: SLTT police departments and correctional facilities (often via federal/state grants), plus law-enforcement training providers who could license curriculum. Note the buyer is a government entity: even a five-figure purchase typically requires quotes, approvals, sometimes board sign-off — this is not a swipe-a-credit-card buyer.
Solved today
FACT (by omission): it isn't — the activity was illegal for these agencies until July 6, 2026. The nearest analogues are federal-tier counter-UAS vendors (Dedrone/Axon, DroneShield) and free training bodies like DRONERESPONDERS. HYPOTHESIS: incumbents will initially chase large agencies and federal contracts, leaving the long tail unserved for a window.
Why current solutions are bad
HYPOTHESIS: defense-grade detection systems cost six to seven figures, and their compliance tooling assumes dedicated staff. A 15-officer department or a county jail cannot buy them. But 'nothing exists yet' cuts both ways — the certification framework's actual requirements (curriculum, approved equipment lists, reporting formats) are likely not yet published in implementable detail, so any product built today risks guessing wrong.
Proposed product
Three-layer offer, lightest first: (1) certification-prep study guides/courses mapped to the rule's framework, sold to individual officers and training coordinators; (2) a compliance/incident-reporting micro-SaaS that generates the auditable records the framework requires, priced per agency per month; (3) optional low-cost RF familiarization kit guides built on commodity hardware like QuadRF. Layer 1 can ship before layer 2; layer 3 is a content upsell, not a hardware business.
MVP version
Parse the full rule text, extract every certification, training, recordkeeping, and reporting obligation into a plain-English 'What your agency must do' guide plus checklist templates. Publish as a $99-$299 digital product with a free summary as lead generation. This mirrors the founder's proven read-the-mandate-first ELDT playbook and requires zero partnerships. 1-2 weeks with AI-assisted drafting.
30-day build
Read the rule end-to-end; build the obligations matrix; publish the free summary + paid guide; stand up a landing page targeting 'counter-UAS certification [state] police' search terms; post in police/corrections professional forums and LinkedIn groups; collect emails. Success metric: 200+ email signups or 10 guide sales — this is the demand test the current evidence lacks.
60-day build
If (and only if) 30-day signals show buyers: build the incident-reporting SaaS v1 — log detection events, generate the federally required reports, export audit packets. Offer founding-agency pricing to 3-5 pilot agencies. If signals are absent, stop and keep the guide as passive income.
90-day revenue plan
HYPOTHESIS: $2-8k from guide sales plus 2-3 pilot agencies at $100-300/mo is the realistic ceiling. Honest caveat: government purchasing plus a certification pipeline that itself may take months makes meaningful 90-day revenue UNLIKELY — this scores poorly against the founder's 30-90 day cash requirement.
Distribution path
Weakest link. No marketplace, no app store, no existing channel. Realistic paths: SEO on brand-new search terms (low competition, FACT that the market is new), corrections/police association newsletters, and direct outreach to sheriff/corrections training coordinators. All are slow-burn. The ELDT model had trucking schools actively searching for a filing solution; here the searchers don't exist yet.
Pricing hypothesis
Guide: $99-299 one-time. Reporting SaaS: $99-299/agency/month (small enough to fit purchase-card limits, avoiding formal procurement — this threshold is the whole distribution strategy). Curriculum licensing to established police trainers: $1-5k/yr (HYPOTHESIS, untested).
Technical difficulty
Low for the guide and checklist product. Low-to-moderate for the reporting SaaS (CRUD + PDF generation + audit trail — well within solo AI-assisted capability). The founder should NOT build detection hardware or mitigation tooling; that is a defense-contractor game with FCC/FAA/liability exposure.
Legal / regulatory risk
Material and above the founder's usual bar. Advising law enforcement on a federal certification framework invites accuracy liability; anything touching actual mitigation (jamming/takeover) is heavily regulated. Mitigation: sell study aids and recordkeeping software explicitly disclaimed as not legal advice and not detection/mitigation equipment. CJIS data-handling questions may arise for the SaaS if incident records include investigative data (HYPOTHESIS — depends on framework details not in the source).
Platform dependency
Low. No app-store or platform gatekeeper. The real dependency is regulatory: the certifying federal agency could publish its own free training and reporting portal, instantly deleting layers 1 and 2 (this is exactly what FMCSA did NOT do for ELDT uploads — but there is no evidence either way here).
Founder fit
Mixed, and weaker than the surface pattern-match suggests. Matches: read-a-federal-rule-and-productize is his proven ELDT edge; industrial/ops credibility and fire-service background give him public-safety-adjacent legitimacy; the reporting SaaS is per-filing-shaped. Mismatches (important): the ELDT rule FORCED private training providers to file to stay in business — this rule merely PERMITS agencies to opt in, so there is no forced buyer despite the counter-UAS framing; the buyer is government, which drifts toward the relationship/trust sales he avoids; and 30-90 day cash is improbable. This is NOT the very-high-fit forced-filer shape — it is adjacent to it.
Breakout potential
If the certification framework generates mandatory recurring reporting for every operating agency, the SaaS becomes a durable per-agency subscription across thousands of agencies, with curriculum licensing as a second line. That is a real multi-year business — but 'multi-year' is the operative word.
Final recommendation
CONDITIONAL PASS — do not build the SaaS now. Spend at most 2 weeks on the read-the-rule obligations guide as a cheap demand probe (it monetizes his proven skill and costs almost nothing), set a Google Alert / Federal Register watch for the implementing certification guidance, and revisit hard if either (a) the framework mandates recurring reporting or (b) real demand signals (searches, forum questions, job postings, RFPs) appear. Do not count on this for 30-90 day cash; run a faster opportunity in parallel.
Next action
Download and fully read the July 6, 2026 Federal Register rule (2026-13609); extract every certification, training, and reporting obligation into a checklist; publish a free one-page summary with email capture within 14 days to measure whether anyone in the SLTT world is actually searching for help.