What changed
BJA posted the FY25 State Criminal Alien Assistance Program (SCAAP) solicitation, CFDA 16.606, opp O-BJA-2025-172612, closing 07/14/2026 (FACT, grants.gov). SCAAP reimburses states/counties/cities for incarcerating undocumented individuals, and the application requires inmate-level records (identity, custody dates, foreign-born status) plus correctional-officer salary data — data that lives inside jail management systems and is painful to extract and validate (inference).
Why now
The FY25 window closing 07/14/2026 is 3 days away — this cycle is effectively over, which is exactly the right moment to build: jurisdictions that just suffered through the extract-and-validate scramble (or missed the deadline entirely) are maximally receptive, and the founder has ~12 months to build, pilot, and pre-sell before the FY26 cycle. SCAAP recurs annually, so the paperwork burden is a subscription-shaped problem. CAVEAT (hypothesis): SCAAP appropriations have been politically contested in past budget cycles; program continuation each year is likely but not guaranteed and must be verified before committing.
Converging signals
Three signals meet: (1) an annual federal reimbursement program with a hard close date (FACT: grants.gov 362366); (2) a defined applicant class — states, counties, municipalities operating correctional facilities (inference from program design); (3) a data-assembly burden rooted in jail management systems the founder can integrate against. Adjacent evidence shows the reimbursement-paperwork pattern is systemic: OVW's Special Tribal Criminal Jurisdiction Reimbursement Program closes the same day (FACT: grants.gov 362683), and DHS/FEMA reimbursement awards to states run into the billions (FACT: USAspending 4834DRFLP00000001), meaning the same 'extract records → justify reimbursement' engine has replication targets.
Customer pain
A county wanting SCAAP money must produce a clean file of eligible inmates — names, birth dates, custody dates, foreign-born/immigration-status indicators — filtered to the eligibility window and offense criteria, plus correctional-officer salary figures (inference from program structure). Jail management systems (Tyler, Spillman, eOMIS, etc.) don't emit this natively; someone hand-builds queries and spreadsheets annually, or the county pays a contingency consultant a cut of the recovery, or the county simply doesn't apply and leaves the money on the table (hypothesis — validate by interviewing 5 sheriff's-office grant coordinators).
Who pays
County sheriff's offices, county finance/grants departments, and city/state corrections agencies that apply for SCAAP — plus the contingency consultants themselves as a channel (white-label the extraction tool to them). Purchases in the $1-5k range typically fall under small-purchase thresholds, avoiding formal RFP procurement (hypothesis, but consistent with government micro-purchase norms).
Solved today
Hypothesis pending verification: larger counties use contingency-fee claim consultants (Justice Benefits, Inc. is the known incumbent in federal-reimbursement claiming for local governments, historically taking a double-digit percentage of recovery); mid-size counties assign it to a grants coordinator with SQL help from IT; small counties often skip applying because the expected check doesn't justify the labor.
Why current solutions are bad
Contingency consultants take a meaningful percentage of a reimbursement that is already prorated pennies-on-the-dollar (SCAAP historically pays a fraction of claimed costs — hypothesis, verify payout ratios in BJA award data). Manual extraction is error-prone: eligibility hinges on exact custody-day counts and status fields, and validation errors reduce the award. Non-applicants forgo free money entirely. A flat-fee tool that does the extraction and validation converts a percentage tax into a fixed cost and lowers the effort barrier enough to expand the applicant pool.
Proposed product
SCAAP Claim Assembler: (1) importers for the common jail-management-system export formats (start with CSV/report exports, not live API integrations — every JMS can dump a roster report); (2) an eligibility-validation engine encoding SCAAP rules (custody-day windows, offense criteria, foreign-born indicators, 4-consecutive-day threshold — encode from the official solicitation); (3) a salary-data worksheet; (4) output formatted exactly to the BJA/JustGrants submission template, with an exception report listing records needing human review. Founder or a part-time contractor offers a done-with-you service tier the first cycle to learn the edge cases.
MVP version
A pipeline that ingests a jail roster CSV export + booking/release dates + country-of-birth field, applies the FY25 eligibility rules from the posted solicitation, and emits (a) the inmate-record file in submission format and (b) a flagged-exceptions list. Test against one friendly county's data. No JMS integrations, no portal automation in v1 — the county uploads the output themselves.
30-day build
Download the full FY25 SCAAP solicitation and prior-year application instructions; encode the eligibility rules. Pull BJA's public list of prior SCAAP awardees (award data is public) to build the exact prospect list with historical award amounts — this is the sales list, sorted by check size. Interview 5-8 grant coordinators at mid-size counties that applied this cycle: what did the extract cost them, who did it, would they pay $1-3k flat.
60-day build
MVP working against sample/synthetic jail data; recruit 2-3 design-partner counties from the awardee list (pitch: 'flat $1.5k next cycle, we do the extract, you keep 100% of the award'). Approach 1-2 regional claim consultants about white-labeling. Verify FY26 program funding status in the DOJ budget.
90-day revenue plan
Pre-sell FY26-cycle filings at $1-3k flat (paid pilot deposits or PO commitments) to 5-10 counties off the awardee list; sell an off-cycle 'SCAAP recovery audit' ($500-1k) that estimates what a non-applying county left unclaimed using its own roster data — that product monetizes immediately without waiting for the filing window.
Distribution path
The prospect list is public: every prior SCAAP awardee and its award amount is in DOJ/USAspending records — direct outreach to sheriff's-office grants contacts with their own historical numbers ('you recovered $X; here's what the extract should cost'). Secondary channels: state sheriffs' associations, NACo, county grant-coordinator listservs, and white-label deals with claim consultants. This is demonstrated-value selling, not relationship selling — the audit report IS the pitch.
Pricing hypothesis
$1,500-3,000 flat per annual filing depending on facility count; $500-1,000 one-time recovery audit for non-applicants; optional $200/yr data-readiness monitoring. 200 county filings at $2k = $400k/yr recurring on an annual compliance rhythm.
Technical difficulty
Low-to-moderate and squarely in the founder's lane: CSV/report parsing, deterministic eligibility rules, output formatting, plus AI-assisted mapping of heterogeneous JMS export schemas. The hard part is rule fidelity and messy data, not engineering scale. His FMCSA ELDT portal product is the same shape one notch simpler (that was submit-on-behalf; this is prepare-for-submission, with portal automation as a later upgrade).
Legal / regulatory risk
Handling inmate records including immigration-status indicators is sensitive data — needs a data-handling agreement with each county, encryption, and retention limits; CJIS-adjacent expectations may apply if data includes criminal-history fields (hypothesis — scope the data fields to avoid CHRI where possible). Political risk is real: SCAAP touches immigration politics and the program has faced elimination proposals; also some jurisdictions decline to participate for policy reasons. No license required for the founder himself.
Platform dependency
Dependent on SCAAP being funded annually and on BJA's submission format staying stable — a real but government-shaped risk (formats change slowly and publicly). No commercial platform can deplatform this. Mitigation: the same roster-extraction engine points at other reimbursement programs (OVW tribal reimbursement, FEMA public assistance) if SCAAP dies.
Founder fit
Near-maximal. This is precisely his proven pattern: federal program compels/incentivizes a defined class to submit structured data to a government system; he builds the data-assembly layer and charges per transaction. Adds his public-records strength (mining the awardee list for prospects) and operational credibility with sheriff/corrections buyers, adjacent to his fire-service background. The applied lesson 'government-portal mandate opportunities fit this founder best' (confidence 0.79) matches, with one honest deviation: SCAAP filers are incentivized (money-seeking), not compelled — slightly weaker than a true forced-filer class.
Breakout potential
The wedge generalizes: 'reimbursement-claim assembly from operational system exports' applies to FEMA Public Assistance (billions in awards per the USAspending evidence), OVW tribal reimbursement, Medicaid administrative claiming, and state-level inmate-cost recovery programs. Win 100+ counties on SCAAP and the same buyer owns the FEMA PA paperwork problem after every declared disaster.
Final recommendation
PURSUE-WITH-GATE. The shape is the founder's proven money-maker and the prospect list is literally published with dollar amounts attached. But run the two-week kill test first: (1) FY24/FY25 awardee distribution — need ~400+ jurisdictions with awards large enough to justify $1.5-3k flat; (2) five buyer interviews confirming the extract is painful and consultant fees rankle; (3) FY26 funding signal. If all three pass, build the MVP and pre-sell against the FY26 cycle while monetizing the recovery audit immediately.
Next action
Pull the most recent SCAAP award list from BJA/USAspending (public), sort by award size, and call five grant coordinators at $50k+ counties this week to ask exactly how they produced the inmate file this cycle and what it cost them.