What changed
DOE has begun disbursing IRA Section 50121 (HOMES) formula funds to state energy offices — $345,324,713 to the Texas Comptroller and comparable awards to California ($291M), New York ($158M) and others (FACT, USAspending awards cited). The award text states future distributions WILL REQUIRE submission to DOE of Home Energy Rebate Program Plans (FACT). Once states stand up their programs, the money reaches homeowners only through per-home rebate claims that contractors/aggregators must document and file.
Why now
The federal money is now obligated to states (FACT — award dates on USAspending). States are in the plan-submission and portal-standup phase in 2026, which means the downstream per-home claim flow is imminent but not yet saturated with tooling. Building the documentation engine before state portals go live positions the founder as the claim layer when contractors suddenly face a modeling-and-filing burden they've never had.
Converging signals
Three signals meet at one point: (1) a funded federal mandate (IRA 50121, ~$4.3B national pool — FACT for the program, inference for the exact national total); (2) a forced downstream filer class (home-performance contractors/aggregators who must submit modeled-or-measured savings docs — inference from statute); (3) 50 separate but structurally similar state portals, each needing the same calculation and packet assembly.
Customer pain
HYPOTHESIS: HOMES claims require BPI-style modeled energy-savings calculations (modeled path) or measured pre/post consumption analysis (measured path), plus invoices, income verification, and program-specific forms. Small contractors have no in-house energy modeler and no software to produce a compliant packet; getting a claim rejected means the rebate — often the reason the homeowner bought the job — doesn't fund. This pain is inferred from the 50121 statute structure, not from cited complaints (no PAIN or HIRING evidence was provided).
Who pays
Home-performance contractors and rebate aggregators who file per-home claims to a state HOMES portal. Secondarily, the aggregators/program administrators states contract with to process claims. NOT the state procurement office as the only buyer — the reachable buyer is the contractor filing claims.
Solved today
HYPOTHESIS: today contractors use a mix of standalone energy-modeling software (e.g. OptiMiser, Snugg Pro, EnergyGauge), manual spreadsheets, and hand-assembled document packets, then key data into whatever portal the state provides. Energy-efficiency consultants also bill to prepare claims. None of this is verified by the provided evidence.
Why current solutions are bad
HYPOTHESIS: modeling tools compute savings but don't assemble the state-specific compliant claim packet or handle submission; the contractor still stitches documents and re-keys into each state's portal, and each state's forms differ. That gap — calculation-to-compliant-filing-to-submission — is the wedge.
Proposed product
A per-claim SaaS. Contractor uploads audit inputs (or connects their modeling tool's export); the engine runs the required HOMES savings calculation on the modeled or measured path, validates against the state's program rules, assembles the compliant claim packet (savings calc, invoices, income docs, forms), and files it to that state's portal (API where available, assisted/RPA submission where not). Charge per successful filing or a small % of the rebate.
MVP version
Start with ONE state — Texas (the cited $345M award) — modeled path only. Ingest audit data via CSV/manual form, implement the HOMES modeled-savings calculation per DOE guidance, generate the claim packet as a validated PDF/data bundle matching Texas program requirements, and support export-for-manual-upload before building direct portal submission. Sell to 5-10 Texas home-performance contractors.
30-day build
Read DOE HOMES program guidance + the Texas Comptroller SCEP program plan the moment it publishes; map the exact required data fields, the modeled-savings methodology, and the claim packet spec. Interview 10 Texas/CA home-performance contractors to confirm the pain, the current workflow, and willingness to pay per claim. Build the modeled-savings calculation core and a validation harness against DOE's published methodology.
60-day build
Ship the Texas MVP: audit-data intake, savings calc, compliant packet generation, export for upload. Onboard 3-5 design-partner contractors filing real (or test) claims. Instrument rejection reasons and tighten validation. Begin the RPA/API submission layer against the Texas portal as its spec firms up.
90-day revenue plan
Charge per filed claim (design partners live). Prove the packet passes state acceptance. Package the state layer as a config so a second state (California, $291M cited) can be added by swapping rules/forms, not rewriting the engine. Publish a 'HOMES claim compliance' content wedge to pull inbound contractor demand.
Distribution path
Direct to contractors via state home-performance / BPI contractor networks, weatherization trade groups, and DOE-listed program contractor lists as states publish them; content marketing on 'how to file a compliant HOMES claim'; partner with energy-modeling tool vendors as a downstream filing add-on. Demonstrated-value selling (show a completed compliant packet), not relationship sales.
Pricing hypothesis
Per-filing fee (hypothesis: $40-$150/claim given modeling is heavier than 50122's measured-only path) or 2-4% of the rebate as a managed-filing option. Optional per-seat subscription for high-volume aggregators. Undercuts any consultant billing a % to prepare claims.
Technical difficulty
Moderate. The savings calculation must faithfully implement DOE's published methodology (highest-risk component — get it wrong and claims reject). Packet assembly and multi-state rules config are straightforward. Portal submission ranges from easy (API) to RPA-fragile (screen automation) depending on state — mitigate by shipping export-for-upload first.
Legal / regulatory risk
Low-to-moderate. Submitting a homeowner's rebate claim to a state portal means handling income-verification PII (needs proper data handling) and standing behind the accuracy of the savings calculation. This is compliance-as-moat, not a licensing barrier — the founder need not become certified to build the tool. No platform owner can deplatform a government-submission tool.
Platform dependency
None in the deplatforming sense — it submits to government systems. Real dependency is on each state finalizing its portal/forms and DOE methodology; that's schedule risk, not policy risk.
Founder fit
Very high. This is precisely the founder's proven shape: a federal mandate compels a filer class to submit documentation to a government portal, and a solo operator builds the submission/compliance layer and charges per filing — the exact model of his shipped FMCSA ELDT Training Provider Registry app. Systems thinking + government-portal integration + per-transaction monetization all apply directly.
Breakout potential
High. One working state codebase replicates into ~50 structurally similar markets funded by the same statute, plus the adjacent 50123 electrification rebates (HEAR) as a natural second product. The modeled-savings engine is reusable IP.
Final recommendation
PURSUE — high-conviction, but stage it. This is a maximal founder-fit public-money forced-filer play with hard funded-mandate evidence (cited multi-hundred-million-dollar awards across TX/CA/NY). Validate the downstream buyer with 10 contractor interviews in the first 30 days before heavy build, and build modeled-path Texas-only first. Do not build all 50 states speculatively before one state's claims actually open and one contractor pays.
Next action
Pull the DOE HOMES program requirements and the Texas Comptroller SCEP/HOMES program plan, extract the exact modeled-savings methodology and claim data fields, and line up 10 Texas/California home-performance contractor interviews to confirm willingness to pay per claim.