Request type
Lead lists and contact data
Companies or people matching your profile, with public contact details.
Planned
Planned. Publicly listed data only.
Who asks for this
Outbound and sales teams building lists per campaign.
Say it like this
“Find independent coffee roasters in Oregon and Washington with a website. Include the publicly listed contact email and the page where you found it.”
What you supply
- Industry, location, size, or a directory URL
- Fields per lead
- A list cap
What you get back
Your table · 4 rows shownIllustrative
| companytext · collected | websiteurl · collected | statetext · collected | public_emailtext · extra work | email_sourceurl · extra work | last_checkeddate · derived |
|---|---|---|---|---|---|
| Cascade Roastworks | cascaderoast.example | OR | hello@cascaderoast.example | cascaderoast.example/contact | 2026-09-14 |
| Puget Small Batch | pugetsmallbatch.example | WA | — | — | 2026-09-14 |
| Timber Line Coffee | timberline.example | OR | orders@timberline.example | timberline.example/wholesale | 2026-09-14 |
| Salish Roasters | salishroast.example | WA | info@salishroast.example | salishroast.example | 2026-09-14 |
collected from the page · derived at no cost · extra work raises the estimate
Workflow
How the agent handles it.
- 1
You describe the profile and a cap.
- 2
We show which fields need a visit per lead.
- 3
You approve the estimate.
- 4
We collect, deduplicate, and record the source per contact.
- 5
Export to CSV.
Cost and limits
What moves the price, and where the answer can be no.
Cost drivers
- List size
- Contact fields need one visit per lead
- Verification steps
Where we say no first
- Publicly listed contacts only. No guessing.
- Lawful outreach is your responsibility.
Early access
Want lead lists and contact data?
Describe the sources, the columns, and roughly how many rows.