A targeted B2B contact list starts with a reason each person belongs on it. Define the companies you can help, find the people responsible for the problem you solve, then review the matches before paying to reveal a large batch.
A matching record is a prospect to research, not evidence of buying interest.
Write a brief you can turn into search criteria
Use this sentence:
Find people responsible for [problem] at [company type] in [market you can serve], so we can discuss [relevant outcome].
Separate requirements from preferences. Your delivery territory might be fixed. A funding stage might just help you prioritize. If you cannot explain why a condition matters, leave it out of the first search.
Write down:
- The business type and size your offer suits.
- The territory you can serve.
- The responsibility your buyer needs to have, with possible job titles.
- Who to exclude, such as existing customers, active opportunities and do-not-contact records.
- Any useful context you will check on company websites rather than through a database filter.
If you have no customer evidence yet, treat this brief as a hypothesis to test.
Start with the necessary filters
RadarLeads lets you search by title, seniority, company, location and industry. Its public site also describes company-size, funding and revenue filters. Start with the conditions that determine fit, then inspect the matches before adding preferences. [1]
An industry label will not answer every qualification question. A software category, for example, may include consultancies as well as product businesses. Check company websites for distinctions the filters cannot establish.
The result count describes matches in the database, not your whole market. If the search is empty, change one condition at a time rather than dropping a genuine business requirement. Once you have relevant matches, use the steps below to review and prepare the list.
Example: a list for onboarding software
In this hypothetical example, you sell onboarding software to US B2B software companies. Your initial hypothesis is that businesses with 50 to 200 employees have enough onboarding complexity to need it, and that customer success leaders will evaluate it.
Translate that into a brief:
- Keep the United States as the serviceable market.
- Use the nearest suitable company-size ranges, then review boundary cases.
- Investigate Head of Customer Success, VP of Customer Success and Customer Success Director as possible roles.
- Check that each company sells a software product to businesses and that the person's responsibilities include customer onboarding.
- Remove existing customers, active deals and suppressed contacts from your working list.
Run titles separately unless you have confirmed how the interface combines them. Do not assume it supports Boolean operators or expands titles automatically.
A Customer Success Director may fit. An Engineering Director at the same account needs a different reason to be included. Both the person and the company must pass your review.
Review a small batch before revealing more
RadarLeads describes results showing names, titles and companies, plus email and phone availability before reveal. It shows verification status where available, but availability is not a fresh validation of an exported address. [1]
Choose a manageable review batch, such as ten rows. This is a practical exercise, not an accuracy estimate. For each row, check:
- Does the company sell the kind of product you target?
- Does the person own or evaluate the problem you solve?
- Does a current company page or professional profile support the listed role?
- Does the location field describe the geography you need?
- Can you write a specific reason this contact belongs in the campaign?
Record rejection reasons such as "consultancy, not product company" or "wrong department." If the same reason keeps appearing, revise the search before revealing another batch.
Keep a review sheet alongside the CSV
RadarLeads exports contacts as CSV, with LinkedIn URLs and phone numbers where available. You can import that CSV into your CRM; this does not require a direct RadarLeads CRM integration. [1]
Keep the original export and add your own working columns:
- Segment name and export date.
- Fit decision and the reason for it.
- Role-check date.
- Email validation status and date.
- Suppression decision.
- Person responsible for the next action.
These are suggested spreadsheet columns, not promised export headers. Deduplicate across searches using a consistent identifier, such as an exact email address or LinkedIn URL. Review ambiguous matches rather than merging people just because their names match.
For the hypothetical onboarding campaign, your note for a rejected row might read: "Company sells implementation services only; outside product-company brief." That note tells the next researcher what failed and which search criterion to revisit.
Enrich people you already know
If you already have relevant contacts but lack their business emails, CSV enrichment may save you rebuilding the list. RadarLeads accepts LinkedIn URLs, email addresses, or names with company websites. Its public page describes free matching and charging when a row gains a new email or phone. [2]
Enrichment adds contact details. It does not decide whether someone fits your campaign, so keep the same review process for enriched rows.
Budget for paid email validation before sending
Use a reputable paid email validation service on the intended sending file. This is a separate preparation step and budget, not something to assume a RadarLeads export includes. RadarLeads recommends running exports through a verifier and names Reoon as one option. [1]
Keep the validator's returned statuses. Remove invalid addresses and hold unknown or catch-all results for further review. Reoon recommends separating these categories and explains that verification cannot guarantee zero bounces. [3]
Apply your organization's suppression records, outreach approval process and sending-provider requirements before sending. Validation does not establish permission to contact someone.
Save the brief for the next refresh
Save the search with a segment name and keep the brief beside your review sheet. RadarLeads describes saving and reloading searches. [1] Before reusing an old list, recheck roles, apply current suppression records and validate the intended sending file again.
Track which rows passed fit review, which passed validation and which led to relevant conversations. Those findings can improve the next list; export size alone cannot.
Create a free RadarLeads account to preview your segment before committing to a larger reveal.
Sources
[1] RadarLeads product features and search workflow.