What changed
DOI has awarded BIL Sec. 40601 orphan-well formula grants to state agencies — $25M to Kentucky's Energy & Environment Cabinet (FACT, cited award), plus parallel $25-80M awards to Colorado, New Mexico, West Virginia, Texas, Louisiana, North Dakota, Alaska, Florida (FACT, cited). Kentucky's award text states all plugging work is procured from contractors under division inspector coordination, with spill-control and regulatory-compliance duties placed on the contractor (FACT). Phase 2 awards (FY26, e.g., $35M KY, $29.2M WV, $29M CO) show the money is recurring, not one-shot (FACT).
Why now
Phase 2 grants landed in FY26, so states are actively procuring plugging contracts right now and will be for several years. Every plugged well must be documented to the satisfaction of a state inspector, and states must account for spend per well to DOI (per the input's companion-award accounting requirement, stated as FACT in the input; I could not independently verify award 4979 from the provided text — treat as high-confidence input assertion). Contractors are field crews doing this documentation with paper, phones, and Excel (HYPOTHESIS — no direct evidence of current tooling provided).
Converging signals
Three signals meet at one point: (1) appropriated money — $4.7B nationally, with 10+ cited state awards of $25M+ each; (2) a defined actor class — plugging contractors procured by state oil & gas divisions; (3) a documentation obligation — inspector-coordinated work, spill compliance, plugging affidavits/completion reports, and per-well cost accounting flowing up to DOI. Per the system's own scoring rule, a funded mandate naming a filer class and a submission is convergence even though the idea is unglamorous.
Customer pain
A plugging crew closes out a well and must produce: pre/post photos, methane/site-condition readings, materials and cement volumes, disposal manifests, daily inspection-ready reports, and the state completion report/affidavit. Done manually this is hours of office rework per well, errors trigger inspector pushback and payment delays, and the contractor's pay application depends on the paperwork being accepted. Pain is inferred from the obligation structure (HYPOTHESIS as to intensity — no complaint threads provided), but the obligation itself is FACT.
Who pays
The well-plugging contractor (small industrial firm, 1-10 crews). They pay because the documentation is a condition of getting paid by the state, and a per-well fee of $50-150 is noise against a $20-40k per-well plugging revenue. Secondary later buyer: the state division itself, which must aggregate per-well costs for DOI reporting.
Solved today
Paper field tickets, phone photos in camera rolls, Excel cost sheets, and office staff retyping into state forms; some contractors may use generic form apps (GoCanvas, Fulcrum) or oilfield ops software not built for plugging closeouts (HYPOTHESIS — inferred from the absence of any plugging-specific documentation product I can name, and from how small industrial contractors generally operate).
Why current solutions are bad
Generic form tools don't know the state's completion-report format, don't structure methane/site readings the way inspectors want, and don't produce the per-well cost record the state needs for its DOI rollup. Retyping between field notes and state forms creates errors that delay inspector sign-off and contractor payment. Each state's forms differ, which is exactly the moat a focused product can build form-by-form.
Proposed product
Offline-capable mobile app (crew side) + web back office: per-well job file with guided capture (photos with GPS/timestamp, methane readings, casing/cement/materials, disposal manifests, daily logs, costs). One tap generates (a) the state plugging affidavit/completion report as a filled PDF matching the state's form, (b) a daily inspection-ready report, and (c) a per-well cost export matching what the state must report to DOI. Start with Kentucky's forms, then clone state-by-state (WV, CO, NM, LA, TX are all cited award recipients).
MVP version
Kentucky-only: a PWA or simple React Native app with the per-well capture flow and a PDF generator for KY Division of Oil and Gas plugging affidavit/completion forms plus a cost-summary sheet. No integrations, no portal submission in v1 — output is the exact paper/PDF the inspector and division already accept. 4-6 weeks of AI-assisted build.
30-day build
Pull KY's awarded plugging contracts and bidder lists from the state eProcurement portal (public records — founder strength); call 10-15 contractors and 2-3 division inspectors to confirm the current documentation workflow and the exact forms; build the KY capture-to-PDF MVP; get one crew running it free on live wells.
60-day build
Convert the pilot to paid ($100/well or $250/crew/month); use the pilot's inspector-accepted reports as the demo asset; add WV and CO form packs (both have $29M+ Phase 2 awards); begin outreach to contractors on those states' award lists.
90-day revenue plan
3-5 paying contractors across KY/WV at per-well pricing. Realistic first-revenue math: a contractor plugging 15 wells/month at $100/well = $1,500/mo per customer; 5 customers ≈ $7.5k MRR. Then pitch one state division on the aggregation/DOI-rollup layer as an upsell path.
Distribution path
Direct and cheap: state procurement award notices name every winning contractor (public records). Email/call them with a one-page demo showing their state's completed form auto-generated. Also: state oil & gas association meetings, and division inspectors themselves — an inspector who likes the report format becomes a channel. No ad spend, no marketplace dependency.
Pricing hypothesis
$100/well closeout fee (anchored against $20-40k per-well contract value and the office hours saved), or $250/crew/month for high-volume contractors. State-side aggregation product later at $10-25k/yr per state (that one IS government procurement — treat as expansion, not the base case).
Technical difficulty
Low-moderate. Offline-first mobile capture, photo/GPS handling, PDF form filling, simple cost rollups. Hardest parts are state-form fidelity (clerical, not technical) and offline sync robustness in no-signal field locations. Well within solo AI-assisted range.
Legal / regulatory risk
Low. The app documents; the contractor signs and files. No licensure required for the founder — the affidavit remains the contractor's sworn document. Avoid presenting output as regulatory advice; the compliance duty stays where the award text puts it: on the contractor.
Platform dependency
None material. Output is PDFs matching state forms; no government API access required for v1. If distributed as a native app there is routine app-store review, but a PWA sidesteps even that. No platform owner can deplatform a tool whose deliverable is a state form.
Founder fit
Near-maximal. This is the founder's proven ELDT shape — a government-money-driven paperwork burden on a defined class, monetized per transaction — pointed at an industrial field-operations niche where his scrap/industrial-ops and fire-service credibility reads as authentic to the buyer. He can talk to a plugging crew foreman as a peer, which a SaaS salesperson cannot. Public-records skill directly powers customer acquisition (award lists).
Breakout potential
Moderate-to-good. Base business is a niche vertical tool (realistic ceiling low-single-digit $M ARR across 25+ funded states). Expansion vectors: DOI's methane-measurement documentation for performance grants, the state-side per-well cost rollup product, and adjacent funded reclamation programs (abandoned mine lands, also BIL-funded). Not venture-scale; exactly the sellable, cash-flowing shape requested.
Final recommendation
PURSUE as a focused pilot. The money is appropriated (FACT), recurring (Phase 2 FACT), spread across 25+ states, and the award text itself places documentation and compliance duties on contractors (FACT for KY). The unproven link — contractors paying for a tool rather than muddling through — is cheaply testable in 30 days with public award lists and one free pilot crew. This survives the kill attempt because the right kill reasons (no reachable buyer, no spend, enterprise-only channel) are all contradicted by evidence; the residual risk is tool-adoption willingness, which is a testable hypothesis, not a structural flaw.
Next action
This week: pull Kentucky's orphan-well plugging contract awards and bid tabs from the KY eProcurement portal, list the winning contractors, and call five of them asking one question: 'Walk me through what you hand the division inspector when you finish a well, and who types it up.' Build nothing until three describe the same painful workflow.