What changed
OMB published a proposed rule (Federal Register, 2026-05-29, doc 2026-10817) revising the Guidance for Federal Financial Assistance (Uniform Guidance, 2 CFR 200) to 'improve transparency, accountability, and oversight for Federal awards' (FACT from the FR abstract). Law-firm coverage (Ropes & Gray) is already briefing award recipients on what changes (FACT from headline). The rule is PROPOSED, not final — but the underlying duty it revises, pass-through subrecipient risk assessment and monitoring under 2 CFR 200.332, is existing binding law today (inference from UG structure, high confidence).
Why now
Every UG revision cycle forces tens of thousands of recipients to re-check their compliance posture, and law firms/consultants are already publishing client alerts — that alert traffic is the free marketing wave to ride. Critically, the product does NOT depend on the proposed rule finalizing: pass-throughs are already liable for subrecipient monitoring under current 200.332, so the rule is an urgency trigger, not the legal basis. If the rule finalizes, every template and policy document in the market goes stale at once — a rare displacement window against incumbents.
Converging signals
(1) A government-wide rule change (OMB proposed revision, FACT); (2) a defined compelled class — every pass-through entity: states, municipalities, school districts, nonprofits, universities (FACT from FR scope); (3) an existing paperwork obligation with named artifacts — risk assessments, monitoring documentation, single-audit trail feeding the Federal Audit Clearinghouse (inference from UG structure). Rule + filer class + portal is the forced-filer convergence shape. Note: two of the retrieved demand items (CFPB FCRA preemption, Reg B 1071) are semantically similar but off-topic and were disregarded.
Customer pain
A grants manager at a small county receiving, say, an opioid-settlement or CDBG pass-through must risk-assess every subrecipient, document monitoring, chase subaward reports, and survive a single audit — typically with spreadsheets, Word templates, and one overloaded person. The pass-through is directly liable for subrecipient noncompliance (FACT stated in the convergence input); audit findings are public and career-damaging. This is a FORCED BUYER: they cannot opt out and the single-audit deadline recurs annually.
Who pays
Primary: grants/finance managers at small pass-through entities (small cities, counties, state program offices, mid-size nonprofits acting as pass-throughs). Secondary: the CPA firms and grant consultants who serve them (channel + white-label). The single-audit universe is ~35,000 entities/yr (inference, stated in input as inference — verify against FAC data, which is public). These buyers can often purchase sub-$10k software under micro-purchase thresholds without formal procurement.
Solved today
Excel trackers, Word-template risk assessments, email-chased subaward reports; consultants billing hourly or a percentage of the award; at the high end, enterprise grants-management suites (eCivis/Euna, AmpliFund) priced and implemented for large agencies.
Why current solutions are bad
Spreadsheets produce exactly the inconsistent, undated, unauditable trail that single auditors write findings about. Enterprise suites cost $20k-$100k+/yr with months of implementation — small pass-throughs with 5-40 subawards can't justify them. Consultants are proof of spend but don't leave a living system behind. A UG revision makes every static template stale simultaneously.
Proposed product
A focused subrecipient-monitoring workspace: (1) risk-assessment questionnaire engine producing the documented, dated assessment 200.332 requires, auto-scored to a monitoring plan; (2) subaward register with reporting-deadline calendar and automated report-chasing emails to subrecipients; (3) document vault assembling the single-audit-ready monitoring file per subaward; (4) an AI layer (founder strength) that drafts monitoring letters, flags stale documents, and maps requirements to the current vs. revised UG text so customers see exactly what changes if the rule finalizes.
MVP version
Risk-assessment builder + subaward deadline tracker + evidence folder with export-to-audit-binder (PDF/zip). Skip integrations entirely; ingest subaward lists via CSV. Build on the founder's existing FastAPI/Postgres stack. A free 'UG revision redline + updated risk-assessment template' lead magnet ships in week 2 to start list-building immediately.
30-day build
Ship the lead magnet (redlined 200.332 template pack keyed to the proposed rule) and a landing page; post it where grants managers live (NGMA, GFOA lists, state grant-management associations, r/nonprofit, LinkedIn grants groups). Interview 10 grants managers from FAC's public single-audit database — entities with prior subrecipient-monitoring findings are a pre-qualified list of buyers with documented pain. Build the risk-assessment engine.
60-day build
MVP live with 3-5 design partners at $0-99/mo from the finding-flagged list. Add deadline calendar + chaser emails. Publish 'single audit findings by state' content from FAC data for SEO — the founder's public-records skill applied as marketing.
90-day revenue plan
Convert design partners to paid ($150-400/mo by subaward count); direct outreach to the FAC-derived list of pass-throughs with recent 200.332-adjacent findings ('your FY25 audit had a subrecipient-monitoring finding — this closes it'). Offer CPA firms a reviewer seat to become a channel. Target: 10-15 paying entities ≈ $2-5k MRR by day 120-150.
Distribution path
FAC public audit data as a targeting engine (entities with findings = warm list); UG-revision content wave (comment-period deadlines generate recurring news); NGMA/GFOA communities and webinars; CPA single-audit firms as channel partners. Demonstrated-value sales: the free redline/template pack proves competence before the pitch — matches the founder's no-relationship-sales style.
Pricing hypothesis
$150-400/mo tiered by active subawards (a 20-subaward county at ~$3k/yr undercuts one consultant-day); optional $500 one-time 'UG revision readiness' assessment as a paid trial. Per-subaward pricing mirrors the founder's proven per-upload ELDT model.
Technical difficulty
Low-moderate: forms, scheduler, email, document storage, PDF export — squarely within a solo AI-assisted build. No government portal API integration is required for v1 (monitoring documentation is kept by the pass-through, not submitted to a portal), which removes the hardest dependency but also removes the per-filing toll-booth of his ELDT model — revenue is subscription, not per-transaction.
Legal / regulatory risk
Low. The tool documents compliance; it does not practice law or file on anyone's behalf. Standard disclaimer that templates are not legal advice. No license required for the founder.
Platform dependency
None. No app store, no platform owner, no government API gatekeeper. FAC data and Federal Register data are public.
Founder fit
High (8/10). This is the proven ELDT shape — read a federal mandate, identify the compelled class, build the paperwork layer, charge them — minus the portal-submission toll booth. Public-records skill (FAC mining) becomes the sales engine. Weakness: he hasn't sold to local-government finance offices before, and this is seat/subscription rather than per-transaction.
Breakout potential
Strong replication path: every federal program and all 50 states' pass-through structures share the same 200.332 duty; adjacencies include single-audit prep, SEFA assembly, and state-specific subrecipient portals (Texas, California OAL-tracked programs). If the OMB rule finalizes, a 'what changed for your entity' engine becomes a one-time land-grab.
Final recommendation
PURSUE, with the discipline that the existing 200.332 obligation — not the proposed rule — is the legal demand base, and the rule is the marketing event. The forced-buyer class is real, defined, and already paying consultants and auditors; the FAC findings database gives a uniquely targetable warm list that most competitors ignore. Cap exposure: 30 days to a lead magnet and 10 buyer interviews before writing serious product code. Kill if interviews show small pass-throughs uniformly defer to their auditor/consultant and won't self-serve.
Next action
Pull the FAC public single-audit dataset, extract entities with subrecipient-monitoring-related findings in the last 2 audit years, and ship the free UG-revision redline/template pack to start the list — both doable this week with existing skills.