What changed
FACT (per federalregister.gov signal, published 2026-07-06): a federal rule now extends counter-UAS detection/mitigation authority to state, local, tribal, and territorial law-enforcement and correctional agencies, conditioned on a defined certification framework. FACT (per hackster.io signal): open-source RF visualization on ~$100 commodity hardware (QuadRF) exists, lowering the detection-hardware floor. HYPOTHESIS: the pairing means the binding constraint for small agencies is certification and reporting scaffolding, not hardware budget.
Why now
The rule is 4 days old and certification is a precondition to operating, so demand is front-loaded and dated: every agency that wants this authority must complete the same certification and stand up the same reporting obligations before it can act. There is no incumbent tooling aimed at the SLTT tier yet (HYPOTHESIS — asserted by the convergence description, not independently verified). First movers on prep material capture search and association-channel traffic while the framework is novel.
Converging signals
1) Federal rule granting SLTT C-UAS authority under a certification framework (federalregister.gov, 2026-07-06). 2) QuadRF ~$100 open-source RF visualization making signal detection/documentation affordable (hackster.io). 3) Context.dev structured-extraction API making it cheap for a solo dev to monitor state grant programs, agency adopters, and rule guidance pages to build a buyer list (context.dev).
Customer pain
An agency chief who wants counter-drone capability (prisons with contraband drops, stadium/event policing) now faces an unfamiliar federal certification process, program-policy drafting, training documentation, and recurring federal reporting — with no compliance staff. FACT: the authorization is conditional on certification (rule signal). HYPOTHESIS: agencies will pay to shortcut the paperwork rather than parse the Federal Register themselves; this mirrors observed behavior in ELDT, OSHA, and grant-compliance markets but is not yet demonstrated for this rule.
Who pays
Primary: small/mid SLTT police, sheriff, and correctional agencies — often using federal/state grant money (HYPOTHESIS on grant eligibility until guidance is read). Secondary and faster: existing LE training vendors and drone-program consultants who resell curriculum, and individual officers/program leads expensing a sub-$500 prep course on a P-card, which dodges procurement.
Solved today
Nothing purpose-built exists yet for the SLTT tier (HYPOTHESIS). Today the analogous need is met by reading the rule directly, hiring counter-drone consultants, big-vendor turnkey systems (Axon/Dedrone, DroneShield) aimed at large agencies, and free nonprofit resources like DRONERESPONDERS.
Why current solutions are bad
Six-figure vendor systems are priced for major metros, not a 12-officer department or a county jail. Consultants are slow and expensive. The Federal Register text is dense and doesn't produce the artifacts an agency actually needs: a certification study path, a program policy, training records, an evidence-grade detection log, and the recurring federal report.
Proposed product
A layered offer: (L1, immediate) a certification-prep course + document pack — study guide mapped to the rule's framework, model C-UAS program policy, SOPs, training-record templates, and a federal-reporting checklist, $299–$499 per agency. (L2, 60–90d) a lightweight web app: guided certification tracker, incident/detection log designed to be evidence-grade (chain-of-custody fields, timestamps, RF-observation attachments from commodity gear like QuadRF), and one-click generation of the required federal reports, $99–$249/agency/mo. Explicitly hardware-agnostic: pairs with the ~$100 RF tools agencies can actually afford.
MVP version
7–10 days: read the full rule; extract the certification requirements and reporting obligations into a checklist; produce the document pack (policy template, SOPs, training log, reporting calendar) plus a 60–90 minute video/PDF prep course; one-page landing site; sell via Stripe. No portal integration needed for v1 — the moat-building portal/reporting automation comes only after the federal reporting mechanism is published.
30-day build
Days 1–3 read rule + any DOJ/DHS implementation guidance; days 4–10 build document pack + course; days 10–15 launch landing page, post in LE drone communities (DRONERESPONDERS, sheriff/police-chief association forums, r/ProtectAndServe-adjacent professional groups, LinkedIn public-safety UAS groups); days 15–30 use Context.dev-style extraction to build a list of agencies with existing drone programs (public UAS program pages, prior FAA COA holders — public records strength) and run direct outreach with a free 'SLTT C-UAS readiness checklist' as lead magnet. Target: 10–20 sales of the $299–$499 pack.
60-day build
Convert pack buyers into design partners for the logging/reporting web app; sign 1–2 LE training vendors to resell the curriculum at 30–50% margin; publish the definitive free explainer of the certification framework for SEO capture; verify whether the rule's reporting goes through a specific federal portal — if yes, prototype the submission workflow (the proven ELDT pattern: mandate → forced filers → per-filing automation).
90-day revenue plan
Realistic: $5k–$15k from 20–40 document-pack/course sales plus 5–10 early SaaS subscriptions at ~$99–$149/mo. Stretch: a training-vendor licensing deal at $2k–$5k. HYPOTHESIS — no buyer behavior for this specific rule is observable yet; the estimate is patterned on comparable compliance-pack markets and his ELDT experience.
Distribution path
No enterprise sales: content + direct outreach. SEO on 'SLTT counter-UAS certification' terms while competition is zero; DRONERESPONDERS and state police-chief/sheriff association newsletters; LinkedIn public-safety UAS groups; direct email to the public-records-derived list of agencies with existing drone programs; reseller deals with LE training vendors so their reps carry it into agencies.
Technical difficulty
Low for L1 (documents + course). Moderate for L2 (CRUD app with audit-grade logging and PDF report generation — well within solo AI-assisted range). High only if evidence handling must be CJIS-compliant or the federal reporting requires a portal integration with credentialing — the latter is actually his proven strength (ELDT/TPR precedent).
Legal / regulatory risk
Material and must be managed by positioning: C-UAS mitigation touches federal statutes (signal interference, aircraft protection), and mis-stating what an agency may do could create liability. Mitigation: sell preparation and record-keeping, never legal advice or mitigation authorization; prominent disclaimers; cite the rule verbatim. Evidence-grade logging for LE may trigger CJIS data-handling expectations (HYPOTHESIS — depends on whether logs contain CJI); keep v1 logs free of PII to sidestep it. Risk the certification details are still pending sub-regulatory guidance — building prep for a test that isn't finalized (checkable in days 1–3).
Platform dependency
Low. No app store, no API gatekeeper. Dependency is regulatory: a delayed, amended, or litigated rule stalls the market; a federal-run free certification portal with built-in reporting would shrink L2 (L1 prep value survives — the ELDT registry didn't kill paid ELDT tooling).
Founder fit
Very high pattern match with one caveat. This is exactly his proven shape: a federal rule compels a party to certify/report, and he builds the scaffolding and charges per transaction/seat (ELDT/TPR precedent). Fire-service background gives public-safety credibility a generic SaaS founder lacks, and the buyer-list build is a public-records play. Caveat: buyers are government agencies, not private CDL schools — procurement and trust cycles are slower, which is why the wedge must be the sub-$500 P-card-priced product, not the SaaS.
Breakout potential
If the reporting mechanism is a portal, this can become the 'ELDT play at 10x': recurring per-report or per-seat revenue across thousands of agencies, expanding into adjacent LE compliance filings (UAS program audits, grant reporting). Also licensable curriculum to every LE training company entering the space.
Final recommendation
CONDITIONAL GO. Spend 2–3 days reading the actual rule to confirm (a) the certification requirements are concrete enough to prep against and (b) what the reporting mechanism is. If confirmed, ship the $299–$499 prep/document pack within 10 days while competition is zero, and treat the logging/reporting SaaS — and especially any portal-submission automation — as the follow-on funded by pack sales. Do not build the SaaS first, and do not touch anything resembling mitigation authorization.
Next action
Read the full Federal Register rule (2026-13609) end-to-end today; extract the certification framework and reporting obligations into the readiness checklist that becomes both the lead magnet and the product spine.