What changed
FACT (source text): On 2026-05-01 Treasury/IRS published temporary regulations (and a parallel notice of proposed rulemaking) implementing the statutory provision for Section 6435 payments to taxpayers with respect to certain previously taxed dyed fuel. The regulations 'provide guidance delineating which taxpayers may claim such payments and the procedures these taxpayers must follow to claim the payments,' and 'affect taxpayers that withdraw previously taxed dyed fuel from a terminal.'
Why now
FACT: the claim procedures are newly specified — before these temporary regs there was no delineated procedure, so no incumbent workflow is entrenched around this specific claim. INFERENCE: the window between a new claim procedure taking effect and excise-tax software vendors shipping support for it is the wedge, and it is measured in quarters, not years. HYPOTHESIS: the earliest claim periods will be filed in the first full quarter after the regs take effect, which is when substantiation pain peaks.
Converging signals
Three things meet at one point: (1) a federal rule that creates a payment entitlement, (2) a defined class that can claim it — taxpayers withdrawing previously taxed dyed fuel from a terminal, i.e. position holders, distributors and jobbers, and (3) an existing federal data trail (ExSTARS Forms 720-TO/720-CS terminal operator and carrier reports, plus bills of lading) that is exactly the substantiation the claim requires. The data needed to prove the claim already exists in a standardized federal reporting format. INFERENCE: the ExSTARS/BOL linkage is not stated in the rule text and is inferred from how terminal fuel movements are ordinarily documented.
Customer pain
HYPOTHESIS (not proven by the source text): a distributor who withdrew previously taxed fuel that was subsequently dyed must tie each removal, gallon-by-gallon, to a prior tax payment upstream in the fuel's chain of custody. That reconciliation spans terminal operator reports, carrier reports, purchase invoices and BOLs held in different systems. FACT: the regulation itself states that the procedures taxpayers must follow to claim the payments required guidance — the IRS considered the 'how do I claim this' question non-obvious enough to issue temporary regulations about it. That is the only direct evidence of pain in the input; everything about the difficulty of substantiation is inference from how fuel excise claims generally work.
Who pays
The claimant: fuel distributors, jobbers and position holders who withdraw previously taxed dyed fuel from a terminal (FACT, from the rule's 'affects' statement). Secondary buyer: the fuel excise tax consultants and CPA firms who would otherwise do this reconciliation by hand and bill for it — they are a channel, not just a competitor. The money flows TO the filer, which inverts the usual compliance sale: this is not a cost the buyer resents, it is cash recovery, and cash-recovery tools sell on a demonstrated-number basis, which suits the founder's 'sell through demonstrated value' preference exactly.
Solved today
INFERENCE — no source in the input describes current practice. Almost certainly: (a) a fuel excise consultant or specialist CPA reconciles records manually and bills hourly or on contingency, (b) an incumbent excise platform (Avalara Excise, Thomson Reuters ONESOURCE, IGEN, DMA) prepares Form 8849 / Form 720 schedules as part of a broader compliance subscription, or (c) the distributor simply does not claim, because the substantiation cost exceeds the perceived refund. Option (c) is the founder's real market.
Why current solutions are bad
HYPOTHESIS: consultants price on a percentage of the recovered refund, which means the smaller the claim the worse the economics, and mid-size distributors get ignored. Incumbent excise suites are sold as annual compliance subscriptions with implementation cycles — the wrong shape for a claim you want to file once and see money from. Neither approach gives the distributor a self-serve way to answer 'how many gallons can I actually claim?' before committing to spend.
Proposed product
A claim assembler, not a compliance suite. Ingest the distributor's terminal withdrawal records (ExSTARS 720-TO/720-CS extracts, terminal invoices, BOLs, and purchase records), normalize them into a gallon-level ledger, apply the Section 6435 eligibility rules as codified in the temporary regs, compute claimable gallons and dollars, and emit a filing-ready claim package with a per-withdrawal substantiation exhibit that survives audit. The output is a PDF/e-file package plus an evidence workbook, not a submission bot — the IRS excise claim channel is INFERENCE and should not be assumed to be programmatically writable.
MVP version
A gallon-reconciliation engine plus a claim-package generator. Concretely: a CSV/EDI importer for 720-TO and 720-CS layouts and terminal BOL exports; a matching engine that ties dyed-fuel removals to prior taxed receipts by terminal control number, product code, date and gallons; a rules layer encoding the eligibility conditions from the temporary regs; a 'claimable gallons' report; and a generated Form 8849-style claim package with per-line substantiation. Ship the reconciliation engine first and sell the number it produces, not the software.
30-day build
Read the temporary regulations in full and codify the eligibility conditions and required substantiation into an explicit rules document — this is the asset, and getting it wrong is the whole risk. In parallel, obtain real 720-TO/720-CS layouts and at least two anonymized terminal withdrawal datasets from friendly distributors. Retain a fuel excise tax attorney or specialist CPA for a paid opinion on eligibility edge cases; the founder has capital and this is the correct place to spend it. Deliverable at day 30: a written eligibility spec plus a hand-worked claim on real data.
60-day build
Build the ingestion and matching engine against those datasets and reproduce the hand-worked claim automatically. Run free 'claim sizing' analyses for 10-15 distributors sourced from state fuel-license public registries — these are public records, which the founder is strong at mining. Each analysis outputs one number: your estimated claimable dollars. That number is the entire sales pitch.
90-day revenue plan
Convert the sizing analyses. Charge a flat per-claim preparation fee well below a consultant's percentage — for a claim in the tens of thousands of dollars, a fee in the low four figures is trivially justified and requires no procurement. Concurrently pitch two or three fuel excise consultancies on white-labeling the engine so they can serve mid-size clients they currently decline. First revenue realistically lands 90-150 days out, not 30 — the first claim cycle has to actually run.
Distribution path
State fuel distributor and supplier license registries are public records in most states and give a near-complete, contactable list of the filer class. That is a rare thing: a finite, enumerable, forced-eligible buyer list. Layer on the fuel excise consultant channel and the state/regional petroleum marketers associations (SIGMA, NATSO, state PMAA affiliates), whose members are exactly the mid-size distributors incumbents ignore. No ad spend, no network effects, no relationship sales — a spreadsheet of licensees and a demonstrated dollar figure.
Pricing hypothesis
Per-claim preparation fee of roughly $1,500-$5,000 depending on gallon volume, plus an optional annual subscription for distributors who will claim every quarter. Explicitly do NOT price on contingency: a percentage of refund makes the founder look like the consultant he is undercutting, invites state-by-state questions about who may charge contingency fees for tax claims, and caps the software's margin. Undercut the 2-5% consulting fee with a flat number; that IS the wedge.
Technical difficulty
Moderate on engineering, high on domain. The software is CSV/EDI parsing, a matching engine and a document generator — comfortably solo-buildable. The hard part is encoding the eligibility rules correctly and defensibly. Get that wrong and the product generates rejected or, worse, audited claims. Budget for a paid expert opinion and a professional-liability policy before the first claim ships.
Legal / regulatory risk
Real and specific. Preparing tax claims for compensation may bring the founder under Circular 230 / IRS preparer rules depending on how the product is positioned; a software tool that computes and outputs a package is meaningfully different from a person signing as preparer, and the line must be drawn deliberately with counsel. This is the one place the 'compliance is the moat, not a burden' rule does NOT fully apply — the founder could be pulled into a licensed-preparer posture. Mitigation: sell the tool to the distributor or to the CPA/consultant who signs, never sign as preparer. Errors-and-omissions insurance is mandatory. Not a kill, but not free either.
Platform dependency
Essentially none. There is no platform owner who can deplatform a tool that produces an IRS claim package. If a direct e-file integration is later added, the dependency is on the IRS, which does not act like a commercial platform. The real dependency is on the regulation itself: these are TEMPORARY regulations with a parallel proposed rule, so the procedures can change when the final rule issues. That is a maintenance obligation, not an existential one — and rule-tracking is something this system is already built to do.
Founder fit
Very high, with one caveat. Shape-match to the FMCSA ELDT product is near-exact: a federal rule defines a forced class, the class must file, the filing needs data assembly, and the founder charges per filing. Add his industrial/scrap operations background — fuel distributors, terminals, BOLs and gallon reconciliation are his native operational vocabulary, not an abstraction he has to learn — and his public-records strength maps directly onto the state licensee registries that constitute the buyer list. The caveat: ELDT was a submission tool against a portal with a mechanical pass/fail. This is a TAX claim, where correctness is adjudicated years later by an auditor. The domain-risk profile is genuinely harder than his prior win, and the lesson 'government-portal mandate opportunities fit this founder best' (confidence 0.80) should be applied with that discount.
Breakout potential
Moderate, and honestly capped. The Section 6435 claim itself is a narrow instrument. But the reconciliation engine — tie gallon-level fuel movements to tax status across ExSTARS, BOLs and invoices — is the substrate for every fuel excise refund claim there is: off-road use, agricultural use, export, state-level refunds across all 50 states, and the alternative fuel credits. The Section 6435 claim is the wedge that gets the data plumbing installed. The expansion is state fuel tax refunds, which are 50 near-identical markets with weaker incumbents. That is where the real business is, and it is the reason to build this even if the initial claim pool disappoints.
Final recommendation
CONDITIONAL PURSUE — gated on one measurement, not on building anything. The shape is the founder's best shape: a federal rule, a delineated filer class, a procedural filing, and money flowing to the filer. Founder-fit is genuinely near-maximal and the buyer list is enumerable from public records. But two of the kill arguments are unresolved and one of them is fatal if true. Before writing a line of code, spend two weeks and a few thousand dollars answering: how many gallons of previously-taxed fuel are actually dyed and withdrawn annually, and can a claimant obtain the substantiating terminal data? Read the temporary regs and the preamble in full; the preamble very likely contains a Paperwork Reduction Act respondent estimate, and that number is the honest size of this market. If the respondent count is in the hundreds or low thousands and average claims are five figures, build it — the state fuel-refund expansion makes it worth the domain investment even at a modest start. If the respondent count is tiny, kill it and redirect the reconciliation-engine concept at state-level off-road and agricultural fuel tax refunds, where the volumes are known to be large and the incumbents are weaker. The engine is the asset; Section 6435 is only one claim it can produce. Note that the demand evidence here is entirely structural — three FORCED BUYER items that are the same two Federal Register documents (the rule and its companion proposed rule), self-similar rather than independent. That is sufficient to establish a compelled filer class per the founder's thesis, and it is correctly NOT a reason to score demand low. It is also not evidence that the class is large.
Next action
Pull the full text of the temporary regulations and, critically, the preamble at federalregister.gov/documents/2026/05/01/2026-08545 and the companion NPRM at .../2026-08546, and extract the Paperwork Reduction Act section: the estimated number of respondents and burden hours. That single figure resolves the pie question and decides go/no-go. Do this before anything else. In the same pass, extract the exact statutory conditions on who may claim and what substantiation is required, and check whether the claim rides on Form 8849 or a new form.