What changed
FACT (per cited Federal Register document, 2026-05-01): the CFPB finalized revisions to the Section 1071 small-business lending data rule under Regulation B, changing institution/transaction coverage, the small-business definition, required data points, and the compliance date. Every covered lender must rework data collection and reporting pipelines against the revised spec.
Why now
FACT: the revised rule resets the spec, so even lenders who prepared for the 2023 version must re-map data points and dates. HYPOTHESIS: cheap frontier reasoning (GPT-5.6 signal) and extraction-as-API lower the cost of building the intake/validation layer solo. CAUTION (hypothesis): 1071 has a multi-year litigation and delay history, so many buyers are conditioned to wait — urgency depends on how near the first compliance tier actually is, which must be verified in the final rule text.
Converging signals
(1) Finalized 1071 revisions creating a forced-buyer class of filers [federalregister.gov]; (2) schema-defined structured extraction via one API call [context.dev] — though note 1071 data mostly originates from loan applications, not public websites, so this signal is only weakly load-bearing; (3) better cost-per-task reasoning [openai.com/index/gpt-5-6] for classification/validation of messy application data.
Customer pain
HYPOTHESIS (no PAIN evidence was provided in demand_evidence): banks have HMDA muscle and incumbent vendors, but newly covered NON-BANK commercial lenders — merchant cash advance providers, equipment finance, factoring companies, small CDFIs — have never had a federal data-reporting obligation, have no compliance staff, and face ECOA exposure for getting it wrong. Their pain is 'I have no idea what to collect or how to file, and I can't afford Wolters Kluwer.'
Who pays
The covered lender itself. Target the smallest covered tier: non-depository commercial finance companies and sub-$1B community lenders. They are forced buyers by regulation (FACT that the mandate exists; HYPOTHESIS about their willingness to buy a small vendor's tool).
Solved today
HYPOTHESIS: banks extend existing HMDA vendor stacks (Wolters Kluwer, Ncontracts, Asurity RiskExec); non-bank lenders currently do nothing, use spreadsheets, or wait for their loan-origination software to add it. The CFPB also provides its own filing platform, so the raw submission channel is free — the paid value is data capture, validation against the edit rules, and audit trail.
Why current solutions are bad
Incumbent compliance suites are priced and sold for banks (annual contracts, vendor due diligence). Spreadsheets can't enforce the revised data-point definitions or the applicant-demographic collection rules. Doing nothing risks ECOA violations once the compliance date hits.
Proposed product
A per-file 1071 pipeline: (a) intake widget/CSV mapper that captures the required data points at application time, (b) validator implementing the CFPB edit/format rules for the revised spec, (c) one-click preparation of the submission file for the CFPB filing platform, (d) audit log. Priced per application record or a low flat monthly fee — the same 'read the mandate, build the portal layer, charge per filing' shape as the founder's shipped FMCSA ELDT product.
MVP version
A web-based 1071 file validator + gap-analysis report: upload your loan tape, get back exactly which required data points you are missing under the revised rule and a formatted submission file. No integrations, no PII storage beyond the session if possible. Buildable solo in 2-4 weeks since the CFPB publishes the filing instructions and validation specs.
30-day build
Read the final rule's coverage thresholds and compliance-date table; build the validator against the published data spec; publish a free '1071 revised-rule readiness checklist' targeting MCA/equipment-finance operators; post in commercial-finance broker communities (deBanked forums, LinkedIn groups, ELFA/AACFB adjacents) to test awareness and collect emails.
60-day build
Convert checklist leads into paid gap-analysis reports ($249-$499 per lender); ship the intake/capture module for 2-3 design partners at a founding-customer rate; add automated demographic-collection language templates (with a lawyer-review disclaimer, not legal advice).
90-day revenue plan
HYPOTHESIS: 10-20 paid gap analyses plus 3-5 lenders on $99-$299/mo capture+validate subscriptions ≈ $3-8k. Real recurring revenue scales only as the compliance date approaches; if the first tier is >12 months out, 90-day revenue depends almost entirely on the gap-analysis report product, not the SaaS.
Distribution path
Content + community: deBanked and MCA/commercial-finance operator communities, equipment-finance associations, CDFI networks, SEO on 'revised 1071 rule requirements'. No enterprise sales, but note honestly: even small lenders may require security questionnaires before uploading loan data — this is the main distribution friction.
Pricing hypothesis
Free checklist → $249-499 one-time gap analysis → $99-299/mo capture+validation → per-record fee (e.g., $0.50-1.00/application) at filing time, mirroring the proven per-upload ELDT model.
Technical difficulty
Low-moderate. The spec is published; the work is careful implementation of edit rules and a clean intake UX. The Context.dev-style extraction API is mostly irrelevant here (data is private, not on public websites) — flag that the convergence framing overstates that signal.
Legal / regulatory risk
Material. The tool touches ECOA-regulated data including applicant demographic information (fair-lending sensitivity). Mis-validation that causes a bad filing creates customer liability; storing demographic data raises privacy/security obligations. Mitigate by validating client-side/ephemerally and disclaiming legal advice, but this is genuinely heavier compliance exposure than the ELDT product.
Platform dependency
Depends on the CFPB filing platform's specs and the rule surviving further litigation/administrative change — 1071 has already been stayed and rewritten once, and a future delay would freeze buyer urgency (this exact risk materialized for vendors who built for the 2023 version).
Founder fit
High on shape: regulation compels a class of filers, founder has shipped exactly this pattern against FMCSA's Training Provider Registry with per-upload pricing. Weaker on buyer: financial institutions, even small ones, are more diligence-heavy and risk-averse than CDL training schools, and the founder profile excludes long trust-building plays. The non-bank long tail is the only segment where the fit holds.
Breakout potential
Moderate: wedge into the non-bank lender compliance stack (1071 today; state commercial-financing disclosure laws in CA/NY/VA/GA as adjacent forced-filer regimes) — a genuine multi-regulation expansion path for the same buyers.
Final recommendation
CONDITIONAL GO — do not build the full SaaS yet. Spend one week verifying the two kill conditions: (1) the actual compliance-date tiers in the final revised rule, and (2) whether non-bank commercial finance operators are discussing/worrying about 1071 in their communities. If the earliest tier is within ~12 months and awareness-pain is visible, ship the validator + paid gap-analysis immediately; otherwise tag 'revisit later' and set a trigger 9 months before the first compliance date.
Next action
Read the compliance-date and coverage-threshold sections of the final rule at the cited Federal Register URL, then post a diagnostic question in 2-3 MCA/equipment-finance operator communities to test whether the long tail knows it is covered.