What changed
FACT: the CFPB finalized (2025-10-02) its interim final rule amending Regulation B to EXTEND the compliance dates for the 2023 Dodd-Frank §1071 small-business lending data-collection rule. FACT: the CFPB has multiple open/final 2025-2026 rulemakings RECONSIDERING and NARROWING 1071 coverage (2025-11-13 proposed rule and 2026-05-01 final rule revising covered transactions, covered financial institutions and the small-business definition). Net effect: the mandate still exists and now has a defined (later) runway, but its exact scope and thresholds are actively moving.
Why now
Compliance dates were pushed out, which resets the buying window: lenders that deferred now have a fresh, dated deadline to build collection into their loan-origination workflow, and the coverage changes mean every covered lender must re-check whether it is in scope. A dated, extended deadline is a sales calendar, not a reprieve.
Converging signals
Three signals meet at one point: (1) a federal rule (Reg B/§1071) compelling data collection; (2) a defined forced-filer class (banks, credit unions, CDFIs, online/fintech lenders above the origination-count threshold); (3) a single government portal (CFPB 1071 submission platform) with a rigid file spec. The parallel Financial Data Transparency Act joint data-standards rule (2026-06-25) signals machine-readable regulatory filing is the durable direction of travel.
Customer pain
HYPOTHESIS (not proven by the source text, but structurally strong): smaller covered lenders (community banks, CUs, CDFIs) lack a system to capture the required demographic/pricing/decision fields at application time, dedupe them, validate against the CFPB spec, and produce a conformant annual file. Manual spreadsheet collection risks fair-lending liability and a rejected/late filing. The provided evidence proves the OBLIGATION exists; it does not contain end-user complaints, so pain is inferred from the mandate, not observed.
Who pays
The covered lender (per institution). Buyer is the compliance officer / CFO / head of lending at a small bank, credit union or CDFI — reachable directly, NOT a government procurement office. Secondary channel: consultants and core-banking resellers who serve these lenders.
Solved today
FACT-adjacent (industry knowledge, not in source): large banks use enterprise compliance suites (Ncontracts/Ncino, Wolters Kluwer Wiz/OneSumX, Fiserv, TRUPOINT/Ncontracts, ARComply, Encompass add-ons). Smaller lenders either buy expensive modules they don't need, rely on their LOS vendor's promised feature, or plan to hand it to a consultant. Some will attempt spreadsheets.
Why current solutions are bad
The enterprise suites are priced and scoped for banks far larger than a single-branch CU or a CDFI; they bundle 1071 into six-figure platforms. That leaves a real gap at the small end: a lender that just needs to collect, validate and file, not buy a GRC platform. The wedge is a focused, cheap, spec-accurate collect→validate→submit tool.
Proposed product
A micro-SaaS with three jobs: (1) an embeddable/point-of-application intake form + API that captures the exact §1071 required fields with built-in prompts for the firewall/demographic-collection rules; (2) a validator that checks a lender's exported records against the current CFPB file spec (field types, enumerations, edits) and returns a fixable error report; (3) a filing generator that outputs the conformant submission file (and, if the portal permits, assists direct submission) plus an audit-trail archive. Sell the validator as the free/cheap wedge, the collection+filing as the paid tier.
MVP version
Start with the VALIDATOR — the highest-value, lowest-risk piece: ingest a CSV/LOS export, validate every record against the published CFPB 1071 file spec and edit rules, output a line-by-line error/warning report and a clean conformant file. No portal write access needed, no PII stored server-side if run per-session. This is buildable solo in weeks and demos its own value.
30-day build
Read the current §1071 filing instructions/file spec and the 2026 coverage revisions; encode the field dictionary, enumerations and validation edits. Build the validator (CSV in → error report + conformant file out). Stand up a landing page targeting 'small bank / CDFI 1071 filing.' Interview 8-12 compliance officers at community banks/CUs/CDFIs to confirm scope, current tooling and willingness to pay (validate the inferred pain before building more).
60-day build
Add the point-of-application collection form/API and the audit-trail archive. Add a 'am I covered?' scoping wizard reflecting the narrowed coverage rules (a genuine anxiety given the moving thresholds). Onboard 3-5 design-partner lenders at a discounted rate. Publish a plain-English 1071-for-small-lenders guide as inbound content.
90-day revenue plan
Convert design partners to paid annual subscriptions; open self-serve signup. Target first real revenue from per-institution subscriptions plus a per-filing fee at the annual submission window. Partner with 1-2 LOS/core resellers or compliance consultants for referral distribution.
Distribution path
Demonstrated value: free validator that a compliance officer can run on their own export and immediately see errors. Content/SEO on '1071 small-business lending data' and '1071 file spec validation.' Direct outreach to CDFIs (a defined, listed, reachable population), state credit-union leagues, and community-bank associations. Consultant/reseller referral.
Pricing hypothesis
Per-institution subscription roughly $150-$600/mo depending on size, plus a per-annual-filing fee ($500-$2,000) at submission. Free/low-cost validator as the lead magnet. Undercuts both the enterprise suites and a percentage-of-engagement consultant.
Technical difficulty
Moderate. The hard part is not code — it's precisely encoding a moving file spec and edit rules, and handling PII/fair-lending data safely (per-session processing, encryption, minimal retention). No exotic tech; a solo AI-assisted founder can build it. Ongoing maintenance burden as the spec changes is the real cost.
Legal / regulatory risk
Real but manageable. Handling applicant demographic and decision data means data-security and privacy obligations, and getting a validation wrong could contribute to a lender's mis-filing — so ship with clear 'lender remains responsible' terms and strong accuracy testing. NOT founder-licensing risk: the founder does not need a license to build filing software. Do NOT treat this as disqualifying heavy_compliance — compliance is the product.
Platform dependency
Low platform-policy risk: the counterparty is a federal portal/spec, not a platform owner who can deplatform you. The genuine dependency is REGULATORY: the CFPB is actively narrowing 1071 and could further shrink, delay, or (tail risk) gut the collection requirement, which would shrink the addressable filer class.
Founder fit
Very high on shape — this is exactly the proven FMCSA-ELDT pattern: a federal mandate forces a defined class to file structured data to a government system, and a solo operator builds the submission/validation layer and charges per institution/per filing. Matches [[government-portal-mandate-fit]]. The one gap vs. ELDT: 1071 is a crowded, well-funded compliance category, whereas ELDT was greenfield.
Breakout potential
Moderate. If the wedge lands, expand to adjacent lender-reporting obligations (HMDA for the mortgage side, CRA data, FDTA machine-readable standards) — the same buyer, same collect-validate-file muscle. That reporting-compliance suite for small lenders is the breakout, not 1071 alone.
Final recommendation
BUILD-TO-VALIDATE, don't go all-in. The forced-filer shape and founder-fit are excellent, but this is the rare public-money idea with a real competitive_gap problem (entrenched incumbents) and real coverage-uncertainty. De-risk cheaply: ship the standalone validator, run 8-12 buyer interviews, and only build the full collect→file product if small lenders confirm the incumbents don't serve them and the coverage rules stabilize enough to sell against. Pursue, but scope the first 30 days around killing the incumbent-and-uncertainty risk, not around code.
Next action
Pull the current CFPB §1071 filing instructions and file-spec/edit rules and build a standalone validator (CSV export → line-by-line error report + conformant file); in parallel, line up 8-12 interviews with community-bank/CU/CDFI compliance officers to confirm they lack adequate tooling and will pay.