What changed
FEMA/DHS posted the FY2026 Port Security Grant Program (CFDA 97.056, OPP # DHS-26-GPD-056-00-99) on Grants.gov with an application close of 07/24/2026. This is a FACT from the provided Grants.gov detail (url 362824). Adjacent FY2026 FEMA preparedness programs are posted with near-identical shapes and close dates: Transit Security (97.075, 07/24/2026), Pre-Disaster Mitigation (97.143, 07/22/2026), plus National Cybersecurity Preparedness Consortium (97.148, 07/31/2026) — all FACT from the demand_evidence array.
Why now
A hard statutory application deadline of 07/24/2026 (FACT) is ~2 weeks out from today (2026-07-11). That window is too tight to WIN a first application this cycle, but it is a live, dated event that (a) proves the filer class is acting right now and (b) sets up the recurring post-award reporting business and the NEXT cycle. The reusable value is post-award: every awardee must file quarterly SF-425 (FFR) financial reports and performance reports for the multi-year period of performance (HYPOTHESIS on the exact cadence — 'quarterly FFR/SF-425' is asserted in the convergence text, not in a quoted NOFO here).
Converging signals
Three signals meet at one point: (1) a funded federal program with an appropriation and eligible class, (2) a defined forced-filer class — MTSA-regulated facility operators, port authorities, terminal operators, and (3) a government portal (Grants.gov intake, FEMA GO for management/reporting — FEMA GO is INFERENCE, not quoted). The same FFR/SF-425 + performance-report shape recurs across PSGP/TSGP/IBSGP/PDM (INFERENCE), giving one codebase many markets.
Customer pain
PAIN evidence is NOT present in the input — no complaint threads or job ads were supplied, so I will not fabricate it. The demand is structural: applicants must produce a per-project Investment Justification tied to a vulnerability/risk assessment and cost-effectiveness narrative (asserted in convergence text), then sustain years of SF-425/performance filings or risk drawdown holds and clawbacks. This is real, recurring paperwork, but the acuteness of the pain (vs. handling it in Excel + a grants consultant) is an INFERENCE, not proven by the input.
Who pays
Port authorities, marine terminal operators, and MTSA-regulated facility security officers applying for PSGP; secondarily the fee-for-service grant consultants who already assemble these packages and could white-label the tool. Buyer is the applicant/subrecipient or their consultant — NOT a government procurement office, so this is not enterprise procurement.
Solved today
Today: in-house facility security officers writing IJs in Word/Excel against the NOFO template, or grant-writing consultants billing hourly or a percentage of award; post-award FFRs filed by hand in Grants.gov/FEMA GO or via generalist grant-management suites (eCivis, AmpliFund, Fluxx, Submittable). This is a mix of FACT (those suites exist) and INFERENCE (that ports specifically use them).
Why current solutions are bad
Generalist grant suites are broad and priced for whole agencies/nonprofits; they are not PSGP-specific and don't encode the IJ structure, the port-security investment categories, or the SF-425 mapping. Consultants are expensive and don't scale. A narrow, PSGP-shaped tool that pre-structures the IJ and auto-assembles the quarterly FFR is a defensible wedge — but 'the generalists are inadequate' is a HYPOTHESIS I cannot prove from the provided sources.
Proposed product
A vertical micro-SaaS: (1) an IJ Builder that walks a facility through the PSGP investment-justification structure (project, vulnerability linkage, cost-effectiveness, milestones, budget) and exports a submission-ready package; (2) a post-award reporting workspace that tracks period-of-performance milestones and generates quarterly SF-425/FFR and performance-report drafts, with deadline reminders. Reuse the engine across TSGP/IBSGP/PDM by swapping templates.
MVP version
A single-tenant web app for PSGP FY2026/FY2027: guided IJ form → structured export (PDF/DOCX matching the NOFO template) + an SF-425 generator seeded from the budget. No portal auto-submission in v1 (unlike the ELDT pattern, FEMA GO submission is applicant-authenticated; scope that later). Solo-buildable with a Claude-assisted form engine + PDF templating.
30-day build
Pull the actual FY2026 PSGP NOFO and IJ template and SF-425 form (verify the reporting cadence — do NOT rely on the inferred 'quarterly'). Interview 8-12 port/terminal FSOs and 3-4 PSGP grant consultants to confirm pain and willingness to pay. Build the IJ Builder skeleton. Do not promise to win the 07/24 cycle.
60-day build
Ship IJ Builder + SF-425 generator as a paid tool. Land 3-5 design-partner facilities or one consultant reseller for the NEXT PSGP cycle and for open FY2026 post-award reporting (awardees announced later in FY26 will need reporting immediately).
90-day revenue plan
Convert post-award reporting subscriptions from FY2025/FY2026 awardees (recurring quarterly need starts on award, independent of the application deadline). Templatize TSGP (same 07/24 close, same shape) as market #2. Target first revenue from reporting subscriptions + per-IJ fees.
Distribution path
Direct outreach to MTSA facility security officers and port authority grant staff (identifiable via Coast Guard MTSA facility rolls and port authority directories — public records, a founder strength); partner/white-label with existing PSGP grant consultants; content targeting 'PSGP Investment Justification' and 'SF-425 FEMA GO' search terms. Demonstrated-value selling, not relationship sales.
Pricing hypothesis
$500-1,500 per Investment Justification (matches convergence estimate) + $99-299/mo or $300-600/quarter per facility for post-award reporting. Consultant white-label tier at a flat platform fee. Anchored as a fraction of consultant fees.
Technical difficulty
Low-to-moderate for a solo AI-assisted founder: guided forms, template-driven document generation, SF-425 field mapping, deadline scheduling. No portal RPA needed in v1. The hard part is domain accuracy (IJ scoring criteria, allowable costs), not engineering.
Legal / regulatory risk
Low. Submitting/preparing federal grant paperwork on a client's behalf is a normal consulting-adjacent service; the founder is not the applicant and is not becoming licensed. Avoid any guarantee of award. Handle facility vulnerability-assessment data (sensitive, possibly SSI/CUI) carefully — that is a real handling obligation, not a blocker.
Platform dependency
None in the platform-policy sense: FEMA GO/Grants.gov are government systems with no owner who can deplatform the tool. Dependency risk is that FEMA changes the IJ template or moves reporting cadence — manageable maintenance, not existential.
Founder fit
Very high. This is the exact ELDT-shaped pattern the founder has already shipped: read a federal program, identify the forced-filer class, build the submission/compliance layer, charge per filing + per seat. Public-records sourcing of the buyer list plays to his strengths. Only gap vs. ELDT: no clean per-upload portal API to automate submission yet — v1 is document assembly, not portal auto-file.
Breakout potential
Strong horizontal reuse: PSGP → TSGP → IBSGP → PDM → the broader FEMA preparedness grant family all share the SF-425/performance-report backbone (INFERENCE). Post-award reporting is a recurring subscription across a multi-year period of performance and across every future cycle, so revenue compounds beyond the one-time application spike.
Final recommendation
PROCEED as a validation build, not a deadline sprint. The forced-filer shape and founder-fit are excellent, but treat 07/24/2026 as evidence the class is live, not as your revenue date. Validate willingness-to-pay with real FSOs/consultants in 30 days before heavy build; anchor the business on recurring post-award reporting and the reusable multi-program template, which is where durable revenue lives.
Next action
Download the actual FY2026 PSGP NOFO + Investment Justification template + SF-425 from Grants.gov opp DHS-26-GPD-056-00-99 and confirm the true reporting cadence and IJ scoring criteria; in parallel, cold-outreach 10 MTSA facility security officers / PSGP consultants this week to test the $500-1,500/IJ + reporting-subscription pricing.