What changed
FACT: On 2026-05-20 ED filed a PRA notice proposing an EXTENSION WITHOUT CHANGE of the currently approved ED-524 Budget Information (Non-Construction Programs) information collection (FedReg 2026-10100). INFERENCE: nothing about the form or obligation actually changes — this is a routine OMB re-clearance, not a new or altered mandate.
Why now
Weak. Honest read: there is no 'now.' The notice is an unchanged extension with no stated deadline and no new burden. The ED-524 has been a required attachment in non-construction ED discretionary applications for years; this filing creates no fresh urgency and no compliance cliff.
Converging signals
The regulation (ED-524 required in every non-construction ED discretionary app), the filer class (LEAs, districts, non-profits, universities), and the portal (Grants.gov / ED G5) do meet at one point — the classic forced-filer shape. But the meeting point is a generic, stable budget attachment, not a novel obligation.
Customer pain
HYPOTHESIS (not evidenced in input): grant applicants and grant writers make arithmetic/category errors on multi-year ED-524 budgets, and rejected or returned applications are costly. No complaint threads, job postings, or spend evidence were provided to confirm this pain or willingness to pay specifically for an ED-524 helper.
Who pays
Grant writers, small LEAs/nonprofits without dedicated grant staff, and grant-consulting shops — the parties assembling the application package.
Solved today
Grants.gov already provides the official fillable ED-524 form free; applicants also use Excel templates, grant-management SaaS (Instrumentl, Submittable, GrantHub, Fluxx), and paid grant consultants who bill for the whole package.
Why current solutions are bad
Free fillable form does no cross-year/category total validation and no narrative scaffolding; Excel is error-prone. But this is a mild annoyance, not a forced spend — the buyer can complete the free form.
Proposed product
A focused ED-524 builder: enter object-class categories and multi-year figures, auto-validate that Section A totals reconcile to Section C multi-year totals, flag disallowed/mismatched categories, generate the budget narrative skeleton, and export the exact ED-524 PDF for upload to Grants.gov.
MVP version
Single-page web app: ED-524 A/B/C data model, live total/reconciliation validation, PDF export matching the official form. 2-3 weeks solo.
30-day build
Ship the builder + validator + PDF export; publish an SEO page 'ED-524 budget builder' and template freebies to capture grant-writer search traffic.
60-day build
Add saved projects, multi-user for consulting shops, and a paid tier; test pricing with grant-writer communities (r/grants, grant-writing FB groups, LinkedIn).
90-day revenue plan
Convert free-tool users to a $19-39/mo subscription or per-application fee; realistic first revenue is modest and slow given free alternatives and no deadline pressure.
Distribution path
SEO on 'ED-524' and grant-budget terms, grant-writing communities, and partnerships with grant-writing consultants. Buyer is dispersed (thousands of small orgs) with no single reachable list — a real weakness.
Pricing hypothesis
$19-39/mo micro-SaaS or $15-49 per exported application; percentage-of-award pricing is not defensible here.
Technical difficulty
Low. Deterministic budget math and PDF generation; no portal API integration is even available (Grants.gov ingests the attachment).
Legal / regulatory risk
Low. No submission-on-behalf-of, no licensure required.
Platform dependency
Low — exports a PDF the user uploads themselves; not deplatformable.
Founder fit
Partial. It is the government-portal/forced-filer SHAPE he wins at, BUT unlike his ELDT app there is no per-filing submission automation to own (no ED-524 API — the applicant uploads the attachment), so the per-transaction moat that made ELDT strong is absent. It degrades to a budget calculator competing with a free official form.
Breakout potential
Only as a wedge into a broader ED/federal grant-application assembly suite (full SF-424 family, R&R budgets, cross-agency). Standalone ED-524 is a feature, not a company.
Final recommendation
BORDERLINE / REVISIT LATER. Do not build as a standalone product. This is the right forced-filer shape but a weak instance: free official form, no change, no deadline, no submission-automation moat, dispersed buyers. Keep it as one module in a larger federal-grant-assembly tool, and prioritise mandates where a portal actually accepts an API submission (his true ELDT-style edge) or where a rule genuinely CHANGES.
Next action
Do NOT start a build. Instead filter the ED FedReg feed for type=RULE/PRORULE (not PRA notices), and hunt for an ED or state grant program where subrecipients must submit periodic performance/financial reports to a portal that exposes an API — that shape carries the per-filing monetisation this one lacks.