What changed
USDA-NRCS posted the FY26 RCPP Classic NOFO (opp # USDA-NRCS-NHQ-RCPP-CLASSIC-26-NOFO000145) and the parallel Alternative Funding Arrangements NOFO (USDA-NRCS-NHQ-RCPP-AFA-26-NOFO0001451), both CFDA 10.932, both closing 08/24/2026 — FACT per Grants.gov listings 362909 and 362910. This opens the annual application window for a program at roughly $1.5B/yr scale (inference from prior Farm Bill funding levels, not stated in the source text).
Why now
Two NOFOs are live simultaneously with a hard statutory close date ~6 weeks out (from 2026-07-11). Every prospective partner org is in proposal-assembly mode RIGHT NOW, and every FY25 awardee is entering the award-administration phase where RCPP's paperwork burden is heaviest. The deadline sets the sales calendar: a proposal-assembly tool is sellable this month; the post-award module is sellable to the awardee cohort announced later this year.
Converging signals
Three signals meet at one point: (1) a recurring federal money faucet (RCPP Classic + AFA NOFOs, FACT), (2) a defined filer class — conservation districts, land trusts, ag NGOs, state agencies — who must apply through Grants.gov/the NRCS RCPP portal and then carry multi-year reporting (class named in the NOFO; the administration burden is inference), and (3) the founder's proven pattern of building the submission/paperwork layer against a government program and charging per transaction (FMCSA ELDT precedent).
Customer pain
HYPOTHESIS grounded in program structure: RCPP is widely described by practitioners as the most administratively burdensome NRCS program — partners must negotiate supplemental agreements, track technical-assistance dollars, document every enrolled producer's contracts and practices, and file annual performance + financial reports across a 5-year award. The provided sources prove the mandate and the filer class; they do not contain direct complaint threads, so the intensity of pain is inferred, not evidenced.
Who pays
Primary: partner organizations (conservation districts, land trusts, watershed groups, ag NGOs, state ag/conservation agencies). They can pay from grant TA/admin allowances — meaning federal money itself funds the software line item. Secondary later: the consultants who write RCPP proposals for multiple clients (one consultant = many proposals = leveraged distribution).
Solved today
Word/Excel templates, institutional memory at larger land trusts, and grant consultants who charge fixed fees or a share of the award to write proposals and manage reporting. Generic grant-management SaaS (AmpliFund, eCivis, Submittable) handles the money side but has no RCPP-specific proposal logic, producer-enrollment tracking, or NRCS report formats — HYPOTHESIS based on their public positioning, not verified in the provided sources.
Why current solutions are bad
Generic tools don't know RCPP's structures (supplemental agreements, producer contracts, TA vs FA dollars, the RCPP portal's proposal sections), so partners re-derive them every cycle. Consultants are proof of spend but expensive and don't scale to the annual re-application rhythm. A first-time applicant faces a NOFO of enormous length with no software scaffold at all.
Proposed product
An RCPP-specific back office in two stages. Stage 1 (pre-deadline): a proposal assembler that walks a partner through the FY26 NOFO section-by-section, enforces eligibility/budget rules, generates the narrative skeleton and budget tables in the portal's expected structure, and produces a submission-ready package. Stage 2 (post-award): producer-enrollment tracker (contracts, practices, acres), TA/FA dollar ledger, and one-click generation of the annual performance and financial reports NRCS requires. Note honestly: this is document/package assembly, not automated portal submission — the NRCS RCPP portal has no public submission API (inference), so the wedge is preparation and generation, with the customer doing the final upload.
MVP version
A guided web app (FastAPI + LLM-assisted drafting) encoding the FY26 Classic NOFO's sections, eligibility rules, and budget structure, outputting a complete proposal package (narrative docx + budget xlsx) matching portal requirements. Buildable solo in 3-4 weeks because the NOFO itself is the spec.
30-day build
Week 1-2: parse both NOFOs (362909, 362910) into the assembler's rule set; build package generator. Week 2-3: get 5 design-partner calls via state conservation-district associations and NACD/Land Trust Alliance member lists; offer the assembler free-or-cheap to 3 partners applying this cycle in exchange for testimony. Week 3-4: launch at a per-proposal price with the 08/24 deadline as the urgency engine.
60-day build
Convert the pre-deadline surge; capture every applicant (funded or not) into a list. Begin Stage 2 build against the actual reporting artifacts design partners share (supplemental agreement templates, prior annual reports). Publish an 'RCPP FY26 application field guide' as SEO/distribution flywheel.
90-day revenue plan
Awards announced → sell the award-administration subscription to the new awardee cohort plus existing FY24/FY25 partners mid-award (they carry the same reporting burden for 4 more years). Per-seat/per-award subscription is the durable revenue; the proposal assembler re-arms every year when the next NOFO drops.
Distribution path
Direct and demonstrable: state associations of conservation districts, NACD, Land Trust Alliance, watershed-group networks — small, listable, reachable universes. Past RCPP awardee lists are public (USAspending/NRCS announcements), giving a literal named-account target list. Sell through a working demo against the live NOFO, which matches the founder's demonstrated-value style.
Pricing hypothesis
$750-1,500 per assembled proposal (versus consultants charging thousands or a percentage); post-award: $200-400/mo per active award for the 5-year administration module. A partner with a multi-million-dollar award will not blink at $3-5k/yr that comes out of admin allowance.
Technical difficulty
Low-moderate: NOFO parsing, structured document generation, a CRUD tracker for producers/contracts, and report templating. No portal API integration required for v1. Well inside solo + AI-assisted range.
Legal / regulatory risk
Low. Preparing grant packages is not regulated activity; the customer submits under their own credentials. Avoid representing outcomes ('we get you funded'). No license required — compliance is the product, not a burden on the founder.
Platform dependency
Dependent on RCPP continuing to be funded and the NOFO recurring annually — a Farm Bill/appropriations risk, not a platform-owner risk (no one can deplatform a tool that outputs documents for a government process). The FY26 NOFOs being posted is the current-cycle guarantee; note the adjacent RCDI recission (FedReg 2026-13397) as evidence USDA can pull funding opportunities, so single-program concentration is the real long-term risk.
Founder fit
Very high. This is exactly the FMCSA ELDT shape: federal program → defined filer class → paperwork layer → per-transaction fee, plus a recurring annual cycle and a 5-year post-award tail the ELDT product lacked. Ag/land/operations subject matter suits his industrial-operations credibility; buyers are practical field organizations, not procurement committees.
Breakout potential
Strong horizontal expansion: the same partner orgs handle EQIP, CSP, CIG, state cost-share programs — each is another module. 'Back office for conservation-program partners' is a defensible niche category with hundreds of orgs and 5-year retention mechanics; a $1-3M ARR solo/small business is plausible without VC.
Final recommendation
PURSUE, with a staged commitment. Ship the FY26 proposal assembler in 3 weeks and treat this cycle as a paid discovery exercise: if 3+ partners pay for assembled proposals by 08/24/2026, the demand hypothesis is validated and the post-award subscription (the real business, 5-year tail, forced reporting) is worth the full build. If zero partners pay despite the live deadline, kill it before investing in Stage 2. The deadline conveniently makes this a fast, cheap, self-terminating test.
Next action
Today: download both NOFOs from Grants.gov (362909, 362910), extract the full proposal structure and post-award reporting requirements, and pull the FY24/FY25 RCPP awardee list from NRCS announcements to build the named-account outreach list; book 5 partner-org calls this week.