What changed
FACT (Federal Register, 2026-07-06): A new rule grants state, local, tribal, and territorial (SLTT) law-enforcement and correctional agencies authority to conduct drone detection and mitigation, but only under a defined certification framework. FACT (Hackster): ~$100 open-source hardware (QuadRF) can visualize RF/Wi-Fi signals. FACT (GitHub): OfficeCLI enables headless Office-document automation. HYPOTHESIS: that these three combine into a viable turnkey detect-and-comply kit — the detection half of that claim is weakly supported.
Why now
FACT: the rule is effective now (July 2026), so every agency that wants counter-UAS capability must enter the certification framework from day one. HYPOTHESIS: first grant applications and budget requests are happening immediately — plausible but not evidenced in the sources.
Converging signals
(1) Regulation opens a previously federal-only activity to thousands of small agencies with certification/reporting obligations attached; (2) commodity RF sensing collapses hardware cost; (3) headless document automation collapses paperwork cost. Signal 1 is the load-bearing one; signals 2-3 are enablers of very different strength — QuadRF is a Wi-Fi visualization toy, not a drone-detection sensor (HYPOTHESIS that it generalizes; many drones use proprietary protocols, frequency hopping, or 5.8GHz links a Wi-Fi-class device won't reliably classify).
Customer pain
HYPOTHESIS (structurally strong, not yet observed): a 15-deputy sheriff's office or county jail that wants to detect contraband-drops by drone now faces a federal certification process, mandated incident logging, and reporting obligations with zero compliance staff and no budget for Dedrone-class systems. No forum/complaint evidence of this pain exists yet because the rule is days old.
Who pays
HYPOTHESIS: county jails and small municipal PDs, largely via state/federal grant money. Caveat: grant-funded government buyers are real money but slow money — POs, procurement rules, and fiscal-year cycles conflict directly with a 30-90-day revenue requirement.
Solved today
FACT-adjacent: incumbent counter-UAS vendors (Dedrone/Axon, DroneShield, AeroDefense) sell integrated detection systems priced for airports, stadiums, and large prisons. The new certification paperwork layer is solved by nobody yet — agencies would use Word templates and manual submission. Small agencies' current 'solution' is doing nothing, which until this rule was also the legal default.
Why current solutions are bad
Defense-contractor systems cost 5-6 figures plus install; they don't target 2,800-inmate county jails, let alone 80-bed ones. And none of the incumbents are oriented around the NEW obligation — certification tracking and mandated incident/federal reporting — because it didn't exist until this month.
Proposed product
NOT the convergence's turnkey sensor bundle. Instead: a pure-software 'counter-UAS compliance desk' — tracks an agency's certification status and renewals, generates the required incident logs from a guided form, assembles the federal reporting package automatically (OfficeCLI-style doc generation), and submits/exports it in the required format. Hardware-agnostic: integrates later with whatever detection gear the agency buys. This is the ELDT shape: regulation compels a party to file into a government framework; charge per agency seat or per filing.
MVP version
1-2 weeks of build AFTER reading the rule: (a) parse the actual certification and reporting requirements from the Federal Register text; (b) a form-driven incident-report generator that outputs the compliant document package; (c) a certification-deadline tracker with email alerts. No sensors, no RF, no CJIS-sensitive data storage in v1 (keep incident narratives out of scope or client-side to dodge CJIS initially — HYPOTHESIS that this is achievable, must verify).
30-day build
Read the full rule and any implementing guidance; extract the exact filing artifacts, cadence, and destination (is there a portal? a PDF form? an email submission?). Build the report/package generator. Publish a free 'SLTT Counter-UAS Certification Checklist' as the lead magnet targeting sheriff and jail-administrator associations.
60-day build
Pilot with 2-3 agencies found via the checklist, state sheriffs' association newsletters, and corrections forums; iterate the document package against a real submission. Validate that agencies (not just the founder) perceive the paperwork as painful.
90-day revenue plan
HYPOTHESIS, low-confidence: 3-10 agencies at $99-299/mo or $49-99 per incident package. Realistic risk: even interested agencies may take 90+ days to issue a PO; first revenue may be pilot fees or credit-card-sized subscriptions that fit under procurement thresholds (~$5k) — pricing under the micro-purchase threshold is the key distribution hack.
Distribution path
Content + association channels: state sheriffs' associations, American Jail Association, corrections-tech newsletters, and SEO on 'counter-UAS certification requirements'. No enterprise sales team, but every sale is still a government buyer — expect demos and references. This is the weakest link for a 30-90-day clock.
Pricing hypothesis
Keep every price under agency micro-purchase/credit-card thresholds: $99-249/mo per agency or per-filing fees, annual prepay option sized for grant line items.
Technical difficulty
Low for the compliance SaaS (forms + doc generation + reminders — squarely within founder's proven stack). High-to-unbounded for the proposed hardware kit: RF drone classification, false-positive liability, enclosure/field-hardening, and FCC questions — which is why the kit variant should die.
Legal / regulatory risk
Moderate. Passive RF detection has Wiretap Act/interception gray zones (a reason to stay out of detection entirely); law-enforcement incident data may trigger CJIS security requirements; giving compliance-adjacent advice to LE agencies invites 'is this legal guidance?' questions. All manageable if the product is document assembly + tracking, not detection and not legal advice. UNVERIFIED: whether the rule's reporting goes to a federal portal a third party may submit into (the ELDT analogy) — must be confirmed before betting on per-filing monetization.
Platform dependency
Low. Depends on the federal framework's stability (new rules get amended) and on whatever submission channel exists. No app-store or API-platform risk.
Founder fit
Split verdict. The regulation-compels-filing shape is VERY HIGH fit — identical skeleton to his shipped FMCSA ELDT product (read mandate → find forced filers → build submission layer → charge per filing), plus fire-service/public-safety credibility helps with LE buyers. But the buyer is government (slow, trust-driven, reference-checked), unlike ELDT's private training providers, and the convergence-as-stated adds hardware, which he avoids. Fit is high only for the software-only slice.
Breakout potential
Moderate. If certification/reporting proves recurring and painful, expand to detection-vendor integrations, grant-application templates, multi-state compliance, and adjacent public-safety drone paperwork (agency drone-program COAs, Part 107 fleet compliance). Could become the 'compliance layer' incumbents OEM.
Final recommendation
KILL the turnkey detection-kit version outright (hardware + LE credibility + liability = not solo-buildable). CONDITIONAL GO on the narrow compliance-paperwork SaaS, gated on one cheap research step: read the actual rule text and confirm (a) a concrete recurring reporting/filing obligation exists, (b) its destination and format, and (c) that a third-party tool can prepare or submit it. If the rule creates an ELDT-like filing loop, this is a strong founder-fit play worth a 2-week MVP despite the slow-government-buyer risk; if reporting is trivial or annual-only, revisit later.
Next action
Fetch and read the full Federal Register rule (2026-13609) today; extract every certification, logging, and reporting requirement verbatim, identify the submission mechanism, and list the agency roles forced to file — decision to build hinges entirely on this.