What changed
FACT (Federal Register, 2026-07-06): a new rule creates a certification framework under which state, local, tribal, and territorial (SLTT) law-enforcement and correctional agencies can legally conduct counter-UAS detection and mitigation — an activity previously limited to federal agencies. FACT (Hackster sources): RF sensing/visualization hardware has reached ~$100 open-source commodity class (QuadRF) and dual-band GNSS now runs at half power (u-blox F11). HYPOTHESIS: these combine into a viable low-cost detection-plus-compliance stack for small agencies.
Why now
The rule published four days ago; any agency wanting the authority must certify before operating, so the compliance workflow is the first bottleneck — before defense-contractor incumbents retool federal-grade offerings for down-market buyers. COUNTERPOINT (inference): the certification machinery (forms, portal, reviewing office) may not even be stood up yet, meaning there is nothing to automate against for weeks or months.
Converging signals
(1) Regulation: SLTT counter-UAS authority with certification/reporting obligations (federalregister.gov, 2026-07-06). (2) Industrial: ~$100 open-source RF visualization hardware (QuadRF, hackster.io). (3) Industrial: half-power dual-band GNSS enabling small always-on sensors (u-blox F11, hackster.io). Signals 2 and 3 are enablers, not demand.
Customer pain
HYPOTHESIS ONLY — demand_evidence is EMPTY. No complaints, no job postings, no RFPs were provided showing any agency struggling with or paying for this yet. The plausible pain (small agencies lack counsel/admin staff to navigate a federal certification process) is inferred from the rule's existence, not observed.
Who pays
HYPOTHESIS: SLTT police and correctional agencies (often grant-funded procurement), possibly regional trainers/resellers. CRITICAL CAVEAT: this authority is OPT-IN — the rule permits agencies to run counter-UAS programs, it does not compel them to. That inverts the founder's proven ELDT pattern, where filers were forced to file to stay in business. Here nobody must buy anything.
Solved today
FACT (inference from rule recency): it isn't solved yet — the market is 4 days old. Adjacent incumbents (Dedrone, DroneShield, Axon ecosystem) sell integrated federal/enterprise counter-UAS suites at prices far above small-agency budgets.
Why current solutions are bad
Incumbent suites are five-to-six-figure hardware-led contracts sized for airports and federal sites, not a 12-officer department; and none are yet packaged around this specific rule's certification/reporting paperwork. HYPOTHESIS: that gap closes fast — Axon already owns small-agency distribution and could bundle compliance workflow into its existing platform.
Proposed product
Micro-SaaS 'certification-in-a-box': guided intake that produces the rule's required certification application, program authorization documents, policy templates, training-record tracking, and one-click incident/deployment reports; optionally ingests logs from commodity RF detection kits (QuadRF-class) to auto-populate incident filings. Per-agency annual seat fee plus per-filing pricing, mirroring the founder's ELDT per-upload model.
MVP version
A document-generation web app: agency answers a structured questionnaire → outputs the certification package + policy manual + reporting templates mapped clause-by-clause to the rule. No hardware, no integrations. Buildable solo in 2-3 weeks with AI-assisted drafting. Hardware log ingestion deferred.
30-day build
Read the full rule and its actual certification mechanics; verify which office receives certifications and in what format (this is the go/no-go fact). Build the MVP generator. Post in police/sheriff UAS forums, IACP/NSA drone working groups, and r/ProtectAndServe-adjacent professional channels to find 5 early-adopter agencies already planning programs.
60-day build
Convert forum interest into 3-5 pilot agencies at founder pricing ($99-$199 to generate their certification package). Capture their questions to harden the templates. Publish a free 'Can your agency legally counter drones now? — 10-minute readiness check' lead magnet.
90-day revenue plan
HYPOTHESIS: $1-5k from 10-30 certification-package sales at $99-$299 if — and only if — the certification process is live and early-adopter agencies exist. Recurring incident-reporting subscriptions realistically land beyond 90 days because agencies must first get certified, procure detection gear, and deploy. Government purchase-card thresholds (~$2.5-10k) keep single purchases below formal procurement, which helps, but 30-90-day gov revenue remains unproven.
Distribution path
Weakest link. No self-serve channel like ELDT's private training providers; buyers are chiefs/sheriffs reached via associations, state police-chief listservs, UAS training vendors, and grant-writing consultants. Founder's fire-service background gives some public-safety credibility but this is closer to relationship sales than his demonstrated-value model.
Pricing hypothesis
$99-$299 one-time per certification package; $49-$99/mo per agency for authorization maintenance + incident reporting; potential per-filing fee if the rule requires recurring federal reports (unverified — must confirm in rule text).
Technical difficulty
Low for the paperwork MVP (forms → documents). Medium if ingesting RF detection logs. The $100-hardware angle is a distraction for the MVP: HYPOTHESIS — hobbyist-grade RF gear (QuadRF is a Wi-Fi visualization tool, not a drone detector) likely fails evidentiary/reliability expectations for law enforcement; do not build the hardware kit.
Legal / regulatory risk
Moderate. The product must not constitute legal advice; templates for law-enforcement counter-UAS programs touch FCC/FAA/DOJ equities, and errors could expose agencies. Mitigation (jamming/takedown) is high-liability — stay strictly on the detection/paperwork side. Selling compliance tooling to police also invites scrutiny if documents are wrong.
Platform dependency
Low-moderate: dependent on one 4-day-old federal rule surviving legal challenge and on whatever portal/process the implementing agency stands up. A stayed or litigated rule kills the market overnight.
Founder fit
Mixed, honestly scored. The SHAPE matches his proven ELDT edge exactly (read a federal rule → build the filing/reporting layer → charge per transaction), plus fire-service credibility with public-safety buyers. But two load-bearing differences: (a) ELDT filers were COMPELLED private businesses; these are OPT-IN government agencies, (b) government buyers, even small ones, are slower and more relationship-driven than his no-enterprise-sales preference tolerates. Fit is high on skills, medium on buyer type.
Breakout potential
If early wedge works: expand to critical-infrastructure owners and event venues when/if authority extends further, add training-records module, become the small-agency counter-UAS system of record. HYPOTHESIS only.
Final recommendation
WATCH, don't build yet. The opportunity is real in shape and matches the founder's proven regulatory-filing edge, but with zero demand evidence, an opt-in (not forced) buyer, government sales friction, and a certification process that may not exist operationally, first revenue inside 90 days is improbable. Re-score immediately upon any of: the certification portal/process going live, agency job postings or RFPs mentioning the rule, or forum threads from agencies asking how to certify.
Next action
Spend one day, not thirty: pull the full rule text from federalregister.gov, extract the exact certification/reporting requirements and the receiving office, and set up monitoring (Google Alerts, SAM.gov, police UAS forums) for 'counter-UAS certification' demand signals. Build nothing until at least one real agency is observed asking for help.