What changed
FACT: DOJ's Office of Justice Programs published a Federal Register notice (2026-06-30) that it will submit a revised NMVTIS information-collection request to OMB under the Paperwork Reduction Act, re-affirming and updating the mandatory reporting of junk, salvage, and total-loss vehicle records into the National Motor Vehicle Title Information System.
Why now
FACT: an active OMB comment period is open on the revised collection, which keeps the mandate and its filer burden top-of-mind. INFERENCE: a PRA revision cycle is a natural moment for filers to re-examine how they report, creating a sales window; the underlying reporting duty is long-standing statute (Anti-Car Theft Act / 28 CFR Part 25), so demand is durable, not one-off.
Converging signals
FACT: three signals meet at one point — (1) a federal rule/collection compelling reporting, (2) a defined forced-filer class (junk yards, salvage yards, salvage pools, insurance carriers writing auto), and (3) a designated submission channel (NMVTIS reporting system via approved data consolidators). That is textbook forced-buyer convergence.
Customer pain
HYPOTHESIS (not proven in source): small and mid-size salvage/junk yards must file NMVTIS reports (monthly or per-transaction) but often do it via clunky consolidator web forms or manual keying, and face civil penalties for non/late reporting. INFERENCE: insurers report total-loss records at scale and pay consolidators. The source proves the OBLIGATION, not the specific pain intensity — that must be validated with a handful of yard operators before build.
Who pays
Junk yards, salvage yards, salvage pools, and auto insurers required to report to NMVTIS. Most reachable buyer: independent salvage/junk yards (thousands of them, no compliance staff). Insurers are a second, larger-ticket tier but slower to sell.
Solved today
FACT (from mandate structure): reporting flows through NMVTIS 'approved data consolidators' — third parties that accept yard/insurer data and relay it to the system. Yards either enter data manually into a consolidator portal or pay the consolidator's per-record/subscription fee. Some use their existing yard-management software if it has an NMVTIS module.
Why current solutions are bad
HYPOTHESIS: manual entry is labor and error-prone (penalty exposure); consolidator fees and yard-management NMVTIS modules can be priced for larger operators; small independents lack an affordable, automated pull-from-inventory-and-file tool. Needs primary validation.
Proposed product
A micro-SaaS that connects to a yard's inventory/claims data (CSV export, common yard-management systems like Hollander/Checkmate/Car-Part, or manual upload), validates and maps it to the NMVTIS report schema, and submits via an approved data-consolidator channel (or by becoming/partnering with a consolidator), returning confirmations and an audit trail. Per-report or per-seat pricing.
MVP version
CSV/spreadsheet in → validated NMVTIS-format report out → submitted through one approved consolidator's API or file-drop, with a submission log and error flagging. Single-yard onboarding. No fancy integrations initially.
30-day build
Read 28 CFR Part 25 + the current NMVTIS reporting spec; identify the list of approved data consolidators and which expose an API or bulk file intake; interview 8-12 salvage/junk yard operators to confirm pain, current cost, and willingness to pay; file a comment on the OMB docket to surface as a domain participant.
60-day build
Build the ingest→validate→format→submit pipeline against ONE consolidator's intake; secure a consolidator partnership or reseller/API agreement (this is the critical dependency); onboard 2-3 design-partner yards at a discount.
90-day revenue plan
Convert design partners to paid; launch per-report/per-seat pricing; sell via salvage-yard trade channels (auto recycler associations, Car-Part/marketplace communities, state auto-recycler groups). Target first recurring revenue from small yards.
Distribution path
Direct outreach to independent salvage/junk yards via auto-recycler associations (ARA and state chapters), yard-management software user communities, and salvage-pool networks. Demonstrated-value/free-audit motion (upload your last month's records, see errors), not relationship sales — matches founder.
Pricing hypothesis
Per-report fee (e.g. small per-record charge) and/or a low monthly per-seat subscription for unlimited reporting; premium tier for insurers/high-volume. Undercut consolidator per-record pricing.
Technical difficulty
Moderate. The report schema and validation are tractable for a solo AI-assisted builder. The real difficulty is the SUBMISSION path: NMVTIS requires going through an approved data consolidator — either integrate with one that offers an API/file intake, or pursue consolidator approval (heavier). This gating is the make-or-break.
Legal / regulatory risk
Low-to-moderate. Submitting compliance data on a customer's behalf into a government-designated system is the founder's proven ELDT shape. Main constraint is the consolidator-approval structure and data-accuracy liability (contractual disclaimers + audit logging). No platform-owner deplatform risk.
Platform dependency
Real but not fatal: dependence on NMVTIS's approved-consolidator gateway. Mitigate by partnering with (or reselling through) an existing approved consolidator rather than routing around it. This is a government submission channel, not a commercial platform that can ban you.
Founder fit
MAXIMAL for the shape: a federal mandate forces a defined class to file into a government portal, monetizable per filing — identical structure to his shipped FMCSA ELDT product. Auto-salvage/scrap also overlaps his recycling/scrap operational background. The one caveat vs. ELDT: NMVTIS interposes an approved-consolidator layer, so he cannot file directly to the government — he must integrate/partner. Founder-fit strong, slightly below a direct-portal mandate.
Breakout potential
Solid. Same engine extends across all 50 states' interacting title systems, to insurers (larger contracts), and to adjacent NMVTIS-touching parties (recyclers, auction/salvage pools). A working consolidator integration becomes a reusable moat.
Final recommendation
PURSUE — but gate the build on two validations in the first 30-45 days: (1) confirm at least one approved data consolidator will expose an API / reseller path (kills or unlocks the whole thing), and (2) confirm from 8-12 real yards that current reporting is painful/costly and not already free inside their yard-management software. If both hold, this is a high-fit, forced-buyer, per-filing SaaS in the founder's exact wheelhouse.
Next action
Pull the list of NMVTIS approved data consolidators and email/call each to ask whether they offer an API or reseller intake for third-party reporting tools; in parallel, line up 8-12 salvage/junk-yard interviews via an auto-recycler association to confirm pain and willingness to pay.