What changed
FACT (per Federal Register source): a rule effective July 2026 grants state/local/tribal/territorial (SLTT) law enforcement and correctional agencies authority to conduct drone detection and mitigation under a defined certification framework. FACT (per Hackster source): open-source ~$100 commodity RF hardware (QuadRF-class) now does real-time RF visualization that previously required professional spectrum gear. HYPOTHESIS: the certification framework imposes training records, authorization filings, incident logging, and reporting duties that small agencies lack software for — the rule text confirms a certification pathway exists, but the exact paperwork burden must be verified in the rule itself before building.
Why now
The rule just took effect (July 6, 2026). Agencies that want this authority must enter the certification pathway now, creating a dated, regulation-forced adoption window with no incumbent serving the sub-$10k/yr tier. First-mover on the paperwork layer matters more than the sensor layer, which is commoditizing.
Converging signals
(1) Federal rule opening counter-UAS to thousands of SLTT agencies under a certification framework [federalregister.gov, 2026-07-06]. (2) ~$100 open-source RF sensing collapsing detection-layer cost [hackster.io]. Together: many small buyers simultaneously enabled and burdened, while the hardware excuse for defense-contractor pricing disappears.
Customer pain
HYPOTHESIS (structurally likely, mirrors every federal certification regime): a 12-deputy sheriff's office wanting counter-UAS authority must track officer certifications, maintain authorization documentation, log every detection/mitigation event, and produce reports for federal oversight — with no records clerk, no software budget line, and personal liability for the sheriff if the program is non-compliant. Pain is real only if the final rule mandates specific record-keeping/reporting; verify first.
Who pays
County sheriffs, small municipal PDs, and jails/correctional facilities — often via DHS/state homeland-security grant money earmarked for this new authority (HYPOTHESIS on grant availability). Faster secondary buyer: counter-UAS training vendors who need to issue/track/submit officer certifications — the exact buyer shape as his ELDT training-provider customers.
Solved today
Nothing purpose-built at this price point exists yet (rule is days old). Agencies will default to spreadsheets, PDFs, and email, or to high-end C-UAS vendors (Dedrone/Axon, DroneShield) whose contracts start far above small-agency budgets and focus on sensors, not certification paperwork.
Why current solutions are bad
Spreadsheets fail federal audits and expose the agency's new authority to revocation; defense-tier vendors are 10-100x over budget and won't chase $3-8k/yr accounts. The compliance/reporting layer is precisely the part commodity hardware does not solve.
Proposed product
Software-only, hardware-agnostic 'counter-UAS program in a box': officer certification tracker with expiry alerts, authorization document vault, detection-event log (manual entry + optional API ingest from any RF sensor including QuadRF-class devices), and one-click audit/oversight report generation. Explicitly does NOT control mitigation hardware and does not sell hardware — stays on the records side where legal risk is low.
MVP version
4-6 week build with AI-assisted prototyping: FastAPI/Postgres multi-tenant app (stack he already runs), certification CRUD with expiration alerts, incident log form + CSV/API ingest, PDF report templates matching whatever format the rule/oversight body requires, per-agency login. No sensor integration needed for v1 — the paperwork is the product.
30-day build
Days 1-3: read the full rule text and any DHS/FAA implementation guidance; extract the literal list of required records, filings, and reports (kill the idea if the framework is still unimplemented with no operational certification body). Weeks 1-2: interviews with 5-10 small-agency contacts (fire-service background gives public-safety credibility) and 2-3 counter-UAS training vendors. Weeks 2-4: build MVP against the actual required forms; publish a free 'SLTT Counter-UAS Certification Checklist' as lead-gen.
60-day build
Pilot with 2-3 agencies or 1 training vendor at founder pricing ($99-299/mo or per-officer-certified fee). Iterate report formats against a real audit/oversight requirement. Start content distribution: sheriff association newsletters, police-one style outlets, LinkedIn public-safety groups, and the training vendors' own channels.
90-day revenue plan
Realistic: $1-5k MRR from 5-15 small agencies/training vendors if (and only if) the certification pathway is operational and paperwork burden is concrete. Grant-funded purchases may lag 3-6 months beyond that — treat 90-day revenue as coming from training vendors (fast, private-sector buyers) rather than agencies themselves, mirroring the ELDT model where the training provider pays per filing.
Distribution path
No-enterprise path: (1) counter-UAS training vendors as channel partners who bundle the tracker per certified officer; (2) the free checklist/guide capturing agencies searching for the new rule's requirements; (3) state sheriff association newsletters and conference vendor tables (cheap for this niche); (4) SEO on the rule's exact name — it is brand new and uncontested.
Pricing hypothesis
$99-$299/mo per agency depending on officer count, or per-certification/per-filing fee ($10-25) sold through training vendors — the proven ELDT monetization. Under most agencies' purchasing-card threshold, avoiding formal procurement (HYPOTHESIS: thresholds vary by state, typically $5-10k).
Technical difficulty
Low-moderate. CRUD + alerts + PDF generation + multi-tenancy is squarely within his shipped-production-app capability. Optional sensor-ingest API is a later add. Hardest part is non-technical: tracking the evolving federal guidance.
Legal / regulatory risk
Moderate but manageable if scoped correctly. Detection logging and records software carries low direct risk; NEVER touch mitigation control (jamming/takeover is heavily regulated federal territory). Incident logs may be CJIS-sensitive — hosting/security posture must be credible (HYPOTHESIS: CJIS applicability depends on data content). Selling receive-only sensing info is fine; do not bundle or resell hardware.
Platform dependency
Low. No app store, no third-party platform. Dependency is on the federal rule itself: if implementation stalls or DHS ships a free federal portal that does everything, the product dies. That is the real dependency to monitor.
Founder fit
VERY HIGH — this is a near-exact structural repeat of his proven FMCSA ELDT play: a federal rule compels a party to certify/file/report, small operators lack tooling, he builds the compliance/submission layer and charges per transaction or per seat. Adds his public-safety credibility (fire-service background) for trust with sheriffs, and his systems/automation strengths for the reporting engine. The one mismatch: LE/government buyers are slower than trucking schools.
Breakout potential
Good within the niche: land certification tracking → expand to detection-event ingest from commodity sensors → become the system-of-record for small-agency counter-UAS programs → adjacent public-safety compliance modules (drone-as-first-responder program paperwork, FAA COA tracking). Defense vendors won't chase the low end; Axon might eventually, which is both acquisition path and threat.
Final recommendation
CONDITIONAL GO — this is the best founder-fit pattern in his portfolio (regulation-forced filing + solo-built submission layer + per-transaction pricing), but it currently rests on an unverified assumption about the certification framework's actual paperwork burden and operational status. Spend 2-3 days reading the final rule and calling 3 counter-UAS training vendors before writing any code. If the framework is live with concrete record-keeping/filing duties, build immediately and sell first to training vendors (fast private buyers), agencies second. If the framework is vague or unimplemented, tag revisit-later and set a monitor on DHS/FAA implementation guidance.
Next action
Today: pull the full rule text from federalregister.gov (2026-13609), extract every mandatory record/report/filing verbatim into a checklist, and identify whether a certification body/portal is operational; simultaneously find 3 counter-UAS training vendors and ask what they use to track officer certifications.