Dievio
Key points
- Separate essential audience criteria from optional research context.
- Use staged filter changes to diagnose the query, not change an identical intersection.
- Inspect account fit, title scope and available fields before expanding retrieval.
Build lead searches in layers so you can see which criteria shape the available audience. A smaller result set is not automatically a better list: the records still need to fit the account definition, relevant buying role and campaign requirements.
The useful question is not “How many filters can we add?” It is “Which rules are necessary, which need evidence, and what did each change exclude?”
Use filter order to diagnose, not to change the mathematics
On a fixed dataset, the same effective set of AND conditions produces the same final matching set regardless of the order in which you select them. Applying company size before job title does not restore records excluded by those same two conditions.
Working in stages is valuable because it makes the effect of each criterion visible. You can identify a mistaken rule, missing title variant or poorly understood field before committing to a larger retrieval.
Separate essential criteria from research context
| Criterion | How to use it | What to verify |
|---|---|---|
| Industry, company size and location | Define the relevant account cohort using supported fields | Field meaning, classification and contact-versus-company location |
| Titles, department and seniority | Identify roles relevant to the buying task | Title variants and actual responsibility at the account |
| Stored revenue and funding dates | Add supported account criteria when they matter to fit | Recency and meaning; a stored date is not a live funding-stage feed |
| Technology, intent and current round context | Use separate research and supporting evidence | Source reliability and observation date; do not assume native filters exist |
| Contact-field availability | Require fields the approved campaign actually needs | Presence is not proof of current deliverability or channel permission |
Start with the non-negotiable account and role requirements. Keep optional signals separate until you can explain why they should exclude an otherwise relevant account. The ICP segmentation framework helps make that distinction explicit.
Account for title variants and query logic
Companies name similar responsibilities differently. A VP Engineering, Head of Engineering and technical founder may each be relevant in a different account context. Broader matching still needs a review of the full title and current company.
For an existing executive cohort with missing fields, use the executive-list enrichment workflow to review supported identities and available output. That is a different input from discovering a new role-based audience.
- List relevant variants. Include the variants that fit the buying task, rather than every executive title.
- Check field semantics. A department label and a title match do not necessarily select the same records.
- Use documented logic. Confirm how the tool combines fields and multiple values. Do not assume a pasted Boolean string is supported by every input.
- Apply exclusions deliberately. Check that a broad exclusion does not remove accounts you still intend to serve.
Keep separate segments when the roles require different messages or qualification rules. A wider title set does not mean everyone should receive one sequence.
A Practical Workflow for Balancing Fit and Coverage
- Define the baseline. Write down the account cohort, buying task and mandatory exclusions.
- Preview the matching count. Check the available contact records before retrieving them.
- Change one criterion. Compare the result with the same baseline and record what changed.
- Keep useful variants. Save the definitions and observations in your review process so later comparisons remain interpretable.
- Review a bounded retrieval. Check fit and required fields, then proceed, investigate or revise the segment.
If an optional filter removes too much relevant coverage, review or relax that criterion. Keep genuine constraints in place: a market the team cannot serve does not become appropriate because relaxing geography increases the count.
Use the count preview at each diagnostic stage. Counts refer to matching contact records; they do not measure unique companies or the whole market.
DievioYour next customer starts here.
Find decision-makers by role, company and location. Build your next prospect list in Dievio.
Find my leadsFree audience preview · No credit card
Choose a response to the result
| Observation | Possible explanation | Useful next check |
|---|---|---|
| Few or no matches | Restrictive criteria, missing values, title variation or limited database coverage | Check field definitions and title variants; relax only justified optional rules |
| Many matches but weak account fit | Broad industry or keyword selection does not match the intended business | Inspect companies and refine the account criteria |
| Many contacts at the same company | Several people match the chosen roles | Review the buying committee and account grouping; this is not automatically a filtering error |
| A plausible count but poor contact quality | Availability or source quality does not meet the campaign's needs | Review returned fields and validation outcomes separately from audience size |
No universal percentage drop marks a filter as excessive. The decision depends on the business requirement, the records excluded and the evidence available.
Use the initial records to test your assumptions
A count preview cannot show whether a company keyword describes a genuine fit, or whether a matching person owns the relevant responsibility. Retrieve a bounded set and review it against the written definition.
- Check company identity, business model and relevant location.
- Read the full title and review current responsibility.
- Confirm which contact fields are available.
- Keep unknown values, validation limits and exceptions explicit.
- Review suppression and applicable outreach requirements before activation.
LinkedIn lookup can match known profile URLs to available contact records. It does not provide a guarantee of fresh mailbox verification or current employment. Use the data quality guide for the separate validation task.
Prioritize research after the search when appropriate
Some useful account context is difficult to express as a reliable initial filter. Keep a broader but relevant cohort, then research the specific signals needed to prioritize it. This is different from sending to every returned contact.
For example, first identify the companies and technical roles the offer serves. Then review externally sourced technology context or a current company announcement before deciding which accounts deserve further work.
Make the retrieval and handoff explicit
Record the final filter definition, count observation date, accepted records and unresolved cases. Dashboard searches consume search credits for returned leads; repeating a search can spend credits again. Downloading an already saved list uses no additional search credits.
Check current credit and pricing rules before scaling, and use the pre-export hygiene checklist before campaign delivery.
Build the filtered list when the audience definition and initial record review support the next step.
