Business loan leads built from public filings, not rented lists
Business loan leads are only as good as the event behind them. A rented list is a name that was true when someone else compiled it. A public filing is a business doing something right now — taking a UCC position, registering a new entity, pulling a permit, renewing a license. Recordpipe builds business loan lead feeds from those events, collected on cadence from public sources and delivered as a structured file, API, or webhook stream.
Funders, brokers, and ISOs use the same underlying signals. What differs is the filter. An MCA floor wants merchants with existing positions. An equipment lender wants contractors with new permits and fresh licenses. An SBA-focused shop wants new registrations in target industries. Each feed is scoped to your box: geography, industry, entity age, filing type, and the exclusions you already know you don't fund.
The feed is yours, exclusively. It is built to your spec and never resold. That is the difference between a business loan leads provider and a list vendor whose file every competitor also bought.
MCA leads and merchant cash advance leads: UCC filings are the signal
Merchant cash advance leads start with UCC data. When a funder takes a position, the filing names the debtor, the secured party, the filing date, and the collateral language — usually a blanket lien. For an MCA sales floor, that single record answers the questions that matter: does this merchant borrow, who funds them, and how recently.
Recordpipe delivers UCC filing leads as a standing feed. New filings are collected on cadence, matched to the debtor's registry record for legal name, entity type, and status, and joined with the debtor's mailing address and owner or officer names as published in public filings. Secured-party normalization is part of the build, so filings by the same funder under variant names roll up to one label your reps recognize.
Position age is the filter that turns a file into a call list. Fresh filings are proven borrowers. Filings past a seasoning window you choose are renewal and consolidation conversations. Terminations are merchants who just paid off. Your team sets the windows; the pipeline delivers the rows. The UCC filing leads page covers the underlying feed in depth.
Equipment financing leads from license, permit, and registration activity
Equipment financing leads come from a different set of public events. A contractor who just pulled a large permit needs machinery on site. A newly licensed trucking authority needs a truck. A restaurant with a fresh health or liquor license is fitting out a kitchen. A new business registration in construction, logistics, or manufacturing is a company that has not yet chosen an equipment lender.
Each of those is a public record, and each can be collected as a feed. We scope the signal set to your product: permits above a value threshold you choose, license issuances in the trades you finance, new registrations by industry code where states publish it. Records are matched across sources where the same business appears in several, so a permit and a registration for the same contractor arrive as one row.
What you receive is the business, its owner names and mailing address as published, and the event that triggered it. Contact points are delivered only as they appear in public filings — no scraped private contact data. Enrichment is your call. Related feed: New business registration leads.
How to get MCA leads that stay fresh: the delivery model
How to get MCA leads that stay fresh is an operations question, not a sourcing one. Anyone can pull one file. Keeping a nightly feed running as sources restructure is where internal projects and most lead vendors quietly fail. Recordpipe runs the pipelines on its own infrastructure — the same automation that keeps over one million public records processing nightly — and delivers the output where your floor works.
Delivery options: a daily or weekly file to your bucket or SFTP, a direct load to your warehouse, a webhook push into your CRM the moment a qualifying filing appears, or a hosted API your dialer queries. Every delivery ships with a run manifest and a delta — what is new, what changed, what terminated — so reps never re-call yesterday's rows.
Lending data delivered this way is raw public data, not a consumer report. We are not a CRA. Feeds are for prospecting; if a use case touches credit eligibility decisions, it gets compliance review at intake. Engagements start with a $500 scoping — feasibility, a sample of real rows, and a fixed quote within 5 business days — with contracts from $5,000 to $3 million.
What an engagement delivers
| Deliverable | Description |
|---|---|
| lead_record | Business legal name, DBA where filed, entity type, and registry status, normalized to your schema. |
| trigger_event | The public filing that produced the row — UCC-1, new registration, permit, license — with its filing date and source category. |
| secured_party | Normalized funder name on UCC filings, with variant names and affiliates rolled up to one label. |
| position_age | Time since filing, bucketed into the windows your sales process uses: fresh, seasoned, renewal, terminated. |
| owner_principals | Owner, officer, or member names as published in public filings. |
| mailing_address | Business and registered mailing addresses as filed; contact points only as published in public filings. |
| industry_and_geo | Industry classification where the registry publishes it, plus state, county, and city for territory routing. |
| suppression_flags | Rows matched against your do-not-call, existing-customer, and declined lists before delivery. |
| delta_and_manifest | Per-run summary of new, changed, and terminated rows with run window and checksum. |
| delivery_channel | File drop, warehouse load, webhook push, or hosted API — whichever your CRM and dialer consume. |