Key points
- Agree on target accounts, buying roles and exclusions for each client.
- Keep client criteria and data ownership explicit throughout production.
- Run quality checks and document the delivery handoff.
An agency ABM list starts with the client's account choices and the responsibilities relevant to the purchase. Contact discovery supports that plan; a large export does not create an account strategy on its own.
Keep account fit, stakeholder research and client boundaries distinct. The same public company can legitimately fit two clients, while either client's private notes or campaign plans still require appropriate protection.
Agree on the account definition and campaign task
Document whether an account means a business group, legal entity, operating unit or location. Identify the use case, essential eligibility criteria and client owner responsible for changes.
Retain any client-supplied named accounts and explain why they were selected. Known customers can inform research, but resemblance to a successful customer is not proof of budget or current demand.
- Which account conditions are essential for the offer to work?
- Which business unit or geography matters?
- Which existing relationships or exclusions affect the campaign?
- What research is needed before selecting contact roles?
- Who will coordinate the account once a conversation begins?
The client ICP validation guide resolves the audience assumptions before production.
Research responsibilities within each account
Investigate who operates the problem, evaluates implementation, controls the relevant budget and administers any necessary supplier review. One person may cover several responsibilities; some purchases will not require every type of stakeholder.
Do not use a universal three-to-five-contact rule or infer that a C-level title is always the economic buyer. A person becomes a champion through actual advocacy, not a seniority label or a tracked open.
Keep candidate roles, confirmed responsibilities and unknowns separate. The enterprise contact-routing guide develops coordination around real conversations.
Prioritize accounts from evidence and capacity
| Evidence state | Appropriate investigation | Possible next action |
|---|---|---|
| Required fit established | Confirm relevant responsibilities and operational capacity | Prepare the agreed account approach |
| Fit plausible but incomplete | Resolve the missing condition or identity | Hold or research before activation |
| Relevant client relationship | Check account ownership, context and recipient requests | Coordinate with the existing owner |
| Essential fit fails | Confirm that the exclusion is correctly applied | Remove from this campaign or seek an approved scope change |
If tiers help allocate research effort, define them from the actual service. Do not claim adjacent accounts have faster cycles, require a fixed contact ratio or convert a hand-built fit score into a probability of purchase.
Use supported search criteria for candidate discovery
Dievio supports documented company, title, industry, size, location and other criteria. Stored company revenue and funding dates are available where covered. Native technology-stack, funding-stage, live hiring and intent filters should not be promised.
A free preview measures matching contact records, not unique accounts, a complete buying committee or total addressable market. A small result may reflect source coverage, category matching or the selected criteria; it does not prove an account is unsuitable.
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.
Use external research when the task depends on a fact the source cannot establish. Keep evidence and dates separate from provider retrieval.
Keep client authorization separate from audience segmentation
Use a client identifier, versioned brief, approved destination and access controls in the agency's system. A tag, filename prefix or industry segment is not a security boundary by itself.
Dievio should not be described as providing native API-created agency workspaces, workspace-scoped list generation, automatic client credit pools or destination isolation. Your own application must implement the applicable client controls.
The segmented delivery workflow distinguishes legitimate audience overlap from unauthorized disclosure. Apply actual exclusivity terms where they exist rather than automatically awarding every shared contact to one client.
Review identity, fit and required fields before release
- Resolve the account. Check domains, group relationships and the entity relevant to the brief.
- Confirm contact relevance. Research responsibility and company association.
- Inspect required information. Separate missing, conflicting and unchecked values.
- Apply identity and exclusion rules. Preserve multiple legitimate stakeholders without duplicating the same person.
- Record checking scope. A format check is not evidence of a current mailbox or phone owner.
- Prepare the destination. Test mapping, ownership and missing-value behavior.
- Approve the artifact. Retain a version, reconciliation and open exceptions.
There is no universal ninety-day freshness limit, sampling percentage or acceptable ABM account count. A source update date and a separate validation event can mean different things; record only evidence actually available.
Coordinate recurring work with account history
Specify whether a run seeks new contacts, revisits known roles, researches an event or reformats a retained result. Keep delivery and conversation history so the team does not start conflicting outreach within one account.
Your application owns schedules, pagination handling, CRM writes, release approvals and recovery. API access does not automatically supply those functions or guarantee live fresh data. Retain source results so a destination retry does not needlessly repeat retrieval.
Use the recurring workflow for cycle manifests and the credit guide for approved concurrent work.
Report account progress and unresolved work
Track accounts assessed, role responsibilities confirmed, accepted contacts, held gaps, genuine conversations and agreed next actions. Separate contact-level responses from account-level opportunities.
Later pipeline differences do not prove that more contacts or a tier caused the result. Compare appropriate cohorts and retain the attribution assumptions. Start with a bounded account-focused search and expand coverage only when it serves the researched account plan.



