Agency Lead List Onboarding: From Client Discovery to First Delivery

Onboard a lead-list client by agreeing on what will be built, how suitability will be checked and who approves the first delivery. An enthusiastic discovery call is useful, but the operator needs a written, executable brief.

Keep audience approval, delivery acceptance and later campaign results separate. A client can approve a sample without guaranteeing that the full source output will meet every requirement or that outreach will produce meetings.

Ask what the client sells, which workflow it addresses and which customers can use it. Request relevant customer examples and unsuitable examples, with an explanation of why each belongs in that category.

• What will the recipient recognize as relevant about the offer?
• Which company characteristics are essential for the product to work?
• Who operates the affected process, and who else may evaluate a purchase?
• Which countries, business units or customer types can the client serve?
• What will happen after the list is delivered, and who owns that action?
• Which existing customers, opportunities, competitors or suppressed contacts must be handled separately?

Do not treat the client's desired conversion rate as evidence that the list can achieve it. Record it as a planning goal and identify what would be needed to evaluate the result.

For each requirement, record its purpose, whether it is mandatory and how it can be assessed. There are several possible treatments:

Supported search criterion

An available title, industry, company, size, location or other documented field can help form the candidate query.

External research requirement

A current technology installation, service specialty or regulatory context may need a separate appropriate source.

Destination exclusion

A client-supplied customer or suppression list may need to be applied in the agency's own controlled workflow.

Unresolved assumption

A condition with no agreed meaning or evidence remains a question for the client, rather than a silently invented filter.

In Dievio, stored revenue and funding-date filters are supported where covered. They do not directly provide funding stage, available budget or intent. Native technology-stack and hiring-growth filters should not be promised.

The ICP validation workflow is the next step when the client brief still contains ambiguous terms such as “enterprise,” “high growth” or “decision-maker.”

Write whether the agreement concerns contacts, accounts, researched records, qualified leads or meetings. Define the required fields and evidence, how duplicates are counted and what happens when a field is missing or uncertain.

• Contact identity: what evidence connects the person to the intended firm?
• Role fit: which responsibility matters, and how are adjacent titles reviewed?
• Company fit: which conditions are mandatory, optional or externally researched?
• Contact route: what information is required for the intended channel?
• Exclusions: what must be held or removed before delivery?
• Correction terms: which issues qualify for replacement, revision or a separately agreed scope change?

There is no universal ninety-five-percent email completeness or fixed sample size that proves acceptance. Choose a review method suited to the workload and consequence of errors, and describe what it can and cannot establish.

A free Dievio preview counts matching contact records under the chosen criteria. It does not count unique companies, reveal full contact details, establish required-field accuracy or prove total market size.

Save the query and date. Investigate unexpectedly small or large counts with controlled changes. Keep an essential fit condition unless the client approves a different audience; do not widen it silently to make a promised number attainable.

Retrieve a bounded cohort for actual review. If the source cannot supply a required field or relevant role, explain the gap before committing to the full delivery. Separate the scope estimate from a guarantee of accepted output.

Dievio search retrieval uses one credit per returned lead; empty results use none and repeated retrieval can charge again. Saved-list downloads are free and do not refresh records. API credits are separate from workspace search credits.

Do not add an assumed phone-field surcharge, free full-data sample or generic enrichment charge to a Dievio estimate. Use the documented operation and applicable pricing. Budget separate research, review and destination work according to the actual project.

Record a bounded usage plan and who can approve an expansion. Include client feedback, required research and destination readiness in the timeline. A universal twenty-four-to-seventy-two-hour promise or fixed credit buffer is not justified for every engagement.

The credit management guide supports operation-level tracking. The billing guide connects the agreed scope to the eventual reconciliation.

1. Confirm the brief version. Obtain the required approval and identify the change owner.
2. Retain the source result. Record the query, retrieval date and operation reference.
3. Review the records. Separate accepted, held and rejected cases with reasons.
4. Discuss alignment. Share only the approved review material with the intended client reviewer.
5. Apply agreed corrections. Distinguish a mistake from a new requirement.
6. Test the destination. Check field mapping, identity handling, missing values and ownership.
7. Release the exact artifact. Record the recipient, version, counts, limitations and acknowledgement status.

Agree on when feedback will be useful based on actual activation and campaign age. Request specific evidence: wrong-role cases, missing fields, import failures, recipient feedback and outcomes with consistent definitions.

Do not automatically change the audience because one small segment has no early replies. Investigate cohort size, elapsed time, message and sending conditions. Route a data correction to the responsible production stage and a commercial change to the designated approver.

Use the recurring delivery workflow once the operating responsibilities are clear. Your team owns scheduling, CRM delivery and feedback processing; these are not automatic consequences of API access.

The operator should have an approved brief, acceptance method, bounded usage plan, destination map, access rules and named decision owners. The client should know what will arrive, what remains uncertain and how to request a correction or change.

Use lead search to build the audience the client actually commissioned. If their target is SaaS vendors, a SaaS contact segment can help; if they sell software to hospitals, that same vendor segment would be the wrong audience.