What changed
FERC published a Paperwork Reduction Act extension notice for FERC-556 (OMB 1902-0075), the Certification of Qualifying Facility (QF) status collection (FACT, federalregister.gov/documents/2026/07/07/2026-13692). Nothing about the form changed — the notice simply confirms the QF self-certification regime is active and being renewed, i.e. an ongoing, non-discretionary filing obligation for anyone wanting PURPA benefits.
Why now
The PRA renewal is a marker, not a deadline; the real 'why now' is structural: community/commercial solar and cogeneration project starts remain high, and each ≤80MW facility must self-certify QF status (and re-file on material changes) to secure must-buy rates and regulatory exemptions. Every new project in the pipeline is a forced filing event.
Converging signals
Three signals meet at one point: (1) an active federal mandate (PURPA QF self-certification), (2) a defined, growing filer class (small power producers ≤80MW and cogenerators), and (3) a specific government portal (FERC eFiling / Form 556). This is the ELDT archetype — a regulation compels a class to file into a federal portal — which is the founder's single best-fit shape.
Customer pain
Form 556 is deceptively technical: it demands facility technical data (net power production capacity computed per FERC's method, energy input/output for cogen operating-and-efficiency-standards tests, fuel, ownership/upstream-owner disclosure) and is rejected or deficiency-flagged for miscomputed capacity, missing owner detail, wrong facility category, or self-cert vs. recertification confusion. Developers either overpay energy counsel or risk a rejected filing that delays interconnection revenue. (Pain specifics are inference from the form's known structure, not from a cited complaint.)
Who pays
The facility developer pays (stated in the mandate). Best channel buyers: solar EPCs and developers running multi-project pipelines who file repeatedly, plus the energy-regulatory paralegals/consultants who prepare these today and would white-label a faster tool.
Solved today
Two paths: (a) hire an energy-regulatory attorney/consultant to prepare and eFile Form 556 (commonly $2-5k per filing, inference), or (b) DIY the PDF form and FERC eFiling with no validation, guessing at the capacity and efficiency computations.
Why current solutions are bad
Counsel is expensive and slow for what is expressly a do-it-yourself self-certification; DIY is error-prone and a rejected/deficient filing can jeopardize QF status and the must-buy/exemption benefits the whole project economics depend on. No validation layer exists between the two extremes.
Proposed product
A guided web wizard: interview-style intake → automatic net-capacity and (for cogen) operating/efficiency-standard computations → validation against a library of common rejection/deficiency patterns → a filled, filing-ready Form 556 PDF → a step-by-step FERC eFiling walkthrough (or, later, assisted/automated submission). Positioned strictly as form-preparation software, not legal advice.
MVP version
Single-flow wizard for the most common case (self-certification of a solar PV small power production facility ≤80MW): intake form, capacity computation, category selection, owner-disclosure capture, deficiency checklist, and a generated Form 556 PDF matching FERC's current layout, plus an eFiling how-to. Manual QA against a handful of real accepted filings from FERC's public docket.
30-day build
Reverse-engineer the current Form 556 field-by-field from the official form and instructions; pull a sample of accepted 556 filings from FERC's public eLibrary to build the deficiency/rejection pattern library; build the intake→PDF generation for the solar self-cert path; validate output against real accepted filings.
60-day build
Add the cogeneration path (operating & efficiency standard tests) and recertification/material-change flow; add owner/upstream-owner disclosure logic; recruit 3-5 design-partner developers/EPCs for free filings in exchange for feedback; wire eFiling walkthrough and a review-before-submit gate.
90-day revenue plan
Launch per-filing paid tier; sell directly to EPCs/developers via targeted outreach (solar developer LinkedIn/associations, interconnection-queue lists) and offer a white-label/API tier to consultants and law firms who prepare 556s at volume. Target first paid filings within this window.
Distribution path
Direct outreach to solar EPCs/developers with multi-project pipelines; content/SEO on 'how to file FERC Form 556 / QF self-certification'; partnerships with solar-industry associations and interconnection-service providers; white-label to energy-regulatory consultants/paralegals as a volume channel.
Pricing hypothesis
Per-filing fee (e.g. $199-$499 self-cert, higher for cogen) undercutting $2-5k counsel by an order of magnitude; volume/subscription pricing for EPCs and a white-label/API seat for professional preparers. No statutory fee cap — self-certification is expressly DIY.
Technical difficulty
Moderate. The hard part is correctly encoding FERC's capacity and cogen efficiency computations and the deficiency-pattern library, plus faithful PDF generation; the app itself (intake wizard + PDF + walkthrough) is squarely in the founder's fast-prototyping wheelhouse. Automated portal submission is a later, optional add.
Legal / regulatory risk
Manageable if framed as form-preparation software, not legal advice (avoid UPL — no legal opinions, user reviews and files). No licensure required to sell form-prep software (inference). No finder-fee cap applies — this is a filing tool, not a claims/finder model.
Platform dependency
Low/none in the deplatform sense: the counterparty is FERC's government eFiling system, which has no owner who can ban the tool. Dependency risk is limited to FERC changing the form (versioned, infrequent) — a maintenance cost, not an existential one.
Founder fit
Very high — this is a near-exact replica of his shipped FMCSA ELDT product: read a federal mandate, identify the forced filer, build the submission/prep layer against a government portal, charge per filing. The mandate explicitly names the filer, the form, and the portal.
Breakout potential
Moderate-to-high. Beachhead is Form 556, but the same wizard-over-a-government-form engine replicates to adjacent FERC filings (e.g. FERC-521 appears in the same batch), state PUC interconnection/QF filings, and other per-filing federal forms — a portfolio of narrow filing tools rather than one big product.
Final recommendation
BUILD — high-conviction pursue. This is the closest match in the batch to the founder's proven, monetized government-portal filing archetype, with a defined forced-filer class, a named federal form and portal, an expensive incumbent (counsel) to undercut, and no fee-cap or platform-deplatform risk. The one real gate is validating actual annual filing volume and the reachable high-frequency buyer before scaling spend.
Next action
Pull the last 12 months of accepted FERC Form 556 filings from FERC eLibrary/public docket to (a) count real annual self-certification volume and identify high-frequency filers/EPCs as first customers, and (b) seed the deficiency/rejection pattern library — then build the solar self-cert wizard MVP.