Key points
- Separate matching contact records, unique accounts and reviewed usable output.
- Investigate unexpected coverage without weakening essential audience requirements.
- Plan the next retrieval and handoff from observed effort and review capacity.
Use a coverage count to plan the next investigation, not to declare the number of reachable customers. In Dievio, a free preview counts contact records matching supported criteria; it does not count unique companies or evaluate the contact fields.
Connect that observation to a defined audience and a manageable review process. The useful question is which records to inspect next, not whether the total matches an arbitrary quota.
Define the planning unit
| Unit | Meaning | Additional work required |
|---|---|---|
| Matching contact records | Source records satisfying the effective query | Inspect identity, role meaning and field availability |
| Unique accounts | Companies under a declared parent/subsidiary or site rule | Deduplicate and review account identity separately |
| Reviewed usable contacts | Records meeting the task's evidence and eligibility requirements | Complete the relevant record and campaign review |
| Total market opportunity | A documented market estimate with stated units and assumptions | Use suitable market and financial evidence beyond database coverage |
Several people can work at one company, and some eligible companies can be missing from a source. A large difference between a contact count and an account estimate is not automatically a query error.
The market-planning guide develops that distinction. Keep the preview definition with the number so the next operator can interpret it.
Write the audience before comparing counts
Record account activity, relevant location, scale context, buyer responsibility and exclusions. Separate essential eligibility from optional research context.
- Does location mean the company, the person or a target operating market?
- Which title variants plausibly describe the responsibility?
- Are several contacts per account useful for this campaign?
- Which required facts are supported filters and which need external research?
- What would make a returned record ineligible?
Use the ICP framework to make those choices reproducible.
Investigate unexpected coverage
- Preview a baseline. Use the essential supported criteria and record the effective definition.
- Test an uncertain condition. Compare its effect without changing several assumptions at once.
- Check interpretation. Review title variants, company versus person location and category meaning.
- Check the source limits. Consider missing coverage or unavailable specialist evidence rather than assuming the market is absent.
- Choose a bounded retrieval. Use actual records to assess the account and contact questions the count cannot answer.
Dievio supports stored revenue and funding dates. Installed technology, funding stage and intent need separate evidence where essential; they are not native filters.
On a fixed dataset, the same effective AND conditions produce the same intersection regardless of their order. Staged review helps diagnose a condition rather than guaranteeing a stable drop or extra coverage.
The filter diagnostic workflow covers that investigation in more detail.
Plan work from reviewed records
Separate the work of account research, contact review, personalisation, follow-up and exception handling. Use the team's observed effort rather than a universal leads-per-representative figure.
Begin with a cohort the team can inspect and work. Record where effort goes and which records fail the acceptance criteria. Expand the next batch from those observations and the remaining capacity.
- Keep unavailable records separate from unreviewed records.
- Deduplicate accounts before using account-level planning numbers.
- Keep several stakeholder roles distinct when the account plan needs them.
- Assign an owner and a next action rather than importing a whole result set into an active sequence.
- Retain held cases so the next batch does not recreate the same research problem.
A downloaded record is not necessarily ready for outreach. Review identity, required fields, validation evidence, preferences and the intended channel before activation.
Budget the operation that returns data
Free count preview can support coverage investigation. Search retrieval charges for returned leads; empty searches cost zero and repeating retrieval can charge again.
Downloading an existing saved list adds no search-credit charge. It does not refresh the records or guarantee new validation. API and workspace balances are separate, so record the relevant operation when planning repeated work.
The preview workflow covers the count check. The segment validation guide develops the broader audience decision.
Reconcile the plan with the actual handoff
Compare matching records, unique accounts, reviewed usable contacts and the cohort actually worked. Explain the difference through identity rules, exclusions, field gaps and review capacity rather than treating every lost row as a source error.
Keep the audience version, source date and review findings with the campaign. The lean-team workflow helps connect the planning numbers to ownership and follow-up outcomes.



