Agency Lead List Segmentation: Keep Client ICPs Separate

Keep each client's audience definition versioned and reproducible. The operator should be able to identify the intended client, approved criteria, external research requirements and destination before a query is run.

Criteria separation and data authorization solve different problems. Two clients may target overlapping public audiences; neither should receive the other's private notes, exclusions or commercial information without appropriate authorization.

Use a shared template for the structure, with explicit client values. A reusable template is useful when its inherited fields are inspected rather than assumed correct.

The ICP validation workflow establishes the audience decisions. This specification records how the operator implements them.

Map supported title, seniority, industry, company size, person or company location and other documented fields to the task. In Dievio, stored company revenue and funding dates are supported where covered.

Native technology-stack, funding-stage, hiring-growth and intent filters should not be promised. If a criterion needs separate research, retain the source, date and affected entity rather than omitting it silently or pretending the search proves it.

A title variant is a candidate role, not proof of budget authority. A revenue band can help organize research without establishing available budget. Keep these interpretation limits with the specification.

1. Select the intended client. Confirm the identifier and approval version.
2. Inspect every inherited value. Look for a previous client's geography, titles, company restrictions or destination.
3. Compare with the current brief. Resolve differences before retrieval.
4. Save the effective query. Retain the actual supported criteria rather than just a display name.
5. Bind the job. Connect source result, review and output to the client and version.

There is no need to rebuild every configuration from scratch if a reviewed template can reproduce the intended result. Conversely, renaming a preset does not establish that its values were updated.

A useful artifact reference combines client, audience version, batch and delivery version. For example, client-a_icp-v2_batch-018_delivery-v1.csv identifies the context without relying on a vague “final” filename.

Your application or preparation step can attach the necessary client metadata to the output. Do not claim Dievio supplies a native arbitrary custom-column exporter or multi-client workspace API unless the product documents that feature.

Separate folders, projects or accounts may help implement access requirements. Their effectiveness depends on actual permissions, sharing, copying and release controls. Different tools do not guarantee complete isolation, and tags alone are not access controls.

Choose the design from client requirements and risk, not an invented threshold of five, fifteen or twenty clients.

A free Dievio preview measures matching contact records under the selected criteria. It does not show full free sample records, unique-account coverage, private exclusions or independent field accuracy.

Record controlled query comparisons when a criterion seems too restrictive or broad. A surprising count is a reason to investigate; it is not conclusive proof that a filter is wrong or the market is too small.

Retrieve a bounded cohort for actual review. 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.

• Confirm the company and relevant person identity.
• Inspect role responsibility and essential account criteria.
• Distinguish multiple relevant stakeholders from duplicate people.
• Apply the client's actual exclusions and approved exception rules.
• Separate missing, incorrect and unreviewed contact fields.
• Check that private notes and unauthorized fields are excluded.
• Verify the intended destination and artifact version.

Company-name deduplication can wrongly remove legitimate stakeholders or merge different entities. Choose identity rules appropriate to the task and investigate uncertain matches.

A mailbox or format check cannot guarantee inbox placement. An arbitrary ten-row review or a checklist does not support a claim that ninety percent of all segmentation issues will be caught.

State whether the next delivery contains new contacts, corrections, reviewed existing records or a full agreed replacement. Preserve the earlier artifact and change log as needed under the applicable access and retention arrangements.

Do not automatically delete the client's master list before a replacement or assume append-only delivery prevents every error. Test the destination's actual duplicate and update behavior and agree on recovery.

The recurring workflow supplies a cycle manifest. The segmented handoff guide focuses on final packaging and release boundaries.

Report accepted counts, role or account distributions, exceptions and the specification version. Keep checking evidence distinct from availability and retrieval dates.

Comparing one client's campaign with another client's different offer, audience and execution does not isolate the effect of a title or ICP rule. Use appropriate cohort comparisons and the necessary authorization before combining client evidence.

The billing guide connects the versioned specification to delivered work. Start the next client search from that explicit record, then change only the decisions that have been approved.