What changed
FACT: On 2026-07-06 DOJ/DHS issued an interim final rule codifying the SAFER SKIES Act, authorizing State/local/Tribal/territorial (SLTT) law-enforcement and correctional agencies to conduct counter-UAS operations, with bundled training/certification/reporting/compliance obligations (federalregister.gov 2026-13609). HYPOTHESIS (from convergence text, unverified): the rule carries no attached appropriation, creating an unfunded mandate.
Why now
FACT: The rule is live now. FACT: DHS-FEMA's State Border Security Reinforcement Fund (CFDA 97.159) is open on grants.gov with a hard 08/03/2026 close (grants.gov/362671). FACT: NY announced $100M for law-enforcement technology/equipment (Hochul .gov release). The mandate and at least two funding pots are simultaneously open — the window to connect them is short and deadline-driven.
Converging signals
A forced-buyer regulation (C-UAS authority) + a dated federal grant (97.159, 08/03/2026) + a state procurement pool ($100M NY police tech) meeting at one point: thousands of agencies suddenly obligated to buy/train/report on drone-defense gear with no earmarked budget.
Customer pain
FACT-adjacent: agencies gain a new legal authority bundled with mandatory training, certification, and mitigation-reporting they have 'no existing tooling or expertise for' (per the signal rationale). HYPOTHESIS: agencies don't know which open grant's allowable-use language covers the specific cost drivers (detection gear, mitigation gear, training, reporting tooling). Vendors' pain: they can't tell which prospects have matching open funding, so deals stall on 'no budget.'
Who pays
Primary buyer (per convergence): counter-UAS equipment vendors, paying for channel enablement — a tool that flags which of their agency prospects have a matching open grant + deadline + a ready draft application. Secondary: agencies paying a per-application grant-writing fee. The BENEFICIARY (agency getting money) differs from the BUYER (vendor buying warmer leads / faster close).
Solved today
HYPOTHESIS: manually — vendor sales reps and third-party grant consultants hunt grants.gov/state portals by hand, and agencies hire percentage-of-award grant writers or muddle through. No product ties this specific mandate's cost drivers to live allowable-use terms.
Why current solutions are bad
Manual grant-matching is slow, generic, and not mapped to the exact new obligation; agencies miss deadlines (08/03/2026 is weeks out); vendors waste cycles on unfunded prospects. Percentage-of-award consultants are expensive and don't scale across 50 states of near-identical mandates.
Proposed product
A lookup + draft-generation tool: (1) a structured map of the C-UAS rule's cost drivers to allowable-use language in specific open pots (97.159, NY $100M, and similar public-safety-tech grants); (2) an agency-level query returning matching open opportunities + deadlines; (3) boilerplate application sections tying the mandate to each fund's stated purpose. Delivered first as a vendor-facing lead/enablement dashboard, optionally a per-application grant-draft service.
MVP version
Manually read the actual NOFO/terms for 97.159 and the NY program (KILL TEST). If either genuinely lists counter-UAS or general public-safety technology as an allowable use, build a spreadsheet-backed matcher for ~3-5 pots + a templated application section, wrapped in a thin web UI. Sell a pilot to 2-3 C-UAS vendors.
30-day build
Verify allowable-use terms (the entire idea hinges on this). Build the cost-driver→allowable-use map for the confirmed pots. Assemble the eligibility/deadline lookup. Cold-outreach 10-15 counter-UAS vendors with a demo tied to their actual prospect list.
60-day build
Add more pots (state homeland-security grants, HSGP/UASI, additional state police-tech appropriations). Templatize application boilerplate per fund. Convert 1-2 vendor pilots to paid channel-enablement seats; offer agencies a per-draft fee.
90-day revenue plan
Recurring vendor seats (channel-enablement subscription) + per-application draft fees. Replicate the map into 2-3 additional states (same mandate, different money) — the 50-market replication path is the expansion thesis.
Distribution path
Direct to counter-UAS vendors (a small, reachable, named set — DroneShield, Dedrone, Fortem, Anduril resellers, etc.) via demonstrated value on their own pipeline. Secondary: outreach to agency grant coordinators before the 08/03/2026 deadline.
Pricing hypothesis
Vendor channel-enablement seat: HYPOTHESIS $300-1,500/mo per vendor. Per-application draft: $500-2,500 flat (undercutting percentage-of-award consultants). Avoid finder-fee-cap issues by charging the vendor/agency for software+drafting, not a cut of the award.
Technical difficulty
Low-moderate. The hard part is human research (reading NOFO allowable-use terms accurately), not engineering. Lookup + template generation is a small AI-assisted build.
Legal / regulatory risk
Moderate: grant-application content must be accurate; misrepresenting allowable use could harm agencies. Not licensure-blocked (grant writing is not a regulated profession federally). No platform owner to deplatform a gov-grant tool.
Platform dependency
None material — submits to / references government systems, not a private platform.
Founder fit
HIGH. This is the founder's proven shape: read a federal mandate, identify the forced/served party, build the paperwork layer, monetize per transaction/seat. Directly adjacent to his FMCSA ELDT portal-filing product, plus his public-records and fire/public-safety background.
Breakout potential
Moderate-high IF the pairing is real: one verified mandate↔money map replicates across 50 states and generalizes into a broader 'unfunded-mandate → matching-grant' engine for any new SLTT obligation. Ceiling capped by grant-cycle timing and vendor count.
Final recommendation
CONDITIONAL PURSUE. Do the KILL TEST first — spend one day reading the actual NOFO/terms of 97.159 and the NY $100M program. If allowable use genuinely covers C-UAS or general public-safety tech, this is a high-founder-fit, deadline-driven wedge worth a fast pilot. If not, kill it and keep the mandate-to-grant matcher pattern for a better-matched pot.
Next action
Read grants.gov/362671 (97.159) full NOFO and the NY $100M program terms; confirm whether counter-UAS / public-safety technology is an allowable use. Resolve the kill test before writing any code.