What changed
Per the convergence input, proposed IRS 45Z rules make producer registration a prerequisite to any Clean Fuel Production Credit dollars and require per-pathway emissions-rate documentation, third-party certification, and annual substantiation (source: convergence description; the 45Z claim itself carries no URL in the provided signals, so treat regulatory specifics as needing verification against the actual IRS notice). Simultaneously, two dev capabilities landed: Context.dev exposes schema-defined structured extraction from arbitrary websites via one API (source: https://www.context.dev), and OfficeCLI lets headless agents generate Office-format documents server-side with one binary (source: https://github.com/iOfficeAI/OfficeCLI).
Why now
FACT (per input): rules are in the hearing stage now and registration must precede claiming, so the buying window opens before the first covered tax year and repeats annually. HYPOTHESIS: producers who wait until rules finalize will face a registration crunch, creating a deadline-driven demand spike the way ELDT did for driver-training providers.
Converging signals
(1) Government mandate: 45Z registration + per-pathway CI certification + annual substantiation as a condition of payment (convergence input, no URL provided). (2) Context.dev: structured extraction from feedstock-price/CI-data/registry pages without building scraper infrastructure (https://www.context.dev). (3) OfficeCLI: headless agents can emit the actual Office-format certification packages and filings on any server (https://github.com/iOfficeAI/OfficeCLI). Signals 2 and 3 collapse the build cost of the dossier-assembly layer; signal 1 supplies the forced buyer.
Customer pain
HYPOTHESIS grounded in the input's framing: small and mid-size producers (biodiesel co-ops, renewable-diesel startups) face recurring, deadline-driven document assembly they cannot staff. The credit is material revenue; missing registration means zero credit. Large producers absorb this with consultants; small ones face a choice between expensive consulting engagements and forfeiting money. No direct buyer complaints or forum evidence was provided in the input — pain intensity is inferred, not observed, and must be validated by calling actual small producers.
Who pays
Small and mid-size clean-fuel producers (biodiesel co-ops, renewable-diesel startups, RNG/SAF small entrants) for whom the credit is material but a compliance hire is not affordable. This is a forced buyer: no registration, no credit. HYPOTHESIS: the realistic buyer count is small — likely low hundreds of US producers in this size band — which caps this as a niche cash business, not a scale play.
Solved today
HYPOTHESIS (consistent with input's claim that 'large producers have consultants'): lifecycle-analysis and biofuels-compliance consultancies (e.g., EcoEngineers-type firms) and biofuels-specialist CPA firms do pathway modeling, registration, and credit substantiation as bespoke engagements, typically five figures per pathway. Small producers either buy a slice of that, lean on trade-association guidance, or DIY with spreadsheets and the GREET model.
Why current solutions are bad
Consulting is priced for large producers and doesn't amortize for a co-op with one or two pathways. DIY is error-prone against a tax authority where documentation defects mean credit disallowance or clawback. The work is also recurring (annual substantiation, per-pathway updates when feedstocks or CI inputs change), which is exactly the shape consultants bill heavily for and software should compress.
Proposed product
A 45Z compliance workbench: producer enters production data, feedstock mix, and process parameters; agents pull current CI/feedstock reference data from public sources via Context.dev, run the pathway math against the applicable emissions-rate table or model, and emit the complete registration, certification-support, and annual-substantiation package in Office formats via OfficeCLI — one dossier per pathway, regenerated each tax year. Critical scoping note (kill-test survivor only if respected): under the proposed rules as described, third-party certification is required, and a solo software vendor is NOT the certifier. The product prepares the dossier the verifier signs and the IRS filing rests on; it does not replace the accredited third party. Position as 'verifier-ready package generation,' possibly channel-selling THROUGH the verifiers/CPAs rather than around them.
MVP version
A single-pathway 'registration readiness package': intake form (or spreadsheet upload) → generated registration checklist, data-gap report, and a draft substantiation binder in Word/Excel via OfficeCLI, with CI reference data fetched via Context.dev. No dashboard, no accounts — deliver as a paid document package for 3-5 pilot producers. Buildable in 2-3 weeks solo with AI assistance because the hard parts (extraction, Office generation) are the two cited tools.
30-day build
Verify the actual regulatory text first (read the IRS proposed rule/notice directly — the input provides no URL for it): confirm registration mechanics, what 'third-party certification' legally requires, and the first covered tax year. In parallel, call 10-15 small biodiesel/renewable-diesel producers and 3-5 biofuels CPAs/verifiers; ask what they're doing about 45Z registration and what they'd pay for a prepared dossier. Build the single-pathway MVP package only if calls confirm urgency.
60-day build
Deliver paid pilot packages ($1,500-3,500 per pathway) to 3-5 producers sourced via biodiesel trade associations, state biofuel groups, and the verifier/CPA channel. Instrument every manual step; automate the top three with agents. Publish one authoritative 'small producer 45Z registration guide' as the demand-capture asset (mirrors the demonstrated-value, no-relationship-sales distribution style).
90-day revenue plan
Target: 5-10 paid pathway packages = $10k-30k, plus 2-3 annual-substantiation retainers ($200-500/mo) and at least one verifier/CPA firm reselling the package generation. Realistic risk: if rules are still not final at day 90, revenue slips — mitigate by selling 'readiness' (data collection + gap analysis) now, which producers need regardless of final rule details.
Distribution path
No enterprise sales: (1) biodiesel/clean-fuels trade associations and their newsletters/conferences, (2) the verifier and biofuels-CPA channel — they need clean input dossiers and can white-label the generator, (3) SEO/content on '45Z registration small producer' queries which currently have thin coverage (HYPOTHESIS), (4) direct outreach to producers listed in public EPA/RFS and state fuel-program registries — a public-records lookup task squarely in the founder's wheelhouse.
Pricing hypothesis
Per-pathway package: $1,500-3,500 initial dossier; $750-1,500 annual substantiation refresh; or SaaS-ish retainer $200-500/mo per producer. Mirrors the proven ELDT per-filing monetization: charge per compliance artifact, not per seat.
Technical difficulty
Moderate. Document assembly and data extraction are genuinely easy now (the two cited tools). The hard part is domain correctness: emissions-rate tables vs. GREET-based pathway math, and mapping producer records to what the IRS and verifiers actually accept. That is learnable but is the real moat and the real risk — a wrong number in a tax dossier is worse than no dossier.
Legal / regulatory risk
Real and above-average for this founder's usual plays: the output supports federal tax credit claims. Mitigations: position strictly as document-preparation software/service with the producer and their verifier/CPA responsible for accuracy sign-off; explicit disclaimers; never act as the certifier or tax advisor. Rules are not final — building against a proposed rule risks rework. This is the single biggest caveat.
Platform dependency
Low-moderate. Context.dev is a brand-new YC S26 startup (could pivot/die; scraping is replaceable with conventional tooling). OfficeCLI is an open-source binary (https://github.com/iOfficeAI/OfficeCLI) — replaceable with docx/xlsx libraries. Neither is a gatekeeper platform; no marketplace approval needed.
Founder fit
VERY HIGH on the proven-edge template: a federal mandate forces a party to register/file before money flows, and the founder has already shipped exactly this shape (FMCSA ELDT certificate submission, per-upload fee). Adds his industrial-operations and public-records strengths (producers are industrial operators; registries are public records). The one mismatch vs. ELDT: 45Z involves a required third party (verifier) in the loop and tax-grade stakes, so it is dossier-prep rather than pure submission automation — slightly weaker fit than ELDT but still among the best matches this system can surface.
Breakout potential
Good for a niche: the same workbench extends to 45V (hydrogen), state LCFS programs (CA/OR/WA), and RFS pathway paperwork — each a new mandate with the same dossier shape. Ceiling is a compliance-automation micro-firm doing $300k-1M/yr, or an acquisition target for a biofuels consultancy; not venture-scale, which fits the founder's constraints.
Final recommendation
CONDITIONAL GO — strong founder-fit and correct mandate shape, but two unverified load-bearing claims (final rule requirements; actual willingness-to-pay of small producers). Spend the first 2 weeks on verification calls and reading the actual IRS proposed rule before writing product code; sell a manual 'registration readiness' package first and automate behind it. Do not build the full workbench against a non-final rule.
Next action
Today: pull the actual IRS 45Z proposed-rule text and hearing docket to confirm registration mechanics and certification requirements (the input asserts but does not cite them), then compile a call list of 15 small biodiesel/renewable-diesel producers from public EPA/state fuel registries and book 5 discovery calls this week.