What changed
A Federal Register rule (2026-07-06) extends counter-UAS detection-and-mitigation authority to state, local, tribal, and territorial (SLTT) law-enforcement and correctional agencies — a class that previously had no such authority. Per the source, the new authority is bundled with mandatory training, certification, reporting, and compliance obligations for which no agency has existing tooling or expertise.
Why now
The rule is days old (published 2026-07-06). Agencies are being handed a new operational power AND a paperwork/compliance regime simultaneously, with zero lead time to build internal capacity. Two adjacent federal money streams (NIEHS SBIR e-learning for emergency response; Workforce Pell for short-term credentials) exist in the same window, though neither is counter-UAS-specific.
Converging signals
(1) A regulation compelling a defined filer class (SLTT agencies) to certify personnel and report mitigation events [FACT — Federal Register 2026-13609]; (2) an SBIR line that funds a small business directly to build emergency-response e-learning [FACT — grants.gov 358912, but scoped to HAZMAT/NIEHS, not counter-UAS — INFERENCE that it maps]; (3) Workforce Pell opening federal dollars to short-term workforce credentials [FACT — Federal Register 2026-10013, but qualifying a course for Pell is a heavy, performance-based process — INFERENCE that it is a near-term distribution channel].
Customer pain
HYPOTHESIS (no demand_evidence provided): agencies newly authorized to down drones must certify officers and file mitigation-event reports under a rule they have never operated under, with no template, LMS, or reporting workflow. The pain is structural (the mandate creates it) rather than evidenced by complaints in this input.
Who pays
Primary reachable buyer: SLTT agency training/compliance budgets, paying for (a) a certification-prep course per officer and (b) a mitigation-event reporting/documentation tool per agency. Secondary/non-dilutive: SBIR as build capital. Distant: Pell for enrolled trainees.
Solved today
Nothing exists yet for this specific authority (rule is days old). Agencies default to internal legal counsel, ad-hoc Word/PDF incident forms, and whatever DHS/FBI guidance trickles down. Adjacent counter-UAS training today is vendor/manufacturer-led and aimed at federal buyers.
Why current solutions are bad
Ad-hoc documentation exposes agencies to legal challenge on a use-of-force-adjacent authority (downing an aircraft). No standardized, defensible mitigation-event record; no certification audit trail; no mapping to the rule's specific obligations.
Proposed product
A two-part product: (1) a counter-UAS mitigation-event reporting + documentation workflow (structured incident capture, statutory-obligation mapping, exportable defensible record, certification-tracking) sold per agency; (2) a self-paced certification-prep course mapped clause-by-clause to the rule. Lead with the reporting tool — it is the recurring, sticky, compliance-moat piece.
MVP version
A hosted incident-reporting form that captures each mitigation event against the rule's required fields, produces a court-defensible PDF/record, and tracks which officers hold current certification — plus a 3-4 hour narrated prep course. Buildable solo in weeks.
30-day build
Read the full rule and extract the exact reporting fields, certification requirements, and deadlines. Build the reporting-workflow mockup. Run the KILL TEST: cold-pitch 10 SLTT agencies (start with corrections facilities, which have acute contraband-drone pain) for a pilot or pre-pay.
60-day build
If ≥1-2 agencies commit, build the production reporting tool + prep course. Begin drafting the NIEHS SBIR proposal as non-dilutive build capital (accepting it is a stretch mapping and slow). Recruit a subject-matter reviewer (retired LE/counter-UAS) for credibility.
90-day revenue plan
Sell direct to a handful of agencies at a per-agency SaaS price for the reporting tool plus per-seat course fees. Target first paid pilots converting to annual contracts. Treat Pell as a long-tail channel, not a 90-day revenue source.
Distribution path
Direct outreach to SLTT agency training officers and corrections administrators; state sheriffs'/police-chiefs' associations and corrections associations (conference tables, newsletters); FirstNet/emergency-response networks. Founder's fire-service background gives credible entry to the public-safety buyer.
Pricing hypothesis
Reporting/compliance tool: $2,000-6,000 per agency per year (tiered by size). Certification prep: $250-500 per officer. Managed documentation add-on optional. Undercut any consultant charging hourly for incident write-ups.
Technical difficulty
Low-to-moderate. Structured forms, PDF/record generation, cert tracking, an LMS-lite course player. No government-portal integration required at MVP (unlike FMCSA) — records are agency-held, which simplifies the build.
Legal / regulatory risk
Moderate. The product documents a use-of-force-adjacent action; the founder must be careful to provide a defensible record tool, not legal advice or certification authority. Certification itself is issued by the government/authorized body — the product is PREP, not the credential. Do not overstate that the course confers legal certification.
Platform dependency
None material — no app-store or platform owner to deplatform it. Not submitting to a government portal, so no portal-owner risk.
Founder fit
High. Government-mandate/forced-filer shape + fire-service/emergency-services credibility + compliance-monitoring/operational-tooling strengths. Weakness: this is a public-safety procurement buyer, which is slower and more relationship-sensitive than the FMCSA per-upload model the founder has proven.
Breakout potential
Real: thousands of agencies × 50 states, replicable state-by-state, with a recurring compliance-record product that becomes the system of record. Expansion into adjacent public-safety compliance (BWC, use-of-force reporting) plausible.
Final recommendation
PURSUE the counter-UAS reporting/compliance wedge only — drop the SBIR/Pell framing from the core thesis (keep SBIR as optional non-dilutive capital). This is a genuine fresh-mandate, forced-obligation opportunity in the founder's strongest category, but its central assumption (agencies pay an outside vendor now) is unvalidated. Gate all further spend on the 30-day KILL TEST.
Next action
Pull the full text of Federal Register rule 2026-13609, extract the exact required reporting fields, certification requirements, and deadlines, then cold-pitch 10 SLTT agencies (lead with corrections facilities) with a reporting-workflow mockup for a paid pilot within 30 days.