Request a custom B2B list built from defined company, role, geography and field criteria with scope review before delivery.
CUSTOM B2B LISTS
A custom B2B contact list is prepared from an agreed targeting brief when a standard self-service search does not fully cover the required audience, fields or review process. Define the markets, company criteria, roles, exclusions and delivery format first, then confirm feasibility, scope, pricing and responsible-use requirements before production.
Request a custom list → Review methodology Audience: teams with precise briefsUse case: managed list buildingFields: agreed before productionPricing: scoped per requestLimitation: feasibility variesOn this page
01 / Overview
Use custom delivery when a standard self-service search does not fully capture the target brief, field mix or review requirement.
Document the target market, audience, required fields, exclusions and intended business purpose.
Review expected availability, limitations, volume and commercial terms before production begins.
02 / Project fit
A custom engagement is most useful when the audience has precise criteria or requires additional review.
Target a specific combination of geography, industry, size, role and seniority.
Request an agreed mix of contact and company fields where supported.
Create separate list scopes for different clients, offers or territories.
Add documented exclusions, prioritization rules or manual review steps.
03 / Targeting brief
A complete brief reduces ambiguity, rework and irrelevant records.
| Brief element | Examples | Why it matters |
|---|---|---|
| Geography | Country, region, state, city or market | Defines the operating market and applicable obligations. |
| Company profile | Industry, employee range, revenue range or type | Narrows the account universe. |
| People profile | Department, title, function and seniority | Identifies the relevant professional audience. |
| Required fields | Business email, phone field, company details or profile context | Sets realistic availability expectations. |
| Exclusions | Existing customers, domains, industries or role types | Reduces duplication and conflict. |
| Delivery rules | Volume, format, columns and segmentation | Creates a clear acceptance standard. |
04 / Process
The exact process should match the commercial scope and the complexity of the request.
Submit the targeting criteria, exclusions and intended use.
Review data availability, expected volume and limitations.
Provide a sample or field layout when the scope requires validation.
Build and review the agreed list.
Deliver the approved fields and segments in the agreed format.
Handle documented scope issues under the agreed terms.
05 / Deliverables
The delivery file should contain only the fields, segments and notes agreed in the scope.
Use consistent columns, encoding and field labels for import or review.
Separate markets, roles or campaign groups when requested.
Include supported availability or status fields where relevant.
Document exclusions, limitations and any unresolved criteria.
06 / Quality controls
A custom list can be reviewed for relevance and field presence, but it cannot guarantee campaign results or permanent accuracy.
Check records against the agreed criteria and remove clear mismatches.
Flag missing or unsupported fields rather than presenting them as guaranteed.
List quality does not guarantee delivery, replies, meetings, placements or revenue.
07 / Responsible use
The requester should document the business purpose, access controls, retention period and applicable outreach obligations.
Use the list only for the approved, relevant business purpose.
Limit access and avoid uncontrolled sharing or resale.
Honor applicable opt-out, correction and removal requests.
Data MethodologyData CoverageResponsible UseData Removal08 / Questions
It is a list built from an agreed targeting brief rather than a self-service search completed entirely by the customer.
Typical criteria include geography, industry, company size, job function, seniority and other fields supported by the current data and research process.
No. Feasibility and field availability vary by segment. The scope should be confirmed before production begins.
Pricing should reflect the target complexity, required fields, volume, review work and delivery format. Confirm the commercial terms in a written scope.
No. The requester remains responsible for lawful, relevant and policy-compliant use.
Share the audience, fields, exclusions and delivery format so feasibility and scope can be reviewed before production.
Advance Data Search → Ask a question