Verifying a competitor-customer prospect list
Lists built around who uses a competitor are high-intent but sensitive. Keep what you collect to business contacts from public sources, verify it, and segment by result.
A sample file (fictional data)
| company | signal | source | |
|---|---|---|---|
| Harbor Outfitters | public case study | ops@harbor.example.test | case study page |
| Lumen Goods | job post mentions tool | hiring@lumen.example.test | job board |
| Metric Nest | integration listing | partners@metricnest.example.test | marketplace |
The signal column records why the company is a prospect; keep it factual and public.
Keep it to public business signals
Case studies, integration listings and job posts are public. Do not scrape private data or imply that a competitor shared its customer list.
Segment by result
Valid addresses get your first message. Role addresses such as partners@ fit partnership pitches. Catchall gets a small test batch, and unknown is retried before you decide.
Before you collect
Check the source site’s terms for what you may collect and how you may use it, and follow the privacy and anti-spam rules that apply to your sending. ValidReach verifies addresses you already have; it does not supply contacts from any source.