What changed
FACT (Federal Register, 2026-07-06): DOJ/DHS published an interim final rule codifying the SAFER SKIES Act framework, letting state, local, tribal, and territorial law-enforcement and correctional agencies conduct counter-UAS operations under a certification framework — an activity previously restricted to federal agencies. FACT (Hackster sources): commodity RF sensing has gotten dramatically cheaper (~$100 QuadRF open-source RF visualization; DECT NR+ USB dev kits).
Why now
The rule is 4 days old. Every agency that opts in must stand up certification, operational procedures, and reporting from scratch, and no tooling exists yet that is priced for a 12-officer department or a county jail. Incumbent C-UAS vendors (Dedrone/Axon, DroneShield) are priced and sold for federal/large-metro budgets. First-mover window on the compliance layer is roughly 6-12 months.
Converging signals
(1) Regulation: C-UAS authority extended to SLTT agencies with certification and reporting obligations (federalregister.gov 2026-13609). (2) Industrial: ~$100 open-source RF visualization hardware (QuadRF). (3) Industrial: license-exempt non-cellular 5G/DECT NR+ in USB form factor. Signals 2-3 prove the sensing substrate is commoditizing, but the durable wedge is signal 1's paperwork, not the RF hardware itself.
Customer pain
HYPOTHESIS (structural, not yet evidenced by complaints — the rule is 4 days old): a small agency that wants C-UAS capability must navigate an unfamiliar federal certification framework, document operations to federal standards, and produce required reports, with no counsel or compliance staff dedicated to it. Corrections agencies additionally face a well-documented contraband-drone problem at facilities.
Who pays
SLTT law-enforcement and correctional agencies (per the rule, thousands are newly eligible), typically via DHS/state homeland-security grant money; secondarily, the C-UAS certification training providers that will spring up around the rule and need courseware/lab tooling. Small agencies can buy sub-$5k/yr software on a purchase order without formal procurement.
Solved today
Not solved — the authority did not exist for these agencies before this rule. The nearest analogs: federal agencies use defense-contractor platforms (Dedrone, DroneShield, Hidden Level) with six-to-seven-figure pricing; agencies without authority simply observed and called the FBI/FAA.
Why current solutions are bad
Incumbent platforms are priced for federal budgets, sold through defense channels, and focused on sensing performance, not on the SLTT certification/reporting workflow this specific rule creates. Nothing serves a 15-person sheriff's office or a rural county jail.
Proposed product
KILL THE STATED FRAME, KEEP THE CORE: do NOT sell 'evidence-grade detection kits on $100 hardware' — a QuadRF Wi-Fi visualizer is not a credible forensic drone detector and would be destroyed in court and in credibility. Instead ship the software compliance layer, hardware-agnostic: (a) guided certification-application workflow mapped to the IFR's requirements; (b) incident logging with chain-of-custody-style timestamps/hashing that ingests FAA Remote ID broadcasts (every compliant drone already transmits ID — receivable with a ~$30-200 receiver, legally uncontroversial) plus manual officer observations; (c) one-click generation of the reports the rule requires agencies to file with DOJ/DHS. Optionally resell a vetted Remote ID receiver as a convenience SKU, never as the core claim.
MVP version
A web app with three modules: certification checklist/document assembler keyed to the IFR sections; incident log (Remote ID capture via off-the-shelf receiver + manual entry, tamper-evident hashing, PDF evidence packet export); and the mandated federal report generator. Built solo with AI assistance in 6-10 weeks. Modest spend on a Remote ID receiver, legal review of the IFR (~$2-5k), and a pilot-agency stipend is fully fundable from existing runway.
30-day build
Read the full IFR line-by-line and extract every certification, recordkeeping, and reporting obligation into a requirements matrix (this is the product spec AND the sales one-pager). Interview 5-8 small-agency stakeholders (sheriffs, jail administrators, state homeland-security grant officers) — fire-service background gives warm credibility here. Confirm two kill-questions: does the rule prescribe an approved-equipment list that locks out commodity gear, and is the reporting burden real enough to pay for.
60-day build
Build the MVP against the requirements matrix. Recruit 2-3 pilot agencies (free 90-day pilots) via state sheriffs' associations and corrections associations. Publish a free 'SAFER SKIES certification requirements explained' guide to capture the search traffic every opting-in agency will generate.
90-day revenue plan
Convert pilots to $200-400/month per agency (or $2.5-4k/yr on PO). Realistic first revenue day 120-180 given agency budget cycles — acceptable per founder's runway. Parallel faster-cash channel: sell the requirements-matrix/courseware to C-UAS training providers immediately.
Distribution path
Content/SEO on the rule itself (agencies are all googling the same obligations right now), state sheriffs' and corrections associations, DHS grant-officer channels (grant-fundability is the unlock — write the grant-justification template for them), and partnerships with the certification training providers the rule will spawn.
Pricing hypothesis
$2,500-4,000/agency/year SaaS (under discretionary-PO thresholds), one-time $1-2k setup/certification-package option, courseware licensing to trainers at $5-10k. 100 small agencies = ~$300k ARR; the rule makes thousands eligible.
Technical difficulty
Moderate and solo-tractable IF hardware-agnostic: web app + Remote ID decoding (open protocols, existing open-source decoders) + document generation. HIGH and NOT solo-tractable if you promise RF detection performance — that's the trap in the original framing.
Legal / regulatory risk
Moderate. Selling compliance software to agencies is low-risk; the risks are (a) the IFR could be revised after the comment period, (b) evidence-integrity claims must be worded carefully (log, don't certify), (c) never touch 'mitigation' — jamming/takedown tooling is a federal minefield the software layer must explicitly exclude.
Platform dependency
Low. No app store, no platform API at risk. Dependency is on the rule itself surviving the interim-final comment period substantially intact — an IFR is effective immediately, which cuts in favor.
Founder fit
Strong on the core motion (7/10): this is the ELDT pattern — federal rule creates filing/reporting obligations for a class of small operators, founder builds the submission/compliance layer and charges per agency (matches the accumulated lesson on government-portal mandates, confidence 0.80). Fire-service background = genuine public-safety credibility, and demonstrated-value selling works on small agencies. Deductions: buyer is government (slower than trucking schools), and the mandate is conditional (opt-in), not absolute like ELDT.
Breakout potential
Real: land small LE/corrections, expand to stadiums, utilities, airports' local partners as states extend programs; become the system of record for SLTT C-UAS operations before Axon bothers to notice the low end. Exit path: acquisition by a public-safety software roll-up (Axon, Mark43, Peregrine).
Final recommendation
CONDITIONAL GO, reframed: drop the hardware-kit framing, build the hardware-agnostic certification + incident-reporting compliance SaaS. This matches the founder's proven ELDT motion (regulation → obligated filer → per-agency compliance tool) with a brand-new rule and zero incumbents at the low end. Gate the build on the 30-day validation: full IFR read (approved-equipment question) plus 5+ agency interviews confirming opt-in intent and reporting pain. If agencies signal opt-in interest, this is a top-decile fit; if opt-in looks rare, downgrade to courseware-for-trainers only.
Next action
Pull and read the complete IFR at federalregister.gov/documents/2026/07/06/2026-13609 today; extract every certification/reporting obligation into a requirements matrix; check for an approved-equipment provision; then book 5 calls with small-agency contacts via sheriffs'/corrections associations.