What changed
A final USDA rule (Fed. Reg. 2026-13878, effective 2026-07-09) makes previously-ineligible losses claimable and raises rates: unborn livestock, bird depredation, and drought below prior thresholds now qualify under the Supplemental Disaster Assistance / ELAP-LIP-family programs.
Why now
The eligibility expansion is fresh and, per the convergence framing, 'most won't know the criteria changed'; simultaneously frontier reasoning models (GPT-5.6-class) plus one-call structured-extraction APIs (Context.dev) make it economical to assemble many small, tedious claims that human ag consultants won't touch.
Converging signals
money (new USDA rule expands claimable losses) × ai (cheap capable reasoning per task) × dev (structured extraction of scattered vet bills / geotagged photos / herd & spray logs into a filing packet).
Customer pain
HYPOTHESIS — demand_evidence is empty. The pain is inferred: producers have documentable losses that just became payable, don't know the criteria changed, and won't self-navigate FSA paperwork. No complaint threads, job ads, or forced-filer mandate were provided to confirm willingness to pay.
Who pays
Farmers and ranchers themselves (beneficiary = buyer), on contingency (a % of recovered FSA payment) or a flat per-claim prep fee.
Solved today
FSA county offices assist producers with these applications for FREE; crop-insurance agents, farm-program consultants, and extension agents also help. Producers who know the program file directly.
Why current solutions are bad
Free FSA help requires the producer to already know they qualify and to show up with organized documentation; the newly-eligible categories are obscure and county staff are stretched — so eligible losses go unclaimed out of unawareness, not because filing costs money.
Proposed product
An eligibility wizard encoding the new loss categories + documentation rules, feeding a guided intake that ingests vet bills, geotagged photos, and herd/spray logs via a structured-extraction API and auto-assembles the FSA claim packet + loss narrative; operator files and takes a cut or flat fee.
MVP version
Wizard for the 3 newly-eligible categories + a doc-intake that turns photos/receipts/logs into a completed FSA packet + narrative for one program; run manually behind the scenes for the first cohort.
30-day build
Encode the rule's newly-eligible categories and evidence requirements; validate that paid third-party claim preparation is permitted (no SSA-style bar); interview 15 ranchers in a recent disaster county for the kill test.
60-day build
Build guided intake + structured-extraction pipeline; assemble packets for the first cohort; establish a referral relationship with a vet clinic, feed store, or county cattlemen's association for lead flow.
90-day revenue plan
File 10 real claims end-to-end, refine on FSA kickbacks, collect first contingency/prep-fee revenue, and template the flow to replicate into adjacent disaster counties.
Distribution path
Local/vertical: cattlemen's & farm-bureau associations, feed stores, large-animal vets, county disaster-declaration lists, ag Facebook groups. NOT a self-serve SaaS motion — it is trust-mediated outreach in tight rural networks.
Pricing hypothesis
Contingency 15-25% of recovered payment, or flat $150-400/claim prep fee; bundle multiple loss categories per producer to lift claim size.
Technical difficulty
Low-moderate: the AI/extraction stack is off-the-shelf; the hard part is correctly encoding evolving FSA program rules and handling documentation edge cases FSA rejects.
Legal / regulatory risk
Moderate/unresolved: paid third-party representation before FSA must be confirmed permissible; contingency fees on federal benefits can be restricted in some programs. Holding vet/herd records is modest PII. Never imply guaranteed payment.
Platform dependency
None reputationally risky — files into a government system, no platform owner to deplatform; but wholly dependent on USDA/FSA program rules and forms, which change.
Founder fit
Fits the claimable-money thesis and public-records/AI-workflow strengths, and the fire-service/rural credibility helps. BUT it is a contingency SERVICES business sold trust-first to individual farmers — closer to relationship sales than the founder's preferred demonstrated-value, self-serve motion, and not the clean per-filing forced-buyer SaaS shape of his FMCSA win.
Breakout potential
Moderate: 50-state/multi-county replication and a white-label tool for existing farm-program consultants is the real scale path, not direct-to-farmer contingency.
Final recommendation
WEAK-CONDITIONAL. Do NOT build yet. Run the 15-rancher kill-test and the paid-representation legality check FIRST; only proceed if a third have documentable, fee-worthy losses AND paid contingency prep is clearly permitted — and even then, prefer a white-label tool sold to ag consultants over direct-to-farmer contingency.
Next action
Interview 15 producers in a county with a recent disaster declaration to measure documentable newly-eligible loss rate and willingness to pay a cut, and confirm FSA rules on paid third-party claim preparation.