What changed
FACT (Federal Register, 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. FACT (provided signals): schema-defined structured extraction from arbitrary sources is now a single API call (Context.dev), and one third-party benchmark claims LLM categorization near human-bookkeeper accuracy (GLM 5.2 VAT test — single unreplicated benchmark, treat as HYPOTHESIS). Together these plausibly make a 'loan file in → validated 1071 dataset out' tool solo-buildable.
Why now
Every covered lender must rework its 1071 data collection to the revised fields and coverage before the new compliance date (FACT that rework is required; the exact new compliance dates are in the rule text and were not provided — timing urgency is therefore UNVERIFIED). Incumbent compliance vendors will re-tool too, so any window is now, before their updates ship. HYPOTHESIS: the revision creates a confusion spike ('does the new rule cover us? what changed?') that is monetizable faster than the filing tool itself.
Converging signals
(1) Finalized CFPB 1071 revision forcing data-collection rework (federalregister.gov, FACT). (2) Structured-extraction-as-API collapsing the parsing build cost (context.dev, FACT that the product exists; reliability on loan documents is HYPOTHESIS). (3) LLM categorization accuracy benchmark suggesting classification of loan-file fields is automatable (toot-books.pages.dev, HYPOTHESIS — single benchmark, different domain).
Customer pain
HYPOTHESIS ONLY. No demand_evidence array was provided — zero PAIN complaints, zero HIRING/SPEND postings. The mandate itself (a FORCED BUYER signal via the Federal Register citation) proves obligation, not that covered lenders are searching for or buying point tools rather than leaning on their LOS vendor, core provider, or existing compliance suite. Pain must be assumed, and I decline to assume it at a high score.
Who pays
Covered small-business lenders: community banks, credit unions, and — the more reachable tail — non-depository commercial lenders (equipment finance, merchant cash advance, fintech and online SMB lenders) that lack compliance departments. Inside a bank the buyer is the compliance officer, which means vendor due-diligence, InfoSec review, and committee sign-off — functionally enterprise sales even at a 10-person bank (INFERENCE from standard bank vendor-management practice, not from provided sources).
Solved today
INFERENCE (not from provided sources): incumbent compliance vendors (Wolters Kluwer, Ncontracts, Asurity/RiskExec), LOS/core platforms adding 1071 modules, consultants, and manual spreadsheet collection at small shops. The CFPB also provides its own submission platform and filing instructions, so the pure 'upload to the portal' layer is thinner than it was for FMCSA ELDT.
Why current solutions are bad
HYPOTHESIS: incumbent tools assume data is already structured in an LOS; the painful part is extracting/normalizing 1071 data points from messy loan files and legacy systems, and small non-bank lenders are priced out of enterprise suites. Plausible, but unsupported by any provided complaint or job-posting evidence.
Proposed product
A narrow '1071 scrubber': lender exports loan-application data (CSV/PDFs) → LLM extraction maps to the revised rule's required data points → deterministic validation engine flags missing/invalid/inconsistent fields against the new schema → outputs a submission-ready file plus an exception report. Sell the validation/exception report per filing period, not a platform. Deliberately avoid storing NPI long-term to shrink the security surface.
MVP version
2-3 weeks: hand-code the revised rule's data-point schema and edit checks from the Federal Register text; build file-drop → extraction (Context.dev or direct LLM) → validation → exception report on synthetic loan files. Demo asset: a free '1071 readiness checker' that scores a sample file. No integrations, no portal automation in v1.
30-day build
Do NOT build first. Spend week 1 on demand validation: search Indeed/LinkedIn for '1071 compliance' hires, mine lender/compliance forums (Bankers Online, r/CreditUnions, ABA/ICBA threads) for revision-specific confusion, and email 20 non-bank SMB lenders. Only if concrete pain/spend surfaces, build the MVP validator in weeks 2-4 and publish a plain-English 'what changed in the 2026 1071 revision' guide as the lead magnet.
60-day build
Run 3-5 free pilot scrubs for non-bank lenders sourced via the guide; convert exception reports into paid engagements ($500-1,500 per portfolio scrub). Harden extraction on real (redacted) files. Decide bank-market entry only if pilots demand it — otherwise stay non-depository.
90-day revenue plan
Realistic: $1-5k from pilot scrubs and readiness assessments IF demand validates — consulting-shaped revenue, not SaaS. Recurring per-filing SaaS revenue almost certainly lands beyond 90 days because lender procurement and the (unverified) compliance-date runway both slow the clock. This misses the 30-90-day cash bar; say so plainly.
Distribution path
Weakest link. No app store, no self-serve channel to compliance officers. Content/SEO on the rule revision + direct outreach to non-bank lender associations (SFNet, ELFA, ILPA) + LinkedIn. Every serious deal still passes through vendor review. INFERENCE: no provided evidence of any reachable self-serve channel.
Pricing hypothesis
Free readiness check → $500-1,500 one-time portfolio scrub → $200-500/mo per lender for continuous validation, or per-record fee mirroring the ELDT per-upload model. Unvalidated hypothesis.
Technical difficulty
Moderate. Schema + validation engine is deterministic and solo-easy. Hard parts: extraction accuracy on heterogeneous loan documents (the GLM benchmark is from VAT bookkeeping, not lending — accuracy transfer is a HYPOTHESIS), and demonstrating security adequate for NPI/PII loan data. CFPB submission-format details are public, which helps.
Legal / regulatory risk
Material. Loan files contain ECOA/Reg B-sensitive demographic data and NPI; mishandling has fair-lending and GLBA implications. Errors in a compliance tool that cause a bad federal submission create liability a solo founder cannot absorb without contracts, insurance, and a security posture (SOC 2 expectations from any bank buyer). This is the 'heavily regulated' zone the founder profile says to avoid — adjacent to it, at minimum.
Platform dependency
Low-moderate: CFPB submission platform format changes are manageable (public specs); dependency on Context.dev or a given LLM is swappable. Regulatory-whiplash risk is real — 1071 has a history of litigation and date changes (INFERENCE from general knowledge, not provided sources), and a further delay would freeze buyer urgency.
Founder fit
Superficially strong, structurally weak. The shape matches the proven ELDT edge: federal mandate → forced filers → build the filing layer → charge per transaction. But the ELDT buyers were small training providers with no procurement process; 1071 buyers are regulated financial institutions with vendor-management obligations. 'Sells through demonstrated value, no enterprise sales, no long trust-building' is exactly what bank compliance purchasing is not. Fit only survives if he stays strictly in the non-bank lender tail — and there is no provided evidence that tail is searching for help.
Breakout potential
If it worked: expansion into HMDA validation, CRA data, and general 'regulator-ready data pipeline' for lenders — a real multi-product wedge. But that whole space is where funded compliance vendors already live.
Final recommendation
KILL for the 30-90-day cash objective — the forced buyer is real but is the wrong kind of buyer for this founder's no-enterprise-sales, fast-close model, and no pain/spend evidence was provided to offset that. REVISIT LATER only as a narrow non-bank-lender '1071 exception report' service, and only after a cheap demand test produces concrete evidence (job postings, forum pain, or reply-rate from lender outreach). Do not write product code before that evidence exists.
Next action
2-hour timeboxed demand test, zero code: search Indeed/LinkedIn for '1071 compliance' job postings, scan Bankers Online and credit-union forums for revision-specific complaints, and send 15 cold emails to non-depository SMB lenders offering a free 1071 readiness check. If <2 concrete pain signals or replies, archive the idea.