A business owner contact list built from filings, not guesses
Most B2B contact databases are probability engines: pattern-guessed emails, scraped titles, stale org charts. A business owner contact list from filings works from the other direction — start with documents a real person actually signed, and build outward. Formation documents name officers. Annual reports name principals. License applications name the individual professionally responsible. Every one of those is a public record with a name on it.
Recordpipe assembles decision-maker lists from those filings across the states and verticals you target, on the same infrastructure that processes over one million public records nightly. Each delivered row cites its source filing, so when a rep asks whether a contact is real, the answer is a document, not a confidence score.
The trade is honest and it favors you: fewer rows than the mega-databases, and each one verifiable. For teams measuring connect rates and bounce rates rather than raw list size, verifiable wins.
License and permit holders: the owner-operator layer
For a whole class of businesses — contractors, medical and dental practices, salons, restaurants, trades of every kind — the person on the license is the person who owns the P&L. Licensing and permit records are therefore the cleanest owner-operator list that exists: the state itself maintains it, and the named individual staked a credential on it.
Recordpipe structures license holder data by profession, jurisdiction, and status where published: the holder's name, license type and number, issue and status information, and the business address as filed. New issuances are a timing signal on top of an identity signal — a fresh license is often a practice or shop about to open, which makes it a first-call opportunity for anyone selling equipment, insurance, payments, or services.
Filters are set in scoping: which license categories, which states, new issuances versus the full active roll, and how the license layer joins to entity records for a fuller account view.
Cross-filing joins: one owner, the whole account
The owner you're selling to rarely appears in just one record. She's an officer on an entity filing, the holder of a professional license, the applicant on a permit, maybe the principal behind a second company. Seen separately, those are four thin rows in four datasets. Joined, they're an account: what she operates, where, under what names, and what she just filed that suggests what she needs next.
Recordpipe builds those joins as part of the list: person-level resolution across entities, licenses, and permits within your target set, with the evidence for each linkage carried in the data. Your reps open one record and see the operating footprint, not a name floating free of context.
This also pairs naturally with our other feeds — a landlord list joined to business filings, new registrations joined to license data — because it's all one records infrastructure underneath. Scoping defines which joins your motion actually needs.
Contact points as published in public filings
Here is exactly what the contact data is, because vendors are usually vague on purpose. Names of officers, principals, agents, and license holders: public record, delivered as filed. Business mailing addresses: public record, delivered as filed. Phone numbers and email addresses: included only where the public filing itself publishes one — some corporate and licensing filings do — exactly as filed, with the source cited.
What we don't do: scrape private contact data, guess email patterns, buy shadow databases, or skip-trace individuals. If you want enrichment beyond what the filings publish, that's your call, made on your side, under your policies. We'd rather tell you that plainly than sell you a promise the public record can't keep.
Commercially it's simple: a $500 scoping maps signal density for your verticals and states and delivers a sample within 5 business days, with a fixed-price quote. Contracts start at $5,000 and run to $3 million at enterprise scale. We reply within 2 business days.
What a delivery looks like
| Field | Description |
|---|---|
| business_name | Legal entity name as registered, with DBA names where filed. |
| principal_name | Officer, member, or principal name exactly as it appears on the filing. |
| principal_role | Title or role as filed — officer, managing member, registered agent, license holder. |
| business_address | Business or mailing address as published in the filing. |
| license_type_no | Professional license or permit type and number, where the record is license-sourced. |
| license_status | Status as published by the licensing authority. |
| registration_date | Formation, registration, or issuance date from the source record. |
| contact_as_filed | Phone or email only where the public filing publishes one, exactly as filed. |
| source_filing | The specific filing type and jurisdiction each row traces to. |
| linked_records | Other entities, licenses, or permits resolved to the same person, with linkage evidence. |