What changed
SAMHSA posted OPP SM-26-019 (Safety Through Recovery, CFDA 93.243, closes 07/17/2026) plus a cluster of sibling FY26 opioid/mental-health grants (CFDA 93.490/93.788/93.492, closing 07/13β07/27/2026). FACT (grants.gov 361564, 361577, 361576, 361580, 361581 et al.). Every award in this family carries a standard post-award obligation: report client-level performance data (GPRA interviews) into SAMHSA's SPARS/TRAC system.
Why now
A fresh wave of SAMHSA NOFOs is closing in July 2026 (FACT: multiple close dates 07/13β07/27/2026). Winners are notified ~90β120 days later and must begin GPRA data collection at intake immediately (HYPOTHESIS: standard SAMHSA post-award timeline, not in source text). That creates a dated, recurring compliance need starting Q4 2026 across a new grantee cohort.
Converging signals
Three signals meet at one point: (1) a defined filer class β community behavioral-health providers and state/tribal subrecipients that win these grants; (2) a mandated submission β SF-424 to apply, then recurring GPRA client interviews into SPARS/TRAC; (3) a federal portal (Grants.gov + SPARS). The same reporting spec recurs across ~a dozen concurrent SAMHSA opportunities (FACT: evidence array lists 11+ SAMHSA grants sharing the GPRA/SPARS reporting model).
Customer pain
GPRA requires structured client interviews at intake, 6-month follow-up, and discharge, with high follow-up-rate targets that grantees are penalized for missing. Front-line clinicians hand-key data into SPARS, chase clients for follow-ups, and risk non-compliance findings. HYPOTHESIS β the specific burden/penalty detail is well-known in the field but NOT asserted in the provided source text; the source only names 'SAMHSA performance measures / client GPRA interviews.'
Who pays
The grantee organization (community behavioral-health provider, FQHC, tribal program, or state pass-through subrecipient) that must report to keep drawing down award funds. Secondary buyer: grants-management consultants who currently do this manually and would white-label the tool.
Solved today
SAMHSA's free SPARS web portal (manual entry), spreadsheets, paper GPRA forms, generic EHR modules that don't map cleanly to GPRA fields, or a paid consultant/evaluator billing hourly. HYPOTHESIS β mix of these; source does not enumerate incumbents.
Why current solutions are bad
Manual SPARS entry is double-work on top of the clinical record, follow-up scheduling is ad hoc (killing the follow-up rate that SAMHSA scores), and generic EHRs don't produce a SPARS-ready export. A consultant is expensive and doesn't reduce the front-line data-collection labor.
Proposed product
A focused web app: (1) GPRA-native intake forms (exact SPARS question set/skip logic), (2) automated follow-up scheduling + client reminder workflow to hit the 6-month follow-up target, (3) validation against SPARS rules before submission, (4) batch export/upload to SPARS/TRAC (start with a formatted, upload-ready file; add direct submission once the SPARS interface is mapped), (5) grant-level dashboards for the required aggregate performance reporting. Later: SF-424 application-assembly helper for the apply phase.
MVP version
GPRA intake + follow-up tracker + SPARS-format validated export for ONE grant program (start with the 93.243/93.490 GPRA measure set). Single-tenant, per-org. Manual CSV/XML export the grantee uploads to SPARS themselves β defer direct portal-write integration until a design partner confirms the SPARS import spec.
30-day build
Pull the current SPARS/TRAC GPRA data dictionary and upload spec; rebuild the intake instrument and follow-up rules exactly. Cold-outreach 20β30 named SAMHSA grantees from prior-year award lists (USAspending/TAGGS are public) + this cohort's likely applicants. Land 1β2 design partners at a discount for spec access.
60-day build
Ship intake + follow-up scheduling + validated SPARS export with a design partner running real client interviews. Instrument the follow-up-rate metric as the headline value prop. Build the multi-tenant/per-seat layer.
90-day revenue plan
Convert design partners to paid per-seat + per-active-client pricing; open self-serve signup targeted at the FY26 award cohort as notices land. Recruit 1β2 grants consultants as resellers. First recurring revenue from 3β5 grantee orgs.
Distribution path
Direct outreach to named grantees using public award data (TAGGS/USAspending list every SAMHSA grantee with contact org); content/SEO on 'GPRA reporting' and 'SPARS follow-up rate'; partnerships with grant-writing/evaluation consultants who serve this niche; presence in behavioral-health provider associations.
Pricing hypothesis
Per-seat subscription (~$40β$80/clinician-seat/mo) + per-active-client-record fee, or a flat per-grant tier (~$300β$800/mo) for small grantees. Anchor against the cost of a part-time data clerk or evaluator's hourly billing.
Technical difficulty
Moderate. The hard part is faithfully replicating the GPRA instrument + SPARS validation rules and the follow-up logic β data-modeling work, not novel tech. Direct SPARS submission is the riskiest integration; deferring it to formatted-export in the MVP de-risks the build. Solo-buildable with AI assistance.
Legal / regulatory risk
Handles client-level behavioral-health / substance-use data β this is PHI and specifically 42 CFR Part 2 protected (SUD records), stricter than baseline HIPAA. This is a REAL constraint: BAAs, encryption, access controls, consent handling. Not a kill, but it raises the compliance bar and lengthens trust cycles vs. a pure paperwork tool. Founder does NOT need to become licensed, but must build to HIPAA/Part 2.
Platform dependency
None in the deplatform sense β submits to a government system (SPARS/Grants.gov). No private platform owner can cut off access. Risk is instead that SAMHSA changes the SPARS spec (maintenance burden) or ships its own better importer.
Founder fit
High on the government-portal-mandate shape the founder has already shipped (FMCSA ELDT). Same pattern: read a federal obligation, identify the forced filer, build the submission/compliance layer, charge per transaction/seat. The differentiator vs. his prior win: this touches sensitive clinical PHI (42 CFR Part 2), a domain he has no stated background in β that's the fit gap, not the mechanics.
Breakout potential
Strong horizontal expansion: the GPRA/SPARS reporting model recurs across the whole SAMHSA grant portfolio (FACT: 11+ concurrent grants in the evidence share it), and the broader pattern (federal grantee client-level outcome reporting) repeats at HRSA, ACF, DOJ/OJP, and state block-grant subrecipients β 50-state replication once the first program works.
Final recommendation
PURSUE, but validate the compliance load and incumbency before heavy build. The forced-filer/public-money shape and horizontal replication are exactly the founder's proven wedge, and demand is structurally real (mandated recurring reporting across a dozen live grants). The one thing that makes this different from his FMCSA win is Part 2 PHI β confirm with 2 design partners that (a) their current EHR doesn't already do GPRA/SPARS well and (b) they'll trust a new vendor with client data. If both clear, this is a high-fit build.
Next action
Download the live SPARS/TRAC GPRA data dictionary + upload spec, and pull the prior-year SAMHSA award list from TAGGS/USAspending to build a targeted outreach list of 20β30 named grantees for design-partner calls.