What changed
FY23 VOCA Victim Assistance formula awards landed on state administering agencies — $18.2M to a state Justice & Public Safety Cabinet, $77.8M to NY OVS, $87.9M to FL Legal Affairs, $34.6M to VA DCJS, and more (FACT, USAspending award records). The award text itself states these funds 'are typically competitively awarded by the state to local community-based organizations that provide direct services to crime victims' (FACT) — i.e., the federal award names the downstream filer class explicitly.
Why now
Money is already appropriated and sitting at state agencies; it must be pushed out via competitive subaward cycles on state timelines. Every award cycle creates two paperwork events: the competitive application, and then quarterly subrecipient performance (OVC PMT) plus state fiscal reporting for winners (application competition is FACT from award text; quarterly cadence is a well-grounded inference from OVC PMT program structure, not proven in the source text). Additionally, Crime Victims Fund deposits have been declining industry-wide (HYPOTHESIS, not in sources), which intensifies competition per dollar — making application quality more valuable, not less.
Converging signals
Three signals meet: (1) recurring multi-million formula awards to every state's administering agency across FY20–FY23 (FACT, 19 USAspending citations in evidence); (2) a filer class named in the award text — local community-based victim-services orgs (FACT); (3) a known reporting apparatus (state portals + OVC PMT) that subrecipients must feed (inference). Per the mandate-shape rule: rule + filer class + portal = convergence, even though it is unglamorous.
Customer pain
Small victim-services nonprofits (shelters, CACs, rape crisis centers, legal advocates) run on thin admin budgets. The ED or a program manager writes the VOCA subaward application nights and weekends, then — if they win — owes quarterly PMT performance counts, demographics, match documentation, and state fiscal reports. Losing an application can mean layoffs; a late or bad report can mean clawback or non-renewal. No PAIN-type evidence (complaints/forums) was provided, so the pain narrative is inference from the mandate structure, not from observed complaints — flagged honestly.
Who pays
The subrecipient nonprofit (ED or grants manager) pays: per-application fee ($200–500) at application season, then $99–150/mo reporting subscription after award. Secondary buyer: the small grant-consultant shops that serve multiple nonprofits (sell them a multi-client seat). VOCA subawards generally permit reasonable admin costs, so the tool can be charged to the grant itself (HYPOTHESIS — verify allowability per state).
Solved today
Word docs, spreadsheets, and institutional memory; some hire grant writers ($75–150/hr or 3–5% of award — HYPOTHESIS, standard consulting rates, not in sources). Larger orgs use general grant-management suites (Foundant, AmpliFund) that are org-wide systems, not VOCA-application-specific and not PMT-aware. State agencies use eCivis/AmpliFund on the funder side, which does nothing to help the applicant write a winning application or assemble PMT counts.
Why current solutions are bad
Generic grant software doesn't know VOCA: it can't pre-map a state's subaward questions, doesn't encode the 4 VOCA priority categories or match requirements, and doesn't roll service-episode counts into PMT's exact quarterly format. Consultants are episodic and expensive relative to a small subaward. The result is a class of compelled filers doing bespoke paperwork with commodity tools.
Proposed product
Two-sided micro-SaaS: (1) Application Assembler — intake wizard that captures the org's programs, service counts, budget, and match, then generates a state-specific VOCA subaward application draft (narrative + budget forms) mapped to that state's actual RFP questions; (2) Report Autopilot — winners log services in a dead-simple tracker (or CSV import from their case-management system) and the tool assembles quarterly PMT-format performance numbers and state fiscal report drafts, with deadline reminders. Start with ONE state (the $18.2M cabinet award state), replicate the template across 50 near-identical markets.
MVP version
Single-state wedge: scrape that state's current VOCA subaward RFP and forms; build the intake-wizard → application-draft generator (Claude-assisted narrative + budget spreadsheet output) plus a quarterly PMT worksheet generator. No portal write-integration needed at MVP — output is upload-ready documents and numbers, which sidesteps any unauthorized-access question. 4–6 weeks solo with AI-assisted build.
30-day build
Pull the target state's subrecipient list (public award lists / state agency site) — this is the exact customer list. Interview 5–8 EDs from it. Build the single-state assembler against the live RFP. Pre-sell 10 application-season slots at $250 to validate willingness to pay before the code is done.
60-day build
Ship MVP to pre-sold users during the state's application window; add the PMT quarterly worksheet module; collect win/loss data as marketing ammunition ('drafted in 3 hours, not 3 weekends'). Begin outreach to the state victim-services coalition (every state has one — DV/SA coalitions are the natural channel).
90-day revenue plan
Convert application customers to $99–150/mo reporting subscriptions as award notices land; open state #2 and #3 by cloning the RFP mapping (each state is ~1–2 weeks of form-mapping work). Target: 30–50 paying orgs = $3–7k MRR + application-season fees within ~120–180 days, timed to state cycles.
Distribution path
Direct and list-based, no ad spend: public subrecipient award lists per state (named orgs = named buyers), state DV/SA coalitions and children's advocacy chapters (one warm intro reaches dozens of members), grant-writer/consultant partnerships (white-label seat), and content SEO on '[State] VOCA grant application' which has near-zero competition (HYPOTHESIS).
Pricing hypothesis
$250 per application draft (season revenue), $99–150/mo report autopilot (recurring), $500/mo multi-client tier for consultants. Anchor against a grant writer's $2–5k per application; undercutting consultant spend with software is the wedge.
Technical difficulty
Low-moderate. Document generation, form mapping, a simple service-count tracker, CSV import. No government API integration required at MVP (output is upload-ready), so the hardest part is acquiring each state's RFP forms and keeping them current — a maintenance moat once built, since no incumbent will hand-map 50 states' VOCA forms for a niche this size.
Legal / regulatory risk
Low. No client PII beyond aggregate service counts is strictly needed for PMT (design to keep victim-level data OUT of the system — accept only aggregates/CSV counts to avoid VAWA/VOCA confidentiality exposure; taking case-level victim data would change the risk profile materially). No license required to prepare grant documents.
Platform dependency
None that can deplatform: outputs go to state portals and PMT, which have no platform owner. Dependency is on states not radically changing forms — which creates recurring update work, not existential risk.
Founder fit
Maximal under the stated thesis. This is structurally identical to his shipped ELDT/TPR business: a government program compels a defined class to submit paperwork on a cadence; he builds the assembly/submission layer and charges per transaction plus subscription. Public-records skill applies directly (subrecipient lists ARE the lead list). Fit lesson (confidence 0.79) applies and is corroborated by the shipped comparable.
Breakout potential
50-state replication of the same template, then horizontal spread to adjacent DOJ formula streams flowing through the SAME state agencies and often the SAME nonprofits — STOP/VAWA ($14.3M and $14.1M awards in evidence, FACT) and byrne/JAG — turning one wedge into a state-subaward reporting platform for small nonprofits.
Final recommendation
PURSUE as a top-tier candidate. It survives the kill attempt: the buyer exists and is named (public subrecipient lists), the money is appropriated (FACT, 19 award citations), the paperwork is compelled and recurring, no incumbent serves the subrecipient side of VOCA specifically, and it is a near-clone of the founder's proven ELDT model. The genuine risks — nonprofit price sensitivity and a shrinking VOCA pool — are testable within 30 days for under $500 by pre-selling application slots off a public subrecipient list before writing significant code. Validate willingness-to-pay first; build second.
Next action
Pick the $18.2M cabinet state, download its current VOCA subaward RFP and its public list of current subrecipients, and email/call 10 of them this week offering a $250 application-draft pilot for the next cycle — pre-sales, not conversations, are the go/no-go gate.