What changed
USAspending shows a $236,822,875 IDEA Part B (611) State Grant awarded to the Arizona Department of Education (FACT, cited). That money is a pass-through: it only reaches districts and charter schools after each LEA files an approvable annual Part B application with maintenance-of-effort (MOE), excess-cost, and proportionate-share documentation through ADE's grants management portal (inference — standard IDEA subgrant mechanics, not verified against AZ-specific rules in the source text).
Why now
The award is live money on a fixed annual application cycle — every AZ LEA must re-file each grant year to draw funds. Arizona is also a distinctive market: it has one of the largest charter sectors in the country (hypothesis), meaning hundreds of small LEAs with no dedicated special-ed finance staff facing the same federal compliance math as big districts. This is explicitly a replication instance of an already-identified IDEA Part B SaaS shape; the identical award exists in TX ($1.15B), CA ($1.38B), IL, GA, MA and others (FACT, cited), so a working AZ instance replicates ~50 times.
Converging signals
(1) $236.8M funded mandate landing on AZ ADE (FACT); (2) a defined compelled filer class — subgrantee LEAs and charters (inference); (3) a known submission surface — the state grants portal (inference); (4) sibling awards in every other state proving the replication path (FACT). Per the system's own heuristic, mandate+filer-class+portal is a full convergence even though it is unglamorous.
Customer pain
An LEA that fumbles MOE fails the test and can owe money back or lose eligibility; excess-cost and proportionate-share calculations are genuinely tricky federal math done annually under deadline. Large districts have grants staff; AZ's hundreds of small charter LEAs typically have a part-time business manager or an outside consultant. NOTE: no direct complaint/PAIN evidence was provided for AZ specifically — the pain description is inference from the mandate structure, and per instructions a FUNDED MANDATE naming a filer class and submission scores on its own basis.
Who pays
The LEA (district or charter) — specifically the business manager / SPED director who is personally on the hook for an approvable application. Secondary buyer: the small consultancies and education service agencies that prepare these filings for multiple charters and would use the tool to serve more clients. Neither is government procurement in the enterprise sense; charter purchases at ~$1-3k/yr typically fall under purchasing thresholds (hypothesis).
Solved today
Spreadsheets, AASBO/ADE training sessions, inherited templates from last year's application, and SPED finance consultants who charge flat fees or percentages (inference — consultant presence in this niche is a hypothesis, though it is the norm in grant compliance generally). The state portal itself is free but is a submission surface, not a preparation/validation tool.
Why current solutions are bad
Spreadsheet MOE math breaks silently when a district's data changes (staff turnover, enrollment shifts); the four MOE test alternatives and exception/adjustment rules are exactly the kind of rule-table logic humans get wrong once a year and software gets right every time. Consultants are expensive relative to a charter's admin budget and don't scale their attention down to a 300-student school.
Proposed product
A web app that ingests an LEA's prior-year expenditure data and current budget, runs all four MOE compliance tests plus eligibility-standard projections, computes excess-cost and proportionate share, flags failures while there is still time to fix them, and outputs a portal-ready application package mapped to ADE's grant application fields. Not a replacement for the state portal — the prep-and-validate layer in front of it, the same relationship his ELDT product has to the federal Training Provider Registry (prep/submit on the customer's behalf).
MVP version
MOE calculator (all four tests + exceptions) and excess-cost worksheet for Arizona's chart of accounts, plus a checklist mapped to the actual ADE Part B application sections, delivered as a guided web flow with an exportable package. Skip portal automation in v1 — the calculations and the field mapping are the value; RPA against the state portal is a later upsell if ADE has no API (likely).
30-day build
Verify the inferences that this brief rests on: pull ADE's actual Part B LEA application (it is public), confirm the portal name and application window, get the real count of AZ LEAs/charters receiving 611 subgrants from ADE's public subgrant lists, and interview 5 charter business managers + 2 SPED finance consultants sourced via the state charter association and AASBO. Build the MOE engine in parallel — the federal tests are state-agnostic.
60-day build
Ship the AZ-mapped MVP. Recruit 3-5 pilot charters at $0-500 for the current cycle in exchange for testimonials and their real prior-year data as test fixtures. Publish a free 'AZ IDEA MOE self-check' single-page calculator as the lead magnet.
90-day revenue plan
Convert pilots and sell into the application-season deadline: 15-25 paying LEAs at ~$1,500-2,500/yr ($25-60k ARR) is the realistic first-cycle target, plus 1-2 consultant/ESA multi-seat licenses. If the season timing misses (the application window is annual — this is the biggest timing risk), revenue slips to the next window and the interim sale is the MOE health-check report at $300-500 one-off.
Distribution path
Deadline-driven direct outreach: the subgrantee list is public record (founder strength), so the entire TAM is an enumerable spreadsheet of ~600 named organizations with known contacts. Channels: Arizona Charter Schools Association, AASBO conference/newsletter, SPED director listservs, and the free MOE self-check tool for inbound. No ad spend, no marketplace approval, no platform gatekeeper.
Pricing hypothesis
$1,500-2,500/LEA/yr subscription tiered by enrollment; consultant/ESA license at $6-10k/yr for multi-LEA use; $300-500 one-off MOE health check as the wedge product. Anchor against consultant fees and against the cost of a failed MOE test (repayment liability).
Technical difficulty
Low-moderate for the founder: deterministic rule-table math, form generation, and eventually portal RPA — squarely his demonstrated ELDT pattern. The hard part is domain correctness (34 CFR 300.203-205 MOE rules), which is buyable via one retained SPED finance consultant as a reviewer — affordable given his capital.
Legal / regulatory risk
Low. He is not touching student PII in v1 (expenditure data only), not becoming a licensed anything, and not submitting on behalf of LEAs until the automation phase. Main risk is giving wrong compliance answers — mitigated by positioning as preparation support with expert-reviewed rule logic, and E&O insurance.
Platform dependency
The dependency is ADE's application format, which changes incrementally year to year — that churn is actually the retention moat (the vendor tracks the changes so the LEA doesn't). No deplatforming risk on a government submission target.
Founder fit
Near-maximal on the system's stated thesis: public money flows to a compelled filer class through a government portal, monetized per seat — the exact ELDT shape he has already shipped and charged for. Public-records skill makes the prospect list free. The one gap: he has no K-12 network, so the first 5 conversations are cold — offset by demonstrated-value selling (the free MOE checker) which is his stated style.
Breakout potential
High for a niche: the same 611 award exists in all 50 states (five sibling awards cited in the evidence), and the federal MOE/excess-cost math is identical everywhere — only the state portal mapping layer changes. 50 near-identical replications at even 20 LEAs/state × $2k is a $2M ARR ceiling without ever entering enterprise sales. Adjacent expansion: Title I comparability and Perkins V share the same LEA-application shape (Perkins award present in evidence).
Final recommendation
PURSUE-WITH-VALIDATION. This is a strong instance of the founder's proven pattern with hard-dollar demand evidence ($236.8M FACT) and an enumerable, reachable buyer list, but it is a replication instance — the correct move is to treat AZ as the beachhead state for ONE multi-state IDEA Part B engine (AZ's charter density makes it the best first market: many small LEAs, weak internal staffing, low procurement friction), not to build an AZ-only product. Gate the build on the 30-day validation: confirm the real application burden and that ADE's free tooling doesn't already solve it.
Next action
Download the current Arizona ADE IDEA Part B LEA application package and the public subgrantee list this week; book 5 charter business-manager interviews via the Arizona Charter Schools Association; simultaneously start the state-agnostic MOE test engine since it is reusable regardless of which state wins the beachhead decision.