What changed
SAMHSA posted a fresh wave of FY26 discretionary NOFOs closing July–August 2026 — Assertive Community Treatment (SM-26-022, CFDA 93.532, closes 07/27/2026, FACT per grants.gov 361572) plus at least a dozen sibling programs in the input (CCBHC planning/improvement, SBIRT, mobile crisis, tribal opioid response, PPW, youth treatment). Every funded grantee inherits an ongoing client-level performance-reporting obligation into SAMHSA's SPARS system for a 4–5 year term (inference from standard SAMHSA grant terms — verify in each NOFO's reporting section).
Why now
A new grant cohort is being created right now: applications close within 2–6 weeks of today, awards follow in FY26, and each award manufactures a new forced filer with recurring intake/6-month/discharge data-collection deadlines per enrolled client. Simultaneously, the existing base of active SAMHSA grantees (hundreds at any time — inference) is already living with this burden today, so the market does not wait on award announcements.
Converging signals
Three signals meet at one point: (1) a funded mandate — 20+ posted SAMHSA/HRSA NOFOs in the demand_evidence array, all feeding the same SPARS reporting regime; (2) a defined filer class — community behavioral-health providers, CCBHCs, tribes, crisis centers, ACT teams; (3) a single government portal — SPARS — with a repetitive, deadline-driven, client-level submission workflow. Per the engine's own heuristic (confidence 0.79), this portal-mandate shape is the founder's best fit.
Customer pain
Grantee staff must conduct structured NOMs/GPRA interviews with clients at intake, 6-month follow-up, and discharge, hit SAMHSA's follow-up-rate expectations, and key results into SPARS on schedule for years. The operational pain is (a) remembering which of dozens/hundreds of enrolled clients enters a follow-up window each week, (b) capturing interviews in the field (ACT teams and mobile crisis teams work outside the office by definition), and (c) re-entering data into a government web portal. Missed follow-up windows are unrecoverable and degrade the grantee's compliance standing. NOTE: pain characterization is inference from the mandate structure — the input contains no direct complaint threads, and per instructions a FUNDED MANDATE naming a filer class and submission scores demand on its own.
Who pays
Two reachable buyers: (1) the grantee organization itself — program director or data coordinator at a community mental-health provider, paying from the grant's own budget (data collection/evaluation is an allowable, expected cost); (2) third-party evaluators who contract with grantees to run exactly this data collection and who currently assemble it with spreadsheets and REDCap. Both are small-organization buyers, not government procurement offices.
Solved today
Manual spreadsheets plus SPARS's own web data-entry screens; some grantees hire external evaluators (commonly budgeted at a meaningful % of the award — hypothesis, consistent with standard grant-evaluation practice) who bring their own ad-hoc REDCap/Excel tooling; large CCBHCs may lean on EHR vendors, but the small ACT/crisis/tribal grantees dominating these NOFOs typically have no purpose-built tool (hypothesis).
Why current solutions are bad
Spreadsheets don't track per-client follow-up windows or alert on them; SPARS web entry is duplicate keying; field interviews on paper get transcribed twice; evaluators are expensive relative to a software subscription; nothing ties capture → validation → submission into one pipeline. The follow-up-rate requirement makes silent process failure costly.
Proposed product
SPARS Sidekick: (1) mobile/offline-capable NOMs interview forms mirroring the SPARS instruments; (2) a per-client compliance calendar that computes every intake/6-month/discharge window from enrollment date and alerts staff before windows open/close; (3) validation against SPARS field rules; (4) export in SPARS batch-upload format where the program supports it, and an assisted-entry flow (checklist + formatted record) where only web entry exists. HIPAA-compliant hosting with BAA. Priced per grant, not per seat, to match how grantees budget.
MVP version
One program's instrument set (ACT / CMHS NOMs adult tools), web + mobile-responsive capture, the follow-up-window tracker with email alerts, and CSV/batch export. Skip EHR integration entirely. CRITICAL PRE-BUILD CHECK (week 1): obtain the actual SPARS data dictionary and confirm which programs accept batch upload versus web-entry only — this determines whether the wedge is 'one-click submission' or 'never-miss-a-window tracking + clean re-entry.' The tracking value survives either answer.
30-day build
Download the ACT and 2–3 sibling NOFOs; extract the exact reporting terms (verify the SPARS/NOMs inference). Pull SAMHSA's public list of CURRENT active grantees under CFDA 93.532/93.243/93.490 — these are named organizations with public contact info already reporting today. Interview 5–8 grantee data coordinators and 3 evaluator firms. Stand up HIPAA-eligible infra (e.g., AWS with BAA — modest cost the founder can fund). Build instrument capture + window tracker.
60-day build
Pilot with 2–3 current grantees free-for-feedback; harden validation rules against real SPARS rejections; add batch export for whichever programs support it; sign first evaluator-firm partnership (they resell/deploy across their grantee portfolio — one evaluator can bring 5–20 grantees).
90-day revenue plan
Convert pilots to $250–400/month per grant; direct outreach to the full published grantee lists timed to FY26 award announcements ('you just got funded — your first SPARS deadline is in 90 days'). 10 paying grants ≈ $3–4k MRR by day ~120–150; the FY26 cohort provides a second wave.
Distribution path
Public award lists make the entire buyer universe enumerable and reachable by email/phone — no ad spend, no marketplace. Evaluator firms are a force multiplier. Content wedge: a free 'SPARS deadline calculator' and NOFO reporting-requirements cheat sheet ranks for the exact searches new grantees make. This is demonstrated-value selling, matching the founder's style.
Pricing hypothesis
$250–400/month per grant (or ~$3–4k/year), positioned against (a) hours of staff time weekly and (b) evaluator fees an order of magnitude higher. Multi-grant orgs (CCBHCs often hold several SAMHSA awards) pay per grant — natural expansion.
Technical difficulty
Moderate and squarely in the founder's proven lane: forms, scheduling logic, validation, file-format generation, and a government-portal submission layer — the same shape as his shipped FMCSA ELDT registry product. Main technical unknowns: SPARS batch-upload availability per program and instrument change-management when SAMHSA revises NOMs tools. No ML required.
Legal / regulatory risk
Client-level behavioral-health/SUD data means HIPAA and potentially 42 CFR Part 2. This is a cost and a design constraint (BAA hosting, encryption, access controls, signing BAAs with customers), NOT a licensure requirement on the founder — so it is a moat against copycats, not a blocker. Must not misrepresent affiliation with SAMHSA. If automating web entry where no batch upload exists, respect SPARS terms of use (verify before building robotic entry; assisted-manual flow is the safe fallback).
Platform dependency
Depends on SPARS remaining the reporting system (it is long-established — inference) and on instrument stability. Government portals don't deplatform vendors; the realistic risk is SAMHSA modernizing SPARS APIs, which would help, not hurt, an incumbent tool with the customer relationships.
Founder fit
Near-maximal. This is the exact FMCSA ELDT pattern replayed: federal mandate → defined compelled filer class → government portal → per-transaction/per-seat software layer. Founder's public-records fluency finds every buyer; his fire-service/first-responder background gives credibility with crisis-team and first-responder-adjacent grantees (several NOFOs in evidence are first-responder programs). No enterprise procurement: buyers are small nonprofits spending their own grant budgets.
Breakout potential
Horizontal: every SPARS-reporting SAMHSA program (the demand_evidence array alone spans ~15 distinct NOFOs/CFDAs). Vertical: state pass-through behavioral-health reporting (SABG/MHBG subrecipients report similar data to STATE systems — 50 replicable markets, per the engine's state-scope thesis), then other HHS performance-reporting regimes (HRSA EHBs performance reports). A grantee-compliance suite (SPARS + FFR deadlines + progress-report calendar) is the natural expansion.
Final recommendation
PURSUE, gated on a one-week verification sprint: (1) confirm from the actual NOFOs that SPARS/NOMs client-level reporting is required for these programs (currently a strong inference, not fact); (2) obtain the SPARS data dictionary and confirm batch-upload availability; (3) get 3 current grantees to describe their present workflow. If all three check out, this is an A-shape opportunity: forced filers, enumerable buyers, recurring multi-year obligation, founder's proven playbook, fundable build. If batch upload is closed AND EHR incumbents already cover small grantees, downgrade to the state pass-through variant instead of abandoning the thesis.
Next action
Today: download NOFO SM-26-022 from grants.gov (opp 361572) and extract its data-collection/performance-reporting section verbatim; pull the SAMHSA active-grantee list for CFDA 93.532 and 93.490; request SPARS documentation/data dictionary from the SPARS help desk to settle the batch-upload question before writing any code.