Specialist sales development role

List building and enrichment

Build reviewable prospect lists with explicit sources, exclusions, and acceptance rules.

Audience and problem

Where this role creates useful capacity.

Built for: Revenue teams that need consistent prospect records without giving up source provenance or suppression controls.

A list is not useful when fields are inconsistent, provenance is missing, duplicate accounts remain, or exclusions are applied only after outreach starts.

Inputs required

Ideal-customer and role criteria
Approved enrichment sources
Required field dictionary
Suppression and duplicate rules

Scope of work

Prepare account and contact records
Normalize authorized fields
Check duplicates and approved exclusions
Route ambiguous records for review

Working sequence

A workflow the owner can inspect.

Translate criteria into a written acceptance checklist.
Prepare a bounded list from approved sources.
Run duplicate, exclusion, and required-field checks.
Deliver accepted records and a separate exception queue.

Deliverables

Review-ready prospect list
Source and freshness fields
Duplicate-resolution queue
Exclusion and exception log

Owner decision boundaries

No purchase or use of unapproved data.
No bypass of opt-out, suppression, or territory rules.
Final market and account approval stays with the revenue owner.

Quality controls

Sample source verification
Duplicate and domain normalization checks
Suppression reconciliation
Acceptance and rejection reason review

Operating examples

How the boundary works in practice.

Campaign list preparation

The team provides a target definition and suppression file. The assistant returns a review batch before any sequence enrollment.

Legacy-list repair

Existing records are normalized, deduplicated, and separated into accepted, rejected, and needs-review lanes.

Role questions

Frequently asked questions

Can the role source any available contact data?

No. Sources and permitted fields must be approved by the organization before work begins.

How should uncertain records be handled?

Keep them out of the accepted list and route them with the missing evidence or conflict clearly identified.

Related services

Connect the adjacent handoffs.

Create a controlled first workflow

Turn this scope into a role brief.

Bring the queue, systems, current owner, and known exceptions.

Plan a consultation