What changed
FACT (cited): the National Association of Counties — the buyer class's own trade body — published that FEMA reimbursement policy prolongs disaster recovery for counties, i.e. the customers themselves are naming documentation/reimbursement lag as the pain. HYPOTHESIS: 2026 FEMA policy churn and tightened scrutiny of PA awards increases denial/clawback anxiety among county finance officers.
Why now
Counties front disaster costs and wait months-to-years for FEMA PA reimbursement; every denied or deobligated cost is a direct hit to a county general fund. The buyer class is publicly complaining now (NACo piece). Disasters recur on a rolling basis, so there is always a fresh cohort of counties with new declarations, live deadlines, and money at risk — the sales list regenerates itself from FEMA's public declaration feed.
Converging signals
The mandate structure IS the convergence: (1) a defined filer class (subrecipient counties in declared disasters), (2) a compulsory submission (full PA cost substantiation: procurement compliance under 2 CFR 200, force-account labor/equipment records, appeals on denials), and (3) a fixed portal (FEMA Grants Portal plus state pass-through portals). Only one demand signal was provided, so the convergence is structurally strong but evidentially thin — this is one NACo article, not multiple independent sources.
Customer pain
FACT: counties experience prolonged recovery due to reimbursement policy (NACo). Established program mechanics (FACT-grade, general knowledge of PA): costs are denied for procurement noncompliance, missing force-account documentation, and blown appeal windows; obligated funds can be deobligated years later at closeout or via OIG audit. The pain is not filling a form — it is proving every dollar across a multi-year project lifecycle without losing track.
Who pays
The county itself (emergency management + finance office) — the beneficiary and the buyer are the same party, which is the clean case. Secondary buyers: regional councils of governments (white-label across member counties) and disaster-recovery consultants who could run it across client portfolios. Pricing angle: software used to administer PA grants is plausibly reimbursable as a Direct Administrative Cost (DAC), meaning FEMA effectively subsidizes the subscription — HYPOTHESIS until validated against current DAC policy, but if true it collapses price resistance.
Solved today
Spreadsheets plus the FEMA Grants Portal itself; larger disasters get consultants (Hagerty, Tidal Basin, Witt O'Brien's) billing hourly or as a share of managed awards; a minority of counties use purpose-built software (Crisis Track/Juvare for damage assessment and cost capture, Tempest GEMS for PA documentation) or generic grant-management suites (AmpliFund, eCivis).
Why current solutions are bad
The Grants Portal is a submission system, not a completeness/risk tracker — it will not warn a county that a procurement file is missing before FEMA denies the cost. Consultants are expensive and episodic; they leave at project close and take the institutional knowledge with them. Existing software incumbents are priced and shaped for large jurisdictions and big disasters; thousands of small/mid counties are on spreadsheets. The wedge is clawback-prevention framing at a small-county price point, not another grant-management suite.
Proposed product
A per-county SaaS: ingest the county's PA project list; per-project checklists auto-generated from project type (Category A-G) covering procurement documentation, force-account records, insurance offsets, and EHP conditions; a deadlines engine (appeal windows, period-of-performance, closeout); a drawdown ledger showing obligated vs drawn vs at-risk dollars; and an audit-ready export that packages substantiation per project. Sold as insurance against losing money the county already spent.
MVP version
No portal integration needed for v1 (Grants Portal has no public API — do not build against it first). MVP = structured checklist + deadline + drawdown tracker seeded with FEMA's public PA policy guide requirements, plus the audit-package export. One recently-declared county as design partner, free for 90 days in exchange for reference rights.
30-day build
Pull FEMA's open disaster-declaration and PA-obligation data (OpenFEMA API is public); build the target list of counties with active declarations in the last 18 months. Interview 5-8 county EMs/finance directors sourced via NACo content, state EM association lists, and the founder's fire-service network. Validate the DAC-reimbursability claim against current PA policy. Build the MVP checklist/deadline core.
60-day build
Design-partner deployment in 1-2 counties with live PA projects; iterate the checklist engine against their real project files; produce the first 'dollars at risk' report — that artifact is the sales demo. Draft the white-label pitch for one council of governments.
90-day revenue plan
Convert design partners to paid annual subscriptions; direct outreach to every county on a new major-disaster declaration list (the declaration itself is the trigger event and the urgency). Target: 3-5 counties paying by day 120-150. Realistic first-revenue window is 90-150 days given government purchasing, mitigated by pricing under micro-purchase/small-procurement thresholds so no RFP is needed.
Distribution path
FEMA's public declaration feed is a self-refreshing lead list with built-in urgency. Channels: direct outbound to newly-declared counties, state emergency management associations, NACo affiliate channels, councils of governments (one sale = many counties), and disaster consultants as white-label resellers. Founder's fire-service background gives genuine credibility with EM buyers — demonstrated-value sales, not relationship sales.
Pricing hypothesis
$4,000-$8,000/county/year flat (deliberately under typical procurement thresholds so a department head can buy on a P-card or simple PO), scaled by active project count for large disasters; COG white-label at a multi-county rate. If DAC reimbursability validates, lead with 'FEMA effectively pays for this.'
Technical difficulty
Low-to-moderate build (checklists, ledgers, deadline engine, document storage, exports — squarely in founder's fast-prototyping lane). The hard part is encoding PA policy correctly (2 CFR 200 procurement rules, force-account rules, current PA Program and Policy Guide) — a domain-knowledge problem, addressable with the founder's EM background plus a retained PA consultant for policy review.
Legal / regulatory risk
Low. No licensure required to sell documentation software; the county remains the applicant of record. Must avoid giving what amounts to legal advice on appeals — frame as documentation tracking, not legal representation. No finder-fee or fee-cap regime applies (this is not a claims-finder model).
Platform dependency
None that can deplatform it — FEMA Grants Portal is a government system with no platform owner gatekeeping third-party prep tools. Risk instead is policy dependency: FEMA restructuring PA (actively discussed in 2026) could change documentation requirements — which is churn that helps a tool vendor and hurts spreadsheets, but requires ongoing policy maintenance.
Founder fit
Very high. This is the founder's proven shape — a government program compels a defined class to substantiate/submit, and the software layer monetizes the paperwork burden (FMCSA ELDT precedent). Bonus: fire-service background means he speaks the emergency-management buyer's language natively, and recycling/industrial ops experience maps to force-account equipment/labor records. The one mismatch: the buyer is a local government, so sales cycles are slower than his preferred motion.
Breakout potential
Strong replication surface: 3,000+ counties, plus cities, special districts, school districts, and nonprofits (all PA-eligible applicants); adjacent expansion into HUD CDBG-DR documentation, hazard-mitigation grants (HMGP/BRIC successor programs), and state-only disaster programs. A 'dollars recovered/protected' dataset becomes a marketing moat.
Final recommendation
PURSUE with a validation gate. The shape is the founder's proven thesis (compelled documentation → government portal → per-jurisdiction fee), the buyer and beneficiary are the same party, the pain is named by the buyers' own association, and the lead list self-generates from public declaration data. It survives the adversarial checks (free path inadequate, no fee caps, no licensure, recurring events, low PII). The honest risks are sales-cycle speed and two incumbents — gate the build on 5+ county interviews confirming willingness to pay at the sub-threshold price and on validating DAC reimbursability.
Next action
Pull OpenFEMA declarations + PA obligations for the last 18 months, rank counties by obligated-but-undrawn dollars, and book interviews with 5 county EM/finance directors from that list this month.